spud
I seem to recall running into this problem when I was controlling SmartThings devices using the ST API and JSON calls to/from Homeseer... Best I remember the SmartThings API wants switch commands sent either textually as "On" and "Off", or numerically as "0" for On and "1" for off. Looks like the Plugin is currently using the binary "0/1" option.
Problem with that is those device values don't follow the HS convention of "0" for Off and "255" for On. Therefore if a switch controlled by ST is added to an Easy Trigger group that includes Homeseer controlled switches, commands are not going to work for the ST devices. A command of "0" would turn OFF the Homeseer native devices and turn ON the ST devices.
I'm wondering: Could you change the plugin to use "ON/OFF" strings and parse to conventional values of "0/255" without it being a breaking change?
Thanks,
--Barry
I seem to recall running into this problem when I was controlling SmartThings devices using the ST API and JSON calls to/from Homeseer... Best I remember the SmartThings API wants switch commands sent either textually as "On" and "Off", or numerically as "0" for On and "1" for off. Looks like the Plugin is currently using the binary "0/1" option.
Problem with that is those device values don't follow the HS convention of "0" for Off and "255" for On. Therefore if a switch controlled by ST is added to an Easy Trigger group that includes Homeseer controlled switches, commands are not going to work for the ST devices. A command of "0" would turn OFF the Homeseer native devices and turn ON the ST devices.
I'm wondering: Could you change the plugin to use "ON/OFF" strings and parse to conventional values of "0/255" without it being a breaking change?
Thanks,
--Barry
Comment