Closed dsaaltink closed 7 years ago
@dsaaltink Can you please share your log file and the version you are using? Also the command line options used will be helpful
Sorry for the delay. After the error bellow nothing is working anymore. Need to reset the raspberry. Version 1.4.0
[Tue May 2 19:18:54 2017] 05/02/17 19:18:53 | ps02 | movement woonkamer [Tue May 2 19:24:11 2017] 05/02/17 19:24:09 | ps02 | movement woonkamer [Tue May 2 19:24:59 2017] ERROR | UNKNOWN | 05/02/17 19:24:59 ('Connection aborted.', error(104, 'Connection reset by peer')) [Tue May 2 19:25:00 2017] Gigaset Elements - Command-line Interface [Tue May 2 19:25:00 2017] Configuration | LOADED | /usr/etc/gigasetelements-cli.conf [Tue May 2 19:25:01 2017] Identity | VERIFIED | User logged in successfully. [Tue May 2 19:25:02 2017] Authentication | SUCCESS | [Tue May 2 19:25:04 2017] Basestation | ONLINE | 915BE0032A2B0798FB16678FEB871270 [Tue May 2 19:25:04 2017] Status | GREEN | Modus set from HOME to HOME [Tue May 2 19:25:05 2017] Notification | TOKEN | [Tue May 2 19:25:05 2017] Run as background | DAEMON | /tmp/gigasetelements-cli.pid
@dsaaltink I suggest to upgrade to the develop version to see if this helps.
@dsaaltink Any luck so far?
Cannot replicate using develop branch. Considering this resolved through commits fa23a5b, e3a0f3d and 6beca38
After some day's (2/3) I see an error 104 in the logfile. So no monitoring of gigaset elements anymore and need to reboot the raspberry. Restart Cli will not fix it.