For sometime now I have been running an app I coded on my three C8s. The app (plus a device I coded) uses the "telnet" capability of the hub to communicate with a Windows app I coded. Each hub also is bound to three Honeywell T6 thermostats. The purpose of the app is to allow my home automation system to monitor/control the T6s even though the automation system doesn't have support for T6s. From the home automation systems point of view it "thinks" it is dealing with an RCS brand thermostat that is does support (and for which I had protocol documentation).
Everything has been working fine.
But recently I began the work to re-code the Windows app into a Windows service. So the "telnet" connection from the hubs to the Windows computer was frequently lost and and then re-established as the Windows service was stopped/started as the code was updated.
Two of the hubs just stopped responding to commands, from the Windows app, to query the T6s on their current settings.
It was necessary to re-boot them to get them to work again - but only for a while.
One of them simply gave of the ghost and the web interface ceased to work. That one required a "soft reset" which of course meant restore from a recent backup - which I had.
With the second one I decided to remove the app, remove the device, re-boot, re-install the device and re-install the app.
Now all three hubs are working fine again.
So any thoughts on why two of them went on strike and refused to do their job?
If you post your app/driver someone might be willing to poke through them and spot anything obvious...
I have multiple hubs running telnet clients against multiple devices and haven't seen the hub refuse to process inbound or outbound commands.
I have seen devices hosting telnet servers require a reboot, but that's been pretty rare...
Have other folks look at my code? How embarrassing could that be.
I am fairly new to this and don't have a full grasp of the way the hub works or the programming ins-and-outs (I was going to use paradigm but that word took a beating sometime back).
So it is certainly possible that I am doing something wrong.
The only curious bit is that they worked for a long time and didn't act up until recently when I started covering the Windows app to a Windows service.
Thanks for the feedback. I will post my code - after I look it over very closely.
I have a program call DockLight Scripting which is a diagnostic tool what I use when I need to verify communication with another device or application.
In this case I configured it to connect to the port my App in the Hubitat was using for it's "Telnet" connection. It did connect without issue and it sent the basic command to ask the App to identify itself. The command was sent and received as reported by the Event "log" in the Hubitat but nothing was returned.
And as mentioned after removing my Device and my App from the Hubitat and re-booting and re-installing them both the App worked again.
If it were a Windows app I would suspect something like a memory leak that consumed all the free memory but I don't have any idea if that concept applies to Hubitat Apps/Devices.
