Javi

My guess is the tabs being at the top (Apple API) is causing a calculation issue with the bottom. I'll take a look at both issues when I get some time.

Do any of the devices in the scene also change status? Try disabling the calculations for all devices in UDM then add back one at a time. This only affects UD Mobile's calculation, has no effect to eisy.

See the custom toggle example https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle In short the Display Node and the Command do not need to be related, but the command should cause the Display Node to change. The command should be a Program Run IF so it holds all logic related to the toggle.

Some routers and/or operating systems do not support dot local (.local) addresse, so you may need to use the numerical IP Address is this is the case. PG3 can be accessed from http to avoid warning, so change https to http with the numerical IP Address, you still need to append the port i.e. :3000 so http://ipAddress:3000 If the finder shows a isy.io address this was saved by the user, as it cannot "find" remote controllers. You can also manually add the local IP Address to finder with http://IpAddress:8080/desc

my.isy.io is a remote location, you need to use the local IP Address. Or simply try http://eisy.local:3000

Great, Thanks for checking!

Currently not possible, but similar requests have been made in the past. i.e Tab Tiles. Tab Tiles are on the list but not sure when I'll have time to implement.

How you did this works. The empty status selection is some sort of bug however I cannot replicate. Does this happen with all programs or with just this program? If it is a single program does synchronization fix the issue? If synchronization did not fix the issue: When/If you have time open a ticket or send me a private message with a zipped copy of the UD Mobile backup file? If this only happens with one program include the name of the program (also the path if it is nested into other folders). If it happens with all no need to specify. Thanks!

Great, Can you explain this in more detail? Android or iOS? This may be a bug.

It's due to how insteon processes scenes. A command is not sent to individual devices it is sent to the Scene. A Scene has a predefined rampRate and onLevel (a preset). An Insteon Scene is more like a preset than a controlled group. For eisy to do this it would need to send a command to each device which would be out of sync (the same as sending a command to each device in a program). Not only would be out of sync but would likely fail to trigger some devices due to traffic. So to achieve what you are looking for you have two options. 1) (recommended) Create a new scene with all devices as responders, set the level to 10. Then trigger the new scene from the program. This will allow all devices to come to the specified level at the same time. 2) (not recommended, but this is how it would work if you physically held the switch to a desired on level) Trigger the Fade Up on the scene then Stop after some time.

The favorite must be linked to a Node for Advanced Config, Advanced config is in the Favorite's Tile Menu. Advanced Config can also be found on the Home Tab Node's Menu. Advanced config is linked to a Node. The favorite Type (i.e Toggle) is in "Edit Favorite". The node must support toggle, if not use the command type to create your own toggle (see wiki).

PG3 is not accessible from a remote location (limited functions available in UD Mobile remote). So you will need to click the local IP Address in the AC, not the my.isy.io address.

The instructions need to be updated, click the tile's menu to access the setting, no need for edit mode (except for tiles which do not show a menu when when edit mode is disabled). Can you post a link to the instruction you followed? I will update.

This is how it works now, Each controller can have "links" to WiFi Networks (multiples links in case the 5GHz and 2.4GHz have different names/ssid). UDM will only attempt a local connection when on the "linked" network. Each controller's WiFi links are unique to the controller, but can be shared with other controllers, so you only have to define the network one time if you have multiple controllers on the same network. Issue can arise if both the homes/locations have the same WiFi Network Name (which I have encountered once), but this is rare and, in my opinion, not good practice on the user's end. Android allowed us to read the BSSID(UUID) of the network but iOS does not (gives a faux BSSID) so if this issue arises the user will need to name the WiFi networks differently or use UDM's the automatic detection with a hard coded numerical IP Address for the local connection and the numerical IPs must be different.

The app error is a bug in the app. We have submitted a new version to both app stores. Still awaiting approval from Google/Apple.

Understood, the issue is likely UD Mobile is trying to connect to a local connection (IP Address) when on your WiFi network. The controller settings are in UD Mobile has nothing to do with the Admin Console.

Hi @bob123, This is on my TODO List. Might be a few weeks as this is the only report of the issue so has a lower priority.

In UD Mobile > Automations Tab there is a link to the setup video.

The local connection settings for the cabin are incorrect, accessing a local ip (i.e. eisy.local), or you have defined a WiFi access Point which is incorrect. Go the the Cabin's Controller Settings and check the Local Connection Settings.

It helps if tracking multiple people, it will show if anyone is home or a single person without needing to do the calculations yourself. The same can be achieved with variables. Nothing in the Admin Console has been replaced or changed with regards to email/notifications. However more providers are blocking emails from our servers or all email to sms. This is something explained well in may parts of the forum so will not go into detail. If you choose to use this method I cannot help debug (too may variables), but another user may be willing to help. The Notification Plugin uses the same Notification Customizations as emails, but other than that nothing else (i.e. settings/groups or Recipients) is related. Did you "test" this program, i.e. Run Then? if not the test may not be sufficient. These "Notifications" are not the Notification Plugin, so not related to UD Mobile. They are emails. The Notification Plugin can be found under Devices in Program Action (not under Notify). If you have not yet setup a Notification Plugin notification please follow the example video to and it will create a program for you which you can examine and copy/edit.

If the variables are changing then the issue is not with Geofencing it is with programing. In UDM > Geofencing it shows what is changed on Geofence Enter/Exist (this is likely pointing to your variables. If using the Occupancy Node Server UDM Geofencing needs to change the status of the Occupancy Node Server (not the variables). Then the Occupancy Node Server Status is used to trigger programs. See: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server

Impressive grip on the USB extension in either orientation 😊 The missing add/remove functions are for the original Z-Wave implementation (ISY994 or a non-Z-Matter Hardware) which is the reason it was likely missed in testing. Luckily I still have one 994 running for Google/Apple to run app testing for App submissions, so I replicated the issue. The new Z-Matter implementation has has a barcode scan function and updated ZWave Profiles. Which UD Mobile will not show for your controller even after the fix made. Open a ticket with the Title "ZMatter Hardware has ZW addresses instead of ZY addresses" then state that Javi asked you to open a ticket and add a link to this topic.

Understood. I think I found an issue on Android for non-ZMatter Zwave. Will be fixed 1.2.19 However if you do in fact have a ZMatter Dongle (pictured in screenshot) then then your Controller's Z-Wave implementation is using the older non-Zmatter functions. ZMatter Zwave Addresses start with ZY, if I remember correctly the original implementation has addresses which start with ZW. If this is the case please open a ticket as this is not a UD Mobile issue so will need deeper review. Do not tick the Z-Matter Hardware switch yet as this will remove any devices already added to the controller. Thanks

This should still be supported, except for some features. Please share a screenshot of the error message.

Non-Zmatter Zwave Hardware? Android?