Javi

Hi @MWareman, May be awhile before we can get to these due to our new hardware release. Added issue: https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/36 If on Android this is already possible using one of the notification channels. Basically use one of the sounds as your channel and set "Override Do Not Disturb" to true. You can also change the sound if needed in the same Android settings. Long press app Icon > select info ("i" inside circle) > Notifications > Click on one of the sound channels. Added issue: https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/37

Settings Tab > Backup. Issue: https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/77

Hi @tmorse305, If the issue can be replicated after app is swiped from recents, which will clear database queue, it should be easy to fix. Just PM me a copy of the database file. If it can not be replicated, I'll try to see if anything after edits could cause this.

They should be in GC format, I have not had time to add parameters for an individual code so please see @apostolakisl great writeup on how to add learned codes as a single device.

https://globalcache.zendesk.com/hc/en-us/articles/360026433572-iLearn-Supported-Learners https://globalcache.zendesk.com/hc/en-us/articles/360034920131-iLearn-Learning-Basics For the iTach its next to the power input at the bottom, for iTach flex on the top. It has been sometime since I have used iLearn, but I don't remember it having need for module or connector, I think you might be using the program/setting for thier larger equipment which accepts IR receivers as a module.

At this time UD Mobile can not replace any of these user interfaces, so they will likely be around for some time. The issue with web interfaces is permissions requirements and hardware access which has become difficult/impossible, especially with Apple devices. So, while I don't make the decisions, I think native mobile applications will be needed to ask users/apple for permissions and access hardware features. Example: During onboarding we need to find the ISY on your local network. We need both permission from both Apple and the user. While some of this could be done from the web, it is becoming more difficult with some other permissions impossible to obtain.

It is defined in firmware and on our list to fix. I believe UD Mobile is the first application to use the INIT values as intended so we only noticed the issue when Widgets where implemented. Using INIT values allows Node Server to have the same functionality without UD Mobile hard coding values for each Node Server.

I should work, there is a small hole on the device which is the built in learning receiver. Although it may be easier to download the codeset from the GC Control Tower database if available. See this for Control Tower setup:

Windows subsystem for Android only available on windows 11 on most devices, but is hardware dependent. The app currently works with Android emulators, such as Bluestacks, on Windows 10 if your device has specs required.

Hi @mapeter, Will add this to our wiki soon, but having image upload issues. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Missing_Widget A widget requires both a status value and a command linked to a status value. Not all commands are linked to a status value by default, however users may be able to change a command parameter within UD Mobile to allow widgets. Open the Node's Dashboard and locate the status and command which should be linked. In the image below the "Status" value is not clickable, but we want it to be linked to the "On" command. If the command has 3 dots to the right of the command select the 3 dots, if not select the command. Note that the command must accept a range of value (i.e. 0 - 100) to be linked to a status. Click the edit (pencil) icon at the top of the Editor Range Dialog. If the "INIT" (initialize) value is missing click the "INIT" section. Note that if this value is not empty synchronizing UD Mobile will return this value to its default state, if the value is empty the new value will persist during synchronization. Click the Status value which should be linked to the selected command. In the screenshot below the Status value is named "Status". The "INIT" value should now show the selected Status Value. Backout to the Node's Dashboard. The status value is now clickable and will accept Widgets.

We hope to have UD Mobile ready for Windows 11 late this year or early next year. Already available for M1 Macs. https://developer.amazon.com/apps-and-games/blogs/2022/10/appstore-on-windows11-developer-preview?cmp=US_2022_010_ESM_Windows11-DevPreview&ch=eml&chlast=eml&pub=esm&publast=esm&type=org&typelast=org

If following migration for ISY backup/restore, then you just need to point the app to the new system. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Migration

There is a fire icon in "Weather Icons", other alarm icons in security icons. We can add any icons from https://fonts.google.com/icons?icon.style=Rounded (used filled, rounded) by request. Add requests as issues on github with URL of icon from fonts.google. Issues: https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues

