dbwarner5

@UD2)17rrh If the Plug-in is installed and running, and nothing is showing in the AC, then we need to start with checking to see if the PI has the light bulbs and is connecting to your Hue Hub first. Open PGX and then hit Details on the Hue. Then hit Nodes. Is there anything listed? You should see all of your bulbs AND your Hue Hub. Is just the Hub showing? and if so does it say for the State (ST) a value of 1 for true. See below. If not, then it hasn't connected with your hub correctly. Here are the instructions from the README for the HUE. Once installed - push the button on the Hue Bridge and add NodeServer into Polyglot, that will allow it to pair with the Bridge. Sometimes automatic bridge IP address discovery fails, in that case - you can specify Bridge IP address in a custom parameter ip for the NodeServer using Polyglot's frontend interface. Notes Poly assumes that Bridge IP address never change, so it is recommended that you create an IP address reservation for the Hue Bridge on your router. If you do see your hub but no lights, or if your Hub is not connected, then you may want to uninstall the Plug-in and then re-install it and try again. Follow any prompts upon installation to press the Hue button. However if you DO SEE your lights and hub listed then it's a problem between the PGX and EISY and linking into the AC. If that is the case, be sure to close your AC, then go to the HUE log in PGX and change it DEBUG and then stop the Plugin and then restart it. Open up the AC and see if it shows. If not, download the log and post it. As a side note, in the AC, everything will be grouped under the Hue Hub. So be sure to expand it to look for your lights. You can right click and ungroup them if that is the case and they will show in the tree. An easy way to look for your Hue hub is to click on MyLighting and then click on the column labeled Address. Then scroll down to the node server number. In my case below it's loaded in slot 3 so it is easy to find that way.

so you still have the home wifi in the home controller settings for local connections, and then the cabin wifi in the cabin controller so you will still have local connections there. yes. that was what I was trying to get you to. thanks for the update

So tha means that when you are home, you are actually using hte remote connection vs the local connection since it doesn't recognize you home network since you deleted it? Am not sure what the proper fix / set up is since I dont have two homes with Eisy to test, but ideally, you would want both local networks in UDM and it should know depending on which Controller you select, which network is to be considered the Local network that corresponds to the selected controller, thereby connecting you locally if possible, or remotely otherwise. @Javi seems like once you load a Local connection into UDM, you should be then asked to "link" it to a controller and then have UDM do the logic to use the Local connection or remote connection depending on which local network I am connected to and which controller I chose, this house or the second house.

How do you look at the xml file?

Agree. Thst is why it worked again once in”updated” a line and then re-saved it. am more concerned about the WHY and are other programs also corrupted and how to find them. thanks

Not really sure it’s a motion sensor issue. as I noted: the motion sensor is turning on and off as expected. I can watch it in UDM But the program doesn’t trigger because the eisy thinks the lights are on even though it’s reporting off and is physically off as shown in my screenshots but will change the battery next time it happens

Simple motion detector program turns on my office lights. Have had this program running for >8 years. Suddenly yesterday and today, it's not working. Yesterday I picked any line of the program, hit update and then save and all went back to normal. today, after it working fine for several hours, it suddenly stopped again... after the lights were auto turned off for lack of motion. Program one: Office Motion On - [ID 0122][Parent 0132] If From Sunrise - 1 hour To 9:30:00PM (same day) And ( 'MD Office' is switched On ) And ( 'Office Desk' Status is Off Or 'Office Cans' Status is Off ) Then Set 'Office' Fast On Program two: Office Motion Off - [ID 0176][Parent 0132] If 'MD Office' Status is Off And ( 'Office Cans' Status is not Off Or 'Office Desk' Status is not Off ) Then Wait 10 minutes Set 'Office' Off Wait 1 second Set 'Office' Off Notice that the second program is running its THEN right now, even though the lights are off. And that the EISY knows the lights are off: Strange. If you comment, please dont comment on the programs, or other ways or better ways to do it. This set up works and works just fine. The EISY is not reading the data correctly. That seems to be the issue. I can see the MD getting triggered But program one reads this as FALSE, because it thinks the lights are on. Then when the MD goes to OFF, program two turns true, because again, the EISY thinks the lights are on. The lights are not on. I just did this again..<"I picked any line of the program, hit update and then save and all went back to normal. "> and BAMM.. they work just fine again. Is the EIsy corrupting itself?

