Page 1 of 1

P1 Smart Meter hardware (x) thread seems to have ended unexpectedly

Posted: Tuesday 23 January 2018 12:28
by reynard80
I've built a P1 Smart Meter gateway, using an ESP8266 with ESP Easy. It seems to work well, as I can see neatly formatted telegrams when I connect in serial. Also when I connect the device in the Domoticz, it will work well for some time, sending the Power output, Voltage and Gas usage.

However, after some time (usually a few hours), Domoticz will stop receiving the data correctly. In the log I keep getting these errors:

Code: Select all

P1 Smart Meter hardware (4) thread seems to have ended unexpectedly
When I go to 'Setup', 'Hardware' and update the P1 Smart Meter settings (without changing any setting) Domoticz connects to the ESP again, and it will work for a few hours once again. I've tried using different rate limits, but this doesn't seem to help.

What could be the problem? Can I see some more information in the logs why the the P1 Smart Meter thread crashes? Does it receive malformed data or something; is it possible to see the actual data that Domoticz received from the ESP?

P.S. I'm running Domoticz version 3.8153 on my Synology NAS.

Re: P1 Smart Meter hardware (x) thread seems to have ended unexpectedly

Posted: Friday 26 October 2018 15:21
by globehouse
I have the same problem.
Has someone a solution for this issue??

Re: P1 Smart Meter hardware (x) thread seems to have ended unexpectedly

Posted: Friday 26 October 2018 17:37
by jvdz
I have had the same and for me the WiFi connection was lost. As Domoticz keeps the connection open constantly waiting for data it would fail after this dreconnect of the ESP.
I am on 4.9700, which has some issues when the thread fails it will get somewhat unstable. Think this is worked on in Beta but am not sure.

For me the reason of the failures was that my WiFi AP would change to a different channel every couple of hours for the 2.4 Ghz band, which made the ESP loosing the connection shortly after which domoticz would get the Failure. It would recover a couple of times and then simply go into an unstable state resulting in a hang. Monit would then force a reboot after trying to restart the service for a couple of times.
I solved it by setting the 2.4 Ghz band to a fixed channel.

Jos