garybixler

I needed to restart the LiFX node server after the SSH commands for it to discover the bulbs. Using the Re-Discover button didn't seem to work.

Pretty much this over and over before the servers were stopped. If it happens tomorrow I'll get a debug log. 1/20/2023, 13:08:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DOF 1/20/2023, 13:09:39 [pg3] info: [00:21:b9:02:60:38_3] wtcontroller reporting command DON 1/20/2023, 13:09:52 [pg3] info: [00:21:b9:02:60:38_4] controller reporting command DON 1/20/2023, 13:11:09 [pg3] info: [00:21:b9:02:60:38_12] controller reporting command DOF 1/20/2023, 13:12:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DON 1/20/2023, 13:12:44 [pg3] info: Verifying node servers are installed on IoX correctly 1/20/2023, 13:12:44 [pg3] info: IoX entry for WeatherLink::1 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for VenstarCT::2 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for WirelessTag::3 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Notification::4 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Wemo::5 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for WeatherBit::6 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for LiFX::7 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for iTach-IR::8 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for iTach-IR::9 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for Bond::10 OK 1/20/2023, 13:12:44 [pg3] info: IoX entry for TeslaEV::12 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for AVRemote::13 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for ELK::14 OK 1/20/2023, 13:12:45 [pg3] info: IoX entry for iTach-IR::17 OK 1/20/2023, 13:13:47 [pg3] info: [00:21:b9:02:60:38_14] zone_30 reporting command DON 1/20/2023, 13:14:04 [pg3] info: [00:21:b9:02:60:38_14] zone_30 reporting command DON 1/20/2023, 13:16:09 [pg3] info: [00:21:b9:02:60:38_12] controller reporting command DON 1/20/2023, 13:16:37 [pg3] info: [00:21:b9:02:60:38_14] controller reporting command DOF 1/20/2023, 13:17:44 [pg3] info: Verifying node servers are installed on IoX correctly 1/20/2023, 13:17:44 [pg3] info: IoX entry for WeatherLink::1 OK 1/20/2023, 13:17:44 [pg3] info: IoX entry for VenstarCT::2 OK

It seems to be happing around the same time everyday. Early afternoon. I'll look for any previous problem before the shutdowns. Thanks.

My Node Servers come to a stop for no reason that I am aware of. Need than to start back up one at a time. I captured the log when I think it happened. I changed it to debug so maybe better info if it happens again. So far seems to be daily since updating to 3.1.20. /20/2023, 13:35:23 [pg3] error: uncaughtException: read ECONNRESET Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) 1/20/2023, 13:35:23 [pg3] error: uncaught ECONNRESET exception: Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) 1/20/2023, 13:35:23 [pg3] info: Caught SIGTERM/SIGINT Shutting down. 1/20/2023, 13:35:23 [pg3] info: Stopping running node servers... 1/20/2023, 13:35:23 [pg3] info: [WeatherLink(1)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [VenstarCT(2)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [WirelessTag(3)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Notification(4)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Wemo(5)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [WeatherBit(6)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [LiFX(7)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(8)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(9)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [Bond(10)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [TeslaEV(12)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [AVRemote(13)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [ELK(14)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: [iTach-IR(17)]: Stopping Node Server 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 1/20/2023, 13:35:23 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns

I use putty but I think windows powershaell can start an SSH session to eisy also.

sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring pip3 install --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring==3.1.9

That didn't work but a later set of SSH commands to the eisy did work. Just required restarting the node server to discover the bulbs.

@asbrilHave you checked the LiFX solution in the LiFX forum. I just go mine working again on the eisy.

Good News. After doing the SSH commands and restarting the NS it discovered the bulbs. Thanks so much. Gary

2023-01-20 09:35:05,585 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2023-01-20 09:35:05,586 Thread-106 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-01-20 09:35:05,587 Thread-106 udi_interface ERROR udi_interface:write: Exception in thread 2023-01-20 09:35:05,587 Thread-106 udi_interface ERROR udi_interface:write: Thread-106 2023-01-20 09:35:05,587 Thread-106 udi_interface ERROR udi_interface:write: : 2023-01-20 09:35:05,587 Thread-106 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-01-20 09:35:05,587 Thread-106 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-01-20 09:35:05,588 Thread-106 udi_interface ERROR udi_interface:write: self.run() 2023-01-20 09:35:05,588 Thread-106 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-01-20 09:35:05,588 Thread-106 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-01-20 09:35:05,588 Thread-106 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_7/lifx-poly.py", line 206, in _discovery_process 2023-01-20 09:35:05,589 Thread-106 udi_interface ERROR udi_interface:write: devices = self.lifxLan.get_lights() 2023-01-20 09:35:05,589 Thread-106 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-20 09:35:05,589 Thread-106 udi_interface ERROR udi_interface:write: self.discover_devices() 2023-01-20 09:35:05,589 Thread-106 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-20 09:35:05,589 Thread-106 udi_interface ERROR udi_interface:write: responses = self.broadcast_with_resp(GetService, StateService,) 2023-01-20 09:35:05,589 Thread-106 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-20 09:35:05,590 Thread-106 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-20 09:35:05,590 Thread-106 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-20 09:35:05,590 Thread-106 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-20 09:35:05,590 Thread-106 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-20 09:35:05,590 Thread-106 udi_interface ERROR udi_interface:write: self.packed_message = self.generate_packed_message() 2023-01-20 09:35:05,591 Thread-106 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-20 09:35:05,591 Thread-106 udi_interface ERROR udi_interface:write: self.header = self.get_header() 2023-01-20 09:35:05,591 Thread-106 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-20 09:35:05,591 Thread-106 udi_interface ERROR udi_interface:write: frame_addr = self.get_frame_addr() 2023-01-20 09:35:05,591 Thread-106 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-20 09:35:05,591 Thread-106 udi_interface ERROR udi_interface:write: mac_addr = little_endian(bitstring.pack(mac_addr_format, convert_MAC_to_int(self.target_addr))) 2023-01-20 09:35:05,592 Thread-106 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-20 09:35:05,593 Thread-106 udi_interface ERROR udi_interface:write: s._addright(BitStream._init_with_token(name, length, value)) 2023-01-20 09:35:05,593 Thread-106 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-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: raise CreationError(f"Token with length {token_length} packed with value of length {b.len} " 2023-01-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: bitstring 2023-01-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: . 2023-01-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: CreationError 2023-01-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: : 2023-01-20 09:35:05,594 Thread-106 udi_interface ERROR udi_interface:write: Token with length 64 packed with value of length 0 (bits:64=0).

I redid the commands and copied the results. [polyglot@eisy /usr/home/admin]$ pip3 uninstall bitstring Found existing installation: bitstring 3.1.9 Uninstalling bitstring-3.1.9: Would remove: /var/polyglot/.local/lib/python3.9/site-packages/bitstring-3.1.9.dist-info/* /var/polyglot/.local/lib/python3.9/site-packages/bitstring.py Proceed (Y/n)? y Successfully uninstalled bitstring-3.1.9 [polyglot@eisy /usr/home/admin]$ pip3 install bitstring==3.1.9 Defaulting to user installation because normal site-packages is not writeable Collecting bitstring==3.1.9 Using cached bitstring-3.1.9-py3-none-any.whl (38 kB) Installing collected packages: bitstring Successfully installed bitstring-3.1.9 [polyglot@eisy /usr/home/admin]$

Please show how to display pip3 list. Thanks

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.

I'm using 86400 for the long poll.

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 ?