MMAltair

I only have 1 hub in each house that support all of the devices for that house. If these hubs were changed to the local control hubs (I understand the local hubs are not available currently?) would the local control work for each place independently? My goal is to make sure the water supply can be turned off automatically, without internet, if a leak is detected (similar to how YoLink supports this with the D2D functionality of their water valve motor).

@Panda88, Thanks for the help getting this figured out. I purchased the YoLink plugin for the EISY system in the 2nd home and spent a few hours splitting the YoLink devices between the two houses. Everything is functioning properly now. I continue to be impressed by the YoLink wireless reliability (way better than Z-Wave) and have switched all of my water and temperature monitoring over to these devices (about 40 devices at this point). I am anxious for the local control to be finalized. Mike

One more question. Can you explain how the separate credentials work? I went ahead and created a 2nd home in the App but don't see a way to have separate access credentials. The API access credentials seem to be unique to the Account, not to a Home instance. Thanks

I wasn't aware that you could designate more than one home in the app but see that option now. Thanks for pointing this out. Will you still get notified in the App if there is an issue at either home?

I use YoLink devices extensively at 2 homes (temperature and water sensors). I have an ESIY system at each home and duplicate many of the plugins as needed to manage the 2 places separately. UD Mobile supports this quite well but YoLink creates a unique challenge since the Yolink App is unique to a mobile device and everything needs to be under 1 account. I currently only use the YoLink plugin on 1 of my EISY systems to provide local automation (automatically shutoff the water if a leak is detected). Here's the question. Is there any reason why I can't have the YoLink plugin on both EISY systems connected to the same API? I am aware that all of the YoLink devices would show up on both systems but I can programmatically choose which sensors to use with each independent system. Eventually I would like to move to the local API when this becomes available so would need to consider how this impacts the independent systems. Thanks Mike

I did finally get a shade paired with EISY by not following the Bali motorization instructions. As defined in the manual I first deleted all Z-Wave pairing in the shade by pressing the 'program' button for 7 seconds (basically a 'reset' function to delete all previous pairing). I then had to 'exclude' the shade from pairing with the remote using the exclude function in the remote and again pressing the 'program' button on the shade (this is a new step not specified in the Bali manual). Once I did this I could then 'add' the shade to EISY using the Z-Wave 'add' commend. There must be some residual pairing left in the shade even after doing the Z-Wave the 'reset' function in the shade. My guess is the Bali instructions only apply to a shade that has never been included in a Z-Wave network in the past. Unfortunately I had already added all the other shades back to the remote without EISY first being added as the primary controller and didn't have time to go back through all the excluding and including again. As a result I wasn't able to test the functionality of both EISY and the Bali remote being able to control the shades independently. When I have more time I'll go back and try this again as I want the functionality EISY provides in addition to having the Bali remote for control. Mike

I purchased Bali blinds about a year ago and purchased the Bali Z-Wave controller. I was able to pair the blinds with the Bali controller without problems and then paired the blinds with the remote as a secondary controller (associate), again no problems. Over the past year the Bali controller has been a problem and I no longer use it to control the blinds, just the remote. Now the batteries need to be recharged so I decided to try and pair the blinds with my EISY/Z-Wave/Matter and so far am not having any luck getting the shades to pair with EISY. My shades have to pair through a Z-Wave extender (AEOTEC range extender 6) due to the distance from the Matter device. The range extender shows a good connection to the Z-Wave network so I don't believe it is a problem. Is it possible to pair the Bali shades through a range extender (which supports S0/S2 inclusion)? I know that my Schlage locks have to be paired right next to the Matter controller but then work fine through a range extender which has secure inclusion (S2). If I manage to get the shades paired with EISY I'll try to duplicate the problem reported by walkman9999. Mike

Just a quick follow-up on this thread. The failure has not happened again since the original post (No 12th). At this point I think we can close it and I'll start a new thread if it happens again.

I'll have to wait until it happens again and then send the log. Could be a few days. Thanks

