Javi

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.

Yes, eventually the Home tab will only show devices and scenes as multiple controllers will be in the controller dropdown header.

Fix in 1.1.71 should be live in the app store. The Automations tab has variables.

Thanks, This is the current expected behavior, pressing Home Tab when on Home Tab will shows all controllers, in this case only one, clicking the controller should take the user back to devices and scenes. This will be changed in an upcoming build where the back button is removed when at root Devices and Scenes and if the home tab is pressed when already on the Home Tab it should go to root Devices and Scenes. However, I will be out of the office for a few days and this change, along with others, has not yet been released to tester so It may be a couple of weeks before pushed to production. The bug fixes mentioned above along with others reported today will be pushed to production tonight.

Thanks for the description I replicated an issue on the Automations Tab when the Bottom Tab is clicked when already on the Automations Tab. I could not replicate any issues on the Home Tab. Are there issues on the Home Tab also? I'm going to submit version 1.1.71 tonight with fixes, so hopefully live by tomorrow morning.

Many of the telcoms now block/delay/limit sms from email, so in my opinion another option should be used if you want notifications in a timely manner. The Notification Plugin uses the open API for the UD Mobile Notification Server (ISY Portal). There are instructions on our wiki showing how to send notifications using Network Resources, however the Notification Node Server Setup and Program configuration will be much easier and use the existing Notification Customizations (the same as email).

Assuming this is iOS please upgrade to 1.1.70 as the last few versions had bugs related to the UI changes, including the blank screen. Devices and scenes is now the default, variables/programs/notifications/etc are now in the Automations Tab.

This was removed as we had too many ticket where users hide the controller from themselves. However the most recent version on both Android and iOS now automatically show the default (last selected) controller on the home screen.

Great, Changed not-equal character to "IS NOT EQUAL TO" text in next version.

If this is no/null status then it is likely disabled in settings. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Program_And_Variable_Settings

I cannot replicate, however I notice that the strike through the equals-sign is not easy to see. Which screen has this issue?

iOS or Android?

This is a bug in the AC, and will be fixed in an upcoming update. If there are missing IDs (in sequential order) in Notification Customizations then only the Customizations before the missing IDs are shown. As a temporary fix add Placeholder Customizations to fill in the missing numbers. When adding a new Customization it should be assigned the lowest possible ID, do this until all missing IDs are added. UD Mobile should work without placeholders.

Thanks for the report, will be fixed in 1.1.67 iOS and 1.1.87 Android.

That's not good...I'll push a fix now to correct the issue. Depending on Apple's review could be a few hours or days until live.

We are in the process of an app rebuild. User Preferences are now on the Home Tab Top Menu

Replicated, will be fixed in iOS 1.1.66 Thanks

The command is sent immediately, however a value update is not received immediately which may appear as sluggish. Showing the estimated new value before receiving a value update is on my list, but no time frame. UDM limited the dropdowns to ~200 values so this makes sense if the thermostat has a precision/step of 0.1. Can you try to change the Step value in the editor to "1.0" instead of "0.1". See the Missing Widget example for instructions to get to the editor https://wiki.universal-devices.com/index.php?title=UD_Mobile#Missing_Widget. If this does not work, or the instructions are not clear enough do to UI changes, please send me a copy of the UDM backup file and I will take a look. Please point me to the location of this node if it is not at root Home Tab or Favorites tab.

I cannot replicate this behavior when using Default view type. I just tested both the Properties "Value" and the Commands "Value" and they work as intended. If using a Slider or Switch this it was limited to 0-100 to mimic a light switch as I did not think users wanted the full negative and positive ranges. Is the Default view working in your case? Is this an issue with another View Type? Setting variable values outside of dashboard currently only works in Favorites. If using the Favorite "Picker" type it should allow manual typed input of any value. This is a bug, I've fixed in the next update. Change to Command then back Command with Dashboard to edit until fix is released. A program is the correct approach as this is both a calculation and a command. UDM only supports commands, as calculation logic should be preserved and executed on eisy. The variable value can still be show as the "Display Node" while the command is the Increment Program. See the custom toggle example https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle While this may seem like a simple request it is actually more difficult than it appears on the surface. (1) It is possible the app does not yet have a value for the variable due to latency which will cause the calculation to fail, a longer delay in execution, and/or sending an incorrect value. (2) We try to avoid recreating functionality available in Programs as functionality running in UDM as it creates more possible points of failure, debug logs, etc. (3) If the user does not backup UDM the Program is preserved on eisy, so user will not have to recreate the Program in UDM.

If that was your device, please try version 1.1.86, it may be a few hours before live in the Play Store..assuming the holiday does not delay the app review.