Javi

Hi @sjenkins, Per Bob please try: You'll need to do a re-install (note, not delete and install) for it to pick up the change. https://forum.universal-devices.com/topic/39706-cant-connect-on-eisy/?do=findComment&comment=356126

@garybixler, please try now. Not tested on eisy for reasons previously stated, but made fixed suggested by Bob.

@sjenkins, It should be live now.

Thanks, both of the node servers I published need to be updated to support pg3, hopefully by the end of the day today.

That is the default as folders display status inherit node toggle values. This is the same as setting a scene as the folder display node. Variables do not have a toggle value. Maybe we can add a non-toggle folder in the future, but it may be some time before I get to this.

Thanks @bpwwer. @garybixler I'll try to get it fixed by end of of day on Monday.

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

Ok, thanks. Let's see if @bpwwer has any suggestions as the it appears to be an internal communication issue. 2023-01-04 16:59:50,269 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'set': [{'address': 'itachir', 'driver': 'ST', 'value': '1', 'uom': 2}]} 2023-01-04 16:59:50,269 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'set': [{'address': 'itachir', 'driver': 'ST', 'value': '1', 'uom': 2}]} 2023-01-04 16:59:50,312 Interface udi_interface.interface ERROR interface:_startMqtt: MQTT Connection SSLError: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1134), Will retry in a few seconds. Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026038_9/.local/lib/python3.9/site-packages/udi_interface/interface.py", line 426, in _startMqtt self._mqttc.loop_forever() File "/var/polyglot/pg3/ns/0021b9026038_9/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1742, in loop_forever self.reconnect() File "/var/polyglot/pg3/ns/0021b9026038_9/.local/lib/python3.9/site-packages/paho/mqtt/client.py", line 1073, in reconnect sock.do_handshake() File "/usr/local/lib/python3.9/ssl.py", line 1310, in do_handshake self._sslobj.do_handshake()

iTach does not use SSL and the errors look like PG3 MQTT connection issue. Is IoX updated to the latest firmware? I am also seeing PG3 connection issues on 5.5.0, but need to keep eisy on this version to test package upgrades in UD Mobile. Maybe @bpwwer can check the log file.

You can also use the same email notifications in the Notification Node Server with UD Mobile. There are still some outstanding issues to be worked out in firmware when sending Notification data to a Node Server. Firmware limitations - If there is a subject in the notification then only the subject is used - If there is no subject then the body is used - Maximum of 80 characters are returned

No, the support tickets would take much of my time. I am intentionally vague when discussing this topic as someone could read, try, fail, then ask for support. Network security can be at risk when going this route. If a user has a deep understanding of Certificates then they likely understand the risks involved and know how to configure their device/proxy/client. If you do not want to use ISY portal I recommend setting up VPN. VPN is available on most mid/high end routers and is much easier to configure/manage and usually free. The router MFG usually provides instructions and a certificate which is installed into the VPN configuration on your device. Why use ISY Portal: We manage and support the connection along with additional services such as Google Assistant and Alexa. Our portal subscription cost is less than $1 per month, while the cost of an SSL cert can be anywhere from ~$35 to ~$100 annually. ISY portal configuration can be setup in app in a couple of minutes, even with the best abilities cert management will likely be 10x. With portal your subscription is tied to the device not the account so you can share your devices with users on other portal accounts at no additional charge. Shared account access can be managed locally so you can revoke access to other users without needing to change credentials or VPN cert. Finally, if we look at one of the other Home Automation platforms, the same managed access is $65 or more a year.

Notification shown outside of the app as in app notifications are not affected. The term may be specific to Android Auto notifications, but the same basic concept. Update is now available in the Google Play Store

Nothing changed, UD Mobile has had this requirement from day one for reasons listed in the previous link. We did recently update our Android target so it is possible the platform now requires higher security although this is not likely the cause. It is available for 994, I don't see updated docs so am not sure about IoX. While this is possible with 994 it is not recommended. With regards to UD Mobile we do not provide tech-support for direct remote connections as it causes too many support tickets. Not to mention security issues which could arise from opening a port and cert cost is likely higher than ISY Portal. With that said, UD Mobile can use https basic-auth instead of oAuth remote connection to any proxy or ISY including Portal when the Use Portal switch off. This requires the proxy/ISY have a cert which is trusted by the client. Many clients allow users to add their own trusted certificates, but again out of our tech-support for the same reasons.

That is the default behavior. It requires programs are enabled at startup in settings to get program status. If only needing to trigger If/then/else/stop/ect command then a Widget of type Command can be used also.

Hi All, It was just brought to our attention that newer Android devices are missing heads up notifications. We updated our targeted API for Android and newer devices now require explicit permission. We will try to get version 1.0.12 pushed by the end of the day. Users may have to click the notification tab to accept the new permission.

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

Added Toggle Widget to iOS 1.0.7 and Android 1.0.11. Behavior is the same as the default except Node Dashboard is now triggered from menu (3 dot) icons and no divider between top and bottom of tile.

Did you reserve for both of eisy's network adapters, Ethernet adapter and WiFi adapter? These will be different IP Addresses so it will also need to be changed in UD Mobile as Local connections on UD Mobile currently only accept a single IP Address. This correlates to the error message unreachable host. Can you please clarify if you see "WifiBox" on your WiFi network? If you do not then UD Mobile will also not be able to find it and WiFi Configuration will need to be restarted as eisy likely does not have the correct Wifi credentials.

If checking your router eisy on wifi may be named WifiBox.

Please let me know if this is not accurate Based on your description I think this is because you have UD Mobile setup to only use local credentials. The local only credentials likely have the IP Address of the Ethernet adapter not the WiFi Adapter. Because local only is currently a manual override the IP Address will need to be changed to that of the WiFi Adapter. Try pressing the search icon next to local IP Address entry. If checking your router eisy on wifi may be named WifiBox.

Was this was done from Settings-Tab > WiFi Credentials? If the system was connected to Portal then ethernet was removed the error is expected. However eisy should have reconnected to portal as soon as the connection to your home WiFi was established. Let's first verify eisy received the correct WiFi credentials. Can you see eisy on your WiFi network and is it available in IoX finder? If it is not on your home WiFi network you can try WiFi setup again to reset the credentials. If it is on your home WiFi network what is eisy's firmware version?

Any user with approved access to system has complete admin access. There are a small number of exceptions such as new Portal Account access-approvals require AC/UD-Mobile to be on the same local network.

Thanks. Pushed 1.0.10 to production with fix.

Currently the only restrictions from inside the app is to disable edits. This requires access to the users device. We may be able to do this automatically for Portal sub-accounts in the future but I don't have a timeframe. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Edit_Locks I'm not sure I understand this question/comment. If UD Mobile is setup to only use the local connection then it never contacts portal for the system. If UD Mobile has both Local and Portal connections configured, then UD Mobile routes to portal when not on a local connection. When UD Mobile only has Portal configured (no local) then all requests are routed through Portal.

https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console