Indigo Domotics

Never seen this before, though it MIGHT be due to the whole M1 mini seemingly choking for a minute and becoming unresponsive. I just upgraded from 2021 and to the M1 mini yesterday.

Code: Select all

uniFiAP Error                   Expecting ',' delimiter: line 2424 column 2 (char 33712); line#,Module,Statement:(353, 'raw_decode', 'obj, end = self.scan_once(s, idx)')
   uniFiAP                         checkAndPrepDict JSON len:65923; _be_more_precise": true,"child_devices_count": 2,"child_virtual_devices_count": 3,"created_at": "201...
...  rxBytes": 35076,xxxThisIsTheEndTokenxxx3
   uniFiAP                         .... in receiving DICTs for UDdict-192.168.0.1;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 2022.1/Logs/com.karlwachs.uniFiAP/plugin.log


log says

Code: Select all

# <<<<
2022-08-24 16:16:04 testServerIfOK: =========== known prompts:
{'192.168.0.123': '1# ', '192.168.0.1': '# '}
2022-08-24 16:16:04 getMessage, error reading dict >UDdict-192.168.0.1<, not complete? len(data)69161, endTokenPos:69191; error:Expecting ',' delimiter: line 4271 column 2 (char 69161) ---- retrying
2022-08-24 16:16:08.346   ERROR          Plugin.checkAndPrepDict          Expecting ',' delimiter: line 2424 column 2 (char 33712); line#,Module,Statement:(353, 'raw_decode', 'obj, end = self.scan_once(s, idx)')
2022-08-24 16:16:19 testServerIfOK: =========== 192.168.0.1; prompt not found or reset by restart;  old:'\# ', new candidate:'
# '
2022-08-24 16:16:19 testServerIfOK: =========== for 192.168.0.1  ssh response, setting promp to:'# ' using last 2 chars in ...****************

# <<<<
2022-08-24 16:16:19 testServerIfOK: =========== known prompts:
{'192.168.0.123': '1# ', '192.168.0.1': '# '}
2022-08-24 16:16:20 checkAndPrepDict JSON len:65923; _be_more_precise": true,"child_devices_count": 2,"child_virtual_devices_count": 3,"created_at": "201...
...  rxBytes": 35076,xxxThisIsTheEndTokenxxx3
2022-08-24 16:16:20 .... in receiving DICTs for UDdict-192.168.0.1;  for details check unifi logfile  at: /Library/Application Support/Perceptive Automation/Indigo 2022.1/Logs/com.karlwachs.uniFiAP/plugin.log
2022-08-24 16:16:20 .... ping test:   ok
2022-08-24 16:16:20 .... ssh test:    ok
2022-08-24 16:16:20 .... uid/passwd:>('root', 'hBe-yzs-f7n-FTq')<
2022-08-24 16:16:28 getMessages: relaunching dictLoop.exp / UDdict / 192.168.0.1: code:0; timeSinceLastRestart 233 > forcedRestart:999999999 [sec]  ;  without message:136.3[sec], limitforRestart:135.0[sec], restartCount:0,  len(msg):62067; lastMSG:: 6601818,"txPackets": 94086},{"app": 15,"cat": 13,"rxBytes": 35076,xxxThisIsTheEndTokenxxx3<<
2022-08-24 16:16:38 testServerIfOK: =========== 192.168.0.1; prompt not found or reset by restart;  old:'\# ', new candidate:'
# '
2022-08-24 16:16:38 testServerIfOK: =========== for 192.168.0.1  ssh response, setting promp to:'# ' using last 2 chars in ...****************



that looks like the response from the unifi device is not complete.

it might happen once or twice, but if it repeats SOMETHING is wrong.

eg here
... rxBytes": 35076,xxxThisIsTheEndTokenxxx3
the json is not complete the "end token" = ",xxxThisIsTheEndTokenxxx" comes in the middle of the json.


that is all I can say from that.


Karl

Thanks Karl.

Haven't seen it again, so I'll assume it was new setup glitches for now.