Javi

It's possible it is UDM or Portal as Favorites was recently rebuilt. Do you see any error messages. Does the device work correctly from the Device's Dashboard? Also please verify on 1.1.60 if using iOS

Please open a ticket and include your UUID. In addition to the UUID let us know if synchronization succeeds or fails when connection type is Portal (phone's wifi disabled).

I can not replicate this behavior. Does the Device's Dashboard show a value for High Temperature?

Should be live now, please let me know if there are any other issues.

No need to recreate unless they have been deleted, it's just a lookup error. The UDM wals looking for the node's default display status instead of the favorites defined display status which results in an error.

There was a bug discovered with favorites in version1.1.59, so 1.1.60 is awaiting apples approval.

App setup and configuration is not yet ready for Android, we are working on the required changes, so hopefully within the next few weeks.

Thanks for the report, I'm building 1.1.60 now, so just need to await Apple's processing/approval. Issue caused by architecture changes. A display node is now a group of nodes, although only one is shown to the user in the Favorites Editor.

If using Occupancy V2 there is no need for programs or variables see the link above for instructions https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server

Try reboot eisy, then synchronize UDM.

I think it would be closer to $300 unless you need 2 controllers in different locations (~$200 (controller with power ethernet) + (2 x expansion ~$50 each). Would be hard to find another 24 (or 40 in this case) zone controller for less.

Is the same shown in the Admin Console?

I've used OpenSprinkler for years, and am the author of the same Plugin. OpenSprinkler works great for the most part, and much better than non-connected controller. It has fallen off the WiFi network a few times in the last 5 years (like many WiFi devices) but the programs are local so they still run, just needed to restart and it would reconnect. So I would recommend getting the ethernet adapter if that is an option in the controllers location. There are no "hacks" needed to connect to eisy and no cloud service. eisy will act as the remote access so no need to open/forward ports or have a static IP or Dynamic DNS service.

@JMcKain, We need a additional information. Please open a ticket and include eisy's UUID, and a link to this topic. Thanks

Looking into this.

It can be a program, but be sure the "Command" is executing the correct command. Commands are Run IF, Run Then, Run Else, and Enable (Enable enables or disables a program, it does not run the program). However if using the occupancy Node Server UD Mobile should update the node see https://wiki.universal-devices.com/index.php?title=UD_Mobile#Occupancy_v2.0_Node_Server Likely a programing issue. I would remove all variables and use the Occupancy Node as the trigger, see link above.

It is likely an invalid URL, be sure is starts with "https" and ends with "/desc". Local connection can also be used with the http:<ipAddress>:8080/desc where IP Address is replaced with the units local IP Address (i.e. something like 192.168.1.65).

Module purchase server for ISY994 was shutdown, so if a module was not installed prior to the module purchase deadline then it cannot be installed.

Replicated, UDM was not updated to match the new PG3 API for polls. Will try to get a fix in the next couple of versions.

The last firmware for ISY994 is 5.3.4. If you want new Plugin (PG3) features then hardware upgrade required. The "My Notifications" links to the Notification Plugin which uses PG3 (Plugin) software only available on Polisy or eisy. Network Resources can be used to send notifications, but it is not as easy and will not show up in "My Notifications" or in linked Notifications. Also variable substitution may not work well with Network Resources. Notification Plugin https://youtu.be/t-r1hUeDWjQ Network Resource: https://studio.youtube.com/video/9w-_8AZy4iQ/edit

Try manually running "Then" with the lights on, do the lights turn off If no: Save the program and try again If yes: Manually trigger the switch, did the programs last runtime change?

I just updated our Troubleshooting guide to account for some Mac Security and Privacy Preferences which may cause this issue. https://wiki.universal-devices.com/Main_Page#Unidentified_Developer_Blocked

There is no guarantee this will work with MobiLink, so may want to wait for confirmation that this works. Likely better if user switches to UD Mobile if they have Node Servers. See https://github.com/search?q=org%3AUniversalDevicesInc-PG3 hint&type=code for a few examples. If I recall the following documents may have conflicting information, so I'm not sure which, if any, are used by MobiLinc. https://wiki.universal-devices.com/index.php?title=Node_Hints_Documentation https://github.com/search?q=org%3AUniversalDevicesInc-PG3 hint&type=code

Try to find the Hint (sometimes Type is equal to hint) for a similar device from rest/nodes, then add the same value to the Node Server Node. I think sensors are 7.0.0.0, but may require the second position also, i.e 7.X.0.0 https://wiki.universal-devices.com/index.php?title=Node_Hints_Documentation Below is an example for thermostat with hint added by Node Server developer. <node flag="128" nodeDefId="HwhF"> <address>n006_48a2e687e1a9</address> <name>Home - Hallway</name> <family instance="6">10</family> <hint>5.0.0.0</hint> <type>5.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n006_48a2e687e1a9</pnode> </node>

I believe MobiLinc uses its own static "profiles" for device types. So it may not work well with custom profiles provided by Node Servers. If the node conforms to a static profile then setting the Hint may allow the device to work with MobiLinc. Hints can be set by users if needed using ISY Portal (there is a local API also but no UI). If the hint works the Node Server Developer can set this as the default. Motion Sensor conformance would likely require the Node Server have same status and command IDs as an Insteon Motion Sensor.