Test : Wasserenthärtung judo i-soft plus Adapter

oranggila

@arteck said in Test : Wasserenthärtung judo i-soft plus Adapter:

@oranggila ja

Härtegrad einstellen erfolgreich getestet. Vielen Dank dafür!

mpenno

Hallo,

seit Sonntag läuft der Adapter ohne Neustart. Im auf "silly" gestelltem Log gibt es immer diesen Block an Einträgen, passend zum eingestelltem Polling-Intervall:

2021-02-03 04:13:32 judoisoft.0 (1228) get Consumption data 
2021-02-03 04:13:35 judoisoft.0 (1228) -> WaterCurrent
2021-02-03 04:13:37 judoisoft.0 (1228) -> ResidualHardness
2021-02-03 04:13:37 judoisoft.0 (1228) States user redis pmessage judoisoft.0.ResidualHard
ness/judoisoft.0.ResidualHardness:{"val":"8","ack":true,"ts":1612322017779,"q":0,"from":"system.adapter.judoisoft.0"," user":"system.user.admin","lc":1610288716907}
2021-02-03 04:13:37 judoisoft.0 (1228) --> stateID judoisoft.0.ResidualHardness changed: 8 (ack = true)
2021-02-03 04:13:39 judoisoft.0 (1228) -> SaltRange
2021-02-03 04:13:41 judoisoft.0 (1228) -> SaltQuantity
2021-02-03 04:13:43 judoisoft.0 (1228) -> WaterAverage
2021-02-03 04:13:45 judoisoft.0 (1228) -> NaturalHardness
2021-02-03 04:13:47 judoisoft.0 (1228) -> FlowRate
2021-02-03 04:13:49 judoisoft.0 (1228) -> Quantity
2021-02-03 04:13:51 judoisoft.0 (1228) -> WaterTotaal  265410 170582
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.01 10953 10953
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.02 536 536
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.03 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.04 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.05 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.06 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.07 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.08 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.09 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.10 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.11 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) WaterYearly.12 -1 -1
2021-02-03 04:13:53 judoisoft.0 (1228) -> WaterYearly
2021-02-03 04:13:56 judoisoft.0 (1228) -> StandBy
2021-02-03 04:13:58 judoisoft.0 (1228) -> ValveState
2021-02-03 04:13:58 judoisoft.0 (1228) States user redis pmessage judoisoft.0.WaterStop/judoisoft.0.WaterStop:{"val":false,"ack":true,"ts":1612322038845,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288703551}
2021-02-03 04:13:58 judoisoft.0 (1228) --> stateID judoisoft.0.WaterStop changed: false (ack = true)

Diese beiden Einträge fallen etwas auf ...

2021-02-03 04:13:37 judoisoft.0 (1228) States user redis pmessage judoisoft.0.ResidualHard
ness/judoisoft.0.ResidualHardness:{"val":"8","ack":true,"ts":1612322017779,"q":0,"from":"system.adapter.judoisoft.0"," user":"system.user.admin","lc":1610288716907}
2021-02-03 04:13:37 judoisoft.0 (1228) --> stateID judoisoft.0.ResidualHardness changed: 8 (ack = true)

und

2021-02-03 04:13:58 judoisoft.0 (1228) States user redis pmessage judoisoft.0.WaterStop/judoisoft.0.WaterStop:{"val":false,"ack":true,"ts":1612322038845,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288703551}
2021-02-03 04:13:58 judoisoft.0 (1228) --> stateID judoisoft.0.WaterStop changed: false (ack = true)

Was sie bedeuten weiß ich nicht. Oder ist alles normal?

Viele Grüße

Michael

arteck

@mpenno alles gut

mpenno

@arteck Bei mir ist der Adapter jetzt doch noch einmal zwei mal stehen geblieben. Einmal lief er vom 9.2. bis 17.2. und einmal lief er vom 17.2. bis 20.2.
Am 9.2. hatte ich das Log-Level von Silly auf Info gestellt. Schade. Ich habe es nun aber wieder aktiviert.

Was ich gesehen habe, waren die beiden verschiedenen Meldungen (Log-Level "Info"):

