drprm1

Deleted plugin and reinstalled. Back in business.

Router didn’t change anything as far as I can tell. EISY is on a static ip. It’s got to be just not finding the bridge? I removed the static ip for bridge from router, restarted router and it gave hue bridge a new address. I added it as a custom config in the plugin as key = bridges and value [“192.168.242”]…. Still no hook up

My hue bulbs show reachable as “false” in AC. No control at all. Hue bridge shows connected in AC. They show up and function correctly via Hue app. Plugin dashboard and details show connected. Router changed the bridge ip address lately and I changed it to static in my router and put a custom config parameter in plugin configuration to point to new address. AC and firmware both 5.9.1 Tried restarting Hue bridge, router and Plugin a few times. Restarted EISY and now in AC shows that hue bridge is connected but none of the bulbs are populated with any settings

Rebooted and back on. Does “my.isy.io” just show if it is connected to my Eisy? UD mobile notified me that was offline so I assumed that meant the portal was down (like it has been recently). Where exactly would I see that the portal is down as opposed to lost connection? (If there is a way)

Down again?

Didn’t realize this question was in Yolink group. Never thought to use the node variable from the node server… Thanks!

Make a variable to represent the temperature. Make a program to make the variable equal your temperature sensor’s temperature updating every x minutes. Make a program to send an email each day specifying your outdoor temperature sensor’s reading using a substitution variable https://wiki.universal-devices.com/ISY-994i_Series:EMail_and_Networking_Substitution_Variables

From Yolink…… Thank you for contacting Yolink and taking the time to share your concerns with us. We sincerely apologize for the inconvenience caused. As of today, YoLink devices are currently unable to be controlled via Alexa. We've identified this as an issue with the Alexa service, and our team is actively working with Amazon to resolve it as quickly as possible. We sincerely appreciate your patience and understanding.

I figured that since it was updating and responding from AC.

Don’t know if it was turning Zigbee to “on” from “auto” or trying to add it for the seventeenth time but it is now working. Thanks

Noticed none of my Amazon spokens were working with Yolink devices. Can control devices using AC as usual. One of my troubleshooting steps was to unlink from Alexa then relink. When I try to relink and enable it says “Unable to link at this time. Try again later” Tried a few times the last few hours with same results AC and firmware 5.9.1 Pgx 3.3.18 yolink 1.4.15 Thanks!

Got the Sonoff sensor. I can get it to add to AC and it shows two nodes but it doesn’t respond.”Can’t communicate with sensor”… Zigbee is on auto in AC. Tried many times to add, remove, and reboot. Would appreciate any tricks to get it to work.

To clarify. My controller is on a large air compressor which it controls perfectly. It is not on a scheduled daily program for a pool pump which I would consider more critical. I have thought about using one for my pool pump but the timer it has is fine for now. Have no reason to believe it won’t work.

I have had one of these Aeotec controllers going on five years. Solid

Update successful. Took 11 minutes on eisy. Haven’t found any issues yet.

Got 14 put on during a recent support session but not 5.9.1.

Prob dumb question but I already have 14.1 OS, okay to upgrade?

“All in jest and satire - sort of - but also pointing out that the LA area is particularly affected by recent natural and unnatural phenomena, so cut them some slack.” No shit. Cut them some slack

Of course it’s okay to put in next update. Thanks again

YoLink_1-19-2025_94125_AM.zip

Updated and works great (Battery still shows -1 while doorbell state shows 99) 😃 Thanks

Great

Sorry not a developer so not sure what has to go through Amazon cloud. I just assume when I see the correct update number shown that it’s available…Waited a while and not seeing any 1.3.23

So I wait a while to try install again? Not sure I understand what’s going on with “it may take a while to propagate” thx