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.
    • D
      diti @Guest last edited by

      @pete0815
      ich gehe davon aus dass, der Ventil nie die lokale Temperatur einfach so rum sendet. Die wird bekannt gegeben,wenn der Ventil von Smart Life, Tuya Smart angesprochen wird (auf welche Weise weiß ich nicht), oder wenn er ein Signal für Temperatur-Kalibrierung bekommt, hier muss er logisch Ergebnisse der Kalibrierung zeigen. Warum das bei dir nicht geht, weiß ich nicht. Aktualisierung der lokalen Temperatur mache ich mit einfachen Blockly-Skript
      4.PNG

      Was es um die Ventilposition geht, der Thermostat hat ja kein Data Point ID um das von extern zu steuern, oder?
      Danke für Info über Einpflegung in Zigbee2MQTT, jetzt läuft´s bei mir direkt ohne Umwege.
      1.PNG
      2.PNG
      3.PNG

      Das einzige Problem was ich habe nur diese Meldungen, die ständig auftreten

      2021-11-22 18:07:29.191 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:07:29.314 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:12:20.998 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314f1.current_heating_setpoint" has to be type "number" but received type "string"
      2021-11-22 18:12:21.024 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314aa.current_heating_setpoint" has to be type "number" but received type "string"
      2021-11-22 18:12:21.191 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe631473.current_heating_setpoint" has to be type "number" but received type "string"
      2021-11-22 18:12:22.051 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.current_heating_setpoint" has to be type "number" but received type "string"
      2021-11-22 18:12:27.416 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314f1.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:12:27.514 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314aa.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:12:27.537 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314f1.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:12:27.630 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314aa.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:12:27.703 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe631473.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:12:27.809 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe631473.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:12:28.524 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:12:28.633 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:17:27.398 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:17:27.490 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe631473.local_temperature" has to be type "number" but received type "string"
      2021-11-22 18:17:27.527 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314cb.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:17:27.621 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe631473.local_temperature_calibration" has to be type "number" but received type "string"
      2021-11-22 18:17:28.355 - info: zigbee.0 (8262) State value to set for "zigbee.0.50325ffffe6314f1.local_temperature" has to be type "number" but received type "string" 
      

      ich glaube das hat mit dem neuen Zigbee Adapter 1.6.7 zu tun hat.

      Asgothian ? 2 Replies Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @diti last edited by

        @diti sagte in Tuya Thermostat (_TZE200_hue3yfsn):

        ich glaube das hat mit dem neuen Zigbee Adapter 1.6.7 zu tun hat.

        Da bin ich unsicher. Überprüfe bitte nochmal dein Skript. Die Meldungen besagen das der Wert der in einen Datenpunkt geschrieben wird das falsche Format hat.

        Um festzustellen wer da was macht kannst du in den State zigbee.0.info.debugmessages testweise den Wert 50325ffffe6314cb eintragen und dann das Log beobachten. Passend zu den geposteten Info Meldungen sollten warn Meldungen mit dem Text "ELEVATED" kommen. Wenn du da mal einen Satz posten könntest können wir dem Nachgehen.

        @diti sagte in Tuya Thermostat (_TZE200_hue3yfsn):

        ich gehe davon aus dass, der Ventil nie die lokale Temperatur einfach so rum sendet. Die wird bekannt gegeben,wenn der Ventil von Smart Life, Tuya Smart angesprochen wird (auf welche Weise weiß ich nicht), oder wenn er ein Signal für Temperatur-Kalibrierung bekommt, hier muss er logisch Ergebnisse der Kalibrierung zeigen. Warum das bei dir nicht geht, weiß ich nicht. Aktualisierung der lokalen Temperatur mache ich mit einfachen Blockly-Skript

        Nutzt du die von Dir gepatchte Version der Herdsman Einbindung oder die von der @pete0815 geschrieben hat ?

        Eigentlich sollte der Thermostat temperaturänderungen selbstständig melden. Gut, es ist Tuya, da ist das nicht immer sicher. Trotzdem würde ich statt die Temperaturkalibration zu setzen mal versuchen über den State "Device Query" den Thermostat zu triggern seine vorhandenen Werte zu senden.

        A.

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

          @diti
          Danke fürs Feedback und verstehe Dich als nutzt Du jetzt den 1.6.7 Adapter ohne eigene Modifikationen.
          Das wäre gleich wie bei mir aber ich stelle wesentlich weniger "Reaktionen" des Thermostats fest. Eine Veränderung der Temperaturkalibrierung bewirkt im Prinzip nichts.

          Die Meldungen bzgl. falscher Datentypen habe ich ebenfalls auch für verschiedene DPs.
          Ich habe mal die debugmessages aktiviert um vlt. sehen zu können was dort gesendet und empfangen wird:

          2021-11-21 19:27:37.762 - info: zigbee.0 (23594) State value to set for "zigbee.0.9035eafffe418d35.holiday_mode_date" has to be type "number" but received type "string"
          2021-11-21 19:27:37.798 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"linkquality":69}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.800 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '69' from device 9035eafffe418d35 for 'Link quality'
          2021-11-21 19:27:37.801 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":81,\"dp\":101,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,0]}},\"linkquality\":69,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":93,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.802 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":81,\"dp\":101,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,0]}},\"linkquality\":69,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":93,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 9035eafffe418d35 for 'Message from Zigbee'
          2021-11-21 19:27:37.834 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"boost_timeset_countdown":0}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.837 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '0' from device 9035eafffe418d35 for 'Setting minimum 0 - maximum 465 seconds boost time. The boost (♨) function is activated. The remaining time for the function will be counted down in seconds ( 465 to 0 ).'
          2021-11-21 19:27:37.955 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"linkquality":69}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.957 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '69' from device 9035eafffe418d35 for 'Link quality'
          2021-11-21 19:27:37.958 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":82,\"dp\":102,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,210]}},\"linkquality\":69,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":94,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.959 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":82,\"dp\":102,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,210]}},\"linkquality\":69,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":94,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 9035eafffe418d35 for 'Message from Zigbee'
          2021-11-21 19:27:37.976 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"open_window_temperature":"21.0"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:37.979 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"21.0"' from device 9035eafffe418d35 for 'Open window temperature'
          2021-11-21 19:27:37.999 - info: zigbee.0 (23594) State value to set for "zigbee.0.9035eafffe418d35.open_window_temperature" has to be type "number" but received type "string"
          2021-11-21 19:27:38.113 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"linkquality":75}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.115 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '75' from device 9035eafffe418d35 for 'Link quality'
          2021-11-21 19:27:38.116 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":83,\"dp\":104,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,210]}},\"linkquality\":75,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":95,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.117 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":83,\"dp\":104,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,210]}},\"linkquality\":75,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":95,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 9035eafffe418d35 for 'Message from Zigbee'
          2021-11-21 19:27:38.144 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"comfort_temperature":"21.0"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.147 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"21.0"' from device 9035eafffe418d35 for 'Comfort temperature'
          2021-11-21 19:27:38.272 - info: zigbee.0 (23594) State value to set for "zigbee.0.9035eafffe418d35.comfort_temperature" has to be type "number" but received type "string"
          2021-11-21 19:27:38.290 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"linkquality":75}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.292 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '75' from device 9035eafffe418d35 for 'Link quality'
          2021-11-21 19:27:38.293 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"msg_from_zigbee":"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":84,\"dp\":105,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,170]}},\"linkquality\":75,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":96,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.294 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"{\"type\":\"commandGetData\",\"data\":{\"status\":0,\"transid\":84,\"dp\":105,\"datatype\":2,\"fn\":0,\"data\":{\"type\":\"Buffer\",\"data\":[0,0,0,170]}},\"linkquality\":75,\"groupID\":0,\"cluster\":\"manuSpecificTuya\",\"meta\":{\"zclTransactionSequenceNumber\":96,\"manufacturerCode\":null,\"frameControl\":{\"frameType\":1,\"manufacturerSpecific\":false,\"direction\":1,\"disableDefaultResponse\":false,\"reservedBits\":0}},\"endpoint_id\":1}"' from device 9035eafffe418d35 for 'Message from Zigbee'
          2021-11-21 19:27:38.322 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"eco_temperature":"17.0"}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.325 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '"17.0"' from device 9035eafffe418d35 for 'Eco temperature'
          2021-11-21 19:27:38.346 - info: zigbee.0 (23594) State value to set for "zigbee.0.9035eafffe418d35.eco_temperature" has to be type "number" but received type "string"
          2021-11-21 19:27:38.448 - warn: zigbee.0 (23594) ELEVATED publishToState: message received '{"linkquality":75}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-21 19:27:38.450 - warn: zigbee.0 (23594) ELEVATED publishToState: value generated '75' from device 9035eafffe418d35 for 'Link quality'
          

          @asgothian die Aktualisierung der lokalen Temperatur wurde bis jetzt leider von niemandem automatisch berichtet und die Werte sogar als falsch deklariert. Da ich die Temperatur nur beim Pairing bekomme, bin ich an dem Schritt noch nicht.
          Um im Sinn der Batterie Strom zu sparen und das Ventil nicht zu sehr zu stressen finde ich die Idee ganz gut, dass auch über einen Zeitplan zu lösen (Nachts geringere Aktualisierungsintervalle als Tags).

          Du meinst mit State Device Query den Button in den Objekten? Kann man diesen noch konfigurieren? Derzeit bringt eine Auslösung keine Aktualisierung von DPs oder Meldungen dazu im Log:

          2021-11-23 08:58:31.313 - warn: zigbee.0 (29765) ELEVATED publishToState: message received '{"available":true}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-23 08:58:31.315 - warn: zigbee.0 (29765) ELEVATED publishToState: value generated 'true' from device 9035eafffe418d35 for 'Available'
          2021-11-23 08:58:31.317 - warn: zigbee.0 (29765) ELEVATED publishToState: message received '{"linkquality":10}' from device 9035eafffe418d35 type 'TV02-Zigbee'
          2021-11-23 08:58:31.318 - warn: zigbee.0 (29765) ELEVATED publishToState: value generated '10' from device 9035eafffe418d35 for 'Link quality'
          2021-11-23 08:59:00.853 - warn: zigbee.0 (29765) ELEVATED: User stateChange zigbee.0.9035eafffe418d35.device_query {"val":true,"ack":false,"ts":1637654340836,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1637654340836}
          2021-11-23 08:59:00.895 - warn: zigbee.0 (29765) ELEVATED Change state 'device_query' at device 0x9035eafffe418d35 type 'TV02-Zigbee'
          

          Edit: Gerade einmal ganz frisch nochmal neu versucht, da ja manche Geräte auf einigen Kanälen Probleme machen sollen. Neu Installation und jetzt auf Kanal 18 statt 26 aber wiederholt gleiches Ergebnis -> Keine Aktualisierung durch manuelle Anpassung der Temperaturkalibrierung und schon beim Pairen diese Datentypfehler:

          2021-11-23 15:46:43.278 - info: zigbee.0 (7462) Zigbee: allowing new devices to join.
          2021-11-23 15:47:11.461 - info: zigbee.0 (7462) Starting interview of '0x9035eafffe418d35'
          2021-11-23 15:47:11.661 - warn: zigbee.0 (7462) Device '0x9035eafffe418d35' announced itself
          2021-11-23 15:47:14.189 - info: zigbee.0 (7462) Successfully interviewed '0x9035eafffe418d35', device has succesfully been paired
          2021-11-23 15:47:14.192 - info: zigbee.0 (7462) Device '0x9035eafffe418d35' is supported, identified as: TuYa Thermostat radiator valve (TV02-Zigbee)
          2021-11-23 15:47:20.541 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.current_heating_setpoint" has to be type "number" but received type "string"
          2021-11-23 15:47:20.587 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.local_temperature" has to be type "number" but received type "string"
          2021-11-23 15:47:20.788 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.local_temperature_calibration" has to be type "number" but received type "string"
          2021-11-23 15:47:20.947 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.holiday_temperature" has to be type "number" but received type "string"
          2021-11-23 15:47:21.557 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.holiday_mode_date" has to be type "number" but received type "string"
          2021-11-23 15:47:21.818 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.open_window_temperature" has to be type "number" but received type "string"
          2021-11-23 15:47:21.971 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.comfort_temperature" has to be type "number" but received type "string"
          2021-11-23 15:47:22.054 - info: zigbee.0 (7462) State value to set for "zigbee.0.9035eafffe418d35.eco_temperature" has to be type "number" but received type "string"
          2021-11-23 15:47:44.629 - info: zigbee.0 (7462) Zigbee: stop joining
          

          Edit2: Und schon funktioniert es. Die manuelle Temperaturkalibrierung hat als String Eingabe zu erfolgen, nicht als Number. Dann wird auch die lokal Temperatur sofort aktualisiert.

          Edit3: Leider bleibt das Problem der Datentypen aktuell bestehen. Ich beschreibe Datentypen als String und das erzeugt eine Warnung. Habe versucht die Datentypen der DPs in String zu ändern, aber diese werden bei der nächsten Aktualisierung wieder zurück gestellt. Entsprechend bekomme ich bei "einer Temperaturabfrage" jede Stunde, 24 dieser Warnungen je Tag ins Protokoll geschrieben. Stört natürlich und kann man das lösen?

          	2021-11-24 10:15:02.291	info	State value to set for "zigbee.0.9035eafffe418d35.local_temperature_calibration" has to be type "number" but received type "string"
          	2021-11-24 10:15:02.112	info	State value to set for "zigbee.0.9035eafffe418d35.local_temperature" has to be type "number" but received type "string"
          	2021-11-24 10:15:00.121	info	State value to set for "zigbee.0.9035eafffe418d35.local_temperature_calibration" has to be type "number" but received type "string" 
          
          Asgothian 1 Reply Last reply Reply Quote 0
          • 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

                                  940
                                  Online

                                  31.9k
                                  Users

                                  80.2k
                                  Topics

                                  1.3m
                                  Posts

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