btreinders Posted January 18, 2023 Posted January 18, 2023 (edited) @MrBillor anyone that know the answer. Every time I reload the ISY integration any automations I have based on ISY variables seem to run if they are in the opposite state. Like if a roller shade closes when HA.Kitchen.Roller.Shades = 0 then if I reload the integration because I have changes I need HA to see then the shades close if they are open because they see change even though that variable in the ISY did not really change. Same for switches I have made in the ISY using the HA.switch folder with sub folders for switches. I don't keep track of roller shade position since someone might open or close them with the RF remote and then the state is wrong anyway. I just send a 1 and then 0 to close them and a 0 and then a 1 to open them. I guess I could use two variables so the 0 value never runs anything but that's just more to have to remember why I did things the way I did. Thank you! Edited January 18, 2023 by btreinders
MrBill Posted January 19, 2023 Posted January 19, 2023 I'm not sure why, without more information but my guess is that HA is detecting the variable change from unknown to zero. A better approach is one that I use with my overhead barn door... The ISY variable is normal value is zero. When ISY wants to open a door, the value is changed to 1, the HA Automation then opens the door and calls the service isy994.set_variable to change the isy variable back to zero. When the value of the variable is changed to -1 then HA closes the door and again calls isy994.set_variable to change the ISY variable back to zero. With that method zero is a neutral value, nothing happens when the variable assumes that value. Whenever I get around to migrating to eisy that automation will change, I couldn't figure out how to read an Insteon button back when i created that, but it's likely a good solution for your shade. 1
Recommended Posts