Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Tuya Thermostat (_TZE200_hue3yfsn)

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Tuya Thermostat (_TZE200_hue3yfsn)

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

      @pete0815 Wärst Du bereit in der kommenden Woche einen Test-Adapter von mir zu installieren der versucht das Problem mit den Meldungen zu beheben / umgehen ? Dann würde ich schauen das ich einen Test zusammen bastle.

      Ohne Hardware zum testen kann ich nicht verifizieren ob das erfolgreich war.

      A.

      ? 2 Replies Last reply Reply Quote 0
      • ?
        A Former User @Asgothian last edited by A Former User

        @asgothian
        klar. Muß nur noch "im Notfall" bzgl. Hitze oder Kälte aggieren können. Dann würde ich die Verbindung wohl kappen und auf manuelle lokale Steuerung des Ventils umstellen. Sonst ist hier gerade recht unkritisch der Betrieb und bastel selber viel rum. Das würde ich natürlich einstellen um die Ergebnisse nicht zu verfälschen.

        D 1 Reply Last reply Reply Quote 0
        • D
          Der Mark @Guest last edited by

          @pete0815
          ich würde auch gleich mit testen.
          Ich habe auch 2 Whitelabel Adapter von TUYA als Marke Tesla TVR1 : TS0601 und _TZE200_husqqvux
          Denke, es ist das gleiche Innenleben nur das drumrum ist anders.

          Link zum Adapter (als MOES Version) : https://www.zigbee2mqtt.io/devices/TV01-ZB.html

          MfG

          Mark

          1 Reply Last reply Reply Quote 0
          • ?
            A Former User @Asgothian last edited by A Former User

            @asgothian

            kannst Du mir sagen wie es üblicherweise abläuft bzgl. dem Zigbee Adapter und Übernahme des Herdsmann converters?

            Wenn ich das richtig verstehe, wurden diverse Optimierung vorgenommen und die Open Window Funktion verbessert:
            https://github.com/Koenkk/zigbee-herdsman-converters/pull/3419

            Habe mich dann etwas tiefer in die Änderungen im Code reingeklickt und glaube auch veränderte Datenpunkte zu sehen, die für das Ventil nun gelten. Hierbei insbesondere der Wochenplan, der bisher bei mir nicht funktioniert hat:
            bisher:
            942af9e0-5e72-4163-bfac-4bc7dc438079-grafik.png

            jetzt neu:
            52fa7039-5f6e-4f49-b20c-9d7f3be47ada-grafik.png

            Wir der Herdmann converter regelmäßig übernommen und im IObroker Adapter eingefügt?

            Besten Dank!

            vladi1234 created this issue in Koenkk/zigbee-herdsman-converters

            closed Deverses fix and open_window function #3419

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @Guest last edited by

              @Asgothian @arteck
              Danke!
              7c81ea7f-e2a2-477e-a569-0531ad54db6b-grafik.png

              1 Reply Last reply Reply Quote 0
              • L
                LPTR last edited by LPTR

                Hallo zusammen,

                Ich habe nun auch ein paar dieser Thermostate im Einsatz.

                7feb23b1-27cf-4340-b3b0-b5d58f1a1e2b-image.png

                Zigbee Adaper auf 1.6.11, gestern das letzte mal aktualisiert.

                Paring war möglich, configured wird als 'false' angezeigt. Datenpunkte sind da und es scheint alles zu funktionieren.

                Allerdings habe ich das selbe 'from String to number' Problem.

                Egal ob ich am Thermometer die Temperaturen ändere...

                2022-01-08 11:04:39.606 - warn: zigbee.0 (30720) SetState_typed : converting "14.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:40.224 - warn: zigbee.0 (30720) SetState_typed : converting "15.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:44.114 - warn: zigbee.0 (30720) SetState_typed : converting "15.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:45.106 - warn: zigbee.0 (30720) SetState_typed : converting "16.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:47.391 - warn: zigbee.0 (30720) SetState_typed : converting "16.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:48.594 - warn: zigbee.0 (30720) SetState_typed : converting "17.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:49.983 - warn: zigbee.0 (30720) SetState_typed : converting "17.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:50.982 - warn: zigbee.0 (30720) SetState_typed : converting "18.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:52.476 - warn: zigbee.0 (30720) SetState_typed : converting "18.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:53.150 - warn: zigbee.0 (30720) SetState_typed : converting "19.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:54.273 - warn: zigbee.0 (30720) SetState_typed : converting "19.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:54.951 - warn: zigbee.0 (30720) SetState_typed : converting "20.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:56.261 - warn: zigbee.0 (30720) SetState_typed : converting "19.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:56.862 - warn: zigbee.0 (30720) SetState_typed : converting "19.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:57.631 - warn: zigbee.0 (30720) SetState_typed : converting "18.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:04:58.341 - warn: zigbee.0 (30720) SetState_typed : converting "18.0" for 2c1165fffec31fad.current_heating_setpoint from string to number
                2022-01-08 11:09:55.602 - warn: zigbee.0 (30720) SetState_typed : converting "21.0" for 2c1165fffec320c2.current_heating_setpoint from string to number
                2022-01-08 11:09:55.712 - warn: zigbee.0 (30720) SetState_typed : converting "21.0" for 2c1165fffec320c2.current_heating_setpoint from string to number
                

                ... oder einen Wert über den IOBroker ändere.

                2022-01-08 11:25:47.731 - warn: zigbee.0 (30720) ELEVATED: User stateChange zigbee.0.2c1165fffec61243.current_heating_setpoint {"val":20,"ack":false,"ts":1641637547728,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641637547728}
                2022-01-08 11:25:47.744 - warn: zigbee.0 (30720) ELEVATED Change state 'current_heating_setpoint' at device 0x2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.408 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.409 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:49.419 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"current_heating_setpoint":"20.0"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.420 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"20.0"' from device 2c1165fffec61243 for 'Temperature setpoint'
                2022-01-08 11:25:49.428 - warn: zigbee.0 (30720) SetState_typed : converting "20.0" for 2c1165fffec61243.current_heating_setpoint from string to number
                2022-01-08 11:25:49.521 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.522 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:49.526 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"preset":"manual"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.527 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"manual"' from device 2c1165fffec61243 for 'Mode of this device (similar to system_mode)'
                2022-01-08 11:25:49.649 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.650 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:49.655 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"preset":"manual"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.655 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"manual"' from device 2c1165fffec61243 for 'Mode of this device (similar to system_mode)'
                2022-01-08 11:25:49.762 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.763 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:49.766 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"current_heating_setpoint":"20.0"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:49.767 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"20.0"' from device 2c1165fffec61243 for 'Temperature setpoint'
                2022-01-08 11:25:49.770 - warn: zigbee.0 (30720) SetState_typed : converting "20.0" for 2c1165fffec61243.current_heating_setpoint from string to number
                2022-01-08 11:25:56.033 - warn: zigbee.0 (30720) ELEVATED: User stateChange zigbee.0.2c1165fffec61243.current_heating_setpoint {"val":14,"ack":false,"ts":1641637556028,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641637556028}
                2022-01-08 11:25:56.044 - warn: zigbee.0 (30720) ELEVATED Change state 'current_heating_setpoint' at device 0x2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.312 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.313 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:56.321 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"current_heating_setpoint":"14.0"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.321 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"14.0"' from device 2c1165fffec61243 for 'Temperature setpoint'
                2022-01-08 11:25:56.330 - warn: zigbee.0 (30720) SetState_typed : converting "14.0" for 2c1165fffec61243.current_heating_setpoint from string to number
                2022-01-08 11:25:56.417 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.418 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:56.421 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"current_heating_setpoint":"14.0"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.422 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"14.0"' from device 2c1165fffec61243 for 'Temperature setpoint'
                2022-01-08 11:25:56.425 - warn: zigbee.0 (30720) SetState_typed : converting "14.0" for 2c1165fffec61243.current_heating_setpoint from string to number
                2022-01-08 11:25:56.535 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.535 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:56.542 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"preset":"manual"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.542 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"manual"' from device 2c1165fffec61243 for 'Mode of this device (similar to system_mode)'
                2022-01-08 11:25:56.663 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"linkquality":255}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.663 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '255' from device 2c1165fffec61243 for 'Link quality'
                2022-01-08 11:25:56.667 - warn: zigbee.0 (30720) ELEVATED publishToState: message received '{"preset":"manual"}' from device 2c1165fffec61243 type 'TV02-Zigbee'
                2022-01-08 11:25:56.667 - warn: zigbee.0 (30720) ELEVATED publishToState: value generated '"manual"' from device 2c1165fffec61243 for 'Mode of this device (similar to system_mode)'
                

                Gibt es mittlerweile einen Workaround oder anderweitige Lösung?

                In den Screenshots der DP oben habe ich gesehen, dass es einen DP 'battery_percentage' gibt. Der taucht bei mir nicht auf. Hat den schon jemand?

                Grüße
                Lars

                1 Reply Last reply Reply Quote 0
                • arteck
                  arteck Developer Most Active last edited by arteck

                  was machst du dass du diesen Fehler erzeugst

                  SetState_typed : converting "19.5" for 2c1165fffec31fad.current_heating_setpoint from string to number
                  

                  ich habe den Thermostat auch und der übermittelt kein battery status ausser Battery_low

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    LPTR @arteck last edited by

                    @arteck
                    Fehlermeldungen Block 1 sind Werteänderungen am Thermostat selber (Drehen am Rad).
                    Block zwei ist eine Änderung des Datenpunkts current_heating_setpoint im IOBroker.

                    arteck 1 Reply Last reply Reply Quote 0
                    • arteck
                      arteck Developer Most Active @LPTR last edited by

                      @lptr ok seh gerade doch nicht das gleiche Gerät

                      zeigmal den datenpunkt als RAW

                      am Datenpunkt auf stift klicken
                      62dbe596-c1e0-4f15-8016-001de72cec9d-grafik.png

                      dann Objektdaten

                      L 1 Reply Last reply Reply Quote 0
                      • L
                        LPTR @arteck last edited by

                        @arteck

                        {
                          "type": "state",
                          "common": {
                            "name": "Temperature setpoint",
                            "type": "number",
                            "unit": "°C",
                            "read": true,
                            "write": true,
                            "role": "state",
                            "min": 0,
                            "max": 30
                          },
                          "native": {},
                          "from": "system.adapter.zigbee.0",
                          "user": "system.user.admin",
                          "ts": 1641569348652,
                          "_id": "zigbee.0.2c1165fffec61243.current_heating_setpoint",
                          "acl": {
                            "object": 1636,
                            "state": 1636,
                            "owner": "system.user.admin",
                            "ownerGroup": "system.group.administrator"
                          }
                        }
                        
                        Asgothian 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @LPTR last edited by

                          @lptr Der Fehler liegt in der Implementierung im Herdsman.
                          Die Warn Meldungen musst du zunächst einmal akzeptieren - ggf. kann man da etwas an der State Definition (getter/setter) machen - aber ich muss erst die Gruppen fertig bekommen.

                          Wenn Du mit den Meldungen absolut nicht leben kannst kann ich Dir schreiben wo du sie heraus patchen kannst - sie sind drin um genau diese Fälle von "unsauberen" states zu finden.

                          A.

                          L 1 Reply Last reply Reply Quote 0
                          • L
                            LPTR @Asgothian last edited by

                            @asgothian

                            Danke für die Info. Wenn schon dran gearbeitet wird kann ich super damit leben, dass es dann in absehbarer Zeit wohl weg sein wird. 👍 👍

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

                            Support us

                            ioBroker
                            Community Adapters
                            Donate
                            FAQ Cloud / IOT
                            HowTo: Node.js-Update
                            HowTo: Backup/Restore
                            Downloads
                            BLOG

                            540
                            Online

                            31.9k
                            Users

                            80.2k
                            Topics

                            1.3m
                            Posts

                            8
                            62
                            12407
                            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