BobM99

There are 2 other recent threads about Blink not working.

I've had a UD product for ages and have always been happy with their attentive customer service and the quality of their devices. I've been very appreciative of the supportive environment on this forum and for the very dedicated core of experts who chime in quickly. I recognize that it is very challenging to integrate automation devices that are incompatible and that Blink and other companies appear to have little interest in integrations and playing nice with each other. But more and more I'm wondering how viable this model is. Are there enough people dedicated to maintaining something that needs continual work to make things work, and enough willing to pay hundreds of dollars to do so? I know $10 for a node server is not a lot of money, but if the node server doesn't work, then what? Also, we know there are a lot of alternatives. For example, there are dozens of people working on fixing the Blink integration for Home Assistant, and it appears a solution is coming soon. There are a lot of plusses with eisy, but is that enough?

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.