Javi

Not yet, We have other PG3 fixes close to the top of our list so will look into at the same time.

Nice work! This is one of the more difficult automations. Variable Math functions: This is a little more involved and very dependent on the devices. The best solution I can think of is to use variables similar to bitwise. This would allow you to combine status from multiple nodes into a single variable. Yale lock values as Y: 0= Unlocked 100 = Locked 101 = Jammed Elk Values as E: 0 = Normal (aka closed) 1 = Trouble 2 = Violated (aka open) 3 = Bypassed The variable will be represented as YYYEE or E. So Locked and Bypass would be YYYEE or 10003 (100-03). Note that the multiplication value (i.e * 100 below) is dependent on the number of places occupied by the next variable, in this example it could have been * 10 as Elk values only have the "ones" place, if the Elk values had a "tens" place then * 100, if the Elk values had a "hundreds" place then *1000. Advanced: This could be expanded with the battery property (B) represented as YYYEEBBB. However the Zero values may cause an issue for the third value, so +1 may be required for all variables which have zero values Variable values: Yale Unlocked 0 = Y0 * 100 + E0 1 = Y0 * 100 + E1 2 = Y0 * 100+ E2 3 = Y0 * 100+ E3 Yale Locked 10000 = Y100 * 100 + E0 10001 = Y100 * 100+ E1 10002 = Y100 * 100+ E2 10003 = Y100 * 100+ E3 Yale Jammed 10100 = Y101 * 100+ E0 10101 = Y101 * 100+ E1 10102 = Y101 * 100+ E2 10103 = Y101 * 100+ E3 Now you have a unique value for each combination of states. Example Calculation: Note that this is an example which combines the current temperature (T) with the heat setpoint (H) TTTHHH with multiplication accounting for the hundredths place (*1000) The variable is 74069 or TTHHH Temperature = 74 and Heat Setpoint is 069 (69) Display Battery Level: Currently the standard favorites tiles only shows the state of a single node/var/etc (i.e. display node). So displaying both the status of the variable and battery level is not possible. This is possible with custom tiles but requires some HTML. However the current instructions are only for developer testing and will be changed soon. I'll be releasing new instructions when everything is ready in the app. This is similar to the Thermostat tile which shows multiple properties, but could also show properties from multiple nodes. Node Server (Plugin): When the new instructions are released we will be adding instructions for developers to have Custom Tiles attached to Node Servers. This may work in this situation by creating a node server which observes properties for both the door and lock nodes then combining them into a single node with a custom tile. Developers can charge for their Node Servers, so if this is built for yourself it can be shared with others, and possibly generate income.

It looks like status is not being populated so UDM cannot determine which direction (on/off) to toggle. Pressing the tile when there is no status should take the user to the "Device Dashboard" which forces a query for status, after this point the app can toggle. However it is very likely that status was missing because UDM is not receiving status updates for the device so it may not reflect the current state. What is your eisy firmware? If it is less than 5.8.3 please upgrade as there issues with remote connections on some previous versions.

Very odd, looks like the "Open Sprinkler Stations (Stations) node is being updated with the number of stations in queue but not the station itself. Although it looks like the first station was triggered twice and is being counted twice. Does this happen without using a program, try manually with a least 5 seconds (their apps refresh rate) between commands to as a test? Sometimes Open sprinkler has odd behaviour if multiple commands are sent close together. If this only happens with a program please try adding waits between commands.

Yes, If it is not 5.8.3 try upgrading first as there was an issue with remote connections in earlier versions.

That is one of the tradeoffs a, but almost guarantees the value will be there. That would have been an issue on the SD card, but can't speak on wear over time as there it has only been a few years. Anecdotally there is an SQLite database which holds property (status) history for all node properties, if enabled. So something with many more writes is available to users.

What is your firmware?

Not normal, it may take a few seconds (short poll) for changes to be populated. Are there any errors in the Node Servers Log? Does the "Last Error Message" Property (status) fo the OpenSprinkler Controller node have any errors? Did the IP address change (if it did be sure to setup an IP reservation so it will not do so again)?

In the past many of these issues may have been caused by a bug in PG3 that caused issues when internet was not available at restart which was very likely in the case of power outages . Sounds like a support nightmare. Aside from a few setup reboot requirements, which we are trying to remove, if the user is rebooting then something was not working correctly or power was removed unexpectedly. It is highly probable the "Run at shutdown" program would not run or complete. Some alternatives included; (1) the "init" parameter of a variable survives reboot, so this should be set when a parameter value is changed so it is retained in case of unexpected restart. (2) I believe the "Backup" Node Server restores values, but not tested on my end. (3) UD Mobile allows manual stop/start/restart commands for individual Node Servers, so if PG3 sends a notification saying the Node Server is stopped then manual reboot of only the affected Node Server with issues is possible.

The product must say that it works with Zigbee Controllers....some of the older bulbs do not "work" with Zigbee Controllers. Not sure about sensors, but most common Zigbee devices are supported. If the Zigbee device doesn't work with eisy a user can open a ticket, but it could be a while before it makes it to production firmware. There is also a node server (plugin) which works with the hue hub, but I don't have first hand experience.

If the bulbs are "Zigbee" then they should work without a hub. See this: And this:

ISY cannot communicate with the device where this error was presented. If it is happening on multiple devices, likely an issue communicating with the PLM.

Thanks. Assuming there is only a single device with the issue, then it is highly probable the issue is a defective Switchlink or Switchlinc communication issues. Power gapping may solve the issue, moving the device, or removing/filtering devices (such as computers, power supplies) which may cause linke noise.

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".

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.

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

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.

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.

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.

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?

Is everything else working? I think this may be a debug error not intended for the end user.

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.