2021-02-17 03:04:xx.xxx  : getInfos ERROR{"command":"residual hardness","data":"8","group":"settings","msgnumber":"1","status":"ok","token":"b5a3f70440deba34ade80572bc66282d5cd3291a2a0b95a0707dda46e6837288","wtuType":"...

und

2021-02-20 03:45:18.517  : judoisoft.0 (29961) reconnect 1613789118517

Das Objekt "LastInfoUpdate" hatte aber den Wert " = 20.02.2021 03:56 Uhr".

Mal sehen, was das erweiterte Logging bringt.

arteck

@mpenno ja so wie es aussieht verliert die judo ab und an Verbindung..

installiere bitte die GIT version .. hab da mal was eingebaut um zu schauen woher es kommt

mpenno

@arteck Die 1.0.3 Version habe ich mit der Katze drüber installiert. Anbei das Log. Am 5.3. hat er wieder aufgehört. LastInfoUpdate hat den Wert: "Fri Mar 05 2021 04:17:37"

2021-03-05 04:11:49 debug judoisoft.0 (21415) get Consumption data 
2021-03-05 04:11:52 debug judoisoft.0 (21415) -> WaterCurrent
2021-03-05 04:11:53 info  smartmeter.0 (947) Received 7 values, 3 updated
2021-03-05 04:11:54 debug judoisoft.0 (21415) -> ResidualHardness
2021-03-05 04:11:54 silly judoisoft.0 (21415) States user redis pmessage judoisoft.0.ResidualHardness/judoisoft.0.ResidualHardness:{"val":"8","ack":true,"ts":1614913914466,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288716907}
2021-03-05 04:11:54 debug judoisoft.0 (21415) --> stateID judoisoft.0.ResidualHardness changed: 8 (ack = true)
2021-03-05 04:11:56 debug judoisoft.0 (21415) -> SaltRange
2021-03-05 04:11:57 debug judoisoft.0 (21415) -> SaltQuantity
2021-03-05 04:11:59 debug judoisoft.0 (21415) -> WaterAverage
2021-03-05 04:12:01 debug judoisoft.0 (21415) -> NaturalHardness
2021-03-05 04:12:03 debug judoisoft.0 (21415) -> FlowRate
2021-03-05 04:12:05 debug judoisoft.0 (21415) -> Quantity
2021-03-05 04:12:07 debug judoisoft.0 (21415) -> WaterTotaal  275496 177000
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.01 10953 10953
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.02 9397 9397
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.03 1225 1225
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.04 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.05 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.06 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.07 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.08 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.09 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.10 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.11 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) WaterYearly.12 -1 -1
2021-03-05 04:12:08 debug judoisoft.0 (21415) -> WaterYearly
2021-03-05 04:12:10 debug judoisoft.0 (21415) -> StandBy
2021-03-05 04:12:12 debug judoisoft.0 (21415) -> ValveState
2021-03-05 04:12:12 silly judoisoft.0 (21415) States user redis pmessage judoisoft.0.WaterStop/judoisoft.0.WaterStop:{"val":false,"ack":true,"ts":1614913932710,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288703551}
2021-03-05 04:12:12 debug judoisoft.0 (21415) --> stateID judoisoft.0.WaterStop changed: false (ack = true)
2021-03-05 04:16:54 info  smartmeter.0 (947) Received 7 values, 3 updated
2021-03-05 04:17:12 debug judoisoft.0 (21415) get Consumption data 
2021-03-05 04:17:16 debug judoisoft.0 (21415) -> WaterCurrent
2021-03-05 04:17:17 debug judoisoft.0 (21415) -> ResidualHardness
2021-03-05 04:17:17 silly judoisoft.0 (21415) States user redis pmessage judoisoft.0.ResidualHardness/judoisoft.0.ResidualHardness:{"val":"8","ack":true,"ts":1614914237975,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288716907}
2021-03-05 04:17:17 debug judoisoft.0 (21415) --> stateID judoisoft.0.ResidualHardness changed: 8 (ack = true)
2021-03-05 04:17:19 debug judoisoft.0 (21415) -> SaltRange
2021-03-05 04:17:21 debug judoisoft.0 (21415) -> SaltQuantity
2021-03-05 04:17:23 debug judoisoft.0 (21415) -> WaterAverage
2021-03-05 04:17:25 debug judoisoft.0 (21415) -> NaturalHardness
2021-03-05 04:17:27 debug judoisoft.0 (21415) -> FlowRate
2021-03-05 04:17:29 debug judoisoft.0 (21415) -> Quantity
2021-03-05 04:17:31 debug judoisoft.0 (21415) -> WaterTotaal  275496 177000
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.01 10953 10953
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.02 9397 9397
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.03 1225 1225
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.04 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.05 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.06 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.07 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.08 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.09 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.10 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.11 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) WaterYearly.12 -1 -1
2021-03-05 04:17:33 debug judoisoft.0 (21415) -> WaterYearly
2021-03-05 04:17:35 debug judoisoft.0 (21415) -> StandBy
2021-03-05 04:17:37 debug judoisoft.0 (21415) -> ValveState
2021-03-05 04:17:37 silly judoisoft.0 (21415) States user redis pmessage judoisoft.0.WaterStop/judoisoft.0.WaterStop:{"val":false,"ack":true,"ts":1614914257932,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288703551}
2021-03-05 04:17:37 debug judoisoft.0 (21415) --> stateID judoisoft.0.WaterStop changed: false (ack = true)
2021-03-05 04:21:55 info  smartmeter.0 (947) Received 7 values, 3 updated
2021-03-05 04:22:37 debug judoisoft.0 (21415) get Consumption data 
2021-03-05 04:22:41 debug judoisoft.0 (21415) -> WaterCurrent
2021-03-05 04:22:42 debug judoisoft.0 (21415) -> ResidualHardness
2021-03-05 04:22:42 silly judoisoft.0 (21415) States user redis pmessage judoisoft.0.ResidualHardness/judoisoft.0.ResidualHardness:{"val":"8","ack":true,"ts":1614914562882,"q":0,"from":"system.adapter.judoisoft.0","user":"system.user.admin","lc":1610288716907}
2021-03-05 04:22:42 debug judoisoft.0 (21415) --> stateID judoisoft.0.ResidualHardness changed: 8 (ack = true)
2021-03-05 04:22:44 debug judoisoft.0 (21415) -> SaltRange
2021-03-05 04:22:46 debug judoisoft.0 (21415) -> SaltQuantity
2021-03-05 04:22:57 warntelegram.0 (1158) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
2021-03-05 04:22:58 error telegram.0 (1158) getMe (reconnect #0) Error:Error: EFATAL: Error: read ECONNRESET
2021-03-05 04:23:04 info  telegram.0 (1158) getMe (reconnect): Success
2021-03-05 04:26:55 info  smartmeter.0 (947) Received 7 values, 3 updated
2021-03-05 04:31:56 info  smartmeter.0 (947) Received 7 values, 3 updated
2021-03-05 04:36:58 info  smartmeter.0 (947) Received 7 values, 3 updated

Ich habe mal etwas mehr vom Log stehen lassen.
Kannst Du was erkennen?

arteck

@mpenno sagte in Test : Wasserenthärtung judo i-soft plus Adapter:

2021-03-05 04:22:46 debug judoisoft.0 (21415) -> SaltQuantity
2021-03-05 04:22:57 warntelegram.0 (1158) polling_error: EFATAL, EFATAL: Error: read ETIMEDOUT
2021-03-05 04:22:58 error telegram.0 (1158) getMe (reconnect #0) Error:Error: EFATAL: Error: read ECONNRESET
2021-03-05 04:23:04 info telegram.0 (1158) getMe (reconnect): Success

hier ist dein iobroker offline gegangen.. zumindest hat der die Verbinsung verloren zum Netz
hat nix mit dem Adapter zu tun

Adri525

@arteck
Ich bekomme den Adapter bei mir leider nicht zum laufen, die Instanz ist kurzzeitig Grün und geht dann auf Rot.

Hier der Log:
2021-03-18 12:59:21.207 - info: host.raspberrypi stopInstance system.adapter.judoisoft.0 (force=false, process=true)
2021-03-18 12:59:21.228 - info: judoisoft.0 (22591) Got terminate signal TERMINATE_YOURSELF
2021-03-18 12:59:21.229 - info: host.raspberrypi stopInstance system.adapter.judoisoft.0 send kill signal
2021-03-18 12:59:21.232 - info: judoisoft.0 (22591) cleaned everything up...
2021-03-18 12:59:21.235 - info: judoisoft.0 (22591) terminating
2021-03-18 12:59:21.238 - info: judoisoft.0 (22591) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-03-18 12:59:21.826 - info: host.raspberrypi instance system.adapter.judoisoft.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-03-18 12:59:24.322 - info: host.raspberrypi instance system.adapter.judoisoft.0 started with pid 22669
2021-03-18 12:59:25.618 - info: judoisoft.0 (22669) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v14.16.0, js-controller: 3.2.16
2021-03-18 13:01:37.948 - error: judoisoft.0 (22669) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-03-18 13:01:37.949 - error: judoisoft.0 (22669) unhandled promise rejection: Cannot read property 'data' of undefined
2021-03-18 13:01:37.950 - error: judoisoft.0 (22669) TypeError: Cannot read property 'data' of undefined
at judoisoftControll.getTokenFirst (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:355:69)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async judoisoftControll.onReady (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:57:18)
2021-03-18 13:01:37.950 - error: judoisoft.0 (22669) Cannot read property 'data' of undefined
2021-03-18 13:01:37.967 - info: judoisoft.0 (22669) cleaned everything up...
2021-03-18 13:01:37.968 - info: judoisoft.0 (22669) terminating
2021-03-18 13:01:37.969 - warn: judoisoft.0 (22669) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-03-18 13:01:38.545 - error: host.raspberrypi instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-03-18 13:01:38.547 - info: host.raspberrypi Restart adapter system.adapter.judoisoft.0 because enabled
2021-03-18 13:02:08.590 - info: host.raspberrypi instance system.adapter.judoisoft.0 started with pid 22908
2021-03-18 13:02:09.907 - info: judoisoft.0 (22908) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v14.16.0, js-controller: 3.2.16
2021-03-18 13:04:21.788 - error: judoisoft.0 (22908) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-03-18 13:04:21.789 - error: judoisoft.0 (22908) unhandled promise rejection: Cannot read property 'data' of undefined
2021-03-18 13:04:21.789 - error: judoisoft.0 (22908) TypeError: Cannot read property 'data' of undefined
at judoisoftControll.getTokenFirst (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:355:69)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async judoisoftControll.onReady (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:57:18)
2021-03-18 13:04:21.790 - error: judoisoft.0 (22908) Cannot read property 'data' of undefined
2021-03-18 13:04:21.806 - info: judoisoft.0 (22908) cleaned everything up...
2021-03-18 13:04:21.807 - info: judoisoft.0 (22908) terminating
2021-03-18 13:04:21.808 - warn: judoisoft.0 (22908) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-03-18 13:04:22.411 - error: host.raspberrypi instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-03-18 13:04:22.424 - info: host.raspberrypi Restart adapter system.adapter.judoisoft.0 because enabled
2021-03-18 13:04:52.474 - info: host.raspberrypi instance system.adapter.judoisoft.0 started with pid 23154
2021-03-18 13:04:53.807 - info: judoisoft.0 (23154) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v14.16.0, js-controller: 3.2.16
2021-03-18 13:07:05.632 - error: judoisoft.0 (23154) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-03-18 13:07:05.635 - error: judoisoft.0 (23154) unhandled promise rejection: Cannot read property 'data' of undefined
2021-03-18 13:07:05.637 - error: judoisoft.0 (23154) TypeError: Cannot read property 'data' of undefined
at judoisoftControll.getTokenFirst (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:355:69)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async judoisoftControll.onReady (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:57:18)
2021-03-18 13:07:05.638 - error: judoisoft.0 (23154) Cannot read property 'data' of undefined
2021-03-18 13:07:05.662 - info: judoisoft.0 (23154) cleaned everything up...
2021-03-18 13:07:05.664 - info: judoisoft.0 (23154) terminating
2021-03-18 13:07:05.666 - warn: judoisoft.0 (23154) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-03-18 13:07:06.267 - error: host.raspberrypi instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-03-18 13:07:06.269 - info: host.raspberrypi Restart adapter system.adapter.judoisoft.0 because enabled
2021-03-18 13:07:06.269 - warn: host.raspberrypi Do not restart adapter system.adapter.judoisoft.0 because restart loop detected

Grüße
Adri

arteck

@adri525 sagte in Test : Wasserenthärtung judo i-soft plus Adapter:

2021-03-18 13:01:37.950 - error: judoisoft.0 (22669) TypeError: Cannot read property 'data' of undefined

welche Anlage ist das ??

Adri525

@arteck
Gerätetyp: Judo i-soft safe
Gerätenummer: 198312
Softwareversion: 2.09
Hardwareversion: 5.10
Connectivity-Modul Version: 1.11

Grüße
Adri

arteck

@adri525 https://github.com/arteck/iobroker.judoisoft/issues/2

tommedIO created this issue in arteck/iobroker.judoisoft

closed Webinterface (isoft safe) #2

arteck

so gute Neuigkeiten

der Cloud Zugang sollte jetzt auch gehen...

version. 1.0.5

roughestboy

Neue Kundschaft !
Vielen Dank Arthur für diesen Adapter. Ich habe eine judo isoft safe, gestern installiert, mit 'Cloud', und die Datenpunkte sind schon da.

Vielleicht etwas offtopic oder falsches Forum, trotzdem Frage in die Runde: ich möchte den Adapter auch für 'Wasserszenen' nutzen, z.B. 'Duschen'.
In der Handy-App wird dann die Soll-Härte für 2h auf 4dH gestellt. Mein Dauerwert ist 8dH.
Weiß jemand, welche Gesamthärte des Duschwassers dann beabsichtigt ist ?
Wahrscheinlich haben die meisten ja einen Warmwasserspeicher, ich jedenfalls auch. Da ist dann Warmwasser mit 8dH drin, 50...60 Grad. Ich gehe mal davon aus, mit max. 40 Grad zu Duschen, d.H. vermutlich wird dabei roundabout die Hälfte Kaltwasser zugemischt. Für mein Verständnis kommen dann in der Dusche vielleicht 6dH an. Ist das das Ziel ? Wenn's 4dH wären, müsste ich die Szene ja eher auf 1dH stellen...

mpenno

@arteck Wir hatten uns beide schon vor einiger Zeit einmal ausgetauscht. Mein Judo i-Soft Adapter verliert hin- und wieder die Verbindung (manchmal alle 5 Tage, manchmal geht es auch zwei Wochen gut). Deshalb habe ich mir schon einen Watchdog geschrieben, der den Adapter neu startet.

Nur kann er den Adapter manchmal nicht Neustarten, da was komisches passiert: das Passwort ist nicht mehr unter den Adapter-Instanzdaten eingetragen. Der Benutzername steht noch da.
Jetzt frage ich wieso der hin- und wieder fehlt.

Schaue ich in die Datei: /opt/iobroker/iobroker-data/object.json ist da auch kein Passwort-JSON Schlüssel da, bis ich es wieder im Adapter eintrage:

Hier fehlt es:

..."native":
{"interval":"300","ip":"10.0.0.16","user":"blabla","ipaddress":"0.0.0.0","cloud":false},"protectedNative":["password"],"encryptedNative":["password"],...

Wenn ich es wieder eintrage:

..."native":{"interval":"300","ip":"10.0.0.16","user":"blabla","ipaddress":"0.0.0.0","cloud":false,"password":"IrgendwasVerschlüsseltes"},"protectedNative":["password"],"encryptedNative":["password"],

Ich habe die Versionen:
judoisoft: 1.0.10
Admin-Version: 5.1.23
js-controller: 3.3.15

Hat jemand eine Idee? Oder wie ich meinem Watchdog-Script beibringe den JSON-String zu korrigieren, ohne dass ich was anderes zerstöre

Mein Watchdog-Script läuft alle 15 Minuten und prüft ob sich etwas beim "Last Info-Objekt geändert hat, hier nur ein Ausschnitt mit dem Neustarten:

const idInst = 'system.adapter.judoisoft.0';
...

if (zeitDiff < 900000 ) return;

    var obj = getObject(idInst);
    obj.common.enabled = true;  // Adapter einschalten
    setObject(idInst, obj);
...

Viele Grüße
Michael

mpenno

Zwei Versuche habe ich noch unternommen:

Update des js-controller von 3.3.15 auf 3.3.18, was keine Änderung ergab.
Als letzte Möglichkeit habe ich die Judo i-soft Instanz gelöscht, den ioBroker Container neugestartet und den Judo i-soft Adapter über die Admin-Oberfläche mittels Github-Link "drüber" installiert.

Mal schauen, wie lange er jetzt läuft, ohne das Passwort zu verlieren.

Viele Grüße
Michael

mpenno

Brachte auch nichts, heute morgen um 3:25 Uhr und um 04:11 Uhr stand der Adapter wieder. Das Passwort (zumindestens die Sterne) waren in der Konfiguration noch zu sehen.

2021-09-25 03:07:22.619 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 03:12:23.959 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 03:17:08.843 - warn: zigbee.0 (766) State value to set for "zigbee.0.00158d00045cb942.link_quality" has value "255" greater than max "254"
2021-09-25 03:17:25.514 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 03:22:27.625 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 03:25:22.470 - error: judoisoft.0 (14692) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-09-25 03:25:22.526 - error: judoisoft.0 (14692) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property '_httpMessage' -> object with constructor 'ClientRequest'
--- property 'socket' closes the circle
2021-09-25 03:25:22.527 - error: judoisoft.0 (14692) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property '_httpMessage' -> object with constructor 'ClientRequest'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfosLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:405:53)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-09-25 03:25:22.528 - error: judoisoft.0 (14692) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property '_httpMessage' -> object with constructor 'ClientRequest'
--- property 'socket' closes the circle
2021-09-25 03:25:22.533 - info: judoisoft.0 (14692) cleaned everything up...
2021-09-25 03:25:22.534 - info: judoisoft.0 (14692) terminating
2021-09-25 03:25:22.535 - warn: judoisoft.0 (14692) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-25 03:25:23.129 - error: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-25 03:25:23.167 - info: host.iobroker-2020-05-01 Restart adapter system.adapter.judoisoft.0 because enabled
2021-09-25 03:25:53.199 - info: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 started with pid 26529
2021-09-25 03:25:54.745 - info: judoisoft.0 (26529) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.20.0, js-controller: 3.3.18
2021-09-25 03:27:28.928 - info: smartmeter.0 (607) Received 7 values, 3 updated
...
...
2021-09-25 04:07:40.471 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 04:07:50.580 - warn: zigbee.0 (766) State value to set for "zigbee.0.00158d00045cb942.link_quality" has value "255" greater than max "254"
2021-09-25 04:11:30.010 - error: judoisoft.0 (26529) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-09-25 04:11:30.013 - error: judoisoft.0 (26529) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:11:30.015 - error: judoisoft.0 (26529) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfosLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:405:53)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-09-25 04:11:30.017 - error: judoisoft.0 (26529) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:11:30.028 - info: judoisoft.0 (26529) cleaned everything up...
2021-09-25 04:11:30.029 - info: judoisoft.0 (26529) terminating
2021-09-25 04:11:30.030 - warn: judoisoft.0 (26529) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-25 04:11:30.606 - error: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-25 04:11:30.611 - info: host.iobroker-2020-05-01 Restart adapter system.adapter.judoisoft.0 because enabled
2021-09-25 04:11:34.987 - warn: telegram.0 (569) polling_error: EFATAL, EFATAL: Error: read ECONNRESET
2021-09-25 04:12:00.647 - info: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 started with pid 28836
2021-09-25 04:12:02.114 - info: judoisoft.0 (28836) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.20.0, js-controller: 3.3.18
2021-09-25 04:12:09.051 - error: judoisoft.0 (28836) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-09-25 04:12:09.052 - error: judoisoft.0 (28836) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:12:09.053 - error: judoisoft.0 (28836) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfoStaticLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:147:62)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-09-25 04:12:09.054 - error: judoisoft.0 (28836) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:12:09.061 - info: judoisoft.0 (28836) cleaned everything up...
2021-09-25 04:12:09.062 - info: judoisoft.0 (28836) terminating
2021-09-25 04:12:09.063 - warn: judoisoft.0 (28836) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-25 04:12:09.618 - error: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-25 04:12:09.620 - info: host.iobroker-2020-05-01 Restart adapter system.adapter.judoisoft.0 because enabled
2021-09-25 04:12:39.653 - info: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 started with pid 28887
2021-09-25 04:12:41.307 - info: judoisoft.0 (28887) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.20.0, js-controller: 3.3.18
2021-09-25 04:12:41.866 - info: smartmeter.0 (607) Received 7 values, 3 updated
2021-09-25 04:12:48.526 - error: judoisoft.0 (28887) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-09-25 04:12:48.527 - error: judoisoft.0 (28887) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:12:48.528 - error: judoisoft.0 (28887) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfoStaticLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:147:62)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-09-25 04:12:48.528 - error: judoisoft.0 (28887) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-09-25 04:12:48.533 - info: judoisoft.0 (28887) cleaned everything up...
2021-09-25 04:12:48.534 - info: judoisoft.0 (28887) terminating
2021-09-25 04:12:48.535 - warn: judoisoft.0 (28887) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-09-25 04:12:49.108 - error: host.iobroker-2020-05-01 instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-09-25 04:12:49.109 - info: host.iobroker-2020-05-01 Restart adapter system.adapter.judoisoft.0 because enabled
2021-09-25 04:12:49.110 - warn: host.iobroker-2020-05-01 Do not restart adapter system.adapter.judoisoft.0 because restart loop detected
2021-09-25 04:17:42.980 - info: smartmeter.0 (607) Received 7 values, 3 updated

