Saturday at 04:18 PM4 days Not big issue but it seems that devices that report on/off status are reporting “0 or 1” in UD Mobile and “Internal Server Error” in Eisy-ui. Other devices reporting normally.Remember seeing this a while back.😀
Saturday at 05:27 PM4 days Can you give a device example and ideally a log with debug. I had to change stuff to get eisy-ui working better so it is likely a minor bug that is easy to fix
Saturday at 05:54 PM4 days Author 20 minutes ago, Panda88 said:Can you give a device example and ideally a log with debug. I had to change stuff to get eisy-ui working better so it is likely a minor bug that is easy to fix YoLink-log-2026-11-14T17-53-06.802Z.zip
Saturday at 09:00 PM4 days Author 8 minutes ago, Panda88 said:give 1,.8.80 a spinWorking as it should! (Can’t believe I had to wait an entire hour for you to fix this 😂🤣😂)Thanks!
Saturday at 11:19 PM4 days Author Must’ve put the curse on you….Im on 1.8.80 and status is correct but I’m back to programs and scenes not firing with motion sensors and door sensors. Like before the status changes in the app, UDMOBILE, and Eisy-ui. YoLink-last-two-hours.zip
Sunday at 12:42 AM4 days Author Programs not firing with either. I have some programs using control and some using status. Also like before variables aren’t updating. Edited Sunday at 01:08 AM4 days by drprm1
Sunday at 12:48 AM4 days Author 4 minutes ago, drprm1 said:Programs not firing with either. I have some programs using control and some using status.Looking further it seems that some of the devices which were controllers in a scene are now missing from the scene???
Sunday at 02:12 PM3 days FYI: This is usually caused by a Unit of Measure (UOM) mismatch, or a node being removed then added again.The former (UOM) check the Program Export JSON for the UOM number, then check the Event Log for the UOM, if they differ vars/triggers will not fire. Requires latest staging build.For the latter (program deleted then recreated). a restart is needed, or reload all programs /rest/programs/reload (or reboot). Endpoint, may also require latest staging build.
Sunday at 03:06 PM3 days Author 14 hours ago, Panda88 said:I am not home now. Need to look at log. Did you try a rebootMostly door sensors. MS now appear to be working correctly except not working when variable updated.Just verified that after update door sensors were missing from scenes that they were controlling. Added them back and now working. Only thing now is variables not updating.YoLink-log-2026-11-15T15-04-23.650Z.zip Edited Sunday at 07:18 PM3 days by drprm1
Sunday at 08:08 PM3 days Just to understand the issue better - are the affected sensors part of scenes - this is the only issue I can see in log - the issues seems to be the sensor does not handle commands to be set off when it is the controller - I'll try to address thatIf this is not the case, can you do a log with event and let me know the rough time where the wrong / missing operation occurs, so I can indentify it in the log. Also - if seems you are querying/polling every 10 min - it should not be needed - the nodes update then selves when things change 5 hours ago, Javi said:FYI: This is usually caused by a Unit of Measure (UOM) mismatch, or a node being removed then added again.The former (UOM) check the Program Export JSON for the UOM number, then check the Event Log for the UOM, if they differ vars/triggers will not fire. Requires latest staging build.For the latter (program deleted then recreated). a restart is needed, or reload all programs /rest/programs/reload (or reboot). Endpoint, may also require latest staging build.Can the UOM issue you mention be caused but editor with multiple UOMs? Eg. switching from value to uom25?
Sunday at 08:18 PM3 days Author 4 minutes ago, Panda88 said:Just to understand the issue better - are the affected sensors part of scenes - this is the only issue I can see in log - the issues seems to be the sensor does not handle commands to be set off when it is the controller - I'll try to address thatIf this is not the case, can you do a log with event and let me know the rough time where the wrong / missing operation occurs, so I can indentify it in the log.Also - if seems you are querying/polling every 10 min - it should not be needed - the nodes update then selves when things changeCan the UOM issue you mention be caused but editor with multiple UOMs? Eg. switching from value to uom25?Right now all I could discern is that my door sensors were no longer in scenes where they were controlling scene responders. I have added them back and they are now working. I also noticed one temp sensor didn’t change a variable when it should have. I need to look at this more so I’m good for now.It just took me a while to realize the door sensors were missing from scenes.What you suggest for short and long polls?
Sunday at 08:27 PM3 days I am using 30 min for short poll an 1 hour for long polls - I think 1 hour is the shortest report time for sensors with no activity I did find an issue with the scenes, and I am following Jari's suggestion not to have mismatched uom - it can happen when a node does not send data - I'll change it so data remain but time is not updated so last valid measurement time is shown.
Monday at 03:11 PM2 days 18 hours ago, Panda88 said:Can the UOM issue you mention be caused but editor with multiple UOMs? Eg. switching from value to uom25?If the user selects the wrong UOM to set the variable in the program. AND/ORThe plugin does not set the uom on every property update. This is especially important if using multiple UOMs, as the default may not be what is expected. e.g. property is usually UOM 51, but also has UOM 25 for errors, property updates are sent with value only assuming they will be UOM 51, but udi_interface sets the default as the other UOM, 25.AND/ORA mismatch between the UOMs in the editor and the UOM used to publish the property update. e.g. NodeDef.Property.Editor.Range List has UOM 51 but the status updates contain uom 56. The user has a program that stets a var for the property and selects (or default if one uom) "51". The variable is never populated as the property updates arrive as 56.
Create an account or sign in to comment