Hama Thermostat window_detected immer imme true

mariatschi0815 commented 2 years ago

Hallo,

laut Hama müsste die Funktion der Fenstererkennung einstellbar sein. window_detected steht aber immer auf "true". Somit regelt die Heizung automatisch runter... müsste hier statt dem value nicht ein state rein?

{
  "type": "state",
  "common": {
    "name": "Window detected",
    "type": "boolean",
    "read": true,
    "write": false,
    "role": "value"
  },
  "native": {},
  "from": "system.adapter.zigbee.0",
  "user": "system.user.admin",
  "ts": 1641330428571,
  "_id": "zigbee.0.cc86ecfffea100f2.window_detected",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

und beim Running_Mode war ein Tippfehler im state stand "idle;idle" statt "idle:idle" zumindest vermute ich, dass es so heißen sollte.

{
  "type": "state",
  "common": {
    "name": "Running Mode",
    "type": "string",
    "states": "idle:idle;heat:heat",
    "read": true,
    "write": true,
    "role": "state"
  },
  "native": {},
  "_id": "zigbee.0.cc86ecfffea100f2.running_state",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.admin.0",
  "user": "system.user.admin",
  "ts": 1641331845038
}

Mod Edit: Correct code tags for readability

asgothian commented 2 years ago

Which adapter version are you using ?
What is the exact device ID (Seen on the info page of the units tile
what messages are generated by the system if you enter cc86ecfffea100f2 into zigbee.0.info.debugmessages (Enter the value, change states and use the Thermostat while recording your actions. Afterwards, check the log for warn messages with the keyword "ELEVATED"

A.

mariatschi0815 commented 2 years ago

The Version is: v1.6.6

what id?

model:SEA801-Zigbee/SEA802-Zigbee
description:Thermostatic radiator valve

modelZigbee:TS0601
type:EndDevice
nwk:45911
manuf id:4098
manufacturer:_TZE200_yw7cahqs
power:Battery
app version:85
hard version:1
zcl version:3
stack version:0
date code:
interviewed:true
configured:true

and these are the warnings/errors

<!--StartFragment-->

zigbee.0 | 2022-01-05 12:07:20.013 | warn | ELEVATED Change state 'target_temperature' at device 0xcc86ecfffea100f2 type 'SEA801-Zigbee/SEA802-Zigbee'
-- | -- | -- | --
zigbee.0 | 2022-01-05 12:07:20.004 | warn | ELEVATED:  User stateChange zigbee.0.cc86ecfffea100f2.target_temperature  {"val":20,"ack":false,"ts":1641380839995,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641380839995}
zigbee.0 | 2022-01-05 12:07:12.289 | warn | ELEVATED Change state 'mode' at device 0xcc86ecfffea100f2 type 'SEA801-Zigbee/SEA802-Zigbee'
zigbee.0 | 2022-01-05 12:07:12.273 | warn | ELEVATED:  User stateChange zigbee.0.cc86ecfffea100f2.mode  {"val":"auto","ack":false,"ts":1641380832265,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641380832265}
zigbee.0 | 2022-01-05 12:07:06.167 | error | No converter available for 'SEA801-Zigbee/SEA802-Zigbee' with key 'running_state'
zigbee.0 | 2022-01-05 12:07:06.160 | warn | ELEVATED Change state 'running_state' at device 0xcc86ecfffea100f2 type 'SEA801-Zigbee/SEA802-Zigbee'
zigbee.0 | 2022-01-05 12:07:06.151 | warn | ELEVATED:  User stateChange zigbee.0.cc86ecfffea100f2.running_state  {"val":"heat","ack":false,"ts":1641380826145,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641380826145}
zigbee.0 | 2022-01-05 12:06:59.121 | warn | ELEVATED Change state 'device_query' at device 0xcc86ecfffea100f2 type 'SEA801-Zigbee/SEA802-Zigbee'
zigbee.0 | 2022-01-05 12:06:59.105 | warn | ELEVATED:  User stateChange zigbee.0.cc86ecfffea100f2.device_query  {"val":true,"ack":false,"ts":1641380819095,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1641330515836}

<!--EndFragment-->
</body>
</html>

Mod-Edit: correct code tags for readability

asgothian commented 2 years ago

Please add the device to the "ausschliessen" liste to ensure use of exposes and try again. If the situation remains, please update to the current git version. Some of the effects you describe should be fixed already.

Note that no mention is made of the state window_detected, i.e. the thermostat does not seem to report this, while the change to running_state is not accepted by the zigbee-herdsman-converters.

A.

mariatschi0815 commented 2 years ago

At first it worked with v1.6.8, but there were some values missing (null) so I decied to delete the device and pair it again... after the pairing I'm back where it started

asgothian commented 2 years ago

The current GitHub version is 1.6.11, not 1.6.8
Did you check the "ausschliessen" tab ?
Did you give it time to report the values (up to 6 hrs) ?

mariatschi0815 commented 2 years ago

oh okay, I just updated via ioBroker there was the 1.6.8 the latest version... nevermind, i managed to insatll .11

I checked it with "ausschliessen" with the same results.

Obviously I didn't wait long enough...

and I'll wait until tomorrow.

asgothian commented 2 years ago

Looking in more detail at the implementation and the zigbee2mqtt.io description:

Several states are not reported when changed on the Thermostat and cannot be read directly. Instead, they need to be read via writing an empty payload. I was unable to determine if this is the case in the current zigbee adapter code.
The zigbee adapter code is implementing several states which are not actually referenced in the zigbee-herdsman-converters implementation.

Unfortunately, this will not be an easy fix and will be near impossible without physical access to the device.

I suggest you take a closer look at:

the Hama thermostat description at zigbee2mqtt.io. Take special care to check which states can be read by "setting" them with an empty value. You can use local scripts using the sendTo function to trigger a read of the state . See this post on the iobroker forum for a short explanation (https://forum.iobroker.net/topic/50560/ikea-e1525-e1745-parameter-support/2?_=1641300767872)
The implementation of the device in /opt/ioBroker/node_modules/zigbee-herdsman-converters/devices/saeswell.js
The implementation of the device in /opt/ioBroker/node_modules/iobroker.zigbee/lib/devices.js

In the end, i would suggest that you add the device to the "Ausschliessen" tab and then perform a state cleanup to get rid of unsupported states (which should include the window detection). This can be done using the button with the circular arrows on the device view of the adapter.

A.

mariatschi0815 commented 2 years ago

So, I tried another way. I paired the device with zigbee2mqtt and now it's working. i.e. I can set the window detection off and the away mode, etc.. Maybe there's just a "translation problem" from zigbee2mqtt to the zigbee-adapter?

The window detection seems not to work anyway, but that's no problem because I can set it off and use a door and window sensor instead.

Edit: Sorry, you were absolutely right. Now I know what you mean. I can only get the states, but dont write them. But how does ist work in zigbee2mqtt then? I can set i.e. the temperature.

mariatschi0815 commented 2 years ago

How can I have a look at them?

The implementation of the device in /opt/ioBroker/node_modules/zigbee-herdsman-converters/devices/saeswell.js The implementation of the device in /opt/ioBroker/node_modules/iobroker.zigbee/lib/devices.js

arteck commented 2 years ago

How can I have a look at them?

The implementation of the device in /opt/ioBroker/node_modules/zigbee-herdsman-converters/devices/saeswell.js The implementation of the device in /opt/ioBroker/node_modules/iobroker.zigbee/lib/devices.js

?? vi or nano.. the path to the file is in your post

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

ioBroker / ioBroker.zigbee

Hama Thermostat window_detected immer imme true #1321