Seems to be ok. The temperature sensor info looks good, including the date/time.

I installed the .50 update this morning and immediately when from 18 nodes to 43. So far everything looks back to normal. Thank you for the fix.

SS

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.

Updated version to 1.8.51 - Fixed a needed correction factor for certain water meters - should report correct now (not 10x)

Updated to 1.8.51.

In UD Mobile and from what I can tell, all my door sensors, leak sensors, motion sensors, vibration sensors, and garage door sensors are all showing status as 0 or 1 with a couple showing 99. Program firing is erratic. In plug in dashboard the number of nodes increased with seven new nodes which are all labeled as “schedule”.

Just checked AC and all the statuses are correct showing normal so it’s only in UD mobile.Maybe just how UD mobile interprets and displays the one/zero status.

Not sure if related but none of my Zwave devices show any status and can’t be controlled by AC. This started after update….

Rebooted Eisy a few times with no help.

Thanks

Edited May 12May 12 by drprm1

Log file is here

YoLink_5-12-2026_70006_AM.zip

On 5/9/2026 at 2:43 PM, Panda88 said:

released version 1.8.50 - minor bug fixes

Thanks for the update. At first glance, my temp sensors now all seem to work correctly. The Flex Switches also appear to work, but the status of the additional two button controllers appears as unknown in the Admin Console. I can live with that, as I don't really use that function, but if you'd like to fully support that just let me know and I'm happy to assist with logs, testing, and whatever else might be needed. Heck - message me your shipping address and I'll have Amazon send one to you to test with just to say thanks for the great community support!

Edited May 13May 13 by dwengrovitz

I think it is expected that the 2 swithes start as unknown - there should be 2 sub nodes (one per botton) - The bottons are like the remote, where you can assign a short press to generate DON (switch on) DOF (Switch off) DFON (fast switch on) DFOF and toggle (DON/DOF) or (DFON/DFOF)

Once you press the key it should update from unknown

If that is not the case send me a log with debug enabled and where you press the two keys with short press and long press and I'll see what I can do - if that does not work I may take you up on the Amazon offer :-)

17 hours ago, drprm1 said:

Updated to 1.8.51.

In UD Mobile and from what I can tell, all my door sensors, leak sensors, motion sensors, vibration sensors, and garage door sensors are all showing status as 0 or 1 with a couple showing 99. Program firing is erratic. In plug in dashboard the number of nodes increased with seven new nodes which are all labeled as “schedule”.

Just checked AC and all the statuses are correct showing normal so it’s only in UD mobile.Maybe just how UD mobile interprets and displays the one/zero status.

Not sure if related but none of my Zwave devices show any status and can’t be controlled by AC. This started after update….

Rebooted Eisy a few times with no help.

Thanks

udimobile has stricter rules for the node definitions than AC. I need to find a bug somewhere - I do see it on my side as well (Not a big user of UDImobile so I did not check) Do you know how to run the java console and see if there an any warnings when you start AC.

Also, did you check if there is an update to PG3 (from the AC)

Edited May 13May 13 by Panda88

6 hours ago, Panda88 said:

udimobile has stricter rules for the node definitions than AC. I need to find a bug somewhere - I do see it on my side as well (Not a big user of UDImobile so I did not check) Do you know how to run the java console and see if there an any warnings when you start AC.

Also, did you check if there is an update to PG3 (from the AC)

I updated everything and reinstalled Yolink plugin with no change.

I mentioned that my programs using Yolink sensors weren’t firing. I appears that it is only programs using Yolink motion sensors which are evaluated using “control”. If I change this to “status” the program runs. In scenes where the Yolink device is the controller nothing happens either. (Door sensors work fine in this capacity) I can see in the AC that the status is changing just not responding correctly to “control” in the if statement….(Way over my head as to why)

Appreciate the help!

Edited Wednesday at 01:30 PM5 days by drprm1

Yes - I can see this in your log the node reports it does not know the trigger commands to scenes.

I do not see this in other logs which is strange,

Could you try an thing - try to back up system, delete the node , reinstall it and restore the backup

I also need to look at linking - it seems to be needed for zigbee/zwave, but I have never needed to use it before - maybe something has changed

2 hours ago, Panda88 said:

Yes - I can see this in your log the node reports it does not know the trigger commands to scenes.

I do not see this in other logs which is strange,

Could you try an thing - try to back up system, delete the node , reinstall it and restore the backup

I also need to look at linking - it seems to be needed for zigbee/zwave, but I have never needed to use it before - maybe something has changed

Did all that you suggested unfortunately no change

(Don’t know why none of my Zwave devices were functional after the update but after a few hours they have all come back on line and are functional now.)

Edited Wednesday at 09:52 PM5 days by drprm1

17 hours ago, Panda88 said:

Once you press the key it should update from unknown

A short press on each of the buttons did indeed update the status from Unknown to ON (DON). I'll experiment a bit more with that function, but it looks like the issues I was seeing are now resolved, thanks again! Still happy to send you a Flex Switch if you want one. :-)

