garybixler

After restarting PG3x or rebooting the eisy I always need to do a start on each node server as they come up disconnected. eisy 5.5.4 PG3x 3.1.20

@xKing I tried the suggested SSH commands but no difference. I still get the string of errors when doing a re-discover. Also tried reinstalling the NS. eisy 5.5.4 Thanks

Sadly no responses or solutions so far.

Thanks. The ELK is working as it should. No delays.

@Jimbo.AutomatesThanks ELK is working again as it should No delays.

Just ordered. Would be great for a node server.

@sjenkinsThanks for the suggestion. I just gave it a try but it didn't add the missing input devices to the ZEN17. No change on the ZEN16 either. However my ZEN71 switches are all working great. Thanks

Just upgraded to IoX 5.5.3 and did a Z-Wave synchronize update with interview on the ZEN16 and the ZEN17. The additional two switches were added to the ZEN16 but they aren't functional. Just shows a blank page for those devices. No ON/OFF etc. No additional inputs were added to the ZEN17 representing the dry contact closures when configured to have the inputs separated from the output relays. Just though I'd pass along this info. Thanks Gary eisy 5.5.3 Z-Matter

@JaviI just installed the new version and they are working just great. Thanks so much. @bpwwerMany thanks for all your expertise and follow through with this issue.

@xKing Hi, after checking my network and access points LiFX is still unable to do a discovery. Still produces the above errors. Using the eisy on Ethernet. eisy 5.5.2, PG3 3.1.18 Thanks

Try just doing a reinstall from your purchases.

There's is an issue with the ELK node server running on PG3 right now but am hoping it will be resolved on Monday. How ever I am able to get full functionality. Is the host actually elk://192.168.1.251:2601 ?

I have tried many times and in different slots also. Could something be corrupted?

The eisy is connected using Ethernet. Before migrating to the eisy from Polisy all node servers were working great. After the migration to eisy v 5.5.0 and PG3 3.1.16 all the servers loaded and connected and were working great except for ELK's slow response and lIfx not being able to discover. After the eisy upgrade to 5.5.2 is when the iTech servers could no longer connect. PG3 upgrade to 3.1.17 made no difference. PG3 upgrade to 3.1.18 made no difference. I think that was the order of events. I did submit a ticket about the iTechs not connecting. I think@Jimbo.Automates will be looking into the ELK this weekend. I also submitted the LiFX error log to @xKingin the LiFX forum. So all of my critical servers are working fine with the exception of the ELKs slow command response time. Thanks

I am including the LiFX errors in case there may be a correlation. Thanks LiFX.txt

I have the following installed. WeatherLink: Installed and working VenstarCT: Installed and working WirelessTag: Installed and working Notification: Installed and working Wemo: Installed and working WeatherBit: Installed and working Lifx: Installed but won't discover bulbs Bond: Installed and working TeslaEV: Installed and working AVRemote: Installed and working Elk: Installed and working but commands (arming, etc) to ELK are very slow. 20 secs. Second command following the first is much faster. 3 iTech: They can be installed but won't connect.

Just upgraded PG3x to version 3.1.18 but am still getting the handshake errors. 2023-01-06 11:36:29,557 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'getNsInfo': {}} 2023-01-06 11:36:29,569 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() ssl.SSLError: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1134)

The ioX is presently at 5.5.2. These were working under version 5.5.0.

After moving the NS to PG3x on the new eisy I am getting this error after having to reinstall the NS several times. It install but won't connect. Looks like a handshaking error. I attached the log. Thanks Node servers.txt

@bpwwerSome good news. WeatherBit just popped up while doing an IoX backup.

I guess it would depend how the memory is partitioned. I see a paging scenario with elk as the first command to elk may take 20 seconds but the following command takes only a second or two. Also the initial log load for a NS takes a long time. What I saw before was like the elk and iTechs were interfering with each other. Just my observations.

Got the log for WeatherBit and iTech. Takes a long time for the first log to load. Node servers.txt

Basically just shows a non filled in main page. I did get the forecasts earlier and they look good. Tried query but doesn't fill in.

WeatherBit stopped working. All seems to be a lack of memory to support the NSs. Just a guess.

I am now having issues installing iTech NSs. They eventually disconnected after going to version 3.1.17. They seemed to be causing issues with ELK or visa versa. I described some of the issues in the ELK forum. As of now no iTech NS will connect after install. Also having issues with LiFX not being able to discover which was an issue after migrating to eisy from the Polisy. The ELK is working but may take 20 seconds to arm or disarm from an AC command. It was almost instantaneous when on the Polisy.