OTGW does not respond to commands
Posted: Sun Aug 07, 2022 12:56 pm
I have a problem with my OTGW that I cannot seem to figure out.
My OTGW PIC does not seem to respond to any commands received from the serial input... sometimes. Serial output works fine. Running otmonitor I get regular updates from my thermostat and boiler. However, sending a command such as PR=A does not produce any response, not even an error message.
Powercycling the device sometimes restores the behaviour, and I will get the expected responses to commands for a while. Shorting the reset pins seems to be a more reliable method of restoring full communication.
I tried to troubleshoot the issue by connecting an FTDI cable directly to the input pin of the PIC, while also having it connected to an ESP8266. Although the PIC did not respond that time, I could see that it received the commands physically at the correct baud rate.
Suspecting a hardware fault, I already replaced my P16F88 running 5.4 with a P16F1847 running 6.1. This did not have any observable effect.
My setup is a V2 gateway from NodoShop (bought in 2017, revision 0.9.9.3), and I normally have it connected via a NodeMCU.
Connecting it directly via an FTDI cable gave mixed results. One time, it just produced an endless stream of 'SE' messages, without even having sent a command, but other times (after resetting) it does work as expected.
I think I already came across this issue at least a year ago, but it became more noticeable last month as the Home Assistant integration now refuses to work without receiving a response.
Can anyone help me troubleshoot this issue?
My OTGW PIC does not seem to respond to any commands received from the serial input... sometimes. Serial output works fine. Running otmonitor I get regular updates from my thermostat and boiler. However, sending a command such as PR=A does not produce any response, not even an error message.
Powercycling the device sometimes restores the behaviour, and I will get the expected responses to commands for a while. Shorting the reset pins seems to be a more reliable method of restoring full communication.
I tried to troubleshoot the issue by connecting an FTDI cable directly to the input pin of the PIC, while also having it connected to an ESP8266. Although the PIC did not respond that time, I could see that it received the commands physically at the correct baud rate.
Suspecting a hardware fault, I already replaced my P16F88 running 5.4 with a P16F1847 running 6.1. This did not have any observable effect.
My setup is a V2 gateway from NodoShop (bought in 2017, revision 0.9.9.3), and I normally have it connected via a NodeMCU.
Connecting it directly via an FTDI cable gave mixed results. One time, it just produced an endless stream of 'SE' messages, without even having sent a command, but other times (after resetting) it does work as expected.
I think I already came across this issue at least a year ago, but it became more noticeable last month as the Home Assistant integration now refuses to work without receiving a response.
Can anyone help me troubleshoot this issue?