garybixler

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.

After reinstalling the ELK NS none of the iTech NSs will connect. Seems to be some conflict between ELK and iTech. Tried rebooting and reinstalling iTech but no change. Even tried installing a new iTech NS but still can't connect. The attached is the problem with iTech. With the iTechs disconnected the ELK is performing better and the arm status is displayed correctly. Still not responding as fast as it did on the Polisy however. ELK Text Document (2).txt

I attached the log from the time of arming from the AC to where it actually armed. It was a little quicker this time. Can take up to more that 20 seconds. I also reinstalled the NS before trying the arming. Also Area1 Armed Status always shows disarmed even if armed from a keypad. ELK Text Document (2).txt

I installed the ELK NS on the new eisy platform and am finding that commands sent to the ELK are very sluggish. Just took 20 secs. for the arm command to get to the ELK. Zone changes however are seen in less that 2 secs. It seems to be related with sending to the ELK only. Everything is configured as it was on the Polisy. Tried resetting the ELK ethernet interface but no difference. Thanks. eisy- 5.5.2 PG3- 3.1.17 ELK- 3.5.7

@xKing Hi I have moved the LiFX node server onto the eisy and found that it no longer will do a discovery. Just shows the following errors when discovery initiated. Any suggestions. Thanks Gary 023-01-01 13:17:46,081 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-01-01 13:17:46,081 Thread-2527 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-01-01 13:17:46,082 Thread-2527 udi_interface ERROR udi_interface:write: Exception in thread 2023-01-01 13:17:46,082 Thread-2527 udi_interface ERROR udi_interface:write: Thread-2527 2023-01-01 13:17:46,082 Thread-2527 udi_interface ERROR udi_interface:write: : 2023-01-01 13:17:46,082 Thread-2527 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-01-01 13:17:46,082 Thread-2527 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-01-01 13:17:46,083 Thread-2527 udi_interface ERROR udi_interface:write: self.run() 2023-01-01 13:17:46,083 Thread-2527 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-01-01 13:17:46,083 Thread-2527 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-01-01 13:17:46,084 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/lifx-poly.py", line 206, in _discovery_process 2023-01-01 13:17:46,084 Thread-2527 udi_interface ERROR udi_interface:write: devices = self.lifxLan.get_lights() 2023-01-01 13:17:46,084 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/lifxlan.py", line 42, in get_lights 2023-01-01 13:17:46,084 Thread-2527 udi_interface ERROR udi_interface:write: self.discover_devices() 2023-01-01 13:17:46,084 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/lifxlan.py", line 50, in discover_devices 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: responses = self.broadcast_with_resp(GetService, StateService,) 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/lifxlan.py", line 234, in broadcast_with_resp 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: msg = msg_type(BROADCAST_MAC, self.source_id, seq_num=0, payload=payload, ack_requested=False, response_requested=True) 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/msgtypes.py", line 19, in __init__ 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: super(GetService, self).__init__(MSG_IDS[GetService], target_addr, source_id, seq_num, ack_requested, response_requested) 2023-01-01 13:17:46,085 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/message.py", line 43, in __init__ 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: self.packed_message = self.generate_packed_message() 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/message.py", line 47, in generate_packed_message 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: self.header = self.get_header() 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/message.py", line 55, in get_header 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: frame_addr = self.get_frame_addr() 2023-01-01 13:17:46,086 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/lifxlan/message.py", line 80, in get_frame_addr 2023-01-01 13:17:46,087 Thread-2527 udi_interface ERROR udi_interface:write: mac_addr = little_endian(bitstring.pack(mac_addr_format, convert_MAC_to_int(self.target_addr))) 2023-01-01 13:17:46,087 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/bitstring.py", line 4689, in pack 2023-01-01 13:17:46,088 Thread-2527 udi_interface ERROR udi_interface:write: s._addright(BitStream._init_with_token(name, length, value)) 2023-01-01 13:17:46,088 Thread-2527 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/.local/lib/python3.9/site-packages/bitstring.py", line 1435, in _init_with_token 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: raise CreationError(f"Token with length {token_length} packed with value of length {b.len} " 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: bitstring 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: . 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: CreationError 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: : 2023-01-01 13:17:46,089 Thread-2527 udi_interface ERROR udi_interface:write: Token with length 64 packed with value of length 0 (bits:64=0). 2023-01-01 13:17:53,299 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll

Since using the Zmatter both on Polisy and eisy the Zen 17 can be configured to isolate the inputs from the relays but the Zmatter doesn't pickup the additional child devices on 5.5.0 or 5.5.2. So there are no separate input devices showing on the AC The Zen 16 is only showing one power switch where it should be showing three.

I installed notification on the eisy but I am not able to get it to work. Just wondering if the rest port may be different from 8199 as on the polisy. The admin console shows server connected but rest status not running. Thanks

Just one question. I am assuming that the eisy won't be able to load any NSs from PG2. Nothing pressing.

After reinstalling a node server more that once it still remains in disconnected state but is running. It was reinstalled from my purchases list. When I installed a node server not in the purchases list it does get installed. So how will I move the NSs presently in Polisy to eisy?

After delegating a couple of node servers from Polisy they show up in node server purchases. It looks like I can reinstall into the eisy from there. Will that also take care of the license issue? Thanks

I tried to install wake on lan but it doesn't really install. No node is created in the AC. It does show in PG3.

After an eisy reboot with V 5.5.2 everything looks and works great. Thanks

One thing I noticed when I did get logged in and somehow got PG3 to see the IoX there were two mac addresses and neither was the Polisy that is still active. One was the eisy and I am suspecting that the other my be the WIFI mac address of the eisy which I don't use.