In UDM.. go to Settings, scroll down to controller, click on your controller you want to manage, then scroll down you will see two sections; Remote Connections Settings and Local Connection Settings. You local settings are picking up your local network at home and therefore can't connect to the remote cabin. So for your remote setting you should have the long https://my.isy.io/isy/<long string> that you copy and pasted from the Portal. That is working as expected and why when on cellar you can connect to your cabin. For you local settings you will have http://eisy.local. The problem is that the cabin is NOT on your local network. UDM is picking up your house network and thinks you are local and tries to make the connection as http://eisy.local, but with all the wrong controller information, so its trying to actually connect to your house eisy but with the wrong credentials. This probably because under the next section System Network Relations: you have your house network as the local network under the cabins controller. Delete that and the next time you are at you cabin, add the cabins's local network to this section. I think it should work after that.

@GXW While it's true what is pointed out above, you should expect more than 10 minutes of connection. Something else is going on. Have you tried loading the AC with a direct connection versus with the launcher? Go to you browser and type in http://<your eisy ip>:8080/admin.jnlp This should download an Admin file to your computer. click on this link and it should take you directly to the sign in for your eisy on your LAN. This will at lease eliminate Internet connections as an issue.

@slimypizza @Guy Lavoie I am not sure what the latest is. Mine shows 14.1, but I have been working with Michel K on some longer term problem solving, so I know he updated my system at one point to test out some changes. But if @Eby Creek is also on 14.1, then you may want to run Upgrade Packages from the AC (after doing a backup).

@paulbates @coinserv Another easy way to see al your current versions of the imbedded software components is to type this into a browser. https://<local IP address of Eisy>:8443/WEB/sysconfig.txt On the top line, it will tell you the OS system version, and then below all the package components of that system.

@Javi Group name. Yes, but the old names are the ones showing up in the AC, not the new names which are in UDM.

Thanks @Javi. My apologies, I think you said that above or in the help section. Some challenges still: It took a few times to get the group to show up. But I did not see our "individual " phones so assumed I needed a group of "one" for each of them. Set that up. Was able to get all three groups to show in the AC after sync, plug in restart, and then AC. However, I then tried to change the names of the two individual phone names. I cant seem to get these to the AC. When I restarted the Plug in again, these showed in the Info log: WARNING Controller:write_profile: Waiting for Service ISYPortal UDM Notiications to initialize, timeout in 1 seconds... 2024-12-29 23:01:24.868 Thread-9 (node_queue) udi_interface ERROR Controller:write_profile: Node Service ISYPortal UDM Notiications failed to initialize init_st=None I then tried to delete them and go this message after the delete confirmation., Any thoughts? thanks! LOVE THE CONTINUED GROWTH OF UDM!

@Javi Thanks Javi.. I was not aware of that. I went into UDM and cleaned up my devices, and also added a group. I then did a sync with the controller.. .....however when I opened up the AC, nothing shows up under Notification Controller / UD Mobile except default. Did I miss something? thanks. UPDATE.. I received an ERROR on UDM: "An SSL error has occurred and a secure connection to the server cannot be made"

@abartello If you use the Notifications plug in with Pushover on the phones, you can specify which phone it goes to, but its a bit more complex as it requires setting up Pushover and adding that plug in.

I tried to add my own network at the bottom of config: 192.168.68.255. and it still wont find anything while under wifi.

I seem to have just remembered that there may be an issue of the EISY being on wifi and this plugin.. I will hook the eisy back up to an ethernet later today and try it then.

