mystic current
gettin a
Error executing script. Error for call_service at pos 2: Unable to set value 69-37-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 3 attempts. Transmission queue full (ZW0202)
which I don't understand, if, the 69 in that code refers to the nodeid? Does it? In that case, it references a device that is not involved in the script at all... If it doesn't, what would this error code mean?
please have a look with me, thx.
what does this error mean: Unable to set value 69-37-0-targetValue
charred condor
That is the node id
mystic current
nodeid 69, and the other part of the error? -37-0? I figured it would be some parameter, but these devices have only a few, 0-4 to be precise
btw, still enjoying that markdown.... 1 click to any device node-id 😉
summer storm
I think 37 might be the command class?
charred condor
nodeid 69, and the other part of the error? -37-0? I figured it would be some pa...
Binary switch, target value
It's not a configuration parameter
If you check the definition of the switch entity in the node diagnostics, you should see the reference to that value id
mystic current
ok, and 0 meaning turn 'off' ?
charred condor
0 is the endpoint
The error doesn't show the value it's being set to
Here is a graphic that explains this a little
Z-Wave JS UI writes them as nodeid-endpoint-cc-property[-propertykey]
mystic current
thx, will study that tonight. hope it will explain why it failed to send the command, though that might be not related to the device itself, but to the state of the Zwave network at the time
seeing the same as I typed the above....
Error while refreshing value Value(value_id='106-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202
but now for another device
charred condor
I think there is something else going on. Can you share a driver log on loglevel debug that includes the failed attempt?
mystic current
would this be what you need:
charred condor
I could swear I've linked you the docs on how to create driver logs at least 2x in the past 😇
mystic current
most of the time the log is filled with this
2024-11-27T03:14:43.634Z DRIVER dropping CC with invalid values (Reason: Unexpected meter type or corrupted da
ta)
2024-11-27T03:15:01.413Z DRIVER dropping CC with invalid values (Reason: Unexpected meter type or corrupted da
ta)
2024-11-27T03:15:02.538Z CNTRLR [Node 013] Timed out while waiting for a response from the node (ZW0201)
2024-11-27T03:15:02.690Z DRIVER dropping CC with invalid values (Reason: Unsupported meter scale kWh or corrup
ted data)
2024-11-27T03:15:03.684Z CNTRLR [Node 039] Timed out while waiting for a response from the node (ZW0201)
2024-11-27T03:15:08.036Z CNTRLR [Node 102] Timed out while waiting for a response from the node (ZW0201)
2024-11-27T03:15:14.712Z DRIVER dropping CC with invalid values (Reason: Unexpected meter type or corrupted da
ta)
2024-11-27T03:15:43.640Z DRIVER dropping CC with invalid values (Reason: Unexpected meter type or corrupted da
ta)
2024-11-27T03:16:13.643Z DRIVER dropping CC with invalid values (Reason: Unexpected meter type or corrupted da
ta)
but it doesnt seem to hurt the functionality.
charred condor
that's closer, but I need "debug" level
mystic current
I have 1 automation that triggers a zwave refresh of several devices
automation:
- id: force_update_totaal_sensors
triggers:
trigger: time_pattern
minutes: /15
actions:
action: zwave_js.refresh_value
data:
refresh_all_values: false
# target:
entity_id:
- sensor.boiler_bijkeuken_totaal
- sensor.espresso_keuken_totaal
- sensor.wasdroger_bijkeuken_totaal
- sensor.freezer_bijkeuken_totaal
- sensor.quooker_keuken_totaal
few more here
``` maybe that causes it?