-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
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
Missing Manufacturer Specific mode and valve control for Aeotec TRV #45703
Comments
Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with an integration ( |
The Z-Wave JS integration is about the native HA integration with Z-Wave JS (using the WS Server). For best experience in HA you might want to switch to the new Z-Wave JS integration, you can even use the zwavejs2mqtt docker/addon (just enable the WS Server in settings). If you'd like to stay with MQTT, you should file this report to zwavejs2mqtt on github. |
Or do you mean you actually want the described behavior in the Z-Wave JS integration ? EDIT: After carefully reading again I see that you indeed say that you miss this specific feature in the Z-Wave JS integration, the MQTT stuff was just additional info |
correct, i would like to have these features in Z-wave JS integration. The MQTT stuff I was just pasting in the hope that it would be a bit clearer what I wanted to accomplish. :) |
Yeah, It's clear now. I didn't read well enough first time ;-) |
unfortunately I do not know much about programming more than basic edits, but this is something I managed to do on the legacy zwave integration to expose cover/dimmer control for the Aeotec TRV valve position (also applies for the Eurotronic Spirit TRV which is the same device). Do not know if this is in anyway helpful however for the zwave-js integration: https://gist.github.com/insajd/b1c922284ec2e38e84704db16429e001/revisions Also for reference: https://community.home-assistant.io/t/eurotronic-spirit-z-wave-external-temperature-sensor/88430/31 |
For completeness, can you please share a dump of your mesh with us to investigate ? |
Attached. Rename to .jsonl |
That sounds like something that should be changed with a |
Just further clarify, in open zwave beta these thermostats in my case the eurotronic spiritz enumerated with a valve position attribute that could be read in any mode. And then in manufacturer specific mode that attribute becomes the only mechanism to set the valve %. I use the valve % to calculate heat demand in my house, which in turn activates the boiler to provide the heat. So it's going to be a little colder this week, and looking at the weather forecast it is going to be quite a bit cooler, with snow ❄️ on the weekend! |
temp solution that's working for me is to get the valve position via MQTT. I'm doing this by:
|
I have the same issue with Eurotronics Spirit Thermostat Radiator Valves. Currently the only modes that can be specified are: 'None', 'Energy heat', 'Full power'. According to the manual this should be: Is it possible to get the 'Manufacturer Specific' mode available in Zwave JS? I'm running core-2021.3.2 |
Does the thermostat report this mode as supported? |
Doesn't seem like it reports the mode as supported:
So you'll have to wait for the workaround in zwave-js/node-zwave-js#1625 to be implemented or (like I like to preach) bug the manufacturer to fix their shit. Btw, this is the table you should be looking at (Thermostat Mode, not Basic CC): Side note: I'm not sure what's possible in HA, but you should be able to simply set this value to 31 (0x1f) even though that mode is not reported. |
We have a service to change config parameters. |
@MartinHjelmare this is not about config parameters. |
It seems that the 'Manufacturer Specific' mode must be enabled via the BASIC command class. See here for some more information: https://community.openhab.org/t/eurotronic-spirit-unsupported-mode-type-31/57265/35 Is this something that we can enable for this device in ZwaveJS? |
@stefans2904 we could keep the Basic CC from being hidden, so you can use it to enable the mode until the workaround is in place. But this also won't be perfect:
|
For me that won't be a problem as I can use an Automation that triggers when the Thermostat mode changes after pressing the buttons on the device. That automation can then change the Basic Mode to Heating. |
@AlCalzone is this something that can be done (keep the Basic CC from being hidden)? Can I manually do this somehow? |
@stefans2904 you would have to edit the config file for the device and add the compat flag Mount that config file into the correct location in the container, re-interview the node to enable it. |
The problem
Currently, climate entity exposes only Heat and Off modes and three presets for Aeotec Thermostat Radiator Valve (ZWA021).
However, Aeotec TRV supports a third mode, namely Manufacturer Specific, which allows direct valve control. Enabling this should expose a new entity (dimmer or cover type) allowing 0-100 / 0-255 valve control of the TRV.
When using Zwavejs2mqtt via mosquitto broker and mqtt integration, this third mode can be enabled by adding the following code in the ZWJS2M control panel - with fan_only: 31 being used to set the TRV to Manufacturer Specific
This lets the user set the thermostat in Manufacturer Specific mode and control the valve position via a separate light dimmer entity. This allows to move the valve logic from the controller level up to HA level and allows the user to create more useful and precise automations for the TRV.
I know that the Zwave-js integration is at its beginning, but it would be useful if we could replicate this functionality via the Z-wave JS integration, without having to depend on a mqtt broker.
Environment
HA core-2021.2.0b1 supervisor-2021.01.8 Z-Wave JS addon 0.1.1
The text was updated successfully, but these errors were encountered: