Javi

If you have ISY portal I believe this will work

Please try reboot (press power button 5 times). If this does not work please open a ticket.

@ISY4Me, Can you please copy this to your ticket. Assuming when you checked the portal this was on Ethernet, it should have reconnected to Portal automatically. So may need someone working with firmware to debug. The only reason I can think of WiFi not working is the ssid or password is incorrect or the app is incorrectly encoding characters. Do you have any special chars in your SSID or password? Also there is a manual way to add the credentials linked below. This will not work from iOS (reasons link below). So you could try this from a PC/Mac. https://wiki.universal-devices.com/index.php?title=UD_Mobile#Troubleshooting

Thanks @ISY4Me and @JTsao, I've noticed that sometimes if the user reboots/power-cycle during update they have issues along with the system not being fully ready. I'll try to get the update checking in soon.

Depending on your mobile device, home router, and network connection method (Wifi/ethernet) eisy may support eisy.local as the url. The app's finder will try to locate and test this URL and show it in finder if it is found. With that said the app's finder will only show the first address it matches to a UUID so it will only show the numerical address or eisy.local whichever is found first. Thank you for the detailed screenshots. Based on your screenshots it appears the app connected to eisy in AP mode and uploaded the credentials you provided. It then the app failed to find the system on your network using the Finder in the background. Please help me find the issue if you have time. What is the last 2 digits of the mac address on the bottom of the system? What is the firmware version of the system? If less than 5.5.3 pleas upgrade and try again. Note that the upgrade may take upto 30 minutes, during this time your system may be partially accessible but this does not indicate the upgrade is complete. I hope to have this automated and show update status in the future. Try WiFi onboarding again, If the issue persists please go back out of onboarding and go to to the System's Local Connection settings and press the search icon. Is eisy found on Wifi? If so what is the last 2 digits of the UUID and IP Address which is populated? Is http://<IpAddress>:8080/desc with <IpAddress> replaced with the IP Address in finder accessible from a browser? Sorry for so many steps. we had bugs in some previous firmware versions which should now be corrected so I need to verify this is true. Fixed the "Could not match section error in the next release for Android and iOS, missing click event listener.

Thanks. Do you have the app setup for Local Connections? If you do and the issue is encountered again please disconnect the mobile device from WiFi to see it is replicated on Portal. If replicated on portal I can do a remote session, assuming I catch in time, to try to find the issue. Usually if the app is "stuck" on Starting Subscription it is not actually stuck but trying to connect to the system and waiting to timeout. On timeout you may get your other errors. This usually indicates a route to the system does not exist on the current network or the network is extremely slow.

Hi @ISY4Me, Thank you. I'll look into this soon, just been a busy morning.

Nothing changed regarding subscriptions in the last few updates. From the description it sounds like a network issue. Is this on WiFi or Cell network?

Ok thanks. Also please be sure the system is on the latest firmware. Press the power button once and wait 30 minutes, during this time the system may be partially accessible but this does not indicate firmware update is complete. After 30 minutes if system cannot be found by App/IoX Finder press the power button 5 times to reboot. We hope to automate this from within the app in a future update.

Hi @ISY4Me, Possibly 2 issues. The first is the local connection settings currently only allow one IP Address. The app will automatically populate the Local IP address the first time the system is setup, in your case ethernet. However because this is a manual override setting the app will not overwrite the local IP Address on a subsequent setup. So when the connection is changed to WiFi the IP Address is incorrect and will need to be updated manually by pressing the search icon next to the local IP Address. This should find the new IP Automatically if the app knows the UUID, if the app does not know the UUID you will have to select the system from the selection dialog. The second issue is the WiFi setup screen not finishing/closing? I assume the WiFi setup was successful based on your other comments, is this assumption correct?. Is this iOS or Android? Did you start WiFi setup by adding a new System or from Settings > WiFi configuration?

All please try now

Locked related topic https://forum.universal-devices.com/topic/39794-error-404/ Looking into this

Thanks. Locking this topic and using topic created in Portal as it appears local connections are not affected.

Do these issues persist this morning?

Thanks. I'm not seeing issues with my system. Does anyone still have the issue, if so what is your firmware version?

Great. Maybe migration related?

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.