dpfrez

can you explain what noise has to do with the issue? I've see noise in the system before, but it produces random results. This stuck status produces the same results once its stuck until it is queried. Also, the links are never lost and do not need restored. The only thing happening is the device will not respond to an "on" command until it is queried.

I have a number of insteon switches in our home and occasionally the devices will stop responding to an ISY program command such as a program that turns the lights on at sunset. When I log in to the management console of the ISY device, it shows an incorrect status. Manually initiating a query updates the status and seems to bring it back in response to the program. I further tested this with stuck devices by initiating the on command by triggering the IF statement in the ISY program. It will not respond. I thought if I programmed a query into the program ahead of the on it would clean up the status and keep this from happening but it did not. So, there is clearly something different about how the ISY program initiates a query and how the ISY admin console (via a right click / query) initiates a query. Does anyone here know what the difference is or what else I can try to get the devices out of this stuck state? PS - after further testing it appears a fast on responds in this stuck state but an on does not.

I have a number of insteon switches in our home and occasionally the devices will stop responding to an ISY program command such as a program that turns the lights on at sunset. When I log in to the management console of the ISY device, it shows an incorrect status. Manually initiating a query updates the status and seems to bring it back in response to the program. I further tested this with stuck devices by initiating the on command by triggering the IF statement in the ISY program. It will not respond. I thought if I programmed a query into the program ahead of the on it would clean up the status and keep this from happening but it did not. So, there is clearly something different about how the ISY program initiates a query and how the ISY admin console (via a right click / query) initiates a query. Does anyone here know what the difference is or what else I can try to get the devices out of this stuck state? PS - after further testing it appears a fast on responds in this stuck state but an on does not.

Right, that's the whole reason for my question. Does anyone know how that sensor communicates with the thermostat? I need a different type that can be screwed into a pipe to measure water temp.

Does anyone know the type of probe that is compatible with the Insteon thermostat? I'm needing a pipe plug type probe to monitor the water temp from the pipes going to my pool pump. There is not an easy way for me to get a wire all the way to the pool itself. The pipe plug taps into the PVC pipe and monitors that way. Alternatively, I was looking at DS18B20 type probe via the EZIO8SA but don't have any idea how that would work or if it natively integrates with the ISY device. My pool heater had at least one temp probe but that seems to be outputting AC voltage which I can't find support for on a device either.... Thanks for any guidance.... Daniel

Was the ability to store variables with status ever completed?