Javi

Hi @jwagner010, While the following is not the exact solution you are looking for, it is very similar. Enable program status at startup, Settings Tab > Systems > Your ISY > Advanced. Now you will have the status of your program at app startup. The Program Toggle works as follows: If program is not running, the toggle button will RUN IF. If programs is running (then or Else), the toggle button will STOP the program. Note: You must select "Status" as the visible control for the toggle to be present in Favorites.

Hi @GaryT, Currently it is not possible. We hope to have push notifications implemented at some point in the future. With that said, many users are currently using Pushover to get push notifications on their devices. Pushover notifications can be triggered from Network Resources or the Notification Node Server.

Thanks @asbril, This is expected behavior when a sync fails to find a node or node status definition. The app assumes the node or status has been removed from the ISY so it removes the favorite as well. This should be a rare occurrence so if it can be replicated we may be able to find a firmware, App, or Portal issue when running a remote diagnostic. Please send me your UUID in a Private message and I will provide additional instructions. EDIT: Sync issues related to items in this post should be resolved in UD Mobile for iOS version 0.2.1.

Hi Jim, Google Play will send us a small amount of crash data, although it can be very ambiguous. More often than not, it will show the system function that crashed instead of the App function or class. There is one crash in the last day related to SQL however as mentioned it is ambiguous. Can you please email me a copy of the current database (backup) so I can try to replicate?

It will take a day until we get the crash report, but I could not replicate in a quick test just now. I have been using this method for all folders as it has been been available from the initial release. Edit method was recently changed so this may have introduced a bug. Does it crash every time the folder is open? The empty folder message is correct as the new folder has no children.

We still need to make adjustments on Android so the process is the same. In Android click edit, then click the plus next to the favorite, there is an option to change a Node to a folder

Hi @asbril, The sync errors should not happen this often, if encountered again please send me an email and I can run a remote diagnostic to see if we can find the root cause of the issue. Try not to reboot the ISY before the diagnostic. As for the missing status, after you have created a folder click on the menu (three dots) on the right side of the folder. This should show the Node Dashboard which includes the current value for each node in the scene as reported by the ISY. Do the included nodes have values? Compare this with a folder which is showing the correct status, is there anything obviously different?

Hi @asbril, This should not be related to the scene. Although rare this may happen when a file can not be downloaded from the ISY, for this reason the sync specifies the need to make a backup. There could be many reasons why the file could not be downloaded, most of the time rebooting the ISY prior to sync will resolve the issue. After reboot import UD Mobile backup, if you have one, then sync.

This is already possible if all of your devices are in a scene or you create a scene with all of the devices. Add the Scene to favorites then change the type to "Folder", now you have a folder which shows status. I agree, however as far as I know the smallest widget available is 2x2. There are rumors that Apple will have a 1x1 widgets in the future, but if it does not happen I'll see if we can add a setting to set favorites as the default View.

Thanks @fahrer16 ! Please also pull the following: https://github.com/fahrer16/udi-rachio-poly/pulls

Hi @rob.bushkaufer, The Magic home NS has an error which crashes the Apps XML Parsers. I have submitted a pull request to fix the issue, however we are still waiting for the Author's approval. https://github.com/fahrer16/udi-magichome-poly/pull/2

Hi @whywork, Thanks for the feedback! I see you have figured out most of the setup. I'm adding notes below to help others with similar issues and questions. Remote: We try to steer users to setup the Portal on initial install, most of the Portal error messages are human readable. The Apps also allow for direct remote connections. Direct remote connections require a valid CERT and error messages are raw to help users whom choose this route. Local: The local connection has no CERT requirement and should be a few seconds faster then the portal when the app is opened. The app reads the (WiFi) SSID of the current network and compares it to the users list local networks (SSIDs) to determine if it should connect using the local or remote connection settings. Both local and remote connections have a "test" buttons under their settings to help diagnose issues. VPN: Another remote option is to use a VPN and select "Only Use Local Connection", this will instruct the app to ignore WiFi SSID checks and use the local connection. This option can also be used if users want to user the local connection settings without granting the app permission to read Wi-Fi networks. This should be faster if done on a local connection. The app must download Node Server files to get all control options and values, the app may not know something has changed unless these files are downloaded. So I'm not sure it can be much faster. Sync should only be needed after adding a new node or if Node Server files have changed.

