Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test : Wasserenthärtung judo i-soft plus Adapter

NEWS

  • Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar
    BluefoxB
    Bluefox
    12
    2
    266

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.7k

Test : Wasserenthärtung judo i-soft plus Adapter

Test : Wasserenthärtung judo i-soft plus Adapter

Scheduled Pinned Locked Moved Tester
i-softjudowasserenthärtung
216 Posts 22 Posters 31.6k Views 21 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M mpenno

    @oranggila Schöne Visu!

    Bei mir aktualisieren sich jetzt auch keine Werte mehr. Alle Daten sind vom 21.01. ca. 3:00 Uhr morgens, auch der Zetistempel vom "Connection Status = OK".

    Das Log ist unauffällig.

    Soll ich was bestimmtes Prüfen, was der Sache dienlich sein kein, bevor ich den Adapter neu starte?

    Viele Grüße
    Michael

    M Offline
    M Offline
    mpenno
    wrote on last edited by
    #40

    Habe dann gestern aufgrund vom Aktualisieren einiger Pakete, darunter auch den js-controller, neugestartet. Das war gestern gegen 16:30 Uhr.
    Heute aktualisieren sich wieder keine Daten. Stehen geblieben ist er gestern um 21:24 Uhr.
    Wieder mit Connection-Status = OK.
    Er denkt scheinbar immer noch, er sei verbunden. Adapterspezifische Log-Meldungen gibt es nicht.
    Zur Info: Mein Judo iSoft ist mit einem Netzwerkkabel angebunden, nicht per WLAN.

    Viele Grüße
    Michael

    arteckA 1 Reply Last reply
    0
    • M mpenno

      Habe dann gestern aufgrund vom Aktualisieren einiger Pakete, darunter auch den js-controller, neugestartet. Das war gestern gegen 16:30 Uhr.
      Heute aktualisieren sich wieder keine Daten. Stehen geblieben ist er gestern um 21:24 Uhr.
      Wieder mit Connection-Status = OK.
      Er denkt scheinbar immer noch, er sei verbunden. Adapterspezifische Log-Meldungen gibt es nicht.
      Zur Info: Mein Judo iSoft ist mit einem Netzwerkkabel angebunden, nicht per WLAN.

      Viele Grüße
      Michael

      arteckA Offline
      arteckA Offline
      arteck
      Developer Most Active
      wrote on last edited by arteck
      #41

      @mpenno hmm..
      aktualisiere nochmal vom GIT und stell den adapter mal auf silly und beobachte die logs.. wo der aussteigt

      zigbee hab ich, zwave auch, nuc's genauso und HA auch

      M 1 Reply Last reply
      0
      • arteckA arteck

        @mpenno hmm..
        aktualisiere nochmal vom GIT und stell den adapter mal auf silly und beobachte die logs.. wo der aussteigt

        M Offline
        M Offline
        mpenno
        wrote on last edited by
        #42

        @arteck Ja OK, mache ich.

        Ich habe mal kurz das Netzwerkkabel vom Judo iSoft für 10 Minuten abgezogen. Das scheint dem Adapter nicht zu interessieren (Abfrageintervall war Standard=300s). Er scheint wirklich fest zu "hängen".

        Ich melde mich später.

        Danke übrigens für Deinen Support!
        Habt Ihr eine PayPal-Kasse?

        1 Reply Last reply
        0
        • arteckA Offline
          arteckA Offline
          arteck
          Developer Most Active
          wrote on last edited by arteck
          #43

          jetzt auch mit cloud Login

          ff07ed93-f343-4e86-9625-c17163b5fda7-grafik.png

          leider musste ich die Einstellung wieder ausbauen da die Cloud nicht die funktionalität hergibt

          zigbee hab ich, zwave auch, nuc's genauso und HA auch

          M 1 Reply Last reply
          0
          • arteckA arteck

            jetzt auch mit cloud Login

            ff07ed93-f343-4e86-9625-c17163b5fda7-grafik.png

            leider musste ich die Einstellung wieder ausbauen da die Cloud nicht die funktionalität hergibt

            M Offline
            M Offline
            mpenno
            wrote on last edited by
            #44

            @arteck Kleiner Zwischenstand: mit der 1.0.1 läuft es schon seit über 24h.

            M 1 Reply Last reply
            0
            • M mpenno

              @arteck Kleiner Zwischenstand: mit der 1.0.1 läuft es schon seit über 24h.

              M Offline
              M Offline
              mpenno
              wrote on last edited by
              #45

              Neuer Zwischenstand: Ich musste den Test abbrechen, da meine Docker-Instanz instabil lief. Mein RAM wurde knapp, so dass ich erst einen neuen Speicherriegel für meine Synology bestellen musste. Ich hoffe, er wird am Samstag geliefert 🙂

              M 1 Reply Last reply
              0
              • O Offline
                O Offline
                oranggila
                wrote on last edited by oranggila
                #46

                gelöscht

                Intel NUC - ioBroker in Proxmox-VM, Zigbee TCP CC2652P2, MG4 Trophy (e-Auto)

                1 Reply Last reply
                0
                • arteckA arteck

                  @oranggila ok klingt plausibel.. ich bau es ein

                  check 0.0.6

                  O Offline
                  O Offline
                  oranggila
                  wrote on last edited by oranggila
                  #47

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

                  @oranggila ok klingt plausibel.. ich bau es ein

                  check 0.0.6

                  @arteck Ist das Einstellen der Wasserhärte schon eingebaut in der 1.0.1?

                  Intel NUC - ioBroker in Proxmox-VM, Zigbee TCP CC2652P2, MG4 Trophy (e-Auto)

                  arteckA 1 Reply Last reply
                  0
                  • O oranggila

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

                    @oranggila ok klingt plausibel.. ich bau es ein

                    check 0.0.6

                    @arteck Ist das Einstellen der Wasserhärte schon eingebaut in der 1.0.1?

                    arteckA Offline
                    arteckA Offline
                    arteck
                    Developer Most Active
                    wrote on last edited by
                    #48

                    @oranggila ja

                    zigbee hab ich, zwave auch, nuc's genauso und HA auch

                    O 1 Reply Last reply
                    0
                    • arteckA arteck

                      @oranggila ja

                      O Offline
                      O Offline
                      oranggila
                      wrote on last edited by
                      #49

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

                      @oranggila ja

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

                      Intel NUC - ioBroker in Proxmox-VM, Zigbee TCP CC2652P2, MG4 Trophy (e-Auto)

                      1 Reply Last reply
                      0
                      • M mpenno

                        Neuer Zwischenstand: Ich musste den Test abbrechen, da meine Docker-Instanz instabil lief. Mein RAM wurde knapp, so dass ich erst einen neuen Speicherriegel für meine Synology bestellen musste. Ich hoffe, er wird am Samstag geliefert 🙂

                        M Offline
                        M Offline
                        mpenno
                        wrote on last edited by
                        #50

                        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

                        arteckA 1 Reply Last reply
                        0
                        • M 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

                          arteckA Offline
                          arteckA Offline
                          arteck
                          Developer Most Active
                          wrote on last edited by
                          #51

                          @mpenno alles gut

                          zigbee hab ich, zwave auch, nuc's genauso und HA auch

                          M 1 Reply Last reply
                          0
                          • arteckA arteck

                            @mpenno alles gut

                            M Offline
                            M Offline
                            mpenno
                            wrote on last edited by
                            #52

                            @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.

                            arteckA 1 Reply Last reply
                            0
                            • M 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.

                              arteckA Offline
                              arteckA Offline
                              arteck
                              Developer Most Active
                              wrote on last edited by
                              #53

                              @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

                              zigbee hab ich, zwave auch, nuc's genauso und HA auch

                              M 1 Reply Last reply
                              0
                              • arteckA 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

                                M Offline
                                M Offline
                                mpenno
                                wrote on last edited by mpenno
                                #54

                                @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?

                                arteckA 1 Reply Last reply
                                0
                                • M 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?

                                  arteckA Offline
                                  arteckA Offline
                                  arteck
                                  Developer Most Active
                                  wrote on last edited by arteck
                                  #55

                                  @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

                                  zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                  A 1 Reply Last reply
                                  0
                                  • arteckA 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

                                    A Offline
                                    A Offline
                                    Adri525
                                    wrote on last edited by
                                    #56

                                    @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

                                    arteckA 1 Reply Last reply
                                    0
                                    • A 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

                                      arteckA Offline
                                      arteckA Offline
                                      arteck
                                      Developer Most Active
                                      wrote on last edited by
                                      #57

                                      @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 ??

                                      zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                      A 1 Reply Last reply
                                      0
                                      • arteckA 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 ??

                                        A Offline
                                        A Offline
                                        Adri525
                                        wrote on last edited by
                                        #58

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

                                        Grüße
                                        Adri

                                        arteckA 1 Reply Last reply
                                        0
                                        • A 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

                                          arteckA Offline
                                          arteckA Offline
                                          arteck
                                          Developer Most Active
                                          wrote on last edited by
                                          #59

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

                                          tommedIO created this issue in arteck/iobroker.judoisoft

                                          closed Webinterface (isoft safe) #2

                                          zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          159

                                          Online

                                          32.4k

                                          Users

                                          81.3k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe