[WIP] Add support for Aeotec ZWA021 TRV (Eurotronics Spirit Z clones)

[alucryd]

Motivation:

The Eurotronics Spirit Z series of Z-Wave TRVs can accept temperature from an external sensor instead of the included one, or accept manual valve positions via a hidden mode dubbed "Manufacturer Specific". Clones include the Aeotec ZWA021 which I'm targeting here, and the Donexon Varmo TZ eco, which I just received and will be testing later.

This is a good starting point for a zwave_js adapter.

Changes:

• Added a zwave_js adapter
• Added a WZA021 device fix
• Started implementing direct valve control

Related issue (check one):

• fixes Support for zwave #579
• there is no related issue ticket

Checklist (check one):

• I did not change any code (e.g. documentation changes)
• The code change is tested and works locally.

Test-Hardware list (for code changes)

HA Version: 2023.8.4
Zigbee2MQTT Version: N/A
TRV Hardware: Aeotec ZWA021

New device mappings

• I avoided any changes to other device mappings
• There are no changes in climate.py

[alucryd]

Highly WIP, it seems the direct valve control is not implemented yet despite the various set_valve functions being present. Right now the adapter loads fine and picks up the device quirks for the hidden mode, however override_set_hvac_mode is never called when I change modes using the UI card. Since I can't get remote debug to work and debugging with logs is extremely annoying, I need help figuring why that is.

[KartoffelToby]

Hey @alucryd thanks for your work, how can i help you to finish this PR?

[alucryd]

@KartoffelToby If you have any tip to make remote debugging work with VSCode, that would be awesome. I can't get the debugpy HA integration to work. I can connect a debugging session to my HA instance, but VSCode never stops on any breakpoint, I tried a local VSCode and even the VSCode server add-on in HAOS, I am sure the code is identical and breakpoints are recognized since they are not greyed out, but they don't do anything. The debugpy HA developer suggested using setting justMyCode to false in the VSCode debug configuration, but that didn't help.

[KartoffelToby]

@alucryd i'm also not happy with the current dev Setup, so far, i start the vscode dev Container and then start Up hass with a little custom config that adds dummy sensors and trvs. And set the logging to debug for bt:

logger:
  default: warning
  logs:
    custom_components.better_thermostat: debug

Like hass -c .haconfig then you can see all the logs from in the console Output.

Hope this will help

[KartoffelToby]

PR #1058 shoud fix your problem :)

[fisch55]

Hello all,

Any news here yet regarding zwave? Also have the Spirits....
Currently it does not seem to work with BT yet, right?

[xpavli44]

same issue here :(

[alucryd]

Sorry about the lack of reply, turns out working 2 jobs and taking care of a newborn is eating all my free time xD
I settled on using the valve opening percentage to control my heat pump for now, it's working quite well as long as I apply an offset of about -2 degrees Celsius to my target temperature. Optionally you could feed the valves the temperature of an ideally placed temp sensor and do the same without using an offset (as that option is officially supported, unlike directly setting the valve position which isn't exposed by default).

I'd love to continue working on supporting these in BT, but the lack of a usable debug environment doesn't encourage me in the least, running a local instance with a dummy TRV is not exactly feasible, I need to interact with a real Zwave TRV. I'll give remote debug another try when I find some time, but for now I have other priorities.