Hi Ray, and everyone else.
We've got a couple of Afterburner units, and generic Chinese heaters. We're using them for keeping our polytunnels full of plants frost free. After a long summer sleep, they've been revived as it's getting cold in the UK now. I updated the firmware on one unit and have had some issues since. (Of course because everything was off for quite a while, it may not have been the update.)
Afterburner: V3.5.2
Date: 2 Jul 2024
MQTT Webburner: 3.5.1.18
Date: 07 Jul 2024
I've twice had e-07 showing up, which as I understand it suggests a fault on the blue wire. I'll check in a bit more depth when I can see it and maybe give the connectors a little clean. I could potentially swap the units over too if that is worth a try.
At the same time as this E-07 was showing, the web UI was behaving a bit weirdly, the web page loaded, but was not connecting to the websocket. On both occasions I resorted to removing the power and afterwards it was back to working fine again. During this, the Virtual Console (nice feature BTW) was still responsive, but I don't believe that the MQTT broker got any messages at all, the last thing showing in HomeAssistant was E-00 OK.
It ran for a couple of days between E-07 / unresponsive web front end.
As an aside, the logging feature seems like it could be useful, but is there any way the logs could be sent to a syslog server? I believe the protocol is really simple so it might be a handy to monitor how it's all going.
Thanks,
Ed.
We've got a couple of Afterburner units, and generic Chinese heaters. We're using them for keeping our polytunnels full of plants frost free. After a long summer sleep, they've been revived as it's getting cold in the UK now. I updated the firmware on one unit and have had some issues since. (Of course because everything was off for quite a while, it may not have been the update.)
Afterburner: V3.5.2
Date: 2 Jul 2024
MQTT Webburner: 3.5.1.18
Date: 07 Jul 2024
I've twice had e-07 showing up, which as I understand it suggests a fault on the blue wire. I'll check in a bit more depth when I can see it and maybe give the connectors a little clean. I could potentially swap the units over too if that is worth a try.
At the same time as this E-07 was showing, the web UI was behaving a bit weirdly, the web page loaded, but was not connecting to the websocket. On both occasions I resorted to removing the power and afterwards it was back to working fine again. During this, the Virtual Console (nice feature BTW) was still responsive, but I don't believe that the MQTT broker got any messages at all, the last thing showing in HomeAssistant was E-00 OK.
It ran for a couple of days between E-07 / unresponsive web front end.
As an aside, the logging feature seems like it could be useful, but is there any way the logs could be sent to a syslog server? I believe the protocol is really simple so it might be a handy to monitor how it's all going.
Thanks,
Ed.