I hope you’re making progress! I’ve been very busy and haven’t had as much time to dedicate to my own issues as I’d like but things are moving along. Yes, frustrating to have to move the PLM around! I have some PLMs, too, but have chosen to mothball them because the hubs (cheap, used) allow me to continue to use my mix of Insteon and X10 devices with the Insteon app as I slowly learn and migrate everything to openHab2. The other advantage of the hubs is that they are TCP/IP addressable so no physical reconfiguration is required to swap between Windows and Linux tools/platforms, the problem that you’re facing. The app also allows for easy device linking and initial troubleshooting; button pressing only required occasionally, generally only on older devices.
The Insteon app also seems to coexist nicely with openHab (other than delays in device status showing up on openHab) and has been a great backup during the past while as myopenhab/openhabcloud evolves. It will also remain indispensable for my two-site, Ubiquiti-brdige-connected configuration until the ability for openHab to support multiple hubs (and PLMs) at a time gets addressed. I’ve also been using Insteon Terminal on Linux occasionally and, as yet, haven’t wiped my hub link database by also using Windows HouseLink but take the warning in the docs seriously!
Yes, the Insteon devices definitely need to be linked but not so for X10 devices. Sorry if my comments were misleading. Having dual hubs/PLMs, one for each leg, is def a solution to the bridging issue, IMO. As I move forward, my approach is to stop having my Insteon and X10 controllers control Insteon (through scenes etc.) and X10 devices directly. Each will be on a different house code and the openHab rule engine can be responsible for routing the control commands to the appropriate devices. This will, of course, make Insteon control via their app awkward (Android app still doesn’t support multiple hubs (homes) without signing off and on to a different account but the iPhone app does) but it’s only for backup anyway, so it’s not a long-term problem as along as the multiple hub issue gets resolved.
The problem, as I mentioned earlier in the thread, is that there doesn’t seem to be a way to pick which port to send X10 commands to, unlike with the Insteon addressing scheme that is possible because the linking database of each hub/PLM is loaded at startup which tells openHab which hub/PLM to send Insteon device commands to afterwards. Because X10 devices aren’t linked into each hub/PLM, openHab has no way to tell which hub/PLM and thus leg (or site in my configuration) to send X10 commands to. This would probably need to be set in the items file but there is currently no provision for picking which port in an X10 item definition. I hope to patch something in myself and then submit it to the project but it’s going to take me some time to be at that level, considering the learning curve I’m facing.
Maybe someone with more knowledge who happens to read this can offer some support or guidance. Unfortunately, there doesn’t seem to be a lot of love for our legacy X10 and Insteon products on the team, anymore, with all the exciting new tech getting the focus. Speaking of which, I picked up some Hue products over the last few days cheap and can fully understand! One Hue bridge is here at home and the other at the remote site later today!
All-in-all, I’m having a great time and have to say how happy I am to have found openHab! Open source home automation tech is, at worst, a great project with which to modernize one’s skills. Soon I’ll be writing my own bindings etc.! Kudos to the team!
Yes, I’ll be doing the Kodi thing, too, eventually! So cool LOL!
Once again, I hope you’re making progress!