I am using a NodeMCU v3, HS3, 1.0.0.166 version of the plugin and is configured for NodeMcu API.
According to the Homeseer log, the plugin is sending a reset command every few minutes – even though the status says “Connected”. I thought that there was something in the code I added to the ino file so I used the ino file downloaded from the config page without making any changes to it. A reset is still being sent frequently. I read in another post that power could be the problem so I disconnected all the I/O from the board. So the USB is the only connection. I tried a second board with the same results.
Any idea as to why is this occurring?
Also, is there any way to disable resets? In my application, there would be times when it would be bad to issue a reset.
- Robert
According to the Homeseer log, the plugin is sending a reset command every few minutes – even though the status says “Connected”. I thought that there was something in the code I added to the ino file so I used the ino file downloaded from the config page without making any changes to it. A reset is still being sent frequently. I read in another post that power could be the problem so I disconnected all the I/O from the board. So the USB is the only connection. I tried a second board with the same results.
Any idea as to why is this occurring?
Also, is there any way to disable resets? In my application, there would be times when it would be bad to issue a reset.
- Robert
Comment