10 hours ago, drprm1 said:

Did all that you suggested unfortunately no change

(Don’t know why none of my Zwave devices were functional after the update but after a few hours they have all come back on line and are functional now.)

There are 5 of your door sensors that do not register the DON/DOF (triggers for scenes or actions) - others do not have this issue - You can see what they are if you look in nodes in pg3 interface

Line 5763: 2026-05-12 01:43:43.741 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e752f command DOF not defined

Line 5764: 2026-05-12 01:43:43.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e735a command DOF not defined

Line 7098: 2026-05-12 02:16:54.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000a41c7 command DOF not defined

Line 7099: 2026-05-12 02:16:54.824 Command udi_interface.node ERROR node:runCmd: node 8b4c04000354c2 command DOF not defined

Line 9269: 2026-05-12 02:40:37.239 Command udi_interface.node ERROR node:runCmd: node 8b4c0200013692 command DOF not defined

Is there anything unique about them? It must be coming from PG3 as other door sensors are using the same code and work well - Is this related to the zwave devices not working - e.g. are these doorsensors paired with ZWave in scenes or similar?

4 hours ago, drprm1 said:

Did all that you suggested unfortunately no change

37 minutes ago, Panda88 said:

There are 5 of your door sensors that do not register the DON/DOF (triggers for scenes or actions) - others do not have this issue - You can see what they are if you look in nodes in pg3 interface

Line 5763: 2026-05-12 01:43:43.741 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e752f command DOF not defined

Line 5764: 2026-05-12 01:43:43.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000e735a command DOF not defined

Line 7098: 2026-05-12 02:16:54.781 Command udi_interface.node ERROR node:runCmd: node 8b4c01000a41c7 command DOF not defined

Line 7099: 2026-05-12 02:16:54.824 Command udi_interface.node ERROR node:runCmd: node 8b4c04000354c2 command DOF not defined

Line 9269: 2026-05-12 02:40:37.239 Command udi_interface.node ERROR node:runCmd: node 8b4c0200013692 command DOF not defined

Is there anything unique about them? It must be coming from PG3 as other door sensors are using the same code and work well - Is this related to the zwave devices not working - e.g. are these doorsensors paired with ZWave in scenes or similar?

I’ve tried to see what is different and why these aren’t working. All these devices look like they have their command settings set to ON ONLY. All the programs they are in look for “if control X is switched on” then the programs are ran….These are also all motion sensors

Problem is I have one motion sensor whose program works correctly. 🤷🏻

Edit: I changed a couple of the motion sensors command settings to ON/OFF and they appear to be working correctly….I’ll send a new log later if it will help you pick up any differences.

Thanks again!

Edited Thursday at 05:03 AM5 days by drprm1

I have contacted UDI to see if they have any idea

11 minutes ago, Panda88 said:

I have contacted UDI to see if they have any idea

Appreciate all your help. I have over 60 Yolink devices and they work great. Last year replaced all my Insteon motion sensors with Yolink in an effort to quell the occasional ALL ON episode which still affects my older Insteon switches.Hope this gets resolved as one of my new motion sensors controls lights on some steps I frequent in the night….before I break my neck. 😂

Edited Thursday at 06:03 AM5 days by drprm1

Working to get some help - Have other experienced this

One temporary solution should be to use status (not control) of the motion sensor in a program to trigger your scenes - I assume that would work - from the log I can see status changing - adds a small delay but not significant

Tried changing the programs to status yesterday and programs still didn’t respond so changed back to control. This morning I changed all my motion sensors command to ON/OFF and everything is working for the time being.

Let me know if/when you need to test

Again appreciate the help

Can you send me another log with it working - it may help identify the issue

23 minutes ago, Panda88 said:

Can you send me another log with it working - it may help identify the issue

Here's the log.

Also just curious as to why the number of nodes showing on dashboard went up, in my case, by nearly ten?

YoLink_5-14-2026_24829_PM.zip

Edited Thursday at 07:52 PM4 days by drprm1

Most likely it is the schedules - yolink operated schedules are now separate child nodes (I did not look at log yet)

2 minutes ago, Panda88 said:

Most likely it is the schedules - yolink operated schedules are now separate child nodes (I did not look at log yet)

That’s it. Thanks

1.8.56 released

Minor bug fixes. Water meter measure was off for some meters (correction factor) and old thermostat issue. Was trying to fix the UDmobile issue with labels not showing, but it is believed to be a known issue with current udx release, so hopefully it will get fixed with an upcoming release of this

Does anyone have issues with scenes not triggering from sensors? One user has this issue, but I cannot reproduce it here. May be the same udx issue mentioned above (but less sure about this one)

Edited 12 hours ago12 hr by Panda88

Hey @Panda88, I just set up a Yolink plug as responder in a scene, and it worked perfectly. However, when i set it up as a controller, it would not control. It would respond though.

I did the tests on .56 by the way.

.56 fixed most issues with UDM. Everything now populates and is very responsive. Excellent work! And Thank You!!!

-Tim