bhihifi

I have some buttons that control scenes not turn off even when the scene is turned off from a voice command or from another controller scene member. I fail to fix it because I don’t remember how to duplicate the problem. You want a mutually exclusive set where each button is a responder to the inverse state of the active button. So after each button is a scene by itself, turn the other scene(s) off when another scene is on. You could use a single subprogram that you run as part of each scene’s main program to clean up the other buttons using a single state variable or argument specifying the desired active scene. You could use a series of if-then statements to mimic a case statement conditional on the active scene.

@larryllix Good additional option. Was not an issue in selling previous homes but buyers behave strangely. I got into HA because a home I bought had an X10 system and I got the bug. One realtor opined, due to the contemporary styling of my home and price point, that the HA system would be a selling feature, not a detriment. I will have to negotiate what I will and will not do. But I shall prepare for option 4 as well.

If I understand you correctly, the HA system is the signaling and status interface but the real control lies in your EISY setup. I'm not well-versed in mutual exclusivity but you can implement this in EISY program logic with conditions and state variables. May not be as fast as having mutual exclusivity within the switch itself, assuming that this was also an option. As an exercise, I would actually draw out my desired states and actions in a flowchart first to see what I want to have happen, then figure out the implementation that created the least dependency on hardware features.

This hit home (sorry) for me. Either in the event of my demise or relocation to a more age-appropriate home, I need to make a succession plan for my setup. I have a mix of Z-wave and Insteon devices with the Polisy, Zmatter and a USB PLM to communicate. My only programs turn things on and off at specific times; I use scenes and voice commands with Alexa. I haven't gotten into more sophisticated programming. My alarm system has Z-wave capabilities. I have not enrolled my Zmatter devices with the alarm system. I am pondering options: 1. Only have Insteon devices and leave a Hub behind for the next owner. This would mean swapping out some Z-wave devices but I have only 5-6 of them in use. The only reason for the Hub would be to allow voice commands for the next owner and scene management for the 6-button switches in some places. 2. Leave the mixed bag with Polisy setup and let the next owner figure it out. With documentation, of course. I update all the switches and scenes configuration via the Polisy topology export. 3. Leave the Insteon switches to communicate with each other without a hub. Let the next owner add the Z-wave to the alarm system or implement something else. The Polisy scenes that mix Z-wave and Insteon devices will no longer work. Would appreciate your feedback on these options.

Following. I'm here to learn but sharing some thoughts which may help. I wonder if you may be setting yourself up for future issues with multiple control points. Although you may have good reasons for doing this, as a former real-time software developer, I would anticipate situations that might be difficult to troubleshoot between systems, especially with timing and status updates. Others who run multiple control systems for years may disagree. In that case, I'm here to learn. You may have a lot of time and effort invested in the Home Assistant setup and the porting of all of that to a different platform will seem redundant and time-consuming. If I were implementing this, I would keep all of the scene and device control elements on one platform, and use the other platform just for signaling (requesting action by setting variables or flags) and displaying status. Then you isolate all the decision making to one place and only have to troubleshoot the signaling.

Essentially new. I took it out of the box to test it with Home Assistant (on a Raspberry Pi 4) and Polisy Pro, then cleared the link table. Works well with both systems. I prefer the dual band PLMs. This one relies only on the wireless Insteon protocol so you need a dual band device nearby. It eliminates the need to connect a cable between your controller and a PLM. Free insured shipping to continental US. Payment via PayPal Goods and Services. $129. It is listed on eBay for $150 but I would rather sell to someone in this community for less. Priced similarly to recent eBay sales.

Sent you a message.

@CJVann There may also be an upgrade or discount code to buy the Polisy if you already own a 994i. You may have to search on this forum to find it.

Many of the advantages of Polisy are listed above; I'll only add a few that I found useful. I purchased the Polisy Pro, because I wanted the flexibility to install without Ethernet nearby and the ability to use both serial and USB (wireless and plug-in) PLMs. I ended up installing near my router, so not using the WiFi. It also has a multiport Ethernet switch built in so if you needed to expand your wired network it works well. My main router does not have extra ports, and I would have needed a switch for a wireless access point which I was able to connect to the Polisy Pro.

First, a huge thanks and praise for @firstone who wrote this great, useful NS and for his very attentive and rapid responses to resolve an issue. Also thanks to @Geddy for creating this sub-forum to make it easier to post and find information on AVRemote. The LG WebOS TV is finicky and for some versions, one needs a secret menu to enable IP control before the NS works. The LG ThinQ app will control the TV but Alexa skills barely work and are not easy to set up (need to enable 2 skills and link to ThinQ). I first installed version 0.8.9 of the NS to control my LG WebOS TV but could not turn the TV on. I sent a message to the developer and he responded very quickly with troubleshooting and data gathering steps, even walking me through the ssh commands needed to perform them. He quickly identified the issue and updated the Node Server within a few days to include specifying a subnet mask if necessary to make the on command work. I hope he will port to PG3 so I can support his work. The Power On command from the Admin Console causes the NS to send a Wake on LAN (WOL) packet to the TV's IP Address (aka HostName in the NS configuration page). WOL is a broadcast command that uses an IP subnet mask which defaults to 255.255.255.255. However, my LG TV will respond to WOL only if the subnet for the LG TV is narrowed to xxx.yyy.zzz.255 where xxx.yyy.zzz are the first three octets in the TV's IP address. Apparently lgwebostv does not always work as a proxy for the LG TV's IP address, so my LG TV needs the HostName configuration field to have the TV's actual IP address. Here's what I did to make it work: Configure the TV: Go into the Main setup screen (All Settings) > Connection When Connection is highlighted, key in 82888 and you will get a secret menu (IP Control). Make sure Network Control and Wake On LAN are enabled). Note down the IP address and MAC address for the TV here for both WiFi and Ethernet connections; these addresses will help configure the Node Server. Hit the Back key to return to Configuration. Set the TV Name to whatever you like. You'll use this in the Node Server configuration as well. For the Node server configuration screen: AVRemote Node Server Version should be 0.9.1. If not, you need to stop and start it again to force an update. TV's name should match the TV's name that you set up for the TV (using the LG TV Menus) HostName is TV's IP Address xxx.yyy.zzz.### Port is 3000 MAC address needs to be delimited with periods, like AA.BB.CC.DD.EE.FF Broadcast address should match TV's IP subnet xxx.yyy.zzz.255