Pimatic crashes every 4h without any hind for the reason

OrTiN

Hey guys,
I deleted my last topic, because it was more confusion, than informative. Tonight my system was down once more. That is the 4th time it stops working after round about 4h.

This is the current log:

22:55:02.832 2017-01-09 Monday
22:55:07.682 [pimatic] info: Starting pimatic version 0.9.38
22:55:10.802 [pimatic, ppm] info: 2.15.11
22:55:10.848 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
22:55:11.273 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.11)
22:55:11.885 [pimatic] info: Loading plugin: "pimatic-iframe" (0.2.0)
22:55:11.916 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4)
22:55:11.971 [pimatic] info: Loading plugin: "pimatic-pushbullet" (0.9.0)
22:55:12.525 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7)
22:55:12.558 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4)
22:55:12.700 [pimatic] info: Loading plugin: "pimatic-gpio" (0.8.15)
22:55:12.768 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5)
22:55:12.808 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.8)
22:55:12.841 [pimatic] info: Loading plugin: "pimatic-filebrowser" (0.9.0)
22:55:12.953 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11)
22:55:13.562 [pimatic] info: Loading plugin: "pimatic-mqtt" (0.9.5)
22:55:14.194 [pimatic] info: Loading plugin: "pimatic-links" (0.8.6)
22:55:14.219 [pimatic] info: Loading plugin: "pimatic-log-reader" (0.9.1)
22:55:14.256 [pimatic] info: Loading plugin: "pimatic-metar-weather" (0.9.1)
22:55:14.817 [pimatic-cron] info: the time is: Mon Jan 09 2017 22:55:14 GMT+0100 (CET)
22:55:15.018 [pimatic-pushbullet] debug: apikey= xxxxxxxxxxxxxxxxxxxxxxxx
22:55:15.022 [pimatic-sunrise] info: Your location is set to lat: xxxxxxxxxx, long: xxxxxxxxxx
22:55:15.875 [pimatic-mqtt] info: Successfully connected to MQTT Broker default
22:55:16.009 [pimatic] info: New device "ESPEasy Sonne MQTT"...
22:55:16.049 [pimatic] info: New device "Daniel's Handy"...
22:55:16.080 [pimatic] info: New device "Brina's Handy"...
22:55:16.098 [pimatic] info: New device "Link Einfahrt"...
22:55:16.117 [pimatic] info: New device "Link Terrasse"...
22:55:16.130 [pimatic] info: New device "ESPeasy Sonne"...
22:55:16.176 [pimatic] info: New device "Jalousien Alle"...
22:55:16.192 [pimatic] info: New device "Jalousien Alle, außer Schlaf & Kinderzimmer"...
22:55:16.208 [pimatic] info: New device "Jalousien Schlaf & Kinderzimmer"...
22:55:16.227 [pimatic] info: New device "Jalousien Westen"...
22:55:16.246 [pimatic] info: New device "Jalousien Süden"...
22:55:16.261 [pimatic] info: New device "Jalousien Osten"...
22:55:16.276 [pimatic] info: New device "Galerielicht"...
22:55:16.290 [pimatic] info: New device "Lüften"...
22:55:16.306 [pimatic] info: New device "Zirkulationspumpe"...
22:55:16.331 [pimatic] info: New device "Zirkulationspumpenstatus"...
22:55:16.364 [pimatic] info: New device "Temperaturfühler-Bad nativ"...
22:55:16.445 [pimatic] info: New device "OpenWeather aktuell"...
22:55:16.483 [pimatic] info: New device "Temperaturfühler Adrian nativ"...
22:55:16.510 [pimatic] info: New device "Temperaturfühler Wohnzimmer nativ"...
22:55:16.537 [pimatic] info: New device "Temperaturfühler Kühlschrank nativ"...
22:55:16.575 [pimatic] info: New device "Sonnensensor"...
22:55:16.619 [pimatic] info: New device "System"...
22:55:16.666 [pimatic] info: New device "Systemzeit"...
22:55:16.716 [pimatic] info: New device "Systemlaufzeit"...
22:55:16.744 [pimatic] info: New device "CPU"...
22:55:16.773 [pimatic] info: New device "Systemspeicher"...
22:55:16.795 [pimatic] info: New device "Festplattenspeicher"...
22:55:16.868 [pimatic] info: New device "pimatic Version"...
22:55:16.906 [pimatic] info: New device "Pimatic Version Abfrage"...
22:55:16.926 [pimatic] info: New device "pimatic Update Info"...
22:55:16.942 [pimatic] info: New device "Einfahrt"...
22:55:16.977 [pimatic] info: New device "Terrasse"...
22:55:17.029 [pimatic] info: New device "Terrassentür"...
22:55:17.052 [pimatic] info: New device "Vollsonnenschutz 50%"...
22:55:17.067 [pimatic] info: New device "Vollsonnenschutz 75%"...
22:55:17.081 [pimatic] info: New device "Sonnenschutz Schlaf & Kinderzimmer"...
22:55:17.094 [pimatic] info: New device "Sonnenschutz Osten"...
22:55:17.108 [pimatic] info: New device "Sonnenschutz Westen"...
22:55:17.127 [pimatic] info: New device "Sonnenschutzautomatik"...
22:55:17.145 [pimatic] info: New device "Sonnenschutz manuell"...
22:55:17.178 [pimatic] info: New device "Zeitstempel Einfahrt"...
22:55:17.214 [pimatic] info: New device "Zeitstempel Terrasse"...
22:55:17.250 [pimatic] info: New device "Einfahrt Aufzeichungsgröße"...
22:55:17.290 [pimatic] info: New device "Terrasse Aufzeichungsgröße"...
22:55:17.316 [pimatic] info: New device "Außenbedingungen"...
22:55:17.336 [pimatic] info: New device "ESPeasy Sonne Systemlaufzeit intern"...
22:55:17.353 [pimatic] info: New device "Lichtsensor"...
22:55:17.396 [pimatic] info: New device "ESPeasy Sonne Systemlaufzeit"...
22:55:17.442 [pimatic] info: New device "Sonnenverlauf"...
22:55:17.564 [pimatic] info: New device "Temperaturfühler Schlafzimmer nativ"...
22:55:17.583 [pimatic] info: New device "Terrassenlicht"...
22:55:17.611 [pimatic] info: New device "Galerie DummyDimmer"...
22:55:17.633 [pimatic] info: New device "Terrasse DummyDimmer"...
22:55:17.656 [pimatic] info: New device "Zirkulationspumpe DummySwitch"...
22:55:17.676 [pimatic] info: New device "Gaszählerimpuls"...
22:55:17.678 [pimatic] warn: The device type GpioContact does not implement a destroy function
22:55:17.704 [pimatic] info: New device "Gasverbrauch"...
22:55:17.736 [pimatic] info: New device "Stromverbrauch"...
22:55:17.759 [pimatic] info: New device "Klingel"...
22:55:17.779 [pimatic] info: New device "Temperaturfühler Aquarium"...
22:55:17.795 [pimatic] info: New device "Sonnenschutz Süd+"...
22:55:17.819 [pimatic] info: New device "Mama's Handy"...
22:55:17.852 [pimatic] info: New device "Garagentore"...
22:55:17.865 [pimatic] info: New device " ESPeasy Aquarium"...
22:55:17.884 [pimatic] info: New device "Temperaturfühler Wohnzimmer"...
22:55:17.915 [pimatic] info: New device "Temperaturfühler Adrian"...
22:55:17.952 [pimatic] info: New device "Temperaturfühler Schlafzimmer"...
22:55:17.983 [pimatic] info: New device "Temperaturfühler Bad"...
22:55:18.005 [pimatic] info: New device "Temperaturfühler Kühlschrank"...
22:55:18.025 [pimatic] info: New device "Dimmerstatus"...
22:55:18.044 [pimatic] info: New device "Jarolift Wandsender anlernen"...
22:55:18.078 [pimatic] info: New device "VZLogger Strom"...
22:55:18.118 [pimatic] info: New device "ESPeasy Aquarum Systemlaufzeit"...
22:55:18.138 [pimatic] info: New device "ESPeasy Aquarium Systemlaufzeit intern"...
22:55:18.159 [pimatic] info: New device "Gaskorrektur"...
22:55:18.183 [pimatic] info: New device "Beleuchtung Vorgarten"...
22:55:18.197 [pimatic] info: New device "HP Spectre"...
(node) warning: possible EventEmitter memory leak detected. 201 variableRemoved listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at VariableManager.addListener (events.js:239:17)
    at VariablePredicateHandler.PredicateHandler.dependOnVariable (/home/pi/pimatic-app/node_modules/pimatic/lib/predicates.coffee:63:23)
    at VariablePredicateHandler.setup (/home/pi/pimatic-app/node_modules/pimatic/lib/predicates.coffee:625:10)
    at /home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:590:21
    at RuleManager._addPredicateChangeListener (/home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:587:9)
    at /home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:711:10
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:510:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:604:10)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
22:55:56.369 [pimatic, VariablesDevice] error: Error getting attribute value sonnensensor.ds18b20-differenz: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
22:55:56.389 [pimatic] warn: Could not update variable sonnensensor.ds18b20-differenz: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
22:55:56.825 [pimatic] info: rule relaisboard-initialisieren: ausführen "sh /home/pi/Homation/initHomation.sh": 
22:55:57.395 [pimatic-mobile-frontend] info: packing static assets
22:55:58.150 [pimatic-mobile-frontend] info: packing static assets finished
22:55:58.156 [pimatic-mobile-frontend] info: rendering html
22:56:01.737 [pimatic-homeduino] info: Connected to homeduino device.
22:56:05.641 [pimatic-mobile-frontend] info: rendering html finished
22:56:05.736 [pimatic] info: Listening for HTTP-request on port 80...
Unhandled rejection Error: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
    at /home/pi/pimatic-app/node_modules/pimatic/lib/variables-ast-builder.coffee:111:21
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:510:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:612:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:691:18)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
02:55:59.129 [pimatic-shell-execute] error: [ShellActionHandler] Error: Command failed: /bin/sh -c sudo sh /home/pi/Homation/vzlogger.sh >/dev/null 2>&1
02:55:59.129 [pimatic-shell-execute] error:>
02:56:08.589 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:19.374 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.311 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.358 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.359 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.361 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.362 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.364 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.365 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.367 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.369 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.436 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.438 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.439 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.442 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.443 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.445 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.447 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.450 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
02:56:33.536 [pimatic] error: Error on evaluation of rule condition of rule stromzaehler-auslesen: undefined
02:56:33.539 [pimatic] error: rule stromzaehler-auslesen error executing an action: undefined
07:33:17.466 2017-01-10 Tuesday
07:33:27.740 [pimatic] info: Starting pimatic version 0.9.38
07:33:39.911 [pimatic, ppm] info: 2.15.11
07:33:39.955 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
07:33:40.487 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.11)
07:33:41.321 [pimatic] info: Loading plugin: "pimatic-iframe" (0.2.0)
07:33:41.355 [pimatic] info: Loading plugin: "pimatic-openweather" (0.9.4)
07:33:41.428 [pimatic] info: Loading plugin: "pimatic-pushbullet" (0.9.0)
07:33:42.182 [pimatic] info: Loading plugin: "pimatic-sunrise" (0.8.7)
07:33:42.222 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.4)
07:33:42.383 [pimatic] info: Loading plugin: "pimatic-gpio" (0.8.15)
07:33:42.465 [pimatic] info: Loading plugin: "pimatic-ping" (0.9.5)
07:33:42.526 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.8)
07:33:42.566 [pimatic] info: Loading plugin: "pimatic-filebrowser" (0.9.0)
07:33:42.722 [pimatic] info: Loading plugin: "pimatic-homeduino" (0.9.11)
07:33:43.490 [pimatic] info: Loading plugin: "pimatic-mqtt" (0.9.5)
07:33:44.274 [pimatic] info: Loading plugin: "pimatic-links" (0.8.6)
07:33:44.302 [pimatic] info: Loading plugin: "pimatic-log-reader" (0.9.1)
07:33:44.356 [pimatic] info: Loading plugin: "pimatic-metar-weather" (0.9.1)
07:33:46.390 [pimatic-cron] info: the time is: Tue Jan 10 2017 07:33:46 GMT+0100 (CET)
07:33:46.607 [pimatic-pushbullet] debug: apikey= xxxxxxxxxxxxxxxxxxxxxxxx
07:33:46.611 [pimatic-sunrise] info: Your location is set to lat: xxxxxxxxxx, long: xxxxxxxxxx
07:33:47.575 [pimatic-mqtt] info: Successfully connected to MQTT Broker default
07:33:47.714 [pimatic] info: New device "ESPEasy Sonne MQTT"...
07:33:47.758 [pimatic] info: New device "Daniel's Handy"...
07:33:47.786 [pimatic] info: New device "Brina's Handy"...
07:33:47.801 [pimatic] info: New device "Link Einfahrt"...
07:33:47.821 [pimatic] info: New device "Link Terrasse"...
07:33:47.835 [pimatic] info: New device "ESPeasy Sonne"...
07:33:47.853 [pimatic] info: New device "Jalousien Alle"...
07:33:47.905 [pimatic] info: New device "Jalousien Alle, außer Schlaf & Kinderzimmer"...
07:33:47.922 [pimatic] info: New device "Jalousien Schlaf & Kinderzimmer"...
07:33:47.951 [pimatic] info: New device "Jalousien Westen"...
07:33:47.969 [pimatic] info: New device "Jalousien Süden"...
07:33:47.984 [pimatic] info: New device "Jalousien Osten"...
07:33:47.999 [pimatic] info: New device "Galerielicht"...
07:33:48.013 [pimatic] info: New device "Lüften"...
07:33:48.029 [pimatic] info: New device "Zirkulationspumpe"...
07:33:48.054 [pimatic] info: New device "Zirkulationspumpenstatus"...
07:33:48.084 [pimatic] info: New device "Temperaturfühler-Bad nativ"...
07:33:48.165 [pimatic] info: New device "OpenWeather aktuell"...
07:33:48.205 [pimatic] info: New device "Temperaturfühler Adrian nativ"...
07:33:48.233 [pimatic] info: New device "Temperaturfühler Wohnzimmer nativ"...
07:33:48.261 [pimatic] info: New device "Temperaturfühler Kühlschrank nativ"...
07:33:48.291 [pimatic] info: New device "Sonnensensor"...
07:33:48.333 [pimatic] info: New device "System"...
07:33:48.380 [pimatic] info: New device "Systemzeit"...
07:33:48.431 [pimatic] info: New device "Systemlaufzeit"...
07:33:48.454 [pimatic] info: New device "CPU"...
07:33:48.485 [pimatic] info: New device "Systemspeicher"...
07:33:48.512 [pimatic] info: New device "Festplattenspeicher"...
07:33:50.903 [pimatic] info: New device "pimatic Version"...
07:33:50.953 [pimatic] info: New device "Pimatic Version Abfrage"...
07:33:50.973 [pimatic] info: New device "pimatic Update Info"...
07:33:50.998 [pimatic] info: New device "Einfahrt"...
07:33:51.031 [pimatic] info: New device "Terrasse"...
07:33:51.063 [pimatic] info: New device "Terrassentür"...
07:33:51.099 [pimatic] info: New device "Vollsonnenschutz 50%"...
07:33:51.121 [pimatic] info: New device "Vollsonnenschutz 75%"...
07:33:51.137 [pimatic] info: New device "Sonnenschutz Schlaf & Kinderzimmer"...
07:33:51.150 [pimatic] info: New device "Sonnenschutz Osten"...
07:33:51.167 [pimatic] info: New device "Sonnenschutz Westen"...
07:33:51.185 [pimatic] info: New device "Sonnenschutzautomatik"...
07:33:51.200 [pimatic] info: New device "Sonnenschutz manuell"...
07:33:51.230 [pimatic] info: New device "Zeitstempel Einfahrt"...
07:33:51.264 [pimatic] info: New device "Zeitstempel Terrasse"...
07:33:51.297 [pimatic] info: New device "Einfahrt Aufzeichungsgröße"...
07:33:51.335 [pimatic] info: New device "Terrasse Aufzeichungsgröße"...
07:33:51.361 [pimatic] info: New device "Außenbedingungen"...
07:33:51.382 [pimatic] info: New device "ESPeasy Sonne Systemlaufzeit intern"...
07:33:51.398 [pimatic] info: New device "Lichtsensor"...
07:33:51.439 [pimatic] info: New device "ESPeasy Sonne Systemlaufzeit"...
07:33:51.487 [pimatic] info: New device "Sonnenverlauf"...
07:33:52.068 [pimatic] info: New device "Temperaturfühler Schlafzimmer nativ"...
07:33:52.087 [pimatic] info: New device "Terrassenlicht"...
07:33:52.111 [pimatic] info: New device "Galerie DummyDimmer"...
07:33:52.134 [pimatic] info: New device "Terrasse DummyDimmer"...
07:33:52.158 [pimatic] info: New device "Zirkulationspumpe DummySwitch"...
07:33:52.181 [pimatic] info: New device "Gaszählerimpuls"...
07:33:52.183 [pimatic] warn: The device type GpioContact does not implement a destroy function
07:33:52.214 [pimatic] info: New device "Gasverbrauch"...
07:33:52.247 [pimatic] info: New device "Stromverbrauch"...
07:33:52.272 [pimatic] info: New device "Klingel"...
07:33:52.295 [pimatic] info: New device "Temperaturfühler Aquarium"...
07:33:52.311 [pimatic] info: New device "Sonnenschutz Süd+"...
07:33:52.336 [pimatic] info: New device "Mama's Handy"...
07:33:52.353 [pimatic] info: New device "Garagentore"...
07:33:52.389 [pimatic] info: New device " ESPeasy Aquarium"...
07:33:52.408 [pimatic] info: New device "Temperaturfühler Wohnzimmer"...
07:33:52.439 [pimatic] info: New device "Temperaturfühler Adrian"...
07:33:52.474 [pimatic] info: New device "Temperaturfühler Schlafzimmer"...
07:33:52.508 [pimatic] info: New device "Temperaturfühler Bad"...
07:33:52.531 [pimatic] info: New device "Temperaturfühler Kühlschrank"...
07:33:52.552 [pimatic] info: New device "Dimmerstatus"...
07:33:52.570 [pimatic] info: New device "Jarolift Wandsender anlernen"...
07:33:52.609 [pimatic] info: New device "VZLogger Strom"...
07:33:52.647 [pimatic] info: New device "ESPeasy Aquarum Systemlaufzeit"...
07:33:52.667 [pimatic] info: New device "ESPeasy Aquarium Systemlaufzeit intern"...
07:33:52.698 [pimatic] info: New device "Gaskorrektur"...
07:33:52.722 [pimatic] info: New device "Beleuchtung Vorgarten"...
07:33:52.736 [pimatic] info: New device "HP Spectre"...
(node) warning: possible EventEmitter memory leak detected. 201 variableRemoved listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at VariableManager.addListener (events.js:239:17)
    at VariablePredicateHandler.PredicateHandler.dependOnVariable (/home/pi/pimatic-app/node_modules/pimatic/lib/predicates.coffee:63:23)
    at VariablePredicateHandler.setup (/home/pi/pimatic-app/node_modules/pimatic/lib/predicates.coffee:625:10)
    at /home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:590:21
    at RuleManager._addPredicateChangeListener (/home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:587:9)
    at /home/pi/pimatic-app/node_modules/pimatic/lib/rules.coffee:711:10
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:510:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:604:10)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:138:12)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
07:34:31.772 [pimatic, VariablesDevice] error: Error getting attribute value sonnensensor.ds18b20-differenz: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
07:34:31.793 [pimatic] warn: Could not update variable sonnensensor.ds18b20-differenz: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
07:34:32.226 [pimatic] info: rule relaisboard-initialisieren: ausführen "sh /home/pi/Homation/initHomation.sh": 
07:34:32.849 [pimatic-mobile-frontend] info: packing static assets
07:34:33.785 [pimatic-mobile-frontend] info: packing static assets finished
07:34:33.791 [pimatic-mobile-frontend] info: rendering html
07:34:36.550 [pimatic-homeduino] info: Connected to homeduino device.
07:34:42.427 [pimatic-mobile-frontend] info: rendering html finished
07:34:42.575 [pimatic] info: Listening for HTTP-request on port 80...
Unhandled rejection Error: Expected variable espeasy-sonne_mqtt.espeasy-sonne-temp_high to have a numeric value.
    at /home/pi/pimatic-app/node_modules/pimatic/lib/variables-ast-builder.coffee:111:21
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:510:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:612:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:691:18)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

