Javi

Can you both verify you have the latest version of the iOS app 1.0.6? Then verify the network is NOT (very important) in your phones saved networks, if it is forget the network. Finally try wifi setup again, be sure to double press the front power button when prompted to put eisy in WiFi configuration mode. Troubleshooting: https://wiki.universal-devices.com/index.php?title=UD_Mobile#eisy_WiFi_Configuration

We have had few reports on Android of there being a space after the username or password. It may be caused by auto fill. The next version of the app will trim whitespace from the username field.

Fixed in 1.0.6 Apple shows this as live in production, not yet in beta 🤷‍♂️

The Node server replaces the connector value. Same with repeat value. Why: The control tower database has "1" in for all codes. So this allows the user to copy the entire codeset and not have to manually change the connector value.

Hi @awysocki, Can you or have you tried to include the device from the Admin Console? It is very possible there is a bug in the app. If that does not work please open a ticket and include the log so it gets routed to the correct people. Thanks

Confirmed the empty space is not saved in iOS, will try to fix in the next version

Variable values are not requested at startup by default. See Settings-Tab > Systems > Your System > Program and variable settings. Also I use android and just noticed iOS favorites variables have a bug. Let me know if does not work and I'll get it fixed in the next release.

Fixed scene order in next release for iOS, was already sorted in Android. In the mapped value "Set Formatted Value" change to the word "On" or if you don't want it to display a value set it to an empty space " ". 😊

Hopefully soon, I'll have to look into why M1 is not exporting changed values...based on your post in the other thread.

A "Status only Folder" would be a good addition and it is on my list. However it does not solve the root issue of folder status. In the past I have recommended using a scene as the Folder Display node and having all lights in the folder as part of a scene. In this example all devices are responders so the scene will not trigger other lights when a physical switch is touched at the same time allowing UD Mobile to toggle on/off. In my observations of the Status folder, it was usually used much as you describe, to see if anything is ON. So having the ability to toggle the scene OFF makes it easy to turn everything off without opening the folder. The app tries to avoid calculations/groupings which can be done by IoX. This saves us time in mobile development and saves time/processing resources (database insertion, value calculations) in UD Mobile when the app first connects to ISY. With that said, it is currently possible to have IoX do these calculations/groupings to achieve what you desire without the modifications to UD Mobile. (A) A folder with a scene as the display node will have a toggle. (B) A folder with a variable as the display node will not have a toggle. Finally you can use the custom mappings to change colors/value-names for both scenes and variables. With regards to option (B) a variable can be used to track status of devices in ISY using a program to make the calculation, variables do not have a toggle option in UD Mobile so only variable status will be shown. IoX program would be if any light is on set variable is 1 else set variable is 0. Then map the value 1 to "On" and value 0 to "Off". Geek out: As an example of time/processing resources: Scenes do not have a status, so every time the app receives a status value it needs to query the scene relationship table, then calculate a new percentage of all related scenes, then insert the new scene value. On my main system scene calculations doubled the time it takes for the app to display all initial status values on cold start. This is mostly due to the SQL queue having many insertions queued. So scene relationship queries must wait in queue, thus delaying the next value insertion. Last time I ran a test with/without scene calculations without was ~2.5 seconds and with was ~5 seconds until the last value was displayed.

I would not recommend opening a port even with a valid cert, not to mention the cost (time/money) of cert management is likely much higher than ISY Portal. The next best method would be to get a router which supports VPN which would allow "remote" connections. Most mid/high end routers already have this functionality.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#Program_And_Variable_Settings Enable in Settings-Tab > Systems > Your System > Program and Variable Settings.

Beta 1.0.2 Added sync for ZMatter. Added Z-Wave Smart start scan for ZMatter. Added basic include exclude for Z-Wave ZMatter

Beta 1.0.3 Added sync for ZMatter. Added Z-Wave Smart start scan for ZMatter. Added basic include exclude for Z-Wave ZMatter

