Hey Karl,
Sorry if this message seems a little confusing. I have 7 rPi's up and running for a while now, and all has been going well. However, I'm rebuilding an rPi, using the same IP address and hostname, and am getting the same timeout error.. Figured I'd dump all the oddities in here and see if we can sort this out together, but we can work this in whatever way may work for you.
Here's what's in the indigo log after I tried to add the pi back to the system.:
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)
and here's what's in piBeacon.log:
23:14:09 -pi= 2
23:14:09 -valuesDict= UiValuesDict : (dict)
MSG : Pi server configuration set (string)
beaconOrSensor : iBeacon and Sensor rPi (string)
confirmPiServer : (string)
confirmPiServerConfig : (string)
enablePiEntries : false (bool)
enableRebootCheck : restartLoop,- (string)
infoLabel11 : (string)
ipNumberPi : 10.10.10.102 (string)
passwordPi : pibeacon (string)
piOnOff : 1 (string)
piServerNumber : 2 (string)
userIdPi : pi (string)
23:14:09 -RPI= {u'piDevId': 860592566, u'userIdPi': u'pi', u'lastMessage': 1527789955.979258, u'passwordPi': u'pibeacon', u'piMAC': u'B8:27:EB:A2:03:A9', u'ipNumberPiSendTo': u'10.10.10.102', u'sendToIndigoSecs': 90, u'emptyMessages': 0, u'piUpToDate': [], u'piNumberReceived': u'2', u'input': {}, u'sensorRefreshSecs': 20, u'enableRebootCheck': u'restartLoop,-', u'deltaTime1': 100, u'piOnOff': u'1', u'deltaTime2': 0.5627121925354004, u'rssiOffset': 0, u'sensorList': '', u'ipNumberPi': u'10.10.10.102', u'output': {}, u'enableiBeacons': u'1', u'deltaChangedSensor': 5}
23:14:09 -fixConfig called from buttonConfirmPiServerConfigCALLBACK; with:['all', 'rpi']
Then the log stops updating anything regarding that rPi and goes on to logging other activities, like a new beacon discovered on some other device.
I'm seeing these errors for virtually all of my pi's, though I know that both the known hosts and the passwords are as expected. I even tried removing my authorized_keys file to see if there was something in there causing issues, but that had no impact.:
spawn sftp -o ConnectTimeout=15
pi@10.10.10.102pi@10.10.10.102's password:
Permission denied, please try again.
pi@10.10.10.102's password:
23:01:13 -setup pi response (2) error
Here's the output of piBeacon.log when I try to send an ls command to that rPi:
23:28:02 -send YOUR command to rpi 10.10.10.102; "[{\"cmdLine\": \"ls\", \"command\": \"general\"}]"
23:28:02 -error in socket-send to rPi:10.10.10.102 [{"cmdLine": "ls", "command": "general"}]
23:28:02 -line:6053; err:[Errno 61] Connection refused
Incidentally, I don't even see any entry in /var/log/auth.log on the raspberry pi, so I don't think it ever actually tries to ssh to the rPi.
As for the timeout errors, I'm getting them even when i try to update the logging level. I vaguely recall you mentioning in one of these support threads a while back that the tracking for expired/ignored beacons can sometimes cause timeouts if there are too many, and that we should trim/delete that list and just let it rebuild over time. I'm not sure if that's even relevant now, with all of your updates and, if so, where/how to do so anymore. lol
I just tried to disable and enable this new pi in Initial BASIC setup options, got the timeout, but when I reloaded, the action appeared to have succeeded. But again, I see this in the Indigo logs:
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)
So, I think all of these issues are loosely related, but I just haven't figured out the connection just yet, but these timeouts seem pretty suspicious.
Any thoughts on where to start with this one?
thanx in advance, as always
~ken