Everything posted by Javi
-
Switch Status Not Reflected
To help isolate the issue, I'll need some additional information. Are status updates also missing from the Admin Console? If they are, then please check if this only happens on the Remote Connection. To test this you must be on the same WiFi network as eisy. Go to UD Mobile > Settings > Systems > Your System > Local Connection Settings (expanded), enable "Only use Local Connection". Also verify the Local Credentials, IP and Port are correct. Default local credentials are both "admin" if they have not been changed. There is a search icon next to the Local IP Address which should automatically populate IP and Port if needed. Press the Test Local Connection button at the bottom of the Local Connection Settings, if a success message is received local connection is established. Cancel any request to synchronize. Does status now populate correctly? After this test please disable "Only use Local Connection".
-
Switch Status Not Reflected
Also please verify firmware is at least 5.8.3 and UD Mobile is on the latest version. There was a bug in earlier firmware which may cause similar issues.
-
ELK Node Server not connecting via UD Mobile when connected via Cloud
Please open a ticket and include your UUID, and a copy of the screenshot and/or link to this post. Also in the ticket please clarify if this is ELK only or all Devices. Thanks
-
no sync option
This was recently moved to the menu, so possible we have a bug. If synchronization is missing please verify UD Mobile is on the latest version, then post a screenshot showing the missing menu, or synchronization option.
-
ELK Node Server not connecting via UD Mobile when connected via Cloud
Please first verify eisy's firmware is at least 5.8.3 and UD Mobile is on the latest version, if not upgrade and retest. There was a bug in earlier firmware which caused issues for many users.
-
Unable to get PG3 Node Servers
Thanks, I can't replicate this behavior, please open a ticket and we can run diagnostic. Include your UUID in the ticket and I will provide instructions to allow remote diagnostic.
-
Variables not updating in favorites
Please test the following to help narrow the issue. Is this only favorites or Home Tab also? If Both: Does the Admin Console show the variable update if it value is change from UDM? If it does: With Favorites open showing the variable(s), does UDM show variable update if value is changed from the Admin Console?
-
Unable to get PG3 Node Servers
Is everything else working? I think this may be a debug error not intended for the end user.
-
UD Mobile - Android
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).
-
Variables not updating in favorites
What is eisy's firmware? If not on 5.8.3 please upgrade then check if issue persist.
-
isy to eisy migration issues
Please open a ticket
-
UD Mobile Sorting/Filtering
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.
-
UD Mobile Sorting/Filtering
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
-
UD Mobile Sorting/Filtering
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.
-
Confirm Request Option in Programming?
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.
-
Is this expected or unexpected behavior?
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.
-
Zigbee device turns off unexpectedly
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.
-
Is this expected or unexpected behavior?
What Favorite Type has this behaviour? This has been reported before but I could not replicate, but it was possible I was using "Default".
-
Does the EISY support a Zooz Z-Wave 700 Dongle?
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.
-
Does the EISY support a Zooz Z-Wave 700 Dongle?
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.
-
UD Mobile Notification count error
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.
-
UD Mobile Notification count error
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).
-
UD Mobile Notification count error
Issue found and corrected. This may require delete all notifications as some users had duplicates.
-
UD Mobile Notification count error
Is the "big number" always 100? Are all notifications acknowledged (no circular indicator next to the notification icon)?
-
UD Mobile Notification count error
I can't replicate, please open a ticket and include the eisy's UUID so we can check your account.