Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter rika-firenet 1.0.x-xxxx.n (ALPHA Test)

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Test Adapter rika-firenet 1.0.x-xxxx.n (ALPHA Test)

    This topic has been deleted. Only users with topic management privileges can see it.
    • HAL
      HAL @HAL last edited by

      @hal Adapter läuft und steuert den Ofen.
      Im log sind 2 warn Meldungen:

      rika-firenet.0
      2025-01-20 12:44:57.587	warn	State "rika-firenet.0.23422463.stoveFeatures.bakeMode" has no existing object, this might lead to an error in future versions
      
      rika-firenet.0
      2025-01-20 12:44:57.586	warn	State "rika-firenet.0.23422463.stoveFeatures.airFlaps" has no existing object, this might lead
      

      Screenshot_20250120_125340_ioBroker Visu.jpg

      HAL Codierknecht 2 Replies Last reply Reply Quote 1
      • HAL
        HAL @HAL last edited by HAL

        Hier der Log bisher:

        2025-01-20 09:28:29.056 - info: host.iobroker iobroker url xsawa32/ioBroker.rika-firenet --host iobroker --debug
        2025-01-20 09:28:29.683 - info: host.iobroker iobroker install xsawa32/ioBroker.rika-firenet
        2025-01-20 09:28:29.771 - info: host.iobroker iobroker NPM version: 10.8.2
        2025-01-20 09:28:29.772 - info: host.iobroker iobroker Installing xsawa32/ioBroker.rika-firenet... (System call)
        2025-01-20 09:28:34.145 - info: host.iobroker iobroker added 2 packages, removed 5 packages, and changed 2 packages in 4s
        2025-01-20 09:28:34.146 - info: host.iobroker iobroker 198 packages are looking for funding run `npm fund` for details
        2025-01-20 09:28:34.224 - info: host.iobroker iobroker upload [12] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/de/translations.json i18n/de/translations.json application/json
        2025-01-20 09:28:34.227 - info: host.iobroker iobroker upload [11] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/en/translations.json i18n/en/translations.json application/json
        2025-01-20 09:28:34.229 - info: host.iobroker iobroker upload [10] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/es/translations.json i18n/es/translations.json application/json
        2025-01-20 09:28:34.232 - info: host.iobroker iobroker upload [9] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
        2025-01-20 09:28:34.233 - info: host.iobroker iobroker upload [8] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/it/translations.json i18n/it/translations.json application/json
        2025-01-20 09:28:34.236 - info: host.iobroker iobroker upload [7] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
        2025-01-20 09:28:34.237 - info: host.iobroker iobroker upload [6] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
        2025-01-20 09:28:34.239 - info: host.iobroker iobroker upload [5] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
        2025-01-20 09:28:34.241 - info: host.iobroker iobroker upload [4] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
        2025-01-20 09:28:34.243 - info: host.iobroker iobroker upload [3] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/uk/translations.json i18n/uk/translations.json application/json
        2025-01-20 09:28:34.245 - info: host.iobroker iobroker upload [2] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
        2025-01-20 09:28:34.247 - info: host.iobroker iobroker upload [1] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/jsonConfig.json jsonConfig.json application/json
        2025-01-20 09:28:34.249 - info: host.iobroker iobroker upload [0] rika-firenet.admin /opt/iobroker/node_modules/iobroker.rika-firenet/admin/rika-firenet.png rika-firenet.png image/png
        2025-01-20 09:28:34.252 - info: host.iobroker iobroker Updating objects from io-package.json for adapter "rika-firenet" with version "1.0.0-alpha.6"
        2025-01-20 09:28:34.294 - info: host.iobroker iobroker Update "system.adapter.rika-firenet.0"
        2025-01-20 09:29:06.738 - info: host.iobroker "system.adapter.rika-firenet.0" enabled
        2025-01-20 09:29:07.251 - info: host.iobroker instance system.adapter.rika-firenet.0 in version "1.0.0-alpha.6" (non-npm: xsawa32/ioBroker.rika-firenet) started with pid 861976
        2025-01-20 09:29:07.651 - debug: rika-firenet.0 (861976) Redis Objects: Use Redis connection: 127.0.0.1:9001
        2025-01-20 09:29:07.684 - debug: rika-firenet.0 (861976) Objects client ready ... initialize now
        2025-01-20 09:29:07.685 - debug: rika-firenet.0 (861976) Objects create System PubSub Client
        2025-01-20 09:29:07.686 - debug: rika-firenet.0 (861976) Objects create User PubSub Client
        2025-01-20 09:29:07.767 - debug: rika-firenet.0 (861976) Objects client initialize lua scripts
        2025-01-20 09:29:07.770 - debug: rika-firenet.0 (861976) Objects connected to redis: 127.0.0.1:9001
        2025-01-20 09:29:07.806 - debug: rika-firenet.0 (861976) Redis States: Use Redis connection: 127.0.0.1:9000
        2025-01-20 09:29:07.825 - debug: rika-firenet.0 (861976) States create System PubSub Client
        2025-01-20 09:29:07.826 - debug: rika-firenet.0 (861976) States create User PubSub Client
        2025-01-20 09:29:07.906 - debug: rika-firenet.0 (861976) States connected to redis: 127.0.0.1:9000
        2025-01-20 12:44:55.620 - info: host.iobroker instance system.adapter.rika-firenet.0 in version "1.0.0-alpha.6" (non-npm: iobroker-community-adapters/ioBroker.rika-firenet#xxxxxxxxxxxxxxxxxxx) started with pid 865571
        2025-01-20 12:44:56.345 - info: rika-firenet.0 (865571) starting. Version 1.0.0-alpha.6 (non-npm: iobroker-community-adapters/ioBroker.rika-firenet#9xxxxxxxxxxxxxxxxxxx) in /opt/iobroker/node_modules/iobroker.rika-firenet, node: v20.18.1, js-controller: 7.0.3
        2025-01-20 12:44:56.353 - info: rika-firenet.0 (865571) config user: xxxx@xxxxxx
        2025-01-20 12:44:56.354 - info: rika-firenet.0 (865571) config interval: 1
        2025-01-20 12:44:56.354 - info: rika-firenet.0 (865571) config stoveid: xxxxxxxx
        2025-01-20 12:44:57.318 - info: rika-firenet.0 (865571) Logged in to rika firenet
        2025-01-20 12:44:57.586 - warn: rika-firenet.0 (865571) State "rika-firenet.0.xxxx.stoveFeatures.airFlaps" has no existing object, this might lead to an error in future versions
        2025-01-20 12:44:57.587 - warn: rika-firenet.0 (865571) State "rika-firenet.0.xxxx.stoveFeatures.bakeMode" has no existing object, this might lead to an error in future versions
        2025-01-20 12:49:21.838 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.onOff changed: true (ack = false)
        2025-01-20 12:57:59.695 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.heatingPower changed: 95 (ack = false)
        2025-01-20 12:58:00.705 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.heatingPower changed: 85 (ack = false)
        2025-01-20 12:58:00.780 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.heatingPower changed: 80 (ack = false)
        2025-01-20 12:58:01.071 - error: rika-firenet.0 (865571) setstoveValues error: AxiosError: Request failed with status code 404
        2025-01-20 12:58:23.638 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.heatingPower changed: 85 (ack = false)
        2025-01-20 12:58:24.638 - info: rika-firenet.0 (865571) state rika-firenet.0.xxxx.controls.heatingPower changed: 100 (ack = false)
        
        
        1 Reply Last reply Reply Quote 0
        • Codierknecht
          Codierknecht Developer Most Active last edited by

          @hal
          Vielleicht kann @mcm1957 mal über den Code schauen und mir die Ursache erläutern?

          Das dürfte an der mir noch immer etwas unverständlichen Asynchronität liegen.
          Ich vermute mal, dass da noch einige Funktionen auf async umgestellt und die Aufrufe verändert werden müssen.
          Da sind noch Funktionen mit und ohne async wild gemischt.

          mcm1957 1 Reply Last reply Reply Quote 0
          • mcm1957
            mcm1957 @Codierknecht last edited by

            @codierknecht

            Die Meldung (State "rika-firenet.0.xxxx.stoveFeatures.airFlaps" has no existing object, this might lead to an error in future versions) sagt aus, dass es zu diesem State kein Objekt ergiubt. Das wird mittel setObjectNotExists oder extendObject angelegt - und zwar
            JE ein set/extendObject für

            • xxxx
            • xxxx.stoveFeatures.
            • xxxx.stoveFeatures.airFlaps

            Werden diese set/extendObjects aufgerufen?
            Ev. bau mal bei jedem set/extendObject vorher ein log.debug ein damit man das leicht checken kann.

            Und ja - kann gern mal drüberschaun. Mach mir ne Notiz

            1 Reply Last reply Reply Quote 1
            • Codierknecht
              Codierknecht Developer Most Active @HAL last edited by

              @hal sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

              Im log sind 2 warn Meldungen:

              In GitHub ist jetzt 1.0.0-alpha.9 - da sollte das behoben sein.
              Kam eh nur beim ersten Start des Adapters vor, wenn vorher die Objekte gelöscht wurden.

              HAL 1 Reply Last reply Reply Quote 0
              • HAL
                HAL @Codierknecht last edited by

                @codierknecht ist installiert. Ich werde berichten 😉

                HAL 1 Reply Last reply Reply Quote 0
                • HAL
                  HAL @HAL last edited by HAL

                  @hal sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

                  @codierknecht ist installiert. Ich werde berichten 😉

                  Bis auf Meldungen , wann der Pelletofen ein oder ausgeschaltet wurde heute keine weiteren Meldungen im log. Der Adapter war heute durchgehend aktiv und funktionierte bisher einwandfrei. 🙂

                  (edit)
                  Möglicherweise gibt es ein Problem beim Update von Sensordaten. Ich prüfen das noch mal gesondert

                  HAL 1 Reply Last reply Reply Quote 1
                  • HAL
                    HAL @HAL last edited by HAL

                    Heute früh wurde der Pelletofen um 09:30 Uhr per Script ausgeschaltet , das hat funktioniert. Im log kam kurz danach ein error

                    rika-firenet.0
                    2025-01-22 09:36:40.636	error	getstoveValues error: Error: getaddrinfo EAI_AGAIN www.rika-firenet.com
                    
                    rika-firenet.0
                    2025-01-22 09:30:32.015	info	state rika-firenet.0.xxxxxx.controls.onOff changed: false (ack = false)
                    
                    
                    mcm1957 1 Reply Last reply Reply Quote 0
                    • mcm1957
                      mcm1957 @HAL last edited by

                      @hal
                      Ein getaddrinfo EAI_AGAIN deutet auf ein Problem mit der dsn Namensauflösung hin.

                      @Codierknecht
                      "Normale" State changes sollten nicht als info geloggt werden. Das sollte besser debug sein (weil nach fehler sieht es für mich nicht aus)

                      2025-01-22 09:30:32.015 info state rika-firenet.0.xxxxxx.controls.onOff changed: false (ack = false)

                      Codierknecht 1 Reply Last reply Reply Quote 1
                      • Codierknecht
                        Codierknecht Developer Most Active @mcm1957 last edited by

                        @mcm1957 sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

                        "Normale" State changes sollten nicht als info geloggt werden. Das sollte besser debug sein (weil nach fehler sieht es für mich nicht aus)

                        Ist geändert.
                        Ich war so frei und habe jetzt eine "beta" gemacht. Die grundsätzliche Funktionalität scheint ja gegeben zu sein.

                        mcm1957 1 Reply Last reply Reply Quote 0
                        • mcm1957
                          mcm1957 @Codierknecht last edited by

                          @codierknecht
                          Na ja - hoff es verwirrt nicht zu viele.

                          BEAT Test gibts erst wenn der Adapetr im Repo ist. Bis daher ist er per Definition ALPHA Status.

                          Codierknecht 1 Reply Last reply Reply Quote 0
                          • Codierknecht
                            Codierknecht Developer Most Active @mcm1957 last edited by

                            @mcm1957 sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

                            BEAT Test gibts erst wenn der Adapetr im Repo ist. Bis daher ist er per Definition ALPHA Status.

                            Naja - von mir aus kann der ja auch da rein.

                            mcm1957 1 Reply Last reply Reply Quote 0
                            • mcm1957
                              mcm1957 @Codierknecht last edited by mcm1957

                              @codierknecht

                              https://github.com/ioBroker/ioBroker.repositories?tab=readme-ov-file#add-a-new-adapter-to-the-latest-repository-web-frontend

                              https://github.com/ioBroker/ioBroker.repositories?tab=readme-ov-file#requirements-for-adapter-to-get-added-to-the-latest-repository

                              Und dann muss ich noch zum Review kommen ...

                              Codierknecht 1 Reply Last reply Reply Quote 1
                              • Codierknecht
                                Codierknecht Developer Most Active @mcm1957 last edited by

                                @mcm1957
                                Reicht es, die 0.0.7 ins "latest" zu pushen?

                                841e4e25-f111-4b3c-9340-2a2676cc229f-grafik.png

                                mcm1957 HAL 2 Replies Last reply Reply Quote 0
                                • mcm1957
                                  mcm1957 @Codierknecht last edited by

                                  @codierknecht
                                  Ist egal - LATEST ist immer jene Release auf NPM 'latest' ist.
                                  Wenn der Review durch ist kann ich ja jederzeit eine offizielle BETA / LATEST Release einziehen. Wär dann wohl die 1.0.0.

                                  Bitte dann in Zukunft nur -alphe.x für Zwischentests und offizielle Versionsnummern für BETA / LATEST Tests verwenden. Jetzt mach mal mit beta.x weiter bis ich Zeit für Review habe.

                                  1 Reply Last reply Reply Quote 1
                                  • HAL
                                    HAL @Codierknecht last edited by

                                    @codierknecht zur Info, bisher läuft der von Dir überarbeitete Adapter stabil und zuverlässig 🙂

                                    HAL 1 Reply Last reply Reply Quote 1
                                    • HAL
                                      HAL @HAL last edited by

                                      @hal kleine Korrektur. Es ist jetzt zweimal passiert, das der Adapter steuert, aber die Sensorddaten nicht aktualisiert werden. Dazu muss der Adapter neu gestartet werden. Ich beobachte das noch mal und sende dann den log dazu.

                                      HAL 1 Reply Last reply Reply Quote 0
                                      • HAL
                                        HAL @HAL last edited by HAL

                                        So heute ist es wieder aufgetreten. Der Pelletofen wird korrekt gesteuert (0n/off), aber z.B. der Sensor
                                        "rika-firenet.0.xxxxxxx.sensors.statusMainState"
                                        wird nicht aktualisiert. Erst wenn der Adapter neu gestartet wird, ist der Status sofort aktualisiert.

                                        Log:

                                        2025-01-26 08:30:32.014 - info: rika-firenet.0 (930580) state rika-firenet.0.xxxxxx3.controls.onOff changed: true (ack = false)
                                        2025-01-26 08:30:32.015 - debug: rika-firenet.0 (930580) url: https://www.rika-firenet.com/api/client/xxxxxx3/status
                                        2025-01-26 08:30:32.210 - debug: rika-firenet.0 (930580) 200 - API-Connection successful
                                        2025-01-26 08:30:32.210 - debug: rika-firenet.0 (930580) onOff = true
                                        2025-01-26 08:30:32.362 - debug: rika-firenet.0 (930580) {"revision":xxxxxx,"onOff":true,"operatingMode":0,"heatingPower":100,"targetTemperature":"22","bakeTemperature":"180","ecoMode":false,"heatingTimeMon1":"08150915","heatingTimeMon2":"00000000","heatingTimeTue1":"08150915","heatingTimeTue2":"00000000","heatingTimeWed1":"08150915","heatingTimeWed2":"00000000","heatingTimeThu1":"08150915","heatingTimeThu2":"00000000","heatingTimeFri1":"08150915","heatingTimeFri2":"00000000","heatingTimeSat1":"08150915","heatingTimeSat2":"00000000","heatingTimeSun1":"08150915","heatingTimeSun2":"00000000","heatingTimesActiveForComfort":false,"setBackTemperature":"20","convectionFan1Active":false,"convectionFan1Level":0,"convectionFan1Area":0,"convectionFan2Active":false,"convectionFan2Level":0,"convectionFan2Area":0,"frostProtectionActive":false,"frostProtectionTemperature":"4","temperatureOffset":"0","RoomPowerRequest":3,"debug0":0,"debug1":0,"debug2":0,"debug3":0,"debug4":0}
                                        2025-01-26 09:30:32.015 - info: rika-firenet.0 (930580) state rika-firenet.0.xxxxxx3.controls.onOff changed: false (ack = false)
                                        2025-01-26 09:30:32.015 - debug: rika-firenet.0 (930580) url: https://www.rika-firenet.com/api/client/xxxxxx3/status
                                        2025-01-26 09:30:32.380 - debug: rika-firenet.0 (930580) 200 - API-Connection successful
                                        2025-01-26 09:30:32.381 - debug: rika-firenet.0 (930580) onOff = false
                                        2025-01-26 09:30:32.536 - debug: rika-firenet.0 (930580) {"revision":1737876632,"onOff":false,"operatingMode":0,"heatingPower":100,"targetTemperature":"22","bakeTemperature":"180","ecoMode":false,"heatingTimeMon1":"08150915","heatingTimeMon2":"00000000","heatingTimeTue1":"08150915","heatingTimeTue2":"00000000","heatingTimeWed1":"08150915","heatingTimeWed2":"00000000","heatingTimeThu1":"08150915","heatingTimeThu2":"00000000","heatingTimeFri1":"08150915","heatingTimeFri2":"00000000","heatingTimeSat1":"08150915","heatingTimeSat2":"00000000","heatingTimeSun1":"08150915","heatingTimeSun2":"00000000","heatingTimesActiveForComfort":false,"setBackTemperature":"20","convectionFan1Active":false,"convectionFan1Level":0,"convectionFan1Area":0,"convectionFan2Active":false,"convectionFan2Level":0,"convectionFan2Area":0,"frostProtectionActive":false,"frostProtectionTemperature":"4","temperatureOffset":"0","RoomPowerRequest":3,"debug0":0,"debug1":0,"debug2":0,"debug3":0,"debug4":0}
                                        2025-01-26 11:23:55.033 - info: rika-firenet.0 (930580) state rika-firenet.0.xxxxxx3.controls.onOff changed: true (ack = false)
                                        2025-01-26 11:23:55.033 - debug: rika-firenet.0 (930580) url: https://www.rika-firenet.com/api/client/xxxxxx3/status
                                        2025-01-26 11:23:55.298 - debug: rika-firenet.0 (930580) 200 - API-Connection successful
                                        2025-01-26 11:23:55.298 - debug: rika-firenet.0 (930580) onOff = true
                                        2025-01-26 11:23:55.439 - debug: rika-firenet.0 (930580) {"revision":1737880232,"onOff":true,"operatingMode":0,"heatingPower":100,"targetTemperature":"22","bakeTemperature":"180","ecoMode":false,"heatingTimeMon1":"08150915","heatingTimeMon2":"00000000","heatingTimeTue1":"08150915","heatingTimeTue2":"00000000","heatingTimeWed1":"08150915","heatingTimeWed2":"00000000","heatingTimeThu1":"08150915","heatingTimeThu2":"00000000","heatingTimeFri1":"08150915","heatingTimeFri2":"00000000","heatingTimeSat1":"08150915","heatingTimeSat2":"00000000","heatingTimeSun1":"08150915","heatingTimeSun2":"00000000","heatingTimesActiveForComfort":false,"setBackTemperature":"20","convectionFan1Active":false,"convectionFan1Level":0,"convectionFan1Area":0,"convectionFan2Active":false,"convectionFan2Level":0,"convectionFan2Area":0,"frostProtectionActive":false,"frostProtectionTemperature":"4","temperatureOffset":"0","RoomPowerRequest":3,"debug0":0,"debug1":0,"debug2":0,"debug3":0,"debug4":0}
                                        2025-01-26 12:08:55.033 - info: rika-firenet.0 (930580) state rika-firenet.0.xxxxxx3.controls.onOff changed: false (ack = false)
                                        2025-01-26 12:08:55.033 - debug: rika-firenet.0 (930580) url: https://www.rika-firenet.com/api/client/xxxxxx3/status
                                        2025-01-26 12:08:55.288 - debug: rika-firenet.0 (930580) 200 - API-Connection successful
                                        2025-01-26 12:08:55.288 - debug: rika-firenet.0 (930580) onOff = false
                                        2025-01-26 12:08:55.451 - debug: rika-firenet.0 (930580) {"revision":1737887035,"onOff":false,"operatingMode":0,"heatingPower":100,"targetTemperature":"22","bakeTemperature":"180","ecoMode":false,"heatingTimeMon1":"08150915","heatingTimeMon2":"00000000","heatingTimeTue1":"08150915","heatingTimeTue2":"00000000","heatingTimeWed1":"08150915","heatingTimeWed2":"00000000","heatingTimeThu1":"08150915","heatingTimeThu2":"00000000","heatingTimeFri1":"08150915","heatingTimeFri2":"00000000","heatingTimeSat1":"08150915","heatingTimeSat2":"00000000","heatingTimeSun1":"08150915","heatingTimeSun2":"00000000","heatingTimesActiveForComfort":false,"setBackTemperature":"20","convectionFan1Active":false,"convectionFan1Level":0,"convectionFan1Area":0,"convectionFan2Active":false,"convectionFan2Level":0,"convectionFan2Area":0,"frostProtectionActive":false,"frostProtectionTemperature":"4","temperatureOffset":"0","RoomPowerRequest":3,"debug0":0,"debug1":0,"debug2":0,"debug3":0,"debug4":0}
                                        
                                        Codierknecht 2 Replies Last reply Reply Quote 0
                                        • Codierknecht
                                          Codierknecht Developer Most Active @HAL last edited by

                                          @hal sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

                                          wird nicht aktualisiert. Erst wenn der Adapter neu gestartet wird, ist der Status sofort aktualisiert.

                                          Ich schau mal nach, ob und wie ein Wiederverbinden da erfolgt.

                                          1 Reply Last reply Reply Quote 0
                                          • Codierknecht
                                            Codierknecht Developer Most Active @HAL last edited by Codierknecht

                                            @hal sagte in Test Adapter rika-firenet 1.0.0-alpha.x (ALPHA Test):

                                            wird nicht aktualisiert. Erst wenn der Adapter neu gestartet wird, ist der Status sofort aktualisiert.

                                            1. Du verwendest offenbar noch nicht die letzte Version des Adapters. Die Meldung state xxx changed ... wird mittlerweile als "debug" geloggt.

                                            2. Dass der Wert möglicherweise erst nach 1 Minute aktualisiert wird, ist Dir bewusst?
                                              Das Schreiben der Werte hat nix mit dem Lesen zu tun. Letzteres erfolgt in einem festen Intervall.
                                              Wenn ich so darüber nachdenke, macht es aber ggf. Sinn, unmittelbar nach dem Schreiben die Werte 1x neu zu lesen.

                                            HAL 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            585
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            5
                                            46
                                            1761
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo