Javi

It's likely an error with the node server, but could be an app issue. Is this PG2 or PG3? Have you tried synchronization? Is the node server updated to the latest version?

Added issue to fix Service Notification text and click listener https://github.com/UniversalDevicesInc/UD-Mobile-Android/issues/33

Try Settings-Tab > Portal Accounts > Your Account. It should prompt for login. Will look into automatic prompt for login.

On our list but no ETA: Favorites of type "Command" will execute the command. Favorites of type folder will launch to that folder. Status can not be updated in a timely manner, so any favorites which rely on status will simply open to that nodes dashboard. I may be able to get the intents in sooner, which would allow tasker to launch/execute commands. Covered in your other topic https://forum.universal-devices.com/topic/37092-notification-sounds-submit-your-request/?do=findComment&comment=349042 Currently possible using Custom Mappings, create one entry and select the lowest (i.e. off) value with "Greater Than or Equal To".

UD Mobile Settings. This is an Android service which keeps the connection alive. The Android Service Notification must be shown so users are aware the App is using resources in the background or Android will drop the network connection. This helps the app keep status value current and avoid startup delays when the user leaves the app or screen turns off during the specified duration. I believe the default duration is 1 minute. This should be displayed but should not popup. Is this not the case?

Maybe in the future on Android, but not iOS. This is low on my priority list as Android users already have this ability with notification channels. On Android you can change the sound for any channel (the defined sound files). Long press the app icon, click info (encircled "i") > Notifications > Select a channel (sound file) > Sound.

Apple has "Potential fix identified - For a future OS update". Not sure when it will be implemented.

Restore PLM not yet available on Mobile. Also recommend this is done on site for battery powered devices. My guess is it is a defective PLM, link loss and status loss starts happening before compete failure. Sometimes PLM power cycle fixes the issue, but when we need to do it frequently the PLM usually fails completely within a year. I have a few test systems running and had a few extra PLMs in 2020. I estimate my PLM failure rate to be 20% before a year and over 30% before two years. Most of the defective PLMs were tossed with the assumption we could purchase another, so it's hard to say if a cap replacement fixes the issues.

From AC > Node Servers > Configure > Node Server Name > Delete.....may take a few minutes for PG3 to refresh.

Hi @SteveT, Verified the issue with iOS 16+ and posted to the Apple Developer Forums. https://developer.apple.com/forums/thread/716416

This may help others: Just updated to 3.1.10 from Admin Console>Configuration>Polisy_System_Settings>Upgrade_Packages. Upgrade duration was about 18 minutes Do not interrupt until all lights stop blinking. After upgrade PG3 was restarted from ipAddress:3000 System>Restart_Polyglot_3. After restart PG3 could not find ISY and none were listed. Performed System>Restart_Polyglot_3 again and PG3 started as normal.

@jwagner010, iOS version 0.9.6 should allow widgets for devices without initialization values by linking an INIT Status.

Beta 0.9.6 Added Editor Range Span and Node Def Accepts Param Editor. Fixed SQL error during Favorites Save. Fixed position restoration for Favorites Folders with many items. Workaround for missing INIT values not allowing widgets. How to add an INIT Value (see Android instructions)

0.169 Added user modifications for Node Def Accepts Param Values. This allows users to add INIT values to link a status and a command. Workaround for missing INIT values not allowing widgets. How to add an INIT Value: Go to the Node's Dashboard for the Node which has a status value and command which are related but not known to the app. Note that "Status" item is NOT clickable and the "ON" Command has a parameter option (three dot) menu. Click the (three dot) menu next to the "ON" Command. Click the Command Parameter Edit Button: The INIT value should be empty. If not empty the command is already associated with a Status value. Click the INIT Section. Select the Status Value that should be associated with the parameter. Note selecting a Status value which does not match the command will show widgets but values will not be correct. If a value is entered by mistake click the delete button to clear. Now the Status value is clickable and will work with widgets. Note that "Status" IS clickable as indicated by the chevron on the right.

Hi @tmorse305, Thanks for the report. Fixed in next version. 875937a Fixed incorrect list reference Thanks for checking. Let me know if you see it again.

Beta 0.9.5 Added pause to screen refresh during/after move. Added Widgets as Favorite Type.