@Jimbo.Automates Here is the latest log after the latest restart. Kasa_12-28-2024_123554_PM.zip it seems to be looking at the wrong network. My network is 192.168.68.xx 024-12-28 12:35:08.289 Thread-9 (handler_start) udi_interface INFO Controller:discover: enter: 172.26.18.255 2024-12-28 12:35:18.291 Thread-10 (run_forever) udi_interface INFO Controller:_discover: Discover.discover(172.26.18.255) done: checking for previously known devices 2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:discover: No manual networks configured 2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:discover: exit 2024-12-28 12:35:18.291 Thread-9 (handler_start) udi_interface INFO Controller:add_manual_devices: No manual devices configured 2024-12-28 12:35:18.292 Thread-9 (handler_start) udi_interface INFO Controller:handler_start: exit Kasa Controller

@Jimbo.Automates seems like the KASA plugin stopped recognizing the plugs under the parent. (EP40) The parent plug shows and I can turn it on and off, but it does nothing to the actual plugs. I first deleted the "children" and stopped / restarted the plugin.. It did not re-discover them as it did above. Tried several times. I then deleted the parent (by hitting the x in the plug in on PGX) and restarted. Now it wont find the parent either. I increased the time out to 30 seconds, still no change. The last line in each restart under the INFO log is: 2024-12-28 11:48:45.829 Thread-10 (handler_start) udi_interface ERROR Controller:handler_start: discover failed I then found the local IP address of the plug parent and added that manually in config. Restarted PI. It found the parent and the children and had the correct state for each. But I could not control the children. Then the plug in seemed to have gotten caught up in a loop and I had an error "high traffic" whenever I tried to do anything. Could not restart, quit or delete the PI. Had to reboot the EISY. Upon Eisy reboot, again it found one of the plug parents and children and reported the correct state, but no control and no reflection of changes that I make thru the kasa app etc. Restarted the plug in... it went back into a loop again. Was able to get it to stop so didnt need to reboot EISY this time. Deleted the manual IP. Restarted. Again it found one parent with correct states, but no control of parent or children. Deleted the PI. Reloaded it into the same slot. Now it isnt finding any of my KASA devices; only node is the controller. Any ideas? Thanks

Is the Eisy on the latest version?

Are you using hte yolinnk plugin? Yolink devices wont show in EISY or the AC as they use their own proprietary long range signal. The plug in is the "interface". You also need a YoLink hub.. Maybe stating the obvious here, but just trying to clarify where to start with trouble shooting.

After upgrading to 15.2 I was having problems getting connected locally to the AC. Did all the usual steps: cleared Java, updated Java, redownloaded launcher from UDI, redownloaded local Admin from Eisy. But it would not connect, even after following Mac OS's new Security process for opening downloaded java files --> After trying to open the file, Mac will ask you to move it to the trash or cancel. Instead, go to system settings, Privacy and security and scroll down. After attempting to open it, you will see the file named and the option to open it. Click here and you will again get a warning dialogue that you can click thru to open Finally went to Java control panel under system settings and under the Temporary Internet Files / View, a new box opens up. Here I double clicked on IoX Launcher and I received a new Mac dialogue box asking if I want to give permission for local access. Clicked Yes, and all is working again. FYI for anyone else struggling as this may help.

My Eisy uses the serial out to an ethernet which then runs ~50 to the basement from the second floor to the PLM. Works fine.

try typing this into a web browser... http://<LAN IP>:8080/admin.jnlp this should download a local copy of admin.jnlp which will link to the AC and will give you direct access to the sign in screen. Otherwise, try adding http://<LAN IP>:8080 to the UD Finder and see if it finds it locally.

I was able to get my camera feeds to work after a lot of trials.. but not Ring cameras. This is the path I finally used for local monitoring of my IP cameras, changing the last number in the hundreds digit. (201, 301, 401 etc) rtsp://<Username>:<Password>@192.168.68.101:554/Streaming/channels/301