Als ich mein Watchdog-Script den Adapter starten lies, war das Passwort danach nicht mehr hinterlegt.

const idInst = 'system.adapter.judoisoft.0';
var obj = getObject(idInst);
obj.common.enabled = true;  // Adapter einschalten
    setObject(idInst, obj);

Da scheint etwas nicht zu klappen.

Thomas Braun

@mpenno

node: v12.20.0

Auf was aktuelles bringen.

mpenno

@thomas-braun

Hat etwas gedauert. Da ich nun alles neu gemacht habe:

Neuer Docker Container (läuft im Host-Modus)
gestartet mit leerem ioBroker-Verzeichnis mit Ausnahme der Backup-Datei

Bei mir laufen die Adapter:

iobroker:/opt/iobroker# iobroker update
Used repository: stable
hash changed or no sources cached => force download of new sources
update done
Adapter    "admin"         : 5.1.25   , installed 5.1.25
Adapter    "backitup"      : 2.1.17   , installed 2.1.17
Adapter    "devices"       : 1.0.9    , installed 1.0.9
Adapter    "discovery"     : 2.7.0    , installed 2.7.0
Adapter    "hue-extended"  : 2.0.0    , installed 2.0.0
Adapter    "influxdb"      : 1.9.5    , installed 1.9.5
Adapter    "info"          : 1.9.8    , installed 1.9.8
Adapter    "javascript"    : 5.2.8    , installed 5.2.8
Controller "js-controller" : 3.3.18   , installed 3.3.18
Adapter    "km200"         : 1.1.6    , installed 2.0.3
Adapter    "knx"           : 1.0.45   , installed 1.0.45
Adapter    "mqtt"          : 2.4.0    , installed 2.4.0
Adapter    "simple-api"    : 2.6.1    , installed 2.6.1
Adapter    "smartmeter"    : 3.2.1    , installed 3.2.1
Adapter    "socketio"      : 3.1.4    , installed 3.1.4
Adapter    "synology"      : 1.1.3    , installed 1.1.3
Adapter    "telegram"      : 1.10.0   , installed 1.10.0
Adapter    "text2command"  : 2.1.1    , installed 2.1.1
Adapter    "tr-064"        : 4.2.14   , installed 4.2.14
Adapter    "web"           : 3.4.7    , installed 3.4.7
Adapter    "whatsapp-cmb"  : 0.1.6    , installed 0.1.6
Adapter    "zigbee"        : 1.5.6    , installed 1.5.6

