UD Mobile Icon for Yolink doesn't Update Status

[TJF1960]

Good morning @Panda88, I am running the latest Yolink production in one slot and beta Local Hub Yolink in another. I am seeing in UDM that the icon status for the Yolink plugs does not update when the device changes states. Attached are two screen shots. First pic is of the icon (Yo Plug Tester) properly displaying the status when I opened UDM. Pressing the edge of the icon to turn the device off, does turn the device off but the icon status continues to display the device as being on. The second screenshot is showing the device as off.

This occurs in both versions of beta and production versions.

Thanks!

-Tim

[Panda88]

Does the AC change state - I am not very knowlegdable on UDM - but is AC works I need someone else to give a hint as to what to do on UDM

[TJF1960]

Yes, AC changes state perfectly. The device dashboard in UDM will turn on and off the node switch and properly indicate status changes controlled either with UDM or AC or the Yolink app.

Just an issue with the icon and indicator for the plug node. When you open UDM and go to Yolink and scroll down to the icon, whatever state the node was in when you opened it is what it shows you. But it will not reflect state changes after that.

[Panda88]

can you ask UDI about this. it may be a define somewhere i am missing but i do not know how to fix

[TJF1960]

I had some issues with my plugins playing nice with UDM in the past, something similar to this. I found that I needed to use uom=78 for switch status in order for the icons to properly display. This uom must be also be carried over in the profile files as well for the switch.

I took a quick look and it looks like you are using uom=25. I cant guarantee this is the issue but its worth a try maybe?

@bmercierperhaps you can chime in with your thoughts?

Thanks!

-Tim

[Javi]

Hard to say, I need the first screenshot for both on and off.  If the toggle indicator (circle on the top left) is filled UDM believes the device to be ON, if empty it believes the device to be off.

UDM's calculation of on/off status may be imperfect as not all nodes are the same.  While there are a few exceptions UDM will show the status indicator (empty/filled circle) and allow toggle if there is a Property with the id="ST" and the node supports commands on  (id =DON) and off (id=DOF) commands UDM assumes the Property with the id = "ST" correlates to these commands. 

[Panda88]

I use UOM=25 to support unknow value

 

[Javi]

25 minutes ago, Panda88 said:

I use UOM=25 to support unknow value

 

The UOM should not affect this calculation.  If there are command IDs DON and DOF and a property id "ST", then the app assumes this is a device which supports toggle.  If the ST property has a value greater than zero it assumes on, else assues off.

Based on the screenshots if "Outlet State" has the id "ST", then value 0 is off an 1 is on. So the toggle should work.  Maybe the value was not published quickly enough and user did not see change?

[Panda88]

OK - The issue is ST is used to represent if connected - not on/off for this device 

I guess I can look at changing it but it may cause issues for others

[Javi]

1 hour ago, Panda88 said:

OK - The issue is ST is used to represent if connected - not on/off for this device 

I guess I can look at changing it but it may cause issues for others

Yeah, it is a pain if already released.  There is no great way to identify a toggle, these assumptions worked the best for most devices of all types.  The first version of UDM calculated this differently, If the command with ID="DON" existed and had an init equal to the Primary Property (ST if exists, if not the first listed) UDM would show a toggle.  However cmd init requires a range, so devices without a range did not show a toggle in UDM.   

With that said, I am in the process of a major revamp of the app to replace deprecated APIs and simplify/enhance/speed-up some things. The new app APIs removed the toggle calculation from lower level and is now done at the UI level. So it could change easily when the new APIs are implemented into the Home Tab.  I'm hoping to allow users to change the Primary Property on the Home Tab (like favorites).  So it may be better to use the original calculation first if DON has an init value, and use the existing calculation if DON does not have an init value.  

[TJF1960]

@Panda88, given the hassle involved, and possibly breaking existing installations, If it were up to me, I wouldn't worry about it. Your plugin is and has been working extremely well for everything need. All devices and statuses work great in programs as is.

Thinking about it too, its just as easy, if not easier to just open the yolink app to control the plugs when needed. I am sorry I opened this can of worms.

[Panda88]

I'll keep it in mind next time I change something