atmarosi

I would try turning off any stateful inspection you might have for the EISY via the PAN (Palo Alto). We're a PAN shop at work - and I know it will scrutinize traffic very much and sometimes tooo much. Since it's is unable to reach the internet it likely doesn't send the traffic out to the portal (guessing). So that would explain why when it's unable to ping the internet it stops trying to connect to the portal and not showing any traffic as well. Since you can't reach the internet from the EISY - it obviously won't reach the UD Portal. Assuming you don't have similar issues with other devices on the network I would see how the traffic is any different - different rules? Different path? etc. I'm leaning towards the PAN getting in the way....

Maybe ssh into said eisy and run a ping out to the UD portal and see if maybe the path that it’s taking is troubled? Is the eisy connected to a different switch maybe or AP than your phone or other things?

https://shop.insteon.com/products/led-flicker-glow-eliminator?srsltid=AfmBOopOitXjjLRMMOtmR6bSOykiQ4h5NGuyzQY4OngE1IH9zowHPqHB try these

Instructions seem to be using the same reset button: Further I don't see any mention of any other orifice:

Are you still on a ISY994? Resetting Your ISY - Universal Devices, Inc. Wiki As long as you don't hit the 30second factory reset I don't see how you would...

Check this? https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Resetting_Your_Userid/Password

Wired Polisy here. Upgrade went without issue. Took about 20 minutes.

Motion sensors

I would monitor the ping to the IR device and see if it’s not happy with the new WiFi. If that shows signs of 100% reliability then look at the way the IoX device is reaching the device and see if you can setup a monitor by running a query to the global cache NS maybe and put a THEN to notify you of its failure? Might be able to use that to troubleshoot the WiFi link to the IR device.

Wish I had something to suggest. If no one else does there is always a ticket with UDI.

Tried a reboot of the EISY yet? 🤞

First for everything. Nice

That should match the number of fans you have…. Seems like you need to retry pairing the fan units to the bond first

Under advanced it’ll show “Devices Associated” - is that actually showing all the devices? What kind of Bond hub is it?

I don’t see a SwitchBot (SB) node server plugin currently - but you should be able to use Network Resources and their API if you have a SB hub: https://github.com/OpenWonderLabs/SwitchBotAPI

Alternatively you can get a Bond hub - assuming the fan will work with it. Then assuming you have PG3 already setup use the Bond Hub NS, and then integrate with your insteon network that way.

Is the current switch Insteon? If so you can get a wireless remote and link the two into a scene. https://shop.insteon.com/collections/remotes?srsltid=AfmBOop4wmso7kusQzSJamCFxA8FhcVu7K3NZ-R1LP2OsGy-R_sQAgUL

I get that error sometimes when I input the address in the name field; and name in the address field. Sounds rudimentary - but did you make sure you got the right data in the right field? Also, I never select the device type and let it auto-detect. Any diag output from the event viewer on level three when you try to add it you could include? I know I can't decipher it but others on here typically can; worse case - support ticket.

In the bond app click on the bond pro under my bonds: see IMG910 At the bottom hit advanced: see IMG913 local token should be the second field: see IMG912

Need to get the ISY “stuff” into HA. Then HA will see the status. Then you can setup control of the govee lights based off the ISY statuses in HA.

To Be or Not to Be? - Universal Devices - News (universal-devices.com)

It has a full API. Network resources on the ISY side for each ON/OFF. Bob’s your uncle.

I use a Din IV Relay by digital loggers

Think you have to disable before you can delete.

Found this - could use an Alexa (assuming you have one) to output the sound (mp3 of whatever):