Javi

Got it, its a bug.

If you already upgraded you don't need to press force upgrade.

I think it is related to downloaded icons. The views are "Recycled" (an app thing to reuse views and save resources) and looking at the code it does not appear that the app checks if the download is still valid, it was at one point but must have been removed during an update. When color is changed on a downloaded icon (which does not have an alpha layer) then it will cause the entire icon (i.e. red square) to be filled with the color, so that explains the red square. As for there already being value. Are these all for the same Node? Custom Mapped values are related to a Node Property not a Favorite. So if a Custom Mapped value is added it will be on both the Home tab an the favorites tab.

Thanks. I see you have multiple favorites screens. Does this only happen on this screen or screens which have a a tile with an icon populated by a URL?

Does the Tile's Status show "On"? Edit: Notes: Based on the image of percentage I assume the Editor is incorrect. The editor only supports 0 and 100. So if there are any values in between the Node Server developer needs to use the correct editor to show all possible values to the user. Or The user needs to change the Mapping to >= 1

Nothing has changed in UD Mobile. iOS allows .local for local loads, if bug is fixed in firmware then .local should still work. I should have been more clear in my post, ATS was in regards to .lan

Hi @tmorse305, Thanks, here is prefered. About 90+ percent of Test Flight feedback in useless, so I don't check often. Most feedback is anonymous user saying "not working" or "having trouble" without any other context. I'll have to look into this as Apple States the Matter developer profile is not needed in production, but it appears iOS is not allowing Matter commissioning to start in production. I did not test this as my devices already have a developer profile.

App Transport Security is Apples security layer, so Apple has deemed this unsafe. https://wiki.universal-devices.com/index.php?title=UD_Mobile#App_Transport_Security_(ATS)_iOS

Looks like a bug, will try to review this week

Thanks, it is an error in the Node Server. Range is missing min/max or subset values. The node server developer will need to correct this. <editor id="ONOFF"> <range uom="78"/> </editor>

Hi @apostolakisl, apologies for delay. Please provide response to http://ipaddress:8080/rest/profiles/family/10/profile/6/download/editor/editors.xml

What number slot does the node server reside?

Thanks, this is not an open git project so I can't see the definition files. So will need a few requests to see if the issue is with the node server or UDM. First post the response to the following and let me know the node server's slot http://ipaddress:8080/rest/profiles/family/10/files

Not yet

http://ipaddress:8080 then the path i.e. /rest/history/etc

Currently users need to create a UDM backup and import onto the other device.

The error is likely due to missing definitions in the node server, or updated values which have not been synchronized to UDM. First try synchronization. If that does not fix the issue what is the Node Server?

If anyone encounters this please post a screenshot so we can locate the error. My guess is there is a user setting causing the error message.

If I recall the locks need to be factory reset then you MUST enter one of the default entry codes into the keypad. Upon entry of a default code the lock will extend the deadbolt then retract the deadbolt. After this is done use UD Mobile to scan the QR code. Failure to do this resulted in failed attempt to add the lock. UD Mobile's Zwave implementation needs updating so may be a good idea to also have the Admin Console open to verify lock had been added before canceling (finishing) setup in UD Mobile.

Check out the custom toggle example. A favorite which shows one node as status and executes a program (or node command) when pressed. Search the forum, Others have posted about setup of the same the same. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

My guess is the tabs being at the top (Apple API) is causing a calculation issue with the bottom. I'll take a look at both issues when I get some time.

Do any of the devices in the scene also change status? Try disabling the calculations for all devices in UDM then add back one at a time. This only affects UD Mobile's calculation, has no effect to eisy.

See the custom toggle example https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle In short the Display Node and the Command do not need to be related, but the command should cause the Display Node to change. The command should be a Program Run IF so it holds all logic related to the toggle.

Some routers and/or operating systems do not support dot local (.local) addresse, so you may need to use the numerical IP Address is this is the case. PG3 can be accessed from http to avoid warning, so change https to http with the numerical IP Address, you still need to append the port i.e. :3000 so http://ipAddress:3000 If the finder shows a isy.io address this was saved by the user, as it cannot "find" remote controllers. You can also manually add the local IP Address to finder with http://IpAddress:8080/desc

my.isy.io is a remote location, you need to use the local IP Address. Or simply try http://eisy.local:3000