I haven’ t used the lastes versions of the KAKU app, but I read it was recently changed to reflect the original behavior:
You cannot pair receiver (the AMC-100) to Homey in itself, as it just listens to signals it has learned. So Homey needs a code that is programmed into the AMC-100 receiver.
The app I knew had two ways to accomplish that:
- Homey generates a random code that is learned to the receiver.
- You learn Homey an existing code (i.e. that of the button) that the receiver has previously learned and responds to.
I am thinking that you used the second method. So the code transmitted by the remote is the one that Homey identifies with the AMC-100 receiver.
The old driver behavior was: If Homey “heard” the code corresponding to the receiver ( the bulb) it assumed a remote was used to operate the bulb. So then Homey changed the state of the bulb to reflect wat it assumed must have happened. That would enable you to what I suggested - consider the bulb and the remote to be the same thing.
Maybe the KAKU app that you have does not have that behaviour. (The old one in the community store does.) But if it doesn’t I suggest you use the other method: Change the code that Homey identifies with the AMC-100.
First you need to remove the AMC-100 from Homey. If I’m right you can then pair the remote to Homey. You can then add the AMC-100 to Homey again, as long as you let Homey generate the code.
If you want to keep the AMC-100 state intact you can unlearn the remote from the AMC-100 by putting it in to programming node and sending the remote OFF code. Then you need to create flows to operate the AMC-100 with the remote.
