jamesm007

Excellent, I'll do that. It has happened about 6 times, but three times in the past week. Thanks, James

My eisy has just up and hung randomly lately. It has been very reliable for quite a while. It is running 5.8.4 and has Polyglot 3.2.27. Upon hanging, PG is no longer accessible either. A power plug pull, will get it to restart. When I go to the portal to check it, sometimes it says it is not available. Today the indicator was green, but would not remote reboot it. It always comes back after power cycle, and have lots of backups. Is there a recommended process for a factory reset and restore? Any other ideas? Thanks, James

Just to add, I have been seeing the same issue with status's going to unknown. I have a UniFi UAP-AC-Pro-Gen2, several years old, and I have not had any issues with it. Until I got the ratgdo, and I started getting random changes to unknown. I have a much older Linksys 2700, and moved the ratgdo to that, and no random changes. I have been checking the UniFi UAP-AC-Pro-Gen2 via ssh and uptime, and yes it does randomly reboot, which does cause pain for the ratgdo. All of the other devices seems fine with the outage. Maybe time for an upgrade to the Unifi. Or check the cabling and POE.

Thanks, just did the upgrade, and re-did PIN auth and presto changeo, it is back working! Cheers

Thanks for the info, I thought I was going crazy, I couldn't find much info on it. 👍

I think I upgraded Ecobee to 3.1.5 and to stopped updating. I clicked re-install and no love. I uninstalled, rebooted eisy, and reinstalled still no love. It has been running fine since Jan 2023. I get this continually in the Ecobee log. Thanks 2024-02-11 13:21:22,602 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: User=0021b90262b6_3 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/0021b90262b6_3 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/0021b90262b6_3 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MjE6Yjk6MDI6NjI6YjYiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IldBUk5JTkciLCJ0b2tlbiI6IjNLciZ2dTBncEZBKEt5bHMiLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xOCIsImlzeVZlcnNpb24iOiI1LjguMCIsImVkaXRpb24iOiJTdGFuZGFyZCJ9 2024-02-11 13:21:22,603 MainThread udi_interface INFO __init__:<module>: Loading interface module 2024-02-11 13:21:22,649 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2024-02-11 13:21:23,186 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2024-02-11 13:21:23,424 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2024-02-11 13:21:23,424 MainThread udi_interface INFO __init__:<module>: Loading node module 2024-02-11 13:21:23,425 MainThread udi_interface INFO __init__:<module>: Loading custom module 2024-02-11 13:21:23,425 MainThread udi_interface INFO __init__:<module>: Loading isy module 2024-02-11 13:21:23,425 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2024-02-11 13:21:23,425 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.6 Starting... 2024-02-11 13:21:23,429 MainThread udi_interface ERROR ecobee-poly:<module>: Excption: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b90262b6_3/ecobee-poly.py", line 11, in <module> polyglot = Interface([Controller]) File "/var/polyglot/pg3/ns/0021b90262b6_3/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 253, in __init__ self._mqttc = mqtt.Client(self.id, True) File "/var/polyglot/pg3/ns/0021b90262b6_3/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__ raise ValueError( ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details

The my.isy.io reboot command never returned. Usually back quickly. Did the power pull, and it is back now. The start.jnlp did not work, just an empty IoX Finder. I have deleted all of the old .jnlp's and kept the one you suggested above. I could "Add" it back this time. I guess Finder is not really an auto-discover, but list of registered isy's. Not sure where it keeps the registrations, but it must have wiped them. Never did get the button press procedure to work, but we are back live. Thanks for your advice 👍

Apparently, I have to hit submit! I tried the press the button 6 times. waited, nothing happened. Tried it again 10 min later, still nothing. I will do the isy.io reboot and clear the cache again.

Yep, that works. And I am using a new eisy. But the eisy is not showing in the ISY Finder, but popped up the console anyways. As is shown in the attached pic. Thanks,

Hello, On the weekend, I was in the gui, and did the upgrade all packages as it keeps prompting me. And it mentioned upgrading to 5.5.9 from 5.5.7. I did it, it rebooted. I got in once, and now when I run the IoX Finder, it does not locate it. Everything in the house seems to be running, and if I use the UD Mobile app, it turns things on and off. And my.iso.io sees it, and can reboot it. I did the 4 button press to reset the networking, still the same behaviour. I did the java cache clear, and got the current .jlp from the wiki. Any ideas? Thanks

I was looking at the "Push" Node Server, I should have been looking at the "Notification" Node Server. Way more customizable. The Priority is important for me. Thanks

Bingo, bingo, bingo! I am usually very good at following docs, but apparently I missed that exact step. I think everything is working now, thanks for all of the great help. The node server version is very slick compared to the REST method, but with the REST method, I can specify a priority (like HIGH for water leaks) that are mandatory confirmation to turn off the beeping. Which is great, as I actually had a sewer backup in the basement, and it forced me to get there right now. Cheers!

No, just the Networking Resources in ISY, REST interface to Pushover. Old school. I will investigate the node version now.

Thanks for all the info. It took pulling the power, reboots etc were not enough to get it to Upgrade Modules. Once it came back online, I could do the Upgrade Modules, and now on 5.5.3. And the timezone holds, not off by 4 hours. Woohoo! But under networking, I still cannot use Pushover.net. Email notifications work fine. Many events would call Pushover to notify me about issues, water detection, temperature, movement while away. This was fine for years with the 994i, and I have a valid Network Module License. I get a "Error- Request Failed" and an entry in the log. Not sure if it is a DNS or some other error.

So, not asking to set a static IP, but the networking is not running. eisy cannot reach the outside world. The other fields in the Network Settings group are blank, which is suspicious. This IP (.130) is in the "router", as a reserved address in dhcpd on pfSense, just like the existing 994i. Do other eisy users have their Networks Settings have blank subnet/gateway/dns?