JRissmiller

I see the same thing on my system. I don't recall making any changes for quite some time.

The upgrade packages was the missing piece for me. I also pulled the power on the Ecobee and let it reboot. Following these 2 steps and re-installing the Homekit plugin I as able to get things to work.

Looking good so far - thank you for the hard work on this. My various Temp sensors are correctly reporting humidity again. I haven't check the one motion sensor yet.

@Panda88 I tried to send my logs but I'm not sure they went. I'll try one more time. UD system might be having issues.

The upgrade installed without issue but some of my T\H Sensors are showing humidity is not supported, and the value always shows as 98. It appears the UOM is being set to 25 on the ones that don't work and is 51 on the ones reporting humidity. I have leak sensors, door open\close, and motion sensors and so far these seem to be working. TS_Garage is not working below but TS_CrawSpace is working like before the upgrade. All my sensors worked properly on the old plug-in.

I figured the collective group using the UDI developer pin were probably exceeding the monthly cloud hits. Thought I saw it was 85,000 hits per month.

I've had my Ecobee for several years and it has been very reliable! I really hate cloud based stuff because this is what can happen and with little to no warning. If there is no path forward my next T-Stat will be local API based, possibly a Venstar CT, not sure on Z-Wave. The cloud API is returning 500s, during NS discover, which is not a good sign. https://api.ecobee.com:443 "GET /1/thermostatSummary?json=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 500 None

I ran into the same thing with 32+ devices and if you backup PG you can reverse the changes. There is information in the store warning that this will happen. I figured this is for the best because this plugin is utilizing the new Hue API. The developer is also working on a new plug-in v2.0 that will support the new Hue bridge.

Seamless upgrade for me...took ~10 minutes. I did the SSD upgrade a while back so might explain the speed.

The Ecobee Thermostat can do this with the node server and a program. I have the T-stat set to directly control the Aprilaire humidifier. I typically manually tweak the percent in UD Mobile.

@gzahar Thank you for the assist! Worked for me as well.

I have this lock and it has never relayed status on manual lock\unlock events. I use a YoLink door sensor and when the door closes a program queries the lock in 5 minutes and updates the lock status. If you unlock but don't open\close the door the status will be incorrect. Periodically querying the lock for its status will probably not be good for battery life. Below I unlocked manually and nothing showed up in the logs. I then ran a query, which returned unlocked for the status, and then I clicked lock in the EISY and the results are shown below. The command was successfully executed and the status was changed to locked. Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00161 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00162 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00163 2.0 ] [ZY002_1] Battery Get Sun 05/12/2024 12:01:21 PM : [ZW-DONE 00161 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:22 PM : [D2D EVENT ] Event [ZY002_1] [ST] [0] uom=11 prec=0 Sun 05/12/2024 12:01:22 PM : [ZY002_1 ] ST 0 (uom=11 prec=0) Sun 05/12/2024 12:01:22 PM : [ZW-DONE 00162 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:23 PM : [ZW-DONE 00163 2.0 ] [ZY002_1] Battery Get Sun 05/12/2024 12:01:27 PM : [ZW-TX-A 00164 2.0 ] [ZY002_1] Door Lock Set mode=255 Sun 05/12/2024 12:01:29 PM : [ZW-DONE 00164 2.0 ] [ZY002_1] Door Lock Set mode=255 Sun 05/12/2024 12:01:35 PM : [D2D EVENT ] Event [ZY002_1] [ST] [100] uom=11 prec=0 Sun 05/12/2024 12:01:35 PM : [ZY002_1 ] ST 100 (uom=11 prec=0)

I have the same problem with the BE469ZP. I have a Yolink open/close door sensor and a program that waits 3 minutes after the door status changes to closed to query the lock. I programmed the lock to auto-lock so this updates the lock status and battery level in EISY. Someone else posted this idea in the forum and it's the only thing that works for me. These locks are quite expensive so it's disappointing we can't get status updates from them.

Same here...Thank you!

Same problem as the others and EISY is current on everything. Yo-Link did upgrade to 0.9.63, but is disconnected. I agree Yo-Link and this Node server are great to have.