Javi

Hi All, We are aware of status values not populating when using ISY Portal. We are looking into the issue, and hope to have resolved soon. I'm starting this topic to consolidate all other topics started by users and updates. Until status using remote connections is fixed, if you are using UD Mobile on your Local Network please check out our updated instructions on how to add Local Connection Settings into UD Mobile. This will allow UD Mobile to be even faster when you are on the same network. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Combine_Local_and_Remote_Connections

Thanks, I've replicated the status issue on portal connection, we are looking into this now. The app will do a manual request when clicking the individual device if the status is null which is working as intended.

I have a few reports of the same issue, we are looking into it now.

Try swiping app from recently use application. For some reason app couldn't obtain program information. I'll have to look into the cause, but am out of the office until tomorrow. But maybe related to an AWS outage this morning.

The program looks correct. The Customization with variables will only populate the variables if they exist. If manually running THEN, most of the variables will not exist as there was no event that triggered the program. With regards to the message not being the text entered into the Customization, it is very likely the Customization and/or Program was not saved before running THEN.

The Notification Content uses the same Customizations as the Admin Console Email Customizations. These are superior to Network Resources or content in the Node Server as Variable Replacements is possible and in real time. With that in mind the Admin Console only shows the notification Customization ID, if the program is viewed in UD Mobile it will show the text of the notification content.

The program created by UD Mobile will show in the Admin Console. The only difference is UD Mobile will show the Notification content instead of the Notification Content ID.

If using the Notification Node Server it may be easier to setup notifications from UD Mobile, this creates a program also. UD Mobile will show more detailed notifications content see

If using the Notification Node Server with UD Mobile Notifications then restart eisy and the new groups should be available. If using something else please elaborate.

I can imagine a few ways to accomplish this, depending on how the light and keypad are wired. Is the keypad hardwired to the light? If the light iis hardwired to the keypad, then you can change the On Level (dim level on single button press) to 0% with a program, then back to 100% when time has ended. This will still allow a Fast On (double press) to turn on the lights, but single press will turn the light to 0%. If the light is not hard wired to the keypad, there are multiple ways to accomplish.

I don't think you need to count, just 4 programs without scenes. Then each program references fan status and control of button press. If (control) Off button is pressed turn off fan If (control) On button is pressed and fan (status) is off then set fan low If (control) On button is pressed and fan (status) is low then set fan to med If (control) On button is pressed and fan (status) is med then set fan high (optional) If (control) On button is pressed and fan (status) is high then set fan to low

Yes

Cannot be done from Network Resources. This can be done from a Node Server and is the correct way to do this. You will not need to use ISY variables as a Node Server create nodes that can be used in programs.

If you login with your account the app will behave just as it does on your device. For Geofencing: If using the same Geofence, go to the Geofence then change the commands so that it updates the correct node. If using different Geofences (i.e. you created one for yourself and one for your wife on your phone with the one for your wife disabled on your phone), then enable/disable the geofences as needed on the other device. Note that enable/disabling Geofences on one device will not change settings on the other device.

That is up to you. If using the same account then login. If using a different account, eisy is in the other account also. Delete the Portal account (trash icon) then go to Systems > Your System and login using the other Portal account

Have you tried creating another backup? If you have and it did not work please send me a private message with a copy of the backup file, or open a ticket and include a zipped copy of the backup file. I also see crashes for iOS > 17.0 will push an updated app today, so should be live over the weekend.

Yeah, their chat window disappeared with both agents when reported the issue, so I didn't get far. Couldn't find their email either maybe a call https://www.honeywellhome.com/us/en/support/ (at the bottom of page).

Just tried and I'm also not receiving password resets. Maybe an email to resideo support, I tried their chat and they only support the app.

I registered about a month ago to test this Node Server and it worked. I submitted a pull request to change a URL in the Node Server's instructions as it had changed, but other than that it works as described.

Yes, or create a UD Mobile backup then import onto the other person's device. If this is a new UDM install the backup file can be imported at the bottom of the initial login screen. Import is preferred as it will also add your favorites to the other device. After import you will need to reset the Portal Credentials (Settings Tab > Universal Devices Accounts) if this is the first time import, subsequent imports may retain credentials from previous state due to iOS Keystore. Then either (1) change the Geofence Commands or (2) enable/disable the correct Geofences if you already created the other persons fences on your device. The latter will make it easier if you plan to import favorites on the other person's device at a later date.

Please see the Wiki Example to keep the KPL buttons in sync.

It looks correct, but as with all troubleshooting, I would recommend starting small. Delete all scenes, then create a single scene and add one device at a time while testing to see if controlling the scene from the AC is behaving as desired. Continue until something does not work as desired. Alexa supports fans natively, so the easiest method for Alexa is controlling the fan directly.

If the KPL and Fanlink are linked the same way as the single scene in the Wiki the Fan and PLM stay in sync without PLM/ISY connected. Must be link type Insteon, not default or command. Have you tried air gapping KPL with the pull tab or ~20 seconds?

Likely due to Local IP Address Changed. If you Added a WiFi network in Settings Tab > Systems > Your System > Local Connection Settings (expanded) > System Network Relations. Then the app is on this network it will attempt a direct local connection. So either the IP entered into the app must be reserved on your router or remove the WiFi Network from Local Connection Settings.

Go to your UD Mobile Geofence, and set the enter/exit commands to turn on/off the "Kent" Node on your device and the "Nancy" node on the other device. We do not create Geofences on other devices automatically for various reasons including stocking, privacy, ect. As an alternative you can create a seperate Geofence for all users on a single device (i.e. one named Kent Home and one named Nancy Home) with the same radius, but change the enter/exit command match the node for that user. Then disable Geofences for the other users. Export your backup to the other users device, then enable Geofences for that user and disable or delete those for other users. Edit: Also not that the OS (iOS/Android) may periodically ask the user if they would like to keep location permissions. So the other user must be aware, and accept always allow location access if prompted.