At 22:55 I started the system. Everything works fine. My lights, shutters… were able to be controlled by pimatic.
What I did before the problem occurred was to update pimatic from 0.9.37 to 0.9.38 and apt-get update/upgrade to update Raspbian.

What I can see is, that the problem starts with [pimatic-shell-execute]. The shell vzlogger.sh will be started every 30 seconds. A restart of pimatic does not solve the problem. I must reboot the raspberry!

Hope somebody can help. I have backups but I hope it can be solved without going on a backuped image.

leader21

maybe raise the max number of events for the eventemitter.
you can read more here
https://github.com/pimatic/pimatic/issues/955

so try to add this to your settings section of the config :
"defaultMaxListeners" : 300

mwittig

I suspect this is a kind of overflow issue on the system.
Please check system logs for error messages like “out of memory” and “out of file descriptors” (or similar)

OrTiN

The reason really seems to be an overflow. The problem occurs because my electric house meter was hanging it was totally dead, but my house had power. I’ve never seen such a behavior.
It was necessary to ask for a technician from the local energie supplier. He resets the meter.
Due to the hanging of the meter my vzlogger.sh script was not able to request the data. Unfortunately the script does not stop. It was running and after 30s the next one starts to do the same. After a while the stack seems to be overflowed and pimatic began to hang. The raspi was still available via ssh.

