I don’t know zwave.me - Hass uses have python-openzwave, so you need to have that working.
Also, Hass needs exclusive access to your ZWave USB stick, so you need to stop everything else that might access it.
Ah, I see. That shouldn’t make any difference though - I’m guessing you access it through a tty device and hass needs exclusive access to it.
I’m using an Aeon Labs USB stick that presents itself as /dev/ttyACM0 - so that might be different for your setup.
Also the config path will most likely be different for you as I’m running hass as a Docker container.
Ah, I see. I’m not sure how this integrates into hass, though.
Something is providing the ZWave controller function and creating the MQTT messages - I’m guessing that’s zwave.me doing.
Since hass would only communicate with your thermostats via MQTT messages, you don’t need the ZWave component but rather an MQTT climate component.
Not sure if that exists.
Since you’re probably not the only one using an RPi, there should be some users out there that could show you how this is set up correctly.