I flashed the MJ switch with Tasmota. Your rule above worked. I had a very similar rule at first for both ON and OFF, and could not get it to work last night. This morning I removed the group rule and went back to my ON and OFF rule at it worked…
I changed my rule to match your suggestion as your solution is simplier.
Nope, Profiles can be set through Paper UI. If you are using Simple Mode ON, then turn it off just to adjust the profiles, then to Paper UI -> Configuration -> Items -> search the Item -> change its settings.
I should repeat, I don’t think this is going to help you because your wall switch appears to be configured to produce commands. I’m not sure, because your configuration is still secret.
If you’ve left autoupdate default on your wall switch Item (so that state follows commands) it ought to work out.
Here’s how follow profile is intended for use.
Say you have LampA and LampB configured in an ordinary way, whether that’s zwave or MQTT or whatever doesn’t matter.
Both can be commanded on/off via channels to binding.
Both report their state to openHAB via channels from binding.
If we want LampB to follow LampA, we make an extra link from LampB’s channel to the LampA Item, and apply the follow profile to that link. (so LampA has two links to different channels now)
The effect of this is that when LampA Item state turns on (for whatever reason), its new state in openHAB gets passed to the follow profile - but the profile transforms it into a command and passes that to LampB channel.
LampB channel then does it usually does with commands, and it passes via binding to the LampB real device.
I have two Insteon devices, (A) one wall switch 2466, (B) one plug-in switch module 2635. I want switch B to follow switch A. I set them up per the linking instructions above. I could only get this to work if I had each switch follow each other. Both things had one default profile link and one follow link. I’m OK with that behavior but not what I intended.
The follow setup works fine when controlling via Basic UI or my iOS app.
I cannot get the logic to work when physically switching the wall switch. In fact, I have a couple Insteon wall switches and neither send commands beyond the physical switch, i.e. nothing in the event log, but switch the light as expected.
I wonder if this lack of outbound communication is preventing the logic from firing.
Understood but I have a Martin Jerry switch via MQTT that reports changes from manual changes. I don’t recall seeing a configuration option for reporting changes on any devices I have configured, Insteon or MQTT.
For an MQTT binding channel, you set up a stateTopic, yes? When some remote device publishes to that topic it will result in a state update to a linked openHAB Item. That’s how this binding works.
Of course, whether any remote device actually publishes anything to that topic, or when, is beyond openHABs knowledge and control. In this case, that’s about however this Martin Jerry thingy is designed and set up.
I don’t know anything about Insteon. If you’re using one of the Insteon bindings, and you think you’re missing updates from your devices, someone can help. But we’re now at post 19 in this thread and no-one else has any idea how you’ve configured this stuff.
That is correct. I guess I didn’t realize it at the time. I’m still learning by reading as much documentation and community posts as possible. My last resort is posting my own thread.
I’m making progress now by cross linking the Insteon devices to each other and to the PLM. This seems to have corrected my issue with the devices not providing state changes back to OH2. The PLM was originally configured with another automation platform (Home Control Assistant). Cross linking wasn’t necessary for my simple setup then but I’m slowly climbing the OH learning curve.
Finally have everything working properly. I cross linked each Insteon device back to the Insteon modem to get the devices to send state updates back to OH2. The issue I kept fighting was the logic worked fine when controlling via the BasicUI or the iOS app. When manually switching ON the wall switch (A), module (B) would immediately follow the ON command then power OFF within a second. A manual OFF command and module A switched OFF and module B stayed OFF.
During all the debugging, I cross linked the Insteon modules to each other see if that had an impact. Once I removed the cross linking between module A and B, the logic works perfectly both manually and via BasicUI.