BobM99

Yes, and I get this:

Hi all, Please see the prior post about Blink not working with Home Assistant because of 2FA. It looks like a fix is in the works for HA, though. It's doesn't look like it's working on eisy, either. Anyone else besides @slimypizza and me with this problem? If so, any fix possible? Thanks. Bob

It seems that 2FA has broken the Blink integration on Home Assistant. I'm looking at Blink on eisy now, and the "Arm Status" doesn't look like it's updating properly. Is anyone else using Blink noticing a problem? Github thread on HA integration: GitHubBlink setup and login failing (Known API issue) · Issue #...The problem on restart of HA the blink integration fails to load - first noticed today at 20:00 after an Ha restart. Also on my production instance the core blink integration fails to reload What v...

And getting this when looking for nodes....

Hi, I'd also like to thank you for all your work with this. Regarding-- "By request I changed behavior of ST and added a GV30 variable to all nodes - GV30 is the existing ST (mostly if node is online) - Changed ST to show the most relevant parameter of the node - this is to support udiMobile status icons (they trigger of ST parameter) - I hope that it is not too big a problem as some code may need to be updated if programs tests for online status" --when I sync with UD Mobile I do get errors: 0. Notify Node Server Dev!!! Status name is missing for : ST. Node Server Instance: 11 1. Notify Node Server Dev!!! Status name is missing for: nlshub. Node Server Instance: 11 I have no idea what this means or if it's related.

Thanks for the response. Looking forward to it.

Hi, I attached what I get back below. I'm not savvy enough to use sudo pkg commands. I've tried "Upgrade Packages" and nothing seems to have been upgraded beyond this. Thanks. Bob ---------------------------------------- *** OS *** FreeBSD eisy 14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 #4 releng/14.1-n267727-74b6c983723c-dirty: Fri Nov 15 12:13:25 PST 2024 root@bsdev14.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64 *** Package Information *** ************ UDX ************ udx-3.9.0_9 Name : udx Version : 3.9.0_9 Installed on : Thu Jul 24 21:03:49 2025 EDT Origin : misc/udx Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc --------------------------------------

I don't see a major upgrade yet. Am I missing something? Thanks. Bob

Same here: "eisy.local refused to connect." Can connect to this, though: https://eisy.local:8443/WEB/sysconfig.txt Windows 11, Chrome browser, no VPN.

Belkin, maker of Wemo products, announced it is no longer supporting Wemo as of 1/31/2026. This is a shame. The Wemo plugin has worked flawlessly. "After careful consideration, we have made the difficult decision to end technical support for older Wemo products, effective January 31, 2026. After this date, several Wemo products will no longer be controllable through the Wemo app. Any features that rely on cloud connectivity, including remote access and voice assistant integrations, will no longer work. " https://www.belkin.com/support-article/?articleNum=335419

And now it's up again

That does the trick. Thanks!

Hi, Maybe once an hour is plenty. It would be triggered by detecting a power draw from the pump--I was thinking if a certain amount of wattage is detected. This sounds similar to how you use the plug for your dryer, but the difference is that the pump goes off every few minutes at times.

I appreciate any help and ideas. I have a backup sump pump in place in case the primary one fails. I hooked up a YoLink plug that monitors energy usage to the backup sump pump, and I'm using the YoLink nodeserver. I think I can figure out how to send a message when the backup sump pump goes off, but how do I write a program that won't trigger every single time the pump fires? Thanks. Bob

Coincidence, I had a blackout today. PLM/X-10 wasn't responding, and this advice worked. Thanks!

Many great answers here. Thanks to all! Bob

Hi, follow up from the recent UD message that AT&T is ending email-to-text alerts soon. Right now I use this to send eisy alerts my wife. What is a good alternative, preferably that doesn't involve her installing UD Mobile? She has an iPhone. Also, I'm not the most gifted eisy user. Thanks. Bob

@Rocketron Should see something like this at the top (before upgrade it said 13.1 instead of 14.1): *** OS *** FreeBSD eisy 14.1-RELEASE-p6 FreeBSD 14.1-RELEASE-p6 #4 releng/14.1-n267727-74b6c983723c-dirty: Fri Nov 15 12:13:25 PST 2024 root@bsdev14.isy.io:/usr/obj/usr/src/amd64.amd64/sys/eisy amd64 *** Package Information ***

Looking for advice, please. Can't get 4 nodes to restart: Wemo, Nest, Sonos and Blink. Tried multiple reboots, restart node attempts. Thanks. Follow up: I restored Polygot V3 from the backup file and it's all working again. I didn't see this mentioned in the prior posts. If it was, sorry.

Thanks very much

I've read the documentation for this plugin, but forgive me as I'm nowhere near the level of most of you. I have a GE Cync wall switch that I'd like to program using eisy. The switch can be controlled by Alexa. Is that an example of what this plugin is for? Thanks. Bob

Thanks for the advice, as always!

If I'm selling or giving away an ISY994i and do a factory reset, will the 500 series Z-Wave dongle I installed still be recognized? I'm guessing it won't unless I go back and update the version to 5.0.13. Any suggestions for how to handle this? Thanks. Bob

I had this problem when I changed eisy from wired to Wifi connection. Changing it back to a wired connection fixed the problem

Yes, this problem seems to have started when I performed an update. I did mention this UD support. Maybe a doctor should listen to his patient..... Anyway, is there way to roll this back? Thanks for helping to make the likely connection