[therealdb]

Thanks for the update. I know it’s open source, but I’m not that proficient in C++ – otherwise I’d be more than happy to help with some code.

I was speaking of the ability to get the water level with the station started message. I’m successfully using the MQTT messages, but I still need to perform an HTTP call in order to get the water level, which defect the purpose of not polling via REST API and use MQTT 🙂

[therealdb]

I also think water level is useful. I usually log it and I think it could be useful with the message announcing a station started.

[therealdb]

it’s the same firmware.
it seems to be related to the sockets LUA library. I switched to curl and it’s OK. maybe something related to the fact that the data are sent in chunck, I’m not really sure.

Thanks for the help.

[therealdb]

Thanks Ray, I got it. Was I was referring to it is that sometimes the same endpoint is missing some information, while others everything is present. Is that by design? I really want to just call one single endpoint, if possible, to avoid sending many HTTP calls. Thanks.

[therealdb]

@ray I have a very similar behavior. OS 3 DC connected to a Netgear Nighthawk R7000. In my case, the routers seems to detect the device as connected, but the web UI is not responding.

I have a script checking every 15 seconds for the status, in order to notify me of programs/stations activity (since no webhook or mqtt are available). I don’t know if there’s a correlation, and in my case a reboot helps too, unless a day or two.

[Author]

Posts