Javi

Did you actually test this on HS in the current environment?

Hi @Sirmeili, I commented on your Git issue over the weekend. It is very likely this limitation exists in HomeSeer/Insteon-Hub also or there would be frequent Command Drops or Status Reporting would be incorrect. Many situations where an Insteon device triggers another Insteon Device could be handled in Scenes, this is even faster than using network commands. ISY allows scene adjustments in programs so you can adjust scenes based on (IF/ELSE) conditions. In my experience every protocol has its advantages and disadvantages. Insteon scenes and communication distance (due to power line) work better for me then all the other protocols. Insteon reports status almost instantaneously where as Z-Wave can be delayed by a few seconds. Most of the Insteon battery powered devices have been removed from my system as they had too many issues the biggest being battery life. Z-wave battery life appears to be 5-10 times longer. The Z-Wave battery sensors also appear to report a change in status better than the insteon sensor...unless the insteon device is still awake.

I'll keep this in mind, when I get to scene improvements.

Yes. Scenes don't have a status so it is an Estimated status. You can disable if it doesn't work for you. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Scene_Estimated_Status

I don't believe we have a method to add your own cert to PG3x. In most cases a trusted ssl cert is only needed for direct remote connections, however I would not recommend opening a port to expose ISY/PG3 outside of your home network. If you want encryption on the local network it is safe to click through the browser warnings as you know the site is correct. If there is a MitM attack on your local network you have bigger issues. The browser needs to trust the cert, so all self signed certs would have the same issues. You could trust the cert on the client (PC) like this, although if I recall correctly PG3 creates a new cert on restart. This is no safer than clicking through the warnings when on the local network. This is the same for ISY except the http and https ports are split port 8080 http and 8443 https. We recommend using VPN or Portal for remote connections. VPN uses a cert for the tunnel so this solves the issue for all local devices without needing a unique cert for each device on the local network. UD Mobile can access PG3 from portal for remote connections, but we don't yet have a remote web version.

If controlling the fanlink using native controls (high/med/low) from Alexa or a mobile app the kpl will be out of sync. They are all evaluated, if you had something in the else condition the actions would be triggered. Based on your image the ISY is showing the state you want and logs the same but the kpl is not in sync with ISY. This usually happens when there are multiple devices in a scene with communication issues and the scene, however because it is a single device in the scene my guess the same device is the culprit..... I've had KPLs with issues evey couple of years, pulling out the set button for a minute usually fixes the issues.

Assuming the programs trigger a scenes which turn on a single KPL button and turn off all the other KPL buttons. If the values shown by ISY look correct but do not correspond to the actual value on the KPL, then the issue is likely not programing. It could be line noise, an insteon device is starting to malfunction, or the insteon scene is not functioning correctly. I would first try removing equipment on the same circuit, then air gapping the KPL for a minute then restore links in the scene.

Yes, but the browser defaults to https if not http is not supplied.

Try the local http option, not https. http://<address>:3000

added door_open (filled) for next production release.

Please post link

Beta 1.1.16 Added streaming video/camera support. To access cameras outside of your home network they must be accessible outside of your home network. PG3 Plugin support, coming soon, will allow developers to add streaming video support to their Node Server Plugins. Basic setup example.

Does the "Time of last change" update after the variable valve is changed? Please post a screenshot of the favorite editor screen from Favorites Screen> edit (pencil icon at top) > click favorite tile > edit.

Great. See this post for explanation of certificate error

If you don't have any favorites setup on UD Mobile with eisy, then delete the system, trash icon at the top right. The add the system again by following prompts. After login, or portal account selection, you will be prompted to select system. If the system exists on portal select the system when prompted, if not select Add New System and follow prompts to add system to portal.

When clicking the Default favorite for a variable or when clicking on the home screen the same "Node Dashboard" is opened so I don't believe it would have nothing to do with Favorites. My guess is the variable already changed so a Status change was not triggered. Can you verify Variable status is enabled in UD Mobile> Settings Tab> Systems> System Name > Program an Variable Settings?

Hi @apostolakisl, I believe I understand. Custom tiles are on our list but I don't have an ETA. Until I get to full customized tiles, I'll try to add smaller status only Favorite Types (tiles) such as text-value-only and icon-only. So you can have a row for icon, next row for high temp, next row for low temp, ect. Also add ability to remove tile background color. My plan is to allow users to create custom tiles from a favorites screen. So something like the example above would be created on it's own favorites screen then displayed as a single tile on any other favorites screen.

Beta 1.1.9 Added streaming video/camera support. To access cameras outside of your home network they must be accessible outside of your home network. PG3 Plugin support, coming soon, will allow developers to add streaming video support to their Node Server Plugins. Basic setup example.

The Favorite of Type Command needs the Sensor as the Display Node and the Relay as the Command. So the favorite tile will show the status of the sensor then when clicked will trigger the relay.

Yes, a Favorite of type "Command" then in the Commands section add a new command to set the device off. This will trigger the off command on every press.

Hi @scote, Are you referring to the UD Mobile toggle or the buttons "on" and "off". Due momentary setting you may need a workaround. The door should open/close when ever the "on" button is pressed. Is this correct? The toggle will only send the "on" command if the status is "off". Is this correct? If you are using Favorites then edit the favorite to type command then add a command which turns this device "on". Now when pressing the favorite the "on" command is sent every time. See the custom toggle for an example of how to setup a Favorite Command Type. This situation is simple so no Program is needed. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Favorite_Custom_Toggle

The Network Resource method was created to allow ISY994 hardware the ability to send Push Notifications to UD Mobile as 994 does not include Node Server Support. Although the Network Resource method will continue to work with Polisy/eisy. The Notification Plugin (PG3 Node Server) simplifies the process of creating notifications without the need to "code" a network resource. Creating Notifications from the Plugin also allows UD Mobile to query programs containing the Notification Plugin Node. The ability to query programs allows UD Mobile to show the list of all notifications and list of notifications linked to a single device. Using the Node Server also has other advantages over Network Resources, such as real time variable substitution (which is delayed in Network Resources, and variable may have changed). If you upgrade to the paid version @Jimbo.Automates has implemented retries in case your internet is down or Portal is down. Upgrade UD Mobile. If a firmware update is required UD Mobile will show you this is required. Nothing changes with your current notifications triggered from Network Resources.

Yes, please upgrade to the latest version of UD Mobile and the option will be available. For anyone else with Polisy: Polisy can be migrated to PG3x PG3x also allows remote connections to PG3 (plugin software) although a reboot may be required.

https://wiki.universal-devices.com/index.php?title=UD_Mobile#PG3_to_PG3x_Migration

Please also try rebooting Mobile device. Then synchronize when prompted. If this does not work please open a ticket and include your UUID and we may be able to perform a remote diagnostic.