OTGW stops sending messages after some time
Posted: Tue Dec 08, 2020 11:13 am
Hi all,
I have my OTGW (pre-assembled from NodoShop) connected to my balenaFin home controller (which is a ruggedized raspberry pi CM3 baseboard) through a USB-serial adapter. The device is running balenaOS, so all the services are containerized.
I've set up ser2net to serve the serial port to the Node-RED container that (among other things) controls my heating. Right after starting this up, it's always working fine. I get all kinds of messages from the OTGW. However, after some random amount of time messages just stop arriving. This is where is becomes strange though: after restarting ser2net, the OTGW starts sending messages again (without doing anything to the hardware).
In my previous set-up I was reading the serial port directly from Node-RED and the same thing happened. At that point, restarting the flows helped. I've now rigged up a watcher that restarts the ser2net container as soon as I don't receive any messages for more than a minute, but this is kind of an ugly workaround of course.
Other serial ports are all working fine from Node-RED.
Has anyone seen something similar?
Kind regards,
Marten
I have my OTGW (pre-assembled from NodoShop) connected to my balenaFin home controller (which is a ruggedized raspberry pi CM3 baseboard) through a USB-serial adapter. The device is running balenaOS, so all the services are containerized.
I've set up ser2net to serve the serial port to the Node-RED container that (among other things) controls my heating. Right after starting this up, it's always working fine. I get all kinds of messages from the OTGW. However, after some random amount of time messages just stop arriving. This is where is becomes strange though: after restarting ser2net, the OTGW starts sending messages again (without doing anything to the hardware).
In my previous set-up I was reading the serial port directly from Node-RED and the same thing happened. At that point, restarting the flows helped. I've now rigged up a watcher that restarts the ser2net container as soon as I don't receive any messages for more than a minute, but this is kind of an ugly workaround of course.
Other serial ports are all working fine from Node-RED.
Has anyone seen something similar?
Kind regards,
Marten