@leader21: I will try your hint

Has someone an idea how to config vzlogger in that form, that a request for data will be stopped when the the energy meter does not send any data?

Here the vzlogger.conf

{
"retry" : 15,                   /* how long to sleep between failed requests, in seconds */
"daemon": false,                /* run periodically */
"verbosity" : 15,               /* between 0 and 15 */
"log" : "/home/pi/volkszaehler/vzlogger/log/vzlogger.log",/* path to logfile, optional */

"local" : {
        "enabled" : false,      /* should we start the local HTTPd for serving live readings? */
        "port" : 8080,            /* the TCP port for the local HTTPd */
        "index" : true,         /* should we provide a index listing of available channels? */
        "timeout" : 30,         /* timeout for long polling comet requests, 0 disables comet, in seconds */
        "buffer" : 30 /* 600          /* how long to buffer readings for the local interface, in seconds */
},

"meters" : [{
        "enabled" : true,       /* disabled meters will be ignored */
        "protocol" : "sml",     /* use 'vzlogger -h' for list of available protocols */
        "device" : "/dev/usb-ir-lesekopf0",
        }
]}

mwittig

@OrTiN Interesting. Looks like your smartmeter needs a firmware update

Has someone an idea how to config vzlogger in that form, that a request for data will be stopped when the the energy meter does not send any data?