Some Z-Wave devices only report battery level at certain intervals or situations, many of these only have a few values they will report such as 100%, 90%, 80%, ect. . MFGs known to have this behavior are Eco link and Monoprice but I'm assuming others may have the same behavior given that many components may come from the same MFG. Some of the devices will resend this value if a switch triggered, such as the tamper alarm. So if ISY is rebooted and the device has not updated it's battery value, then the value will be empty. I ran a reboot test on some of these devices along with viewing traffic and there was no commands that would query the battery level, with the exception of node recreation. The devices which have switch, such as tamper, which updates the battery level all populate as expected. So, at this point this appears to be a limitation of some z-wave devices....maybe a parameter exists to change this behavior, but it would be MFG specific.

These devices are 700 series so there could be compatible issues, although I have not seen this on other devices. There was a firmware bump that caused battery level to be displayed as it's own node. Has an exclusion then inclusion been tried? This may result in the battery node being added.

Hi @JSylvia007, With regards to zwave: Is your firmware 5.0.16 or greater? Most of the zwave battery status values are present I the 5.x firmware. 5.0.16 is supported by all 994 hardware. Depending on your zwave hardware you can upgrade it a higher firmware version. With regards to firmware: While we continue support for older hardware, there is a point when hardware can't support firmware. This is true for 994 and the zwave 300 series board (for which we offed an upgrade to 500 for many years). To be honest, at this point there is no reason to offer upgraded 500 zwave modules as the zwave protocol has advanced beyond 500 and you would be purchasing obsolete hardware. Our current integrations require more processing power than available with 994. With regards to Polisy and Eisy (easy) for larryllix: Our newest firmware supports both platforms.

Please open a ticket for help with diagnostic. We also have an app, UD Mobile, which works with ISY Portal and may show a better error message if there is a connection error.

Hi all, Subscription 404 errors, and Network resource 404 errors may not be related. We had some technical issues with Portal over the weekend which causes 404 errors. If the network resources executes but shows a 404 in app it is likely related to timeout or invalid response from the server which the Network Resource is trying to connect. Try increasing timeout.

Hi @PGHBubba, Currently Android and iOS backups are not compatible with each other. We do plan to correct this in the future.

It is possible to install and run on 5.x and 4.x using the same PLM, although you may have to attach the PLM to the new ISY for brief periods. It has been some years since I moved my production system to 5.x, so I don't recall the exact procedure, even worked with zwave using shift primary although more complicated. Upgrade new equipment to the highest supported firmware. Backup your current system, power down, and unplug PLM. Move PLM to new equipment, verify new equipment is on the latest version, restore backup to new equipment. You may now see program errors. If needed power up and check your old ISY for references. I was able to switch the PLM between the 4.x and 5.x ISYs and they both would function normally. Z-Wave is the hardest part and was the reason I did a test run. I believe once you move the backup file over with the same PLM you will likely be fully migrated and not need to go back to the old ISY.

Hi @Blackbird, Yes it's possible using customization. See:

Thanks @Jimbo.Automates!. Yes, hide and/or show a better error in UD Mobile. Added issue to tracker https://github.com/UniversalDevicesInc/UD-Mobile-iOS/issues/68

Thanks @dbuss, The Node Server contains a command that is only available on Polisy. Can you please send me a copy of the UD Mobile backup file so I can see the profile causing the issue? @Jimbo.Automates, is the command with a _sys_notify_short editor in the Elk Node Server important for operation? I'm wondering if we hide the entire accepts-command for 994 or just the accepts-command-parameter (if optional) when this situation is encountered. Notes: NodeDefAcceptsParam.class. iOS line 208.

Hi @dbuss, Is this on ISY or Polisy? If on ISY this is a call specific to ISY on Polisy for Node Servers. If running on ISY does the app sill function after error is dismissed? If on Polisy, I think there are no System Editors Defined so we will need to fix on the app side.

Are the nodes in the Admin Console? No: Check PG3 for connection errors. Yes: Did you reboot ISY before sync?