NEWS
[gefixt] Parser-Adapter (1.0.3) stürzt ab
-
Ich verwende den Parser-Adpater zum Einlesen der Temperaturwerte einer DS1820-Sensoren
Nun habe ich gerade auf die aktuelle Version 1.0.3 des Parser-Adapters (von 1.0.2) aktualisiert.
Die bislang funktionstüchtige Konfiguration habe ich dabei nicht geändert.
Nach der Aktualisierung stürzt der Adapter allerdings hart ab (Ausgaben im Debug-Modus):
host.ioBroker-RasPi 2018-08-10 21:16:00.388 error instance system.adapter.parser.0 terminated with code 0 (OK) Caught 2018-08-10 21:16:00.387 error by controller[0]: at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21) Caught 2018-08-10 21:16:00.387 error by controller[0]: at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:265:49) Caught 2018-08-10 21:16:00.387 error by controller[0]: at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4332:61 Caught 2018-08-10 21:16:00.386 error by controller[0]: at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.parser/main.js:351:21) Caught 2018-08-10 21:16:00.386 error by controller[0]: at poll (/opt/iobroker/node_modules/iobroker.parser/main.js:319:9) Caught 2018-08-10 21:16:00.386 error by controller[0]: at readLink (/opt/iobroker/node_modules/iobroker.parser/main.js:294:13) Caught 2018-08-10 21:16:00.386 error by controller[0]: at readLink (/opt/iobroker/node_modules/iobroker.parser/main.js:319:54) Caught 2018-08-10 21:16:00.385 error by controller[0]: at analyseDataForStates (/opt/iobroker/node_modules/iobroker.parser/main.js:145:5) Caught 2018-08-10 21:16:00.385 error by controller[0]: at _analyseDataForStates (/opt/iobroker/node_modules/iobroker.parser/main.js:127:9) Caught 2018-08-10 21:16:00.385 error by controller[0]: at analyseData (/opt/iobroker/node_modules/iobroker.parser/main.js:195:29) Caught 2018-08-10 21:16:00.384 error by controller[0]: TypeError: (data || "").replace is not a function parser.0 2018-08-10 21:16:00.358 info terminating parser.0 2018-08-10 21:15:59.849 error at normal_reply (/opt/iobroker/node_modules/redis/index.js:726:21) parser.0 2018-08-10 21:15:59.849 error at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:265:49) parser.0 2018-08-10 21:15:59.849 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4332:61 parser.0 2018-08-10 21:15:59.849 error at adapter.getForeignStates (/opt/iobroker/node_modules/iobroker.parser/main.js:351:21) parser.0 2018-08-10 21:15:59.849 error at poll (/opt/iobroker/node_modules/iobroker.parser/main.js:319:9) parser.0 2018-08-10 21:15:59.849 error at readLink (/opt/iobroker/node_modules/iobroker.parser/main.js:294:13) parser.0 2018-08-10 21:15:59.849 error at readLink (/opt/iobroker/node_modules/iobroker.parser/main.js:319:54) parser.0 2018-08-10 21:15:59.849 error at analyseDataForStates (/opt/iobroker/node_modules/iobroker.parser/main.js:145:5) parser.0 2018-08-10 21:15:59.849 error at _analyseDataForStates (/opt/iobroker/node_modules/iobroker.parser/main.js:127:9) parser.0 2018-08-10 21:15:59.849 error at analyseData (/opt/iobroker/node_modules/iobroker.parser/main.js:195:29) parser.0 2018-08-10 21:15:59.849 error TypeError: (data || "").replace is not a function parser.0 2018-08-10 21:15:59.848 error uncaught exception: (data || "").replace is not a function parser.0 2018-08-10 21:15:59.824 debug analyseData CHECK for parser.0.Temp_KiZi_1_b, old=25.700000000000003 parser.0 2018-08-10 21:15:59.820 debug Process ["parser.0.Temp_KiZi_1_b"] for link /sys/bus/w1/devices/10-000802c38ff9/w1_slave parser.0 2018-08-10 21:15:58.939 debug Read file: /sys/bus/w1/devices/10-000802c38ff9/w1_slave parser.0 2018-08-10 21:15:58.937 debug Do Link: /sys/bus/w1/devices/10-000802c38ff9/w1_slave parser.0 2018-08-10 21:15:58.936 debug States for current Interval (10000): ["parser.0.Temp_KiZi_1_b","parser.0.Temp_KiZi_1_a","parser.0.Temp_KiZi_1_w"] parser.0 2018-08-10 21:15:58.798 info starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.parser, node: v8.11.3
Hat jemand eine Idee, an was das liegen kann?
-
Dazu existiert beteits ein issue suf github
Gruß Rainer
-
Dazu existiert beteits ein issue suf github `
Danke für die Info.Und scheint auch in 1.0.4 gefixt zu sein.