My question/point to more about the "why" there are two different functions. If the node server can get feedback for a button press, then it's 100% possible to send it as a control through a node server. That's how all INSTEON and most of Z-Wave works. ISY's equivalent is Control and it does exist and it's been there since the beginning of time. Looking more closely at it, it looks like it was really just designed to support automated shades and scenes. It sounds like it may only support device status, but there isn't any restriction from the Polyglot or the node server API that would prohibit it from supporting control also. Now I don't know if the Lutron Caseta node server does this. When it is sending commands there is no state so it will always send the command. So if the device is in the Off state, responding to an Off command doesn't change it's state. When it is responding to commands, that is setting the device status and the device status has state.
An Insteon switch is both a controller (sends commands) and a responder (responds to commands). It's a bit easier to explain in terms of an Insteon switch. But the node server would have to be written to do this. It is perfectly reasonable for a switch to send multiple On commands or multiple Off commands in row and have each of those trigger the program. A control is triggered when the device sends a command.
You can't change the status from Off to Off, that's not a status change.īut for a switch, control can also be a trigger. That triggers when the status is changed from one value to another as people have described above. The ISY can use two different triggers for something like a switch. Needless to say this would entail a lot of effort to add additional buttons for this. This would change anytime the button is pressed regardless of the parent "state" of On/Off. What could be implemented with a lot of extra work and overhead in a NodeServer such as Lutron Caseta would be adding an additional device status for each button which would auto-reset and all it would do is receive a button press and change a bit from 0 to 1 and revert back to 0. If the device does not change from on to off or vice versa then nothing has actually changed to trigger a program to run. It's truly a "state machine" where the programs only execute if the value changes. ISY (as far as I know) does not have this time stamp change/update which is monitored. This provides a immediate benefit for HomeSeer events which trigger off of this change time not necessarily only on status change. If you press off it updates the change time and does so each time the button is pressed.
HOMESEER VS ISY FULL
Regardless if it's a full status change such as On to Off. This is updated anytime the device changes.
Then there's another attribute of "Changed" which is a timestamp. In HomeSeer a device has it's "Status" which is the On/Off or whatever it may be. I am not sure how the program works in Homeseer but it recognizes a press of the button regardless of what the prior state is in.
0 kommentar(er)
