Fibaro Radiator Thermostat

Avatar
  • updated

Fibaro radiator thermostat error message Devices : No response to Battery.

Every hour for each valve.

It is set to: Enable polling

It transmits the battery charge value at the set interval with polling.

But why does it put a No response to Battery error in the LOG?

Avatar
István Gehl

Hi,


It may be related to the fact that the temperature data is only transferred from the thermostat to the server by polling, and it would have to be transferred even if there is a change. I think this is an incompatibility on the Z-Wave side that cannot be solved.

Best regards, István

Avatar
ignazio cannizzaro

Hi, is fibaro-yubii still integrable with the server?

Avatar
Jürgen Jürgenson
Quote from István Gehl

Unfortunately, network heal doesn't change anything.

Have you tried to remove them and add back? Sometimes, excluding and re-including the device in the Z-Wave network can help clear up errors.

Avatar
István Gehl

Unfortunately, network heal doesn't change anything.

Avatar
Jürgen Jürgenson
Quote from István Gehl


Thanks for the answer, I don't know the solution yet, don't you have such a log?


No response to Sensor Multilevel.

No response to Battery.

Have you tried z-wave network heal? 

Avatar
István Gehl
Quote from Jürgen Jürgenson

Hey,

It's hard to say what might be causing this issue. I only have one Fibaro device with a battery, and when it ran out of power, I logged its battery status but didn't see any errors in the logs. But one disconnected fibaro plug is spamming the log after every 5 minutes.

Do you use an analog log to monitor it? Maybe the read interval is different and doesn't align with the polling interval?


Thanks for the answer, I don't know the solution yet, don't you have such a log?


No response to Sensor Multilevel.

No response to Battery.

Avatar
Jürgen Jürgenson

Hey,

It's hard to say what might be causing this issue. I only have one Fibaro device with a battery, and when it ran out of power, I logged its battery status but didn't see any errors in the logs. But one disconnected fibaro plug is spamming the log after every 5 minutes.

Do you use an analog log to monitor it? Maybe the read interval is different and doesn't align with the polling interval?