I've been having a problem lately where all my Plugins are restarting, sometimes after PG3x restarts, and sometimes without a PG3x restart. When my Elk Plugin restarts it fails to reconnect to my ELK system. I have a number of lights in the house that turn on and off automatically based on ELK zone activity (Stair lights, garage lights, etc). Each time this happens my first indication of the problem is the auto lights are no longer working. When I look in my UD Mobile notifications I can see that all the Plugins have all Connected to PG3x including the Elk Plugin. The fact that all the Plugins are reconnecting seems like a problem in itself but the fact that the ELK Plugin fails to reconnect to the ELK system is the most immediate problem. Each time this happens (twice in the last week) I login into PG3x, restart the Elk Plugin, and everything works again. Any ideas as to what is going wrong? Has anyone else had the problem of all Plugins randomly reconnecting to PG3x? Thanks Mike

Thanks to Andy P for putting this guide together, it was quite helpful. One additional thing I figured out is that on my cell phone the mac id is randomized by default (I have a Samsung phone). This feature can be disabled in the phone settings, with some loss of privacy, and needs to be disabled for the Unifi Presence plugin to work. I don't know if this is an issue with iPhones. Another thing I did is create a Unifi Controller admin login (I have the Dream Machine Pro so the controller is integrated) specifically for the Presence plugin and gave it "view only" rights and "Local Network only" connection capability. No point in giving it more access than is required for the job. Mike

@tazman I started down that path at one point but for some reason changed direction. I'll try putting the buttons in Scenes, all by themselves, and then see if I can control them with the programs. Thanks!

The way I have it implemented now the programs provide the mutual exclusivity when each one executes. This works for everything except for the button LEDs. When I tried including the buttons in the Insteon scenes the lights (the actual lights that are part of the scene) get set correctly but the button LED of the previous scene remains lit when the new scene is activated. For example, let's say there are 2 scenes, each one controlled by a keypad button, one scene is "TV" and the other scene is "Conversation". If the "Conversation" button is pressed the lights in the room get set to level that supports people conversing, playing games, etc. Then the user changes their mind and decides to watch the TV. This requires the lights to be dimmer than conversing so they push the "TV" button. This causes the TVe scene to to be activated, which sets all of the lights in the room to a dimmer or off level, but there are now 2 buttons illuminated on the keypad even though the "conversation" scene is no longer active. When the activity is over the current scene button is pressed again to revert the lights back to there normal behavior. (the actual implementation is far more complicated than this since the "normal" behavior of the lights in this room is controlled by occupancy, time of day, security system armed vs. disarmed, etc). This is another reason for the programs, if a lighting scene is active this overrides the automation of the lights. To get around the mutual exclusivity of the buttons issue I have to press the button for the currently active scene, which turns it off, then press the button for the new scene to turn it on. This is workable but not very family friendly. Hopefully this makes more sense now.

@bhihifi Thanks for the reply. I do use EISY (ISY) for all of my control programming and only use HA as a graphical interface to EISY. With Insteon "scenes" are the way to go for quick responding lighting scene changes and in this case I do have Insteon scenes setup for the different lighting scenes. I need to figure out this mutually exclusive button issue.

I need advice on a 6 button keypad usage scenario. The 2 main buttons are used for triggering a program and are set to mutually exclusive mode, this works fine. Of the other 4 buttons I use 3 to individually trigger programs that control mutually exclusive lighting scenes and this is where I need advice. I know that I could set up individual scenes for the lights, including the buttons but this doesn't work for me since I also control these scenes with Home Assistant which requires that I use programs. The programs also enforce the mutually exclusive requirement for HA and they control variables that affect other program functions. In the Insteon switch setup (I use EISY) there is a dialog where you can make buttons mutually exclusive but this doesn't seem to work. My goal is to only use the 3 buttons as program triggers, with the button LED reflecting which of the 3 different scenes is active. I would also like the button LED to reflect the current lighting scene if initiated by Home Assistant. Is this possible or am I going down the wrong path?