Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devolo Room Sensor is not report as Climate Device (ZWaveJS) #46643

Closed
Minims opened this issue Feb 16, 2021 · 7 comments · Fixed by #47087
Closed

Devolo Room Sensor is not report as Climate Device (ZWaveJS) #46643

Minims opened this issue Feb 16, 2021 · 7 comments · Fixed by #47087

Comments

@Minims
Copy link
Contributor

Minims commented Feb 16, 2021

The problem

The Devolo Room Sensor (MT2649 / DRS21 par Danfoss [Firmware: 1.0]) is not display as a Climate device in home assistant.
It was the case with the deprecated OWZ 1.4 integration.

It only report :

  • Room Thermostat: Air temperature
  • Room Thermostat: Battery level
  • Room Thermostat: Low battery level
  • sensor.room_thermostat_indicator_value

I have tried zwavejs2mqtt and same issue. But I can see 3 setpoint in device configuration with attributes.
So it might be missing something in the configuration of my device.

What is version of Home Assistant Core has the issue?

core-2021.2.3

What was the last working version of Home Assistant Core?

Works with deprecated OZW 1.4

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

zwavejs

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Example YAML snippet

# Put your YAML below this line

Anything in the logs that might be useful for us?

# Put your logs below this line

Here some raw informations, hope it can help :

ZwaveJS2MQTT config
Devolo Room Sensor

ZwaveJS Dump =>
zwave_js_dump.jsonl.zip

ZwaveJS Integration
ZwaveJS

OWZ 1.4 Integration (Depecated) =>

OWZ 1 4

@probot-home-assistant
Copy link

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration (zwave_js) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@kpine
Copy link
Contributor

kpine commented Feb 16, 2021

This device identifies as a sensor not a thermostat, so the way HA is setup it can't recognize it as a thermostat. The rules for discovering a climate entity would need to be updated to allow this device type (or relaxed to be less strict, only checking command classes), or the newly introduced product-specific rules (quirks) could be utilized.

          "deviceClass": {
            "basic": "Routing Slave",
            "generic": "Multilevel Sensor",
            "specific": "Routing Multilevel Sensor",
            "mandatorySupportedCCs": [
              "Basic",
              "Multilevel Sensor"
            ],
            "mandatoryControlCCs": []
          },

The issue is Generic/Specific being Multilevel Sensor/Routing Multilevel Sensor.

@MartinHjelmare
Copy link
Member

Can anything be controlled with this device or does it only measure temperature etc?

@Minims
Copy link
Contributor Author

Minims commented Feb 16, 2021

Can anything be controlled with this device or does it only measure temperature etc?

Yes,

Sensor:

  • give the room temperature
  • give the battery state

Switch:

  • There is a button on top of the Room Sensor.
    => It can be use the launch action.

Climate :

  • You can define a target temperature from this Room Sensor.
    => So with an automation for example, you can control a GenericClimate entity (relay on the gaz boiler) with a physical device.

description_1_en

@Minims
Copy link
Contributor Author

Minims commented Feb 16, 2021

Devolo RS Room Sensor is the same as "Danfoss Link™, Room sensor, 014G0160"

@kristianwh
Copy link

I have also been using these successfully with the old Zwave-integration.
There they appeared as climate devices with setpoint etc. Changing the setpoint from within home assistant also updated the setpoint on the devices (not always, but I guess that was because of wakeup-interval / timeout of the command).
Hope this can be re-added as a climate-device in home assistant, so the setpoint-functionality will be usable again.

@Minims
Copy link
Contributor Author

Minims commented Feb 23, 2021

I don't know how to fix this in HA, but if I can try to debug it. @kpine any idea where I can start ? Thx.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants