System changed, new z-wave stick = problems with the climate sensors

Configuration Z-Wave
1

Hello,

I switched my system from a Raspberry Pi 3 with a Razberry board to an Intel NUC with an Aeotec AEOEZW090-C Gen 5 stick. I have multiple thermostat sensors.
I deleted the entry for zwave in config/.storage/core.config_entries and restarted.
The stick was integrated in /dev/serial/by-id/usb-0658_0200-if00. After that I was able to find all the thermostat sensors in the Z-Wave system. The problem is that there is only one entitie in Hassio for each sensor (no battery etc.). And the devices show the manufacturer and model as unknown.
I tried adding it in the lovelace as a climate card. This is also not possible.
What’s the problem here?

2

With the raspberry pi the entities were called “climate.name”. Now they are called “zwave.name”. Does that make the difference?
The state is ready. And the attributes:
node_id: 7 node_name: Unknown Node 7 manufacturer_name: product_name: query_stage: Complete is_awake: true is_ready: true is_failed: false is_info_received: true max_baud_rate: 40000 is_zwave_plus: false capabilities: routing, beaming, frequent neighbors: 11 sentCnt: 2 sentFailed: 0 retries: 0 receivedCnt: 0 receivedDups: 0 receivedUnsolicited: 0 sentTS: 2020-12-03 16:39:45:614 receivedTS: 2020-12-03 16:39:37:087 lastRequestRTT: 1279 averageRequestRTT: 1279 lastResponseRTT: 0 averageResponseRTT: 0 application_version: Unknown friendly_name: Heizunng Wohnzimmer

3

Your device misses information, try refreshing the node and waking up the device to see if it updates anything and no longer shows “Unknown”

4

It works now. I removed all nodes, re-set the thermostat sensors, and put them in as “add node” rather than “add node encryption”.
But now I have the problem that the sensors (Eurotronic Spirit) did not react to temperature and status changes (heat eco …). Not manually in the app and not with automation. If I change it, it will be changed back automatically. I can change it manually on the device itself (+ and - button).
When I restart hassio (supervisor) everything works again for a couple of hours. Then the same problem again.
Here the log when I change it via the app:

2020-12-05 08:27:52.188 Info, Node013, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Heat Eco
2020-12-05 08:27:52.188 Detail, Node013, Queuing (Send) ThermostatModeCmd_Set (Node=13): 0x01, 0x0a, 0x00, 0x13, 0x0d, 0x03, 0x40, 0x01, 0x0b, 0x25, 0xce, 0x49
2020-12-05 08:27:52.188 Detail, Node013, Queuing (Send) ThermostatModeCmd_Get (Node=13): 0x01, 0x09, 0x00, 0x13, 0x0d, 0x02, 0x40, 0x02, 0x25, 0xcf, 0x42
2020-12-05 08:28:00.603 Detail, Node012,   Received: 0x01, 0x0c, 0x00, 0x04, 0x10, 0x0c, 0x06, 0x31, 0x05, 0x01, 0x42, 0x07, 0x53, 0xce
2020-12-05 08:28:00.603 Detail,
2020-12-05 08:28:00.603 Info, Node012, Received SensorMultiLevel report from node 12, instance 1, Temperature: value=18.75C
2020-12-05 08:28:00.603 Detail, Node012, Refreshed Value: old value=18.22, new value=18.75, type=decimal
2020-12-05 08:28:00.603 Detail, Node012, Changes to this value are not verified
2020-12-05 08:28:00.603 Detail, Node012, Notification: ValueChanged

Heal node etc. does not change anything.
Here a node info of one of the sensors:

Node ID 12
Node name EUROtronic EUR_SPIRITZ Wall Radiator Thermostat
Manufacturer name EUROtronic
Product name EUR_SPIRITZ Wall Radiator Thermostat
Query stage Probe
Is awake true
Is ready true
Is failed false
Is info received true
Max baud rate 40000
Is zwave plus true
Capabilities routing, beaming, frequent, zwave_plus
SentCnt 30
SentFailed 0
Retries 0
ReceivedCnt 34
ReceivedDups 0
ReceivedUnsolicited 18
SentTS 2020-12-05 08:42:15:665
ReceivedTS 2020-12-05 08:28:00:603
LastRequestRTT 1806
AverageRequestRTT 1120
LastResponseRTT 65
AverageResponseRTT 59
Battery level 25
Application version

I had the same issue at the very beginning when I first installed hassio with the raspberry pi and razberry board too. But then somehow everything was fine and the error never came back. Unfortunately, I can’t remember how.
Any ideas?

5

That means the device hasn’t finished loading yet. Battery operated devices have to fully complete the query stages before you can fully manage them. Depending on how soon they check in automatically (every couple of hours, some even up to 24) or waking them by hand it can take quite some time before it all “works”. The more they check in the more the battery will drain.

6

Ah ok, now the query state is complete.
Then it should work now
Thank you very much. Learned something again