I'm running cgate and cgateweb on a Pi 3, nothing else, to surface mqtt to Home Assistant on another Pi. When it works, it works very well and responsive.
What we're seeing tho is that it's an unreliable solution, and I'm trying to understand why, and testing would suggest it's cgateweb not talking to cgate on the same machine. The address is listed as 127.0.0.1
When the system is unresponsive, I'm seeing no read MQTT traffic using mqttexplorer from cgateweb. At the same time, I can from a Windows PC happily talk to cgate on the Pi so we know the transport from the CNI to cgate is working as expected. A quick restart of cgateweb gets things going again. I can write MQTT traffic back.
In summary : more often than not, cgateweb isn't reporting CBUS changes (such as a light being turned on), but can continue to write changes (so it can tell a light to turn on).
Is there a way of debugging the link between cgateweb and cgate better to understand where the break happens? Thanks
I'm running cgate and cgateweb on a Pi 3, nothing else, to surface mqtt to Home Assistant on another Pi. When it works, it works very well and responsive.
What we're seeing tho is that it's an unreliable solution, and I'm trying to understand why, and testing would suggest it's cgateweb not talking to cgate on the same machine. The address is listed as 127.0.0.1
When the system is unresponsive, I'm seeing no read MQTT traffic using mqttexplorer from cgateweb. At the same time, I can from a Windows PC happily talk to cgate on the Pi so we know the transport from the CNI to cgate is working as expected. A quick restart of cgateweb gets things going again. I can write MQTT traffic back.
In summary : more often than not, cgateweb isn't reporting CBUS changes (such as a light being turned on), but can continue to write changes (so it can tell a light to turn on).
Is there a way of debugging the link between cgateweb and cgate better to understand where the break happens? Thanks