Javi

Replicated, we are looking into this again.

Server issue corrected.

Replicated 404. We are looking into this now.

Hi @n_sievers, What ihardware (994/Polisy/eisy) are you using? Do you get any error messages from Settings Tab > Systems > Your System, Remote Connection Section > Test Remote Connection? Note that you will need to disable WiFi on your Mobile device if you have Local Connection Settings configured. May be today's weather in Denver 😁

Is the favorite type "Default"?

iOS or Android? We recently updated the iOS Home Screen so the edit button is missing, will try to re-add soon. Once edit button exists the same process below can be used. On Android Home Tab with the system icon visible, click the edit button (pencil icon at top) click the system > Configure > Click Add at the top (in Mapped Values). Set if status equals null, change icon to. Be sure to disable edits when finish by clicking the edit button. See status mappings for full instructions: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Individual_Status_Mappings

Assuming the backup has a Portal account then yes. In the less likely situation where you manually set Local Credentials these will also need to be updated. Local connection settings override default settings, so if you don't recall setting these values, please do not change default values. This can be found in Settings Tab > Systems > Your System > Local Connection Settings.

Credentials are not included in the backup. The easiest way to do this is restore the backup, do this again as you may have changed something that should not have been changed. Go to settings > Accounts then click your account. The app should ask you to login.

Yes at some point....any suggestions?

This process Links 2 or more nodes/programs/etc to a single tile. If a device is not working/communicating this process will not work.

Great, Thanks for everyone's help and patience during rebuilt.

Favorites cell widths fixed in version 1.1.38, will submit by end of day.

Please send me a PM or open a ticket and include the UDM backup file and I will take a look. If using a ticket the file must be zipped before attaching. Someone else sent a backup with the same issue. Will update as soon as I locate the issue.

You could also create your own nodes with python by creating a Python Node Server. See https://docs.isy.io/

May be related. Please let me know if issue persists on 1.1.37

@ShawnW Will bring up in the next meeting.

Great. If needed you can trigger the program (Run Then) to test the notifications. Status values may not be present in the test notification as it was not triggered by status change. To do this click the notification from the list, then click the program icon (Document with chevrons) at the top, then Run Then. If the test notifications do not work please verify the Notification Node Server is at the latest version and is started. Started parameter is displayed in Node Server Information section. Go to Admin > Plugins > Notification.

If the device are scenes, it is fixed in 1.1.37, which has already been submitted for review. This was reported earlier this morning.

There is an update for PG3, pressing force upgrade should update PG3 and minor 5.7.0 bug fixes. Currently UDM doesn't check PG3 version upgrades or minor firmware updates.

Removing the subscribers can be done from both Local and Portal connections. There are APIs but no User Interface outside of UD Mobile. With that said if you can connect to the system this should continue to work with the errors shown above. Assuming the error is "Already Subscribed" or "Max Subscribers" then the system is still online but the Event Stream (real time status update socket) is not working due to too many connections. Removing subscribers from a remote connections should still work when the Event Stream is not working and system is "online" in Portal.

If I recall correctly PG3 version 3.2.4 had a bug, and the only way to fix was firmware upgrade. This may also be the cause of missed notifications. We recommend being on location for firmware upgrades, in case a hard power cycle is needed. However UD Mobile will not stop you from upgrading firmware on a remote connection. If you have access to a PC, the Admin Console can be used with Portal at a remote location. Currently remote access to PG3 can only be done from UD Mobile. However this error will likely prevent the connection.

It could be the connection to UD Mobile if using Local Connection Settings. PG3 may also be a subscriber depending on installed Node Servers. If clients are behaving correctly they should reconnect automatically when the connection is still being used. The sock number will change. If these are the only 2 subscribers then the Already Subscribed error should no longer be present. Are you still encountering errors?

@jkosharek, Submitted to App Store, should be anywhere from a couple hours to a day to go live. Also what is your hardware and firmware? This is needed to generate a report for your other issue.

The issue has been identified by the app, at this time there are no other troubleshooting steps. Reboot usually solves the issue and is easiest. We recently implemented a manual method for testers to disconnect clients, although we don't have enough feedback to verify this solution works long term. If you would like to try the manual method go to Admin Tab >Subscribers > then press the trash icon next to any list item which has "isPortal: no", deleting the "isPortal: yes" entry may require waiting a few minutes for portal reconnection, but is otherwise not harmful. Some connections may reappear shortly after removal which is intended behavior.

Replicated Scenes issue on Favorites, will look into today. The other errors are related to the system. It is usually caused by a misbehaving client, other users have isolated Home Bridge as one of the clients that may malfunction and create too many connections to eisy/Polisy/isy without releasing any of previous connections. Although it is very possible there are other clients which could cause the issue. Please try reboot again if issue still persists as this should reset all connections. Waiit at least 5 minutes before attempting synchronization. If you are using Home Bridge this may need to be disabled.