Hi @apostolakisl, I'll see what what we can do. We still have some scroll adjustments to make related to centering the current value (if available).

No problem, The App functions a little differently then the Admin Console to save space on a mobile device. I don't own a tesla so I can not test, but we may want to put in a pull request for this in the node server itself. When these items are unhidded do they show a status as well? Also please do let me know if a reboot changes the values to a human readable format.

Hi @carteriii, I took a look at the Tesla node server, both of these status items are flagged to hide. If you click edit (pencil on top) can they be unhidden? I am a curious as to why they are flagged this way. Also the status values should show human readable values, instead of numerical values. If you reboot your ISY do status values show has words instead of numbers?

Hi @carteriii, This should be available in the app, based on the image provided "Charge Port" "and Sentry mode" appear to be linked to a status. If they are correctly linked in the node server then these buttons are available by clicking the status value in UD Mobile, it should have chevron icon next to the status to indicate it is a clickable item. Please post screenshot of the app if this is not the case. Please elaborate, programs should also be available in the app. If you would like program status at startup please go to Settings > Systems > Your ISY > Advanced.

Hi @TrojanHorse, Github is prefered for bugs as it will be easier to track, on this forum is ok also. https://github.com/UniversalDevicesInc/UD-Mobile-iOS

HI @wrj0, It appears the sync is failing somewhere. If you are open to a remote diagnostic please PM me with your UUID (Admin Console > Help > About) and I will provide additional instructions. Thanks

Hi All, UD Mobile for iOS is now available for public testing. Minimum firmware required 5.0.16. https://testflight.apple.com/join/xHtzI5R3

Android Alpha Testing 0.54 Added Node Dashboard edit mode. Node Dashboard status objects and buttons objects now allow for sequence change and can be hidden. Many bug fixes.

Hi @asbril, I'll investigate the error bytes not being decoded (optional). Was this on today's release 0.1.4 or a previous version? <edit> Fixed 62758ed </edit>

I've had our Public Works trucks (trash, recycling, ect) break our overhead internet lines in the alley a few times over the years. I call Centurylink and they tell me there lines are fine and that I need a new modem. When I finally convince them my eyesight is great and the line is physically broken they will come by and fix within a week. During the repair the line it is zip tied to a higher cable to prevent Public Works from breaking the line. Unfortunately the higher cable is property of Xcel Energy, eventually Xcel will come through and cut the zip tie, and the cycle continues.....Not to mention CenturyLink deciding the route the cable through a large evergreen during the last repair, so now everytime it snows I have to get a large pole and shake the branches above the cable to prevent it from breaking. Anyway, I'll see what we can do about resending messages that are missed when we are at that point. I think the Node Server approach may be needed for these situations as data persistence is needed in the event of power failure or restart.

We are looking into push notifications for the UD Mobile apps, however it will be some time after our initial goals have been achieved. This would also require server side so notification triggers may, at least initially, require that the ISY is connected to the Portal. Being that connectivity is required, i'm not sure if it would help if a notification fails due to loss of portal/internet connection. Personally, all my network/home-automation equipment is on a battery backup and I use @Jimbo's Notification Node Server with Pushover and it has been more reliable/configurable than email/text notifications. Some routers, such as Nest Wifi, will notify the user when the router is offline which is also a great way to know if you will be missing notifications. A final note would be to add a timestamp to all notifications. When your mobile devices loses network connection, the device may be flooded with notifications when it is reconnected to a network. I have noticed that after regaining connection notifications may not be in the order they were sent.

Hi @smacbride, Yes, all Z-Wave devices are Nodes. So, they should have the same controls available in the Admin Console.

Hi @smacbride, If the RGBW controllers are Nodes in the ISY then the app should be able to control them. If you encounter Nodes which can not be controlled please report it to us so we can find the error. There are a few know Node Servers with errors in the configuration files which may prevent the app from controlling them. We have created pull request to fix Node Servers with known configuration errors, however some are still awaiting the authors approval.