I'll have to add an edit screen, similar to the edit screen for missing step values. Chris is going to try to add missing INIT for Z-Wave, I'll let him know about non-dimming KPLs also. The latter option is firmware related, so not sure when Chris will get to it or which firmware will get the update (i.e. not sure 994i will be corrected). Does the same happen from the Node's Dashboard when clicking the fan "Status"? Does the same happen for another device type, i.e. a dimmable light? Being as I cannot replicate and it's happening for multiple FanLinks, I'm wondering if there is a program "correcting" the value based on another condition.

Hi @Jimbo.Automates, Thanks! On my list, but on the lower end. That's how Insteon is done on 5.x. Maybe add both UOMs as editor>range values. That would prevent breaking current setups. Changing the UOM will affect existing users with this CMD in programs. Depending on the number of user affected it may be better to only have one UOM (editor range). I'm not quite sure how the app will handle a multiple UOM situation, so adjustments will need to be made on the app side and may require users to select/change the UOM (not sure if that is desirable). Multiple UOMs is rare, so currently for widgets the app requests the first editor>range in the database (not as listed on the profile). Looks like the CMD (DON) parameter does not have an INIT value for non-dimming KPLs (also not clickable from the Node's Dashboard). I think we are going to allow users to add the INIT value for CMD>Parameters to fix devices missing INIT values. https://forum.universal-devices.com/topic/38489-all-on-versus-fast-on/?do=findComment&comment=348235 Could not replicate in 0.168. Does this happen with all devices or only this Fanlink? I've had Fanlinks get out of sync before so it's possible the Fanlink is malfunctioning. Usually power cycle of the Fanlink from the breaker box or ISY reboot fixes the issue, does not happen frequently so I don't remember which action fixed status reporting.

Try Power Cycle. Possible that subscriptions are hanging.

Beta 0.167 0.167 Added pause to screen refresh during/after favorites move. Added Widgets as Favorite Type.

Thanks @jwagner010, Updates: The All-On and All-Off commands are depreciated. With regards to widgets, it does not appear to be safe to make these assumptions without causing errors. I think we could allow user specified commands for a given status which would allow widgets for this situation. I've also requested that we reevaluate some of the Z-Wave definitions to for command init.

Hi @SteveT, I'll have to setup a separate instance of xCode to test this, so it could be awhile before time permits. It does not appear UIDocumentPickerViewController.forExporting has changed so likely an iOS bug.

Hi @jwagner010, At a lower level both questions are related to how the device is defined by the ISY. So I'll ask somebody who is more familiar with definition creation to see if we can get a better answer. I have a similar Z-Wave device on a test system, so I assume the definitions are the same. When you press the parameter button (three dots) next to the "On" Command is a percentage range of 0-100 shown or only "0%" and "100%"? With regards to the widgets, they are only available to status values which are linked to a command (i.e. clickable). This device does not appear to have such a link. I suspect the reason is because the Status and On-Command have different ranges, where Status also has an additional unknown value. (Status: Off/On/Unknown or 0/100/101) (Command-On: 0%, 100% or 0/100). I'll have to ask about this and and report back. There is a bug (or "feature" 😊) in the app which shows the toggle indicator on the home/favorites tab for this device. There are no reports of this bug causing issues and it appears to work, so maybe the app can (1) assume the link should exist or (2) allow users to specify the link. Depending on the answers I get, I can make a better judgment on how to proceed with the bug/feature. I suspect @lilyoyo1 is correct about the All-On and All-Off commands, but am not familiar enough to say with any certainty at this point. I'll have to ask about this also.

First be sure both devices have the latest app version. Regarding multiple portal accounts. When clicking Settings (gear icon) on the Notification tab are you presented with a list of portal accounts? If prompted to pick portal account continue, else the other accounts are not linked to your Mobile Device and must be added in settings tab > Portal Accounts. The devices should be added automatically to the list, can you verify if the API keys are the same (the last 4 or 5 characters should be enough to differentiate)? Devices on the same account should have the same API key, Devices on Sub-Accounts or different accounts will have different API Keys. At one point there was a bug which required each user had to click the notification tab at least once before the device was added to Portal, but I think this was fixed. If the API keys were checked on both devices for equality, this should have satisfied this requirement. If this bug still exists please let us know and we will try to find the issue.

Hi @auger66, It should work for all users on the same account, it is tied to the ISY portal account linked to the app. Are the other users sub accounts? All available devices are listed when clicking the settings (gear) icon at the top of the Notifications tab. See the devices section. Edit: This is a newer feature so it's possible there is a bug. Please let us know if devices are not listed and we can work with you to find the issue.