Javi

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.

Uninstall would likely not change anything as My Geofences is a UD Mobile Feature, not related to eisy. If encountered again, please post a screenshot of the second screen which requires tap as I cannot replicate.

Uninstall will not change anything. I do not understand Are you seeing 2 geofence screens? While the "My Geofences" screen content may change the title should remain the same if on the same screen.

When this happens is the title at the top of the screen "My Geofences"? My guess is My Geofences is the only tile for a brief second, then registers the click for the wrong tile taking you to the My Geofences Screen instead of My Devices. If the tile is different please share a screenshot.

If a device is not writable then eisy cannot communicate with the device, this can affect any scenes with the device, so likely all related. Try air gapping the device (pulling tab out until it stays) waiting some time then reinserting the tab. Or factory reset the device.

If this is showing outside of UD Mobile's Geo fencing, please post a screenshot of the location so we can try to resolve. The screenshot above is in "My Geofences" and working as intended for "when using" permissions level as always is required for Geofencing.

As far as I know it is a standard USB cable. I have not see reports stating otherwise.

While not exactly what you are looking for, the bulb can be set manually using UD Mobile in the Device's Dashboard (coming soon to favorites). Click the menu next to the Hue and/or Saturation properties and select the Hue or Saturation Sliders as the View Type.

Pinouts on generic USB -> RJ45 adapters do not match for Insteon PLMs so they will not work. The options are to build your own cable (instructions are posted somewhere on the forum) or purchase one from UD.

Are you seeing this outside of a Geofencing Screen? If only seeing this in a Geofencing Screen it is expected as the app cannot function without Always permission. The likely cause is the app previously requested that the user "allow always location" but either (1) the request was denied or (2) iOS may periodically alert users an app is using allways location which and give then the option to revoke. If the request is denied or revoked user must manually change this permission in iOS Settings before Geofence screens are shown in UD Mobile.

Great! The "Beta" is because it was installed from the "Non-Production" Store. I think you would need to copy the parameters then delete the Beta Version, then install the Production version in the same slot and replace parameters. I think if done like this it will preserve programs, but have not tried.

Might be related to the version, I've corrected in the database. Please try again....if it does not work reboot may be required first.

The preceding zeros in 2023.01.09 were causing issues with PG3 so they were removed. While I don't think the version is the cause of "Unknown Error" I think you can fix this by selecting the Plugin from the Non-Production Store (Beta), clicking install under "purchase in "Available Purchase/Install Options". Then next to "iTach-IR 2023.1.9 is already installed in slot X" select "reinstall here". For the "Unknown Error (see Logs)" there should be a few logs in the iTach Node Server. The error is likely prefixed with "ERROR : ". Download the iTach Log after and error is encountered then attache here for review. If this happens with the same commands then it it likely invalid formatting. If this happens randomly then it is likely a network issue, is this a WiFi iTach or hardwired?