No idea, as I am not familiar with vz.
As a work-around you could write a wrapper script which calls vzlogger.sh with the timeout command (if it is not installed on your system, install the coreutils package) as follows.

#!/bin/bash
timeout 30s /home/pi/volkszaehler/vzlogger/bin/vzlogger.sh

You could also send a specific signal to the sub process to terminate on timeout. See for details https://linux.die.net/man/1/timeout

leader21

you can contact andreas goetz / andig from the vz project regarding your question.
he has written the volkszaehler plugin and is very active at the vz project.

OrTiN

Thx, I will contact him.

OrTiN

He guys,
since days everything works fine now. I changed from executing the command “timeout 5s vzlogger -c /home/pi/volkszaehler/vzlogger/etc/vzlogger.conf” by a separate shell script, now to executing by pimatic direct from a rule.

      "rule": "when every 60 seconds then execute \"vzlogger -c /home/pi/volkszaehler/vzlogger/etc/vzlogger.conf >/home/pi/Homation/log/vzloggerPoll.log 2>&1\"",

Now I have a question. Will the shell plugin kill commands after a while without responds or is it better to put a “timeout n” in front of the command?

      "rule": "when every 60 seconds then timeout 5s execute \"vzlogger -c /home/pi/volkszaehler/vzlogger/etc/vzlogger.conf >/home/pi/Homation/log/vzloggerPoll.log 2>&1\"",

I want to avoid that when the energie meter will not respond once more pimatic will get into trouble and the whole system starts to hang like last week.

OrTiN

Did nobody know this?

V1per

I think had the same issue as you for a few month. In my case it was that the script I periodic called from pimatic not Closes himself, so I have this script verry often in the Prozess opened and after a few hours there is no Memory and the System crashed.

You can check this when you half an hour after starting pimatic log in with ssh and write:

top

then all Prozesses are listet and when your script is listet more as one times that is your issue.

My solution was that I wrote a second script who called the first script and killes the called script after a few seconds.

OrTiN

Hi,
therefore I put there a timeout before the command. This kills the command after 5s. The script has normally a max runtime of 2 seconds. When it happens that the script is still running and will be killed by the timeout I’m getting a message in the pimatic log.
I am wondering if the execute function kills a not working script by itself after a while, because it seems that it is observing the executed shript somehow? Maybe I’m wrong…