Javi

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.

Thanks for the report, I'm submitting version 1.1.36 now which should correct most of the issues. Note that Favorites have been completely rebuilt to accommodate custom views so some things may be slightly different.

Ok, looking into this also. Hope to have a release by end of day.

Great. Currently Image only tiles adjust image size based on tile size. So if the Image tile is on the same line as a larger tile it may be larger then images on a line with smaller tiles. I'll need to think about this. Please send me a private message with a copy of the app backup using the URL provided which does not work. As of now I can not replicate using the same URL, so there may be something in the Favorites configuration causing the issue.

Great Favorites no longer honors the phones text size setting as this setting caused the scaling issues in previous versions (iOS issue, no way to work around). The text should adjust automatically to fit the tile size. While not yet implemented we plan to allow users the option to select the tile height which should allow for larger text. Replicated Program and Variable status not updating on Favorites. Please let me know if the issue persists in 1.1.36. If issue persists in 1.1.36, which it likely will, I may need a copy of the app backup to replicate.

If this is for Programs or variables it may be broken in the latest (1.1.35) release. I'm looking into this now. If this is not the case please post a screenshot of the Mapped Values list for the node. The mapped values list can be found by clicking the edit button (pencil icon at top), then clicking the node, then clicking Configure (advanced Status Color/Value/Icon Configuration).

http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4 The URL above does not work? While the tiles on Favorites Tiles changed the Node's Dashboard (accessed from the Home Tab) did not. So if cameras were working then they should still work from the Home Tab as nothing changed. If they do not work from the Home Tab then there may be an issue with the URL or connection (VPN, IP Address, etc.)

Favorite Tiles sizes may be slightly different as they were all rebuilt to fix sizing issues and accommodate tiles with multiple status values. Height will be configurable in the near future, but will try to make defaults similar to previous implementation. Lowered empty view height. Pushing these fixes now, so should be available soon. I cannot replicate issues with cameras, do the URLs provided on our WiKi work?

Network Resources will not evaluate these variables as the resource is processed on a seperate thread. System variables (not related to the program) can be substituted but it is possible they change before the substitution in Network Resources occurs. Program Trigger Variables are only available in Notification Content, which is used by the Notification Plugin (Node Server). Also consider upgrading to at least version 5.0.16, preferably 5.2.x or 5.3.x for bug fixes. However being that we no longer offer free support for 994 it may be easier to upgrade to eisy which supports PG3 and the Notification Node Server out of the box.

Added Custom Views section on the UDM Wiki. At some point we hope this will allow users/Node-Server-Developers to create Custom Views for their node/node-servers. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Custom_Views

What is your hardware and firmware? Are you using Network Resources or the Notification Node Server to send to Push Over?

Hi @AnthemAVM, Currently Android and iOS backups for UD Mobile are not compatible with each other. It is still on our TODO list.

The Admin console root directory can be a bit confusing as "My Lighting" is not a "real" folder. In this case "My Lighting" holds devices which have not been moved to a folder and are still in the root director. Due to this not being a "real" folder UD Mobile displays these items at the root Devices and Scenes Directory. To achieve what you are looking for create a new folder (named Devices?) then move all items from "My Lighting" into the new folder. Synchronize UD Mobile and all devices will be inside the new folder. One of the reasons UD Mobile does not create separate directories for Devices and Scenes is because Folders could also be used for locations (rooms) where both devices and scenes for a single location are grouped into a folder. The Directory structure can be considered a user preference, so it is not modified by UD Mobile.

The folder structure on UD Mobile's Home Tab is the same as the Admin Console Folder structure. If changes are made via the Admin Console UD Mobile must be synchronized for changes to show in app. So, users can create seperate folders for Device and Scenes in the Admin Console (or from UD Mobile) then move all devices/scenes into these folders. Moving many devices/scenes may be faster/easier to accomplished from the Admin Console. Favorites of type "Folders" allow a single Display Node but it is not required. If you selected a Display Node then the top part of the Folder Tile may toggle the device/scene similar to adding a favorite of Type "Default", clicking the bottom half will open the folder. If you do not select a Display Node (or delete the Display Node by clicking the Display Node section then selecting the trash icon at the top right) then clicking the Favorite of Type Folder will open the folder. To add items into this new folder you can add the favorite from inside this folder (clicking the + button at the top) OR move the Favorite from the Main Favorites Page by clicking the edit button (pencil icon at top right) then click the Favorite you would like to move, then click Move To Folder. Navigate to the folder then select Paste. Be sure to disable Edit Mode by clicking the pencil icon when finished editing favorites.

The subscription notification will show whenever the app is open on Android as UD Mobile needs to run a background service to ensure status values are updated as fast as possible and to properly handle resource cleanup when the app is closed. Resource cleanup may take longer than Android allows without a Background Service, so this notification may be present for a few dozen seconds after the app is closed even when set to 0 (zero). In your screen shot this variable is a negative number, so this notification may be shown forever as this instructs the app to never terminate the Background Service. The recommended setting is 1 (one minute). This will keep the connection to your system alive for one minute, so if you return to the app within this time frame the app will not need to reconnect. Reconnecting to the system may delay status population by dozens of seconds depending on the seed of your internet connection (i.e. slow mobile internet). During this one minute duration a notification will be shown so that you know the app is running. Edit: The notification is dependent on Android version. Newer version do not show a notification for a background Service, they show as "Running Apps". So this notification may not show on all devices.