Disabling the OTGW (under Hardware in Domoticz) and re-enabling it with a delay of half an hour fixes the issue sometimes, but not always on the first try.
Anyone else having this issue or an idea how to fix it?
For a couple of days now i hooked-up my OTGW to my raspberry PI. When i start the OTmonitor it works for couple of minutes till max 45 min. Then suddenly it stops working and i need to restart the otmonitor. When lucky it still reads the data but often i have to wait for couple of minutes after reboot. Has this maybe to do with the fact that it needs USB with external power?
The other issue is that i cant seem to startup the OTmonitor at start-up. Does anyone has a decent process to manage this?
When i run
CODE: SELECT ALL
./otmonitor-ahf --daemon -f /opt/otmonitor/otmonitor.conf
sometimes it workes... but most of the time i get a internal server error
Unfortunately I ran into a similar issue...
I soldered my OTGW (USB version over WiFi) together and after setting it up I could instantly see the values on the OTmonitor (small side note: I couldn't download the latest Windows version, I had to use an older Beta version. "No permission" error on the site).
After a minute the "fun" became a little less as the log was filled with ERROR 03 messages. Just like the topic starter mentioned, the values drop to 0 as well.
Not sure if it's related or noticed by others, but when the error 03 appears, I also saw C.O on my thermostat.
Plus, in general, I'm not able to change the temperature. Just mentioning this as I'm not sure this is due to the error message.
The only thing which solves the error is disconnecting the gateway from the mains and plugging it back in. This too only "solves" it for a minute, max.
If anyone knows a solution...?
Marc.
---
Using the latest OTGW firmware and an Agpo 127c boiler.
I have problems with latest version of OT firmware 4.2.5, reverted back to 4.2.
It seems my OTGW is resetting more often (multiple times per hour) if I hook it up via a TPLINK (Ser2Net) or (OTMonitor with relay) on a Raspberry.
Connecting it directly to a laptop via USB and running otmonitor 4.2.4.1 allowed me to reduce error 03: to 0 counts. http://www.domoticaforum.eu/viewtopic.php?f=75&t=10882