At least the ZWave part of ZMatter is family 12, not sure about Matter. Most of the legacy Zwave paths (i.e rest/zwave/xxx are migrated to zmatter path. (i.e rest/zmatter/zwave/xxxx) so rest/nodes and rest/nodes/xxx remain the same

Hi @shbatm, https://wiki.universal-devices.com/index.php?title=Polisy_Developers:ZMatter:ZWave:Events https://wiki.universal-devices.com/index.php?title=Polisy_Developers:ZMatter:ZWave:REST

Version 1.0 Major Authorization and onboarding upgrades. Created new Synchronization view, will now prompt to backup before database cleaning. Rebuild many sync functions. Rebuild Location Permission Requests. Rebuild Wifi Network View. Rebuild Reboot Views. Bug Fixes.

Thanks will take a look later this week.

Thanks. Just to be sure I understand "their revised positions do not survive a quit/relaunch" I have a few more questions. Was this on M1? Most testing is on iOS so very possible it is a compatibility issue. Was the edit mode stopped before relaunch? Are the positions correct after stopping edit mode? Stopping edit mode should trigger screen refresh. Also when I replicated I noticed a few things that may allow a work around. The rapid scrolling could only be replicated when moving item and scrolling at the same time. So as a possible work around, until fixed, can you move items to a position on screen, then scroll and move to desired position? If the behavior of your setup is not the same please send me a PM with a copy of the App's backup file which has the error?

Hi @chris.com, Issue replicated added to our issue tracker. But I think the backup revised positions maybe another issue. Very improbable the backup is corrupt. Can you verify both the M1 and iOS device have the same version number? Basically a backup cannot be restored to a lower version number. https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/80

Hi @zmarty, UD Mobile ZMatter integration is not yet completed, but we are working on this now. https://forum.universal-devices.com/topic/39417-issues-creating-widget-for-z-wave-device-added-via-zmatter-board-in-polisy/?do=findComment&comment=353885

Hi @mbking, Thanks for the report. I'm still working on ZMatter support for UD Mobile. On my list after Android eisy onboarding. Hopefully before eisy release date. This is the error on the second screenshot. The synchronization error appears to show the standard Z-Wave definition files are not available but the System is reporting that the module is available. I'll need to check with the team to find the root cause. Do you still or did you ever have devices on the standard Z-Wave module (i.e. Zooz)?

Hi @Deane Johnson, I think there may have been more than one issue and some confusion with the apps prompts, but the direct firmware upgrade is going to be the biggest issue as it is destructive and likely wiped the Z-Wave links. Given the age or your ISY your Z-Wave module likely only supports firmware versions upto 5.0.16. Downgrading with saved state will not work without a viable backup. Do do make a backup before doing the direct firmware upgrade or any have backups that have most of your configuration? If you have a viable backup you could reinstall a 4.x firmware version then import you backup file. This may restore your programs. However depending on the state of the Z-Wave module you may be required to exclude then include your Z-Wave devices, then edit your programs with the new Z-Wave device addresses. This may be equally difficult as installing firmware 5.0.16, importing backup, then doing the same for Z-Wave devices/programs. Unfortunately If you do not have a viable backup, then the system will need to be rebuilt. Installing version 5.0.16 would be the best option before rebuild.

Hi @Deane Johnson, I'm the developer of UD Mobile and guarantee the app can not perform a firmware update. The Firmware Update required confirmation dialog does not have a function, only closes the dialog upon acknowledgment. UD does not provide an automatic update of any 5.x firmware for ISY994, not in app or Admin Console. If your ISY is showing 5.3.0 it was shipped with that version or firmware was installed manually. If 5.x firmware was installed manually from the Admin console and your system has a Z-Wave module the firmware is dependent on the Z-Wave module version. Firmware 5.0.16 for 300 series and 5.3.4 for 500 series Z-Wave Module. So at this point if you are 100% sure you have never downloaded and installed you are having another issue. If you did download and install it's possible you installed firmware incompatible with your Z-Wave hardware. Please let us know the zwave module version, see the link below to help identify. Also do you have a backup? If you do and assuming you did not rename the file, what is the file name? This should include firmware and timestamp. https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions

@Deane Johnson, I read your initial post am a little confused as to how the firmware was updated. The 5.x firmware update is a manual update and requires manual intervention by the user. UD Mobile currently does not have the ability update firmware on your behalf. So if you did not update manually your firmware has not changed.