Dann Judo-iSoft Adapter neu installiert:

/opt/iobroker# iobroker url https://github.com/arteck/iobroker.judoisoft --host iobroker
install arteck/iobroker.judoisoft#e85216336bc3d7fbdbee2929a736d774c367c380
NPM version: 6.14.15
npm install arteck/iobroker.judoisoft#e85216336bc3d7fbdbee2929a736d774c367c380 --loglevel error --prefix "/opt/iobroker" (System call)
upload [4] judoisoft.admin /opt/iobroker/node_modules/iobroker.judoisoft/admin/words.js words.js application/javascript
upload [3] judoisoft.admin /opt/iobroker/node_modules/iobroker.judoisoft/admin/style.css style.css text/css
upload [2] judoisoft.admin /opt/iobroker/node_modules/iobroker.judoisoft/admin/judo.png judo.png image/png
upload [1] judoisoft.admin /opt/iobroker/node_modules/iobroker.judoisoft/admin/index_m.html index_m.html text/html
upload [0] judoisoft.admin /opt/iobroker/node_modules/iobroker.judoisoft/admin/adapter-settings.js adapter-settings.js application/javascript

Dann Instanz erstellt:

$ iobroker add judoisoft auto --host iobroker

Einstellungen vorgenommen und gestartet. Kurz danach gleich der Neustart

