I am using a “On/Off button Tile” as a hack to make another device work with my Harmony Home remote.
I map this “Virtual Button” to my “Real Device On/Off methods” using the smart app “The Big Button”
So when “Virtual Button” is turned on I have "The Big Button " configured to issue the “On” command and vis versa.
The problem is if the “Real Device” state is “On” but the virtual button state is “Off” then issuing a “Off” command to the virtual button doesn’t seem to fire “The Big Button” to switch on off the “Real Device”. I think because the device is seeing it’s state is already “Off” and not changing state therefore the subscription from the Big Button is not issued.
Can I alter “On/Off Button Tile” so it doesn’t know it’s state and always issue the state change ?
I had the idea to add two more states lets call them “off2” and “on2”. Then in my on method I can check the current state and switch to the other.
The problem is then I have to also rewrite the BigSwitch to act on both on/off as well as the on2/off2 states…not even sure that will work ?
Is there a way I can generate the On event for subscribers to see even if the switch is already on ?
A second thought I had was to alter the on/off methods to issue two event changes instead of toggling on/on2 I could just issue event “on” then event “on2”. I could do the same for off…issue off and then off2.
This would leave the device always in the “on2” or “off2” state.
Now any on or off method calls would issue two state changes
on -> on and on2
off -> off and off2
and the subscription would be honored…I think.
Does this make sense or should the subscription always be honored and I am barking up the wrong tree here.
Sorry if this is confusing. Hard to describe what is going on.
BTW: Why does “On/Off Button Tile” have capability “Sensor”, that doesn’t make sense to me.