Javi

Action buttons will be shown above favorites in next update. Bug introduced when we added transparent (scroll through) navigation and tab bars.

The Home, Automation, Settings tabs have a dropdown to change the Displayed Controller, not the displayed Portal Account on the Notifications Tab. Notifications a linked to a Mobile Device and Portal Account, not a Controller, and may be created by third parties outside of the controller. So, grouping by controller is not possible in all situations, grouping by Account works for all situations. Yes, it is new. Most users have a single Portal account with multiple controllers. So, having multiple Portal accounts is an exception, usually reserved for installers, managers, and developers. The account selection on the Notifications Tab should only be shown if the user has multiple Portal Accounts linked in UDM. Before your post I've only seen 2 users (not in the exceptions listed above) with multiple accounts linked to UDM, and one of them may have been you . I see how it can be annoying, but the reverse was also true (feedback). When managing multiple accounts, it was hard to see which account had notifications and too easy to delete notifications which the manager did not intend to delete. I'll keep this in mind while we develop, maybe a User Preference to show notifications from all accounts?

It looks like UD Mobile is signed into two accounts. Press the Account Name to change to the other account's Notifications.

https://www.universal-devices.com/my-tickets/ In your web screenshot above there is a "Log" Tab.

Please open a ticket, included the browser screenshot and a copy of the node server's log

Try rebooting controller. Are the Nodes in the Admin Console? If they are try synchronizing UD Mobile.

Try restarting the Node Server then check the Node Server's Log. On restart the plugin will parse the codesets so any errors will be logged. This looks correct, but the others are definitely incorrect (see https://forum.universal-devices.com/topic/34813-itach-ir-node-server-global-cache/) I just requested a code set from the control tower database and the format does not appear to have changed. Also be sure to press the "Send Code Set" Button, do not "select a Function" when requesting the code set.

ISY access needs to be enabled for this plugin. This was a recent permission change for plugins which can access/control isy. This is safe for this plugin.

From your screenshot it looks like there is no status for this plug-in. The plug-in needs to be restarted.

Is this a Plugin (Node Server)? Has synchronization been performed since the firmware update? It looks like the status values are missing so if it is a plugin it may need to be restarted.

There are no Default Notifications, but you can trigger a notification directly or via program. First add the Notification Plugin if you have not already done this. Then create a Notification Customization for entry and exit. Finally trigger the desired notification on enter or exit.

That is not a valid iox firmware Version. UD Mobile> Settings Tab > firmware

What is your firmware? If it's not on the latest version, please update. Some previous versions had this issue.

Great, found a permanent fix will push by end of day UDM version 1.1.74

Replicated, thanks. It looks like something changed in the recent iOS update, the app is trying to push the user to login but can not launch the view so it restarts at Home Tab. I don't yet have a fix and can only test on the emulator as I left my iPhone cable at home. Please try to disable WiFi and Cell network which should give you time to get to the Account Settings before refresh. Finally re-enable the Mobile Device's network and login. If the refresh happens before you can login, remove the Account (trash icon) from UDM on UDM's Account screen. Then go to the Controller's settings and login when prompted. I'll push an update as soon as I can verify a fix, but could be 24 - 48 hours before approved by Apple.

I can not replicate this behavior. Can you capture a short video showing the refresh? When I force the app to restart connection the menu does not disappear.

The following are not available? The top menu (3 dots) > My Account Or Settings Tab > App Settings > Accounts

The Portal Login is no longer valid. Try going to the UDM Account settings, does it force a login?

I did not read through the entire thread but I've seen similar issues through the years. While most were related to Programs, there are a few less common things to consider. Do you have a query program? It's possible eisy is gaining or losing (a) device's state. A query then triggers a program when query is run or when device finally reports status after query cleared the device's status from Unknown State. A program is in a vicious loop using all available resources. This causes may strange issues. I've seen this happen where issues start at the same time everyday, then there is something that either automatically or manually stops the loop sometime later. The user cannot replicate issue again until the loop starts. This usually correlates to UD Mobile being very slow. User at one point had IFTTT/Alexa/Tasker/etc issue a command to a program/variable and this is still happening. The program/variable may have been deleted, however ISY will reuse program/variable ID's if they are deleted, so the old automation appeared to be removed until the user added a new program/variable which reused the old ID and the automation now triggers the new program/variable. If you find a program which may be the culprit, try copy then delete the original so the program has a new ID. eisy is rebooting. Usually due to a program in a vicious loop or too many requests, similar to denial of service. Too many requests were usually caused by a malfunctioning integration like home assistant or a PG3 node server which the user has allowed ISY access. This usually correlates to UD Mobile not being able to connect. Geofencing is triggering a program/variable with a false entry/exit.

This may happen if the app is deleted or app data is cleared, the new instance of the app creates a new Device. Apple does not let this persists or transfer between apps/devices. If you have a screenshot taken before changing the enabled value, or remember, the "Updated" timestamps it may give some clues. Could have happened recently or long ago, the former could be the cause of your issues using Notification Groups as the "new" device needs to be added to the group. Click the Mobile Device in the list and there should be a delete option at the top.

Go to Notifications Tab > Settings (gear icon) > Device Section, then find the mobile device. Verify it shows Active. Click the mobile device in the list verify "Enabled" and then press the "Send Test Notification" button.

This follows the same logic, either the wait finished and the variable/state change caused the program to reevaluate to False or Wait is interrupted which caused the program to reevaluated to False. This should be easy to see in UD Mobile as the Program's Status would be Idle False indicating the last run time was an evaluation to False which finished running the Else Actions. Idle True would indicate the last evaluation was true and finished running Then Actions. If the Program's Status is Running Then/Else it is no longer possible to link the last finish time to True/False evaluation. If the timestamp for last run on true evaluation (Then) is important, a second disabled program can be used. The original program would be changed to trigger the new program to Run Then Action in Then and Stop in Else. The new program would contain the original programs Then Actions.

Last run time should be called Last Evaluated time. The program was likely (re)evaluated to False when the variable and/or light status changed.

Fixed in next update Root will be the Devices and Scenes in a future update Understood, will try to find an alternative. Most of my development is done in dark mode with white text, so maybe a good idea to have the dark shading and white text for both light and dark modes.

Home Tab top menu or the menu next to the controller name.