2021-10-08 19:22:43.837 - info: host.iobroker iobroker host.iobroker object system.adapter.judoisoft.0 created
2021-10-08 19:22:44.865 - info: host.iobroker iobroker exit 0
2021-10-08 19:24:51.258 - info: host.iobroker "system.adapter.judoisoft.0" enabled
2021-10-08 19:24:51.451 - info: host.iobroker instance system.adapter.judoisoft.0 started with pid 2670
2021-10-08 19:24:52.985 - info: judoisoft.0 (2670) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.22.6, js-controller: 3.3.18
2021-10-08 19:25:00.465 - error: judoisoft.0 (2670) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-10-08 19:25:00.466 - error: judoisoft.0 (2670) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:25:00.467 - error: judoisoft.0 (2670) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfoStaticLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:147:62)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-10-08 19:25:00.468 - error: judoisoft.0 (2670) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:25:00.499 - info: judoisoft.0 (2670) cleaned everything up...
2021-10-08 19:25:00.502 - info: judoisoft.0 (2670) terminating
2021-10-08 19:25:00.503 - warn: judoisoft.0 (2670) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-10-08 19:25:01.081 - error: host.iobroker instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-10-08 19:25:01.082 - info: host.iobroker Restart adapter system.adapter.judoisoft.0 because enabled
2021-10-08 19:25:31.121 - info: host.iobroker instance system.adapter.judoisoft.0 started with pid 2725
2021-10-08 19:25:32.737 - info: judoisoft.0 (2725) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.22.6, js-controller: 3.3.18
2021-10-08 19:25:39.592 - error: judoisoft.0 (2725) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-10-08 19:25:39.593 - error: judoisoft.0 (2725) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:25:39.594 - error: judoisoft.0 (2725) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfoStaticLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:147:62)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-10-08 19:25:39.594 - error: judoisoft.0 (2725) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:25:39.599 - info: judoisoft.0 (2725) cleaned everything up...
2021-10-08 19:25:39.601 - info: judoisoft.0 (2725) terminating
2021-10-08 19:25:39.602 - warn: judoisoft.0 (2725) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-10-08 19:25:40.170 - error: host.iobroker instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-10-08 19:25:40.171 - info: host.iobroker Restart adapter system.adapter.judoisoft.0 because enabled
2021-10-08 19:25:49.449 - info: smartmeter.0 (2385) Received 7 values, 3 updated
2021-10-08 19:26:10.203 - info: host.iobroker instance system.adapter.judoisoft.0 started with pid 2766
2021-10-08 19:26:11.774 - info: judoisoft.0 (2766) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.judoisoft, node: v12.22.6, js-controller: 3.3.18
2021-10-08 19:26:18.682 - error: judoisoft.0 (2766) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-10-08 19:26:18.683 - error: judoisoft.0 (2766) unhandled promise rejection: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:26:18.684 - error: judoisoft.0 (2766) TypeError: Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
at JSON.stringify ()
at judoisoftControll.getInfoStaticLocal (/opt/iobroker/node_modules/iobroker.judoisoft/main.js:147:62)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-10-08 19:26:18.685 - error: judoisoft.0 (2766) Converting circular structure to JSON
--> starting at object with constructor 'TLSSocket'
| property 'parser' -> object with constructor 'HTTPParser'
--- property 'socket' closes the circle
2021-10-08 19:26:18.694 - info: judoisoft.0 (2766) cleaned everything up...
2021-10-08 19:26:18.695 - info: judoisoft.0 (2766) terminating
2021-10-08 19:26:18.696 - warn: judoisoft.0 (2766) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-10-08 19:26:19.263 - error: host.iobroker instance system.adapter.judoisoft.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-10-08 19:26:19.264 - info: host.iobroker Restart adapter system.adapter.judoisoft.0 because enabled

Die Ausgabe von "which nodejs" wird nicht angezeigt:

/opt/iobroker# which nodejs
/opt/iobroker#

Deshalb habe ich es hier weggelassen:

/opt/iobroker# which node && node -v && which npm && npm -v && apt policy nodejs/usr/bin/node
v12.22.6
/usr/bin/npm
6.14.15
nodejs:
  Installed: 12.22.6-deb-1nodesource1
  Candidate: 12.22.6-deb-1nodesource1
  Version table:
 *** 12.22.6-deb-1nodesource1 100
        100 /var/lib/dpkg/status

Den Entkalker habe ich gerade mal vom Strom getrennt und neugestartet. Der Adapter mag ihn troztdem nicht.

arteck

@mpenno es scheint als ob die Anlage ab und am keine Daten liefert.. ergo es kann nix geparst werden und der Json Parser aussteigt..

ich muss mal schauen ob ich das abgefangen bekomme

Skywalker110

@oranggila

Ich habe mal eine Frage zu dem Adapter sorry aber wie gehe ich vor wenn ich auch im VIS paar Dinge steuern will ?
Deine Grafik sieht prima aus .
wie hinterlege ich die Befehle ?
Grundkenntnisse habe ich und kenne mich mit VIS einigermaßen aus.

Super Dapater läuft prima bei mir und füllt mir die Objekte.

Grüße Holger

NEWS

Test : Wasserenthärtung judo i-soft plus Adapter

closed Webinterface (isoft safe) #2

Support us

1.6k
Online

30.4k
Users

76.6k
Topics

1.2m
Posts

NEWS

Test : Wasserenthärtung judo i-soft plus Adapter

closed Webinterface (isoft safe) #2

Support us

1.6kOnline

30.4kUsers

76.6kTopics

1.2mPosts

1.6k
Online

30.4k
Users

76.6k
Topics

1.2m
Posts