peszko wrote:This seem to have happened right after my a scripted status request to the IO link. Which resulted in reply mismatch error.
matt (support) wrote:peszko wrote:This seem to have happened right after my a scripted status request to the IO link. Which resulted in reply mismatch error.
So it looks like you have an incoming Insteon message that causes a Trigger which executes your script that sends Insteon status request messages, right?
If that is the case, then add a delay before your script is executed. The problem might be that the original Insteon module (FY_Porch_OCP) is still sending Insteon clean-up commands which then collide with your script's outgoing status request commands.
peszko wrote:I figured out what is the Button 19 message. Turns out its an undocumented temperature warning. It's below zero here, so the sensor started to send warnings. Apparently it's an undocumented feature which has an error in it. It should send a warning and stop, but it doesn't. I found instructions here on the forum on how to stop it.
If this is the case, then the insteon protocol is really mainly appropriate for small and basic installations with not too many devices and rules. Insteon looks to me like what my professor called, a "work mostly circuit", which he explained as a circuit (or system) where under most low to moderate usage or deployment scenarios it works properly, however when pushed harder or deployed en masse, problems start to show up. Inseon looks to me like a perfect example of the system my professor warned us not to create.
Users browsing this forum: No registered users and 5 guests