GTench

Interesting. I see errors when I click on Zwave but not insteon or Yolink or other node servers like weatherflow. Here is what I see in the console

I have the same issue as @sjenkins Not sure if this is exactly what you mean but I opened the nodes screen in eisy.local, selected a non Yolink node (shows properties correctly) then selected a Yolink node (no properties shown) but I do not see any error message Not sure if this is at all related but I notice when I add in a Yolink node server, the Yolink devices show up scattered among all existing nodes in the AC. That is, they are not automatically grouped under a Yolink master node

@bmercier this is what is in my Java Console

Just get a spinning pointer then nothing. The AC does not open at all. The 8443 added manually works with Iox login. The 8443 that was automatically added works with portal login. The 8080 that was added manually just does not work/respond

@bmercier I don't see the popup in the Java console. It just appears over the AC. Also 8080 does not work for me either

I have the same issue as @sjenkins If I login to default connection on AC with portal login, AC loads but I get these messages popping up every 20 seconds or so Creating the manual one works fine with local user name / password

@bmercier thanks. I originally downloaded from the link to my pc but I then thought curl might just be simpler. Since it did not install, I used pscp earlier this morning to copy it from my PC and that worked fine; I had not posted it though.

@bmercierI downloaded the file using curl -s https://universaldevices-my.sharepoint.com/:u:/g/personal/benoit_universal-devices_com/eisyui-0.4.0.pkg -O

@bmerciernow I get eisyui does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable @bmerciermissed this before admin@eisy ~]$ sudo pkg install -f eisyui-0.4.0.pkg Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating FreeBSD-udx repository catalogue... FreeBSD-udx repository is up to date. Updating udi repository catalogue... Fetching meta.conf: 100% 179 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 10 KiB 9.9kB/s 00:01 Processing entries: 100% udi repository update completed. 14 packages processed. All repositories are up to date. pkg: archive_read_open_filename(/usr/home/admin/eisyui-0.4.0.pkg): Unrecognized archive format pkg: No packages available to install matching 'eisyui-0.4.0' have been found in the repositories [admin@eisy ~]$ sudo service eisyui restart

@bmercier thanks. I downloaded it but get "insufficient privileges" when I try to install it. Gary

Yes, I will wait for the hub too.

Upgraded eisy without any issues. Everything is working well. I liked the status updates from UD Mobile. Good work guys. Gary

Just did the IoX upgrade to 5.9.1. Went very well. I noticed that the upgrade to yolink 1.4.15 happened automatically as well. This upgrade would not take before unless I did a delete and reinstall. Gary

@apostolakisl Not sure if this will help but this is how I check for armed status: https://forum.universal-devices.com/topic/41305-installed-and-working-but-couple-items/#findComment-367200

oops...I spoke too soon. I had not disabled by program that does a rediscover when a disconnect occurs. Just did test again and this time no automatic reconnect occurred. Still need to do a rediscover

@bpwwer the automatic reconnect works well for me now. Did a blue iris update which shuts it down, installs updates, then restarts it. The AC showed node server to remain connected through out the process. The AC server status went to disconnected then back to green when blue iris restarted after the update install. Thanks again for this. Gary

still won't update to 1.2.7

@bpwwer thanks that installed ok. will test later

Tried a Delete and Reinstall but still shows disconnected

@ericmaas I experienced a similar problem but with random lights coming on (with older insteon modules since newer ones do not seem to respond to all on commands). Mine were triggered by DSC motion sensors which activated lights using programs when motion occurred. I believe the motion detectors were triggering too often creating collisions sometimes. I have restructured my programs to minimize the ONs being sent which has so far I believe been helpful. I had originally tried including the motion detectors as controllers in scenes but this did not work as I could not restrict them to only sending ON and not OFF commands Gary

@bpwwer I just installed that version by doing an update. It says version 2.0.4 but it says disconnected. A restart or start did not help. Should I delete and reinstall? Gary

@bpwwer don't know if this will help but I did a test where I stopped Blue Iris then restarted it. I attached the log file. Not sure if your message is there or not. Watching the AC blue iris screen, I noticed that the Server Status went to from Green to Disconnected after about 10 to 20 seconds or more. My program noticed this and after 1 minute the program did a rediscover. I noticed that the AC showed server status as green then went to disconnected than back to green 8 times and I got 8 emails saying it was reconnected. After that it stayed in the green state. Here is the program that I use to check for a disconnected state: Blue Iris Disconnected - [ID 002C][Parent 0001] If 'Blue Iris' Server Status is Disconnected Or 'Blue Iris' Server Status is Red Then Wait 1 minute Send Notification to 'Gary' content 'Blue Iris Disconnected' Set 'Blue Iris' Re-Discover Else - No Actions - (To add one, press 'Action') Here is the program that checks for reconnection: Blue Iris Reconnected - [ID 0052][Parent 0001] If 'Blue Iris' Server Status is Green Then Send Notification to 'Gary' content 'Blue Iris Node Server Reconnected' Else - No Actions - (To add one, press 'Action') Here is a screen shot of the connected server: BlueIris_11-15-2024_24248_PM.zip

I also noticed that the node server did not automatically reconnect but since the rediscover button now works, I use a program to do a rediscover if the node server becomes disconnected. I put a 1 minute wait in the program to allow the blue iris update process to complete Gary

@Guy Lavoie very interesting. Having used the Ocelot and Leopard myself to control my X10 network in the 90s had often made me wonder about IoX's program execution order Gary

@bpwwer Many thanks for doing this. Update did not work for me. I had to delete then reinstall to get your new version. I restarted IoX and the blue iris entry was there but I had to restart the plugin before it displayed a server status (green) I then updated blue iris to its latest version which forces it to shut down and restart. IoX plugin status then showed disconnected. I waited for a few minutes (maybe not long enough?) but no automatic reconnect, then clicked on the rediscover button in IoX. The plugin status then showed green. This was good because I can now hopefully use a program to do a rediscover if the plugin becomes disconnected. The rediscover button in IoX did not work for me in the older blue iris plugin. thanks Again Gary