Javi

Major changes to app. Please let me know if anything is not working. UPDATE: Local Connection test are failing frequently on 994, pushing version 1.1.78 which restores this functionality but keeps the automatic tests. Version 1.1.77 Local connections are now established automatically if the local credentials/ip/port are correct. Using http://eisy.local on port 8080 should work for users with a single eisy if their home network and mobile device support local domains. Router IP reservation of numerical IP is recommended as the Local IP Address may change. Speed improvements, bug fixes. Versions 1.1.62 - 1.1.76 UI Improvements, rebuilt Device Dashboard. Added Color bulb type for Philips Hue and Sengled Zigbee bulbs (possibly works with other "hue" type color control nodes).

What is eisy's firmware? If not on 5.8.3 please upgrade then check if issue persist.

Please open a ticket

Scenes have no status, there no way to determine accuracy of something that does not exist. The estimates can be adjusted, see the link provided above. The issue could also be line noise, so it may be a good idea to troubleshoot before replacing anything.

It sound like a PLM issue. This could indicate the PLM is starting to malfunction or it could be communication issues or a faulty insteon device in a scene. If this is only happening to a small number of devices, or occurs after a scene is turned on/off it is likely the latter, if happening with all devices then likely the former. So, troubleshooting is required but not related to UD Mobile (the subforum where this topic was posted). Both the serial and USB Insteon PLMs work with eisy. Being as Insteon if proprietary, I assume the best place to purchase is through insteon. Also note that the Estimated Scene status in UDM should not be used as an indication of malfunction as Scenes do not have a Status. This is estimated by UDM and may not be the estimate the user expects do to how some device types report status, for example a battery sensor's status will remain the same if you turn a scene on or off from UDM or AC which causes UDM to calculate this status as part of the Estimated Status. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Scene_Estimated_Status

UDM clears status when the user leaves the app, so if status is incorrect (not missing) at UDM startup then the issue is likely not related to UDM. Is status also incorrect in the admin console? Are the devices with incorrect status all Insteon? If both questions are true then it is likely a PLM issue.

Not currently. As an alternative you could send yourself a notification if the garage door is left open for some time after you leave the geofence. Although It would require opening the app to close the door.

OK, I still cannot replicate. Please send me a PM with a copy of the app backup which has a non-working customization and let me know which tile (name) has the issue.

Scenes do not have status, they are more like a preset. The trigger would need to be the status of a device or state variable. A variable can be used as status, then a program with a wait can be used. I.e. if var_x = 1 turn on light, then wait 5 min, run the same program. If the variable changes during wait the program will stop, and else will be run, so else should turn off the device.

What Favorite Type has this behaviour? This has been reported before but I could not replicate, but it was possible I was using "Default".

Factory reset = reset eisy to same state as it arrived from factory. The same configuration tab will show if Z-Wave and/or Z-Matter is enabled. For anyone else reading this both must be enabled for Z-Matter, if not using automatic detection settings.

As far as I know it is supported, but will not get any more updates. It must be enabled in Admin Console Configuration Tab, ZMatter must not be enabled, if it is or ever was then factory reset is required.

Login must have happen at least once to receive notifications, if not Portal would not know your device's ID and could not send push notifications. If the user opened the Notifications Tab during the same session as login it may have caused the Device ID to be added twice.

Issue is caused when a mobile device is added to the user's Portal account twice within milliseconds. I believe the cause is a double refresh on the UDM iOS Notifications tab which races to add the Mobile Device to Portal. If the user logged into portal then opened the notification tab in the same session (without leaving app) the double refresh may have caused the Mobile Device to be added twice. If the user left the app, upon return then there is a single notification refresh which adds the Mobile Device to Portal, thus preventing the issue on double refresh when the user enters the Notification Tab. The next version of of UDM for iOS will fix this race condition. We have also made a correction to Portal to try to fix the issue for other users, although the correction may not happen until after the saved notifications have expired (If I remember it is ~3 months).

Issue found and corrected. This may require delete all notifications as some users had duplicates.

Is the "big number" always 100? Are all notifications acknowledged (no circular indicator next to the notification icon)?

I can't replicate, please open a ticket and include the eisy's UUID so we can check your account.

Do you have, or have you ever had multiple ISY Portal Accounts?

Please upgrade.

Sort/search is on our list, but no time frame. What is your firmware? If not the latest please update, as earlier versions had a bug causing missing status on remote connections.

UD Mobile has edit locks which should/could prevent users from accessing some items in UD Mobile, such as edits (show/hide), Admin Tab, and Settings Tab. The basic concept is to hide nodes, status, and/or commands you do not want shown to the user then lock edits with a pin. Now the user will not see hidden items and cannot get into edit mode without the pin. See https://wiki.universal-devices.com/index.php?title=UD_Mobile#Edit_Locks We are in the process of updating the App's User Interface so it's possible some items may not be locked due to the updates. If something in found please let me know and I'll try to fix soon. I removed the ability to hide the entire system on the Home Tab as too many users hid the system from themselves causing many tickets.

This Log should correspond to A program (IF) Schedule is being evaluated. If this program is not triggering the device and there is nothing else in the log, then off is likely not triggered by eisy. What is the Make/Model of switch?

This shows that an event happened which set the status to 0 (off). More logs before this event are needed.

Thanks but I do have one. The issue is time as the flex device I have is connected to a serial cable and would take time to reset then reconfigure for serial connections after testing. I the new version does not work please attach the Node Server's Log.

Added iTach Flex definitions, although I can not test. Please reinstall, I did not update version as this change should not affect existing users. If there are any errors please attach log.