garybixler

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.

Exact same issues here also. Also I am on 5.5.2

Thanks, you were right. A space was added to my email address. Thanks for the quick response.

For awhile now UD mobile hasn't worked so I decided to reload the app and reboot the phone. The problem is that when I try to log into the portal I just get access denied please check username and password 403. I am using the same user (email) and password that I use to log into the portal from a browser. Any suggestions welcome. Thanks Gary

Not Working again. After a reboot to add Insteon support PG3 again will not load the local ISY. There seems to be some sort of IP addressing issue between PG3 and IoX.

Got it working again. After giving it a new reserved IP address it started right up and is now working. Although I could always connect to the AC. Now on to the conversion.

After inadvertently deleting eisyIOX from the ISYs in PG3 I am unable to add it back. I did a factory reset but it is still not showing up. Did the add ISY with all the parameters but no luck. Did this countless times. Any suggestions appreciated. Thanks Gary

Similar issue as @brianswith the ZEN 17.

I tried a factory reset and re-including. It does work with default settings in the config. But when I set the input type to 10 it won't pick up the additional child devices doing a synchronize with interview. The manual suggests doing an exclude and re-include but that just sets the Zen 17 back to defaults. I tried the write changes but just get errors. Not sure how to save the config so Z wave can pick up the new devices.

I found an issue with another two devices. The Zooz ZEN 16 does not have all its interfaces loaded. Should be 3 switch inputs and 3 relays out. The Zooz ZEN 17 seems to have all the interfaces loaded but the switch state is not being seen by the AC. Tried many things but no luck. The Zooz 71 switches seem to work fine. Just information as I am not using Z-wave for anything necessary. Thanks Gary

I am not getting a status update from one of my z-wave devices. Aeotec by Aeon Labs Nano Switch. Its a small switch that sits inside a switch box. I can turn it on/off from the AC but if I switch it on or off locally the status never gets updated on the AC. I see no device traffic in the event monitor if switched locally. It did work with the Zooz stick. Tried different settings but no changes. Thanks for any suggestions. Gary UPDATE: I found the issue with my Nano switch. Home Assistant forum mentioned a parameter not mentioned in the Nano switch documentation. So after trying a few values I found the one that works. Parameter: 80 Value: 2

All is working now. I installed the latest version, deleted the nodes, restarted and did a discovery. Also did a query on the thermostat to load all the values. Not sure if that was needed however. Thanks Gary

One more.

Two snapshots of the program. It does work using fan state