Replies: 3 comments
-
Somebody has an idea ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
It would be great to know which device throws this error. Also, any automations wrongly coded? |
Beta Was this translation helpful? Give feedback.
0 replies
-
the problem is that there is no information about the device that cause this error ! i have 83 devices so impossible to check manually. Is there a way to trace because debug is not more informative that what i putted in description ! Le 2 nov. 2024 à 17:50, chris-1243 ***@***.***> a écrit :
It would be great to know which device throws this error.
Your device is trying to call "action" but there is no converter available for such command.
Also, any automations wrongly coded?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I get that error in z2M and no way to identify the root cause. no name of device and i have 84 devices. Nothing more in logs
Any idea
Error 2024-08-16 09:55:07z2m: No converter available for 'action' ("")
Info :
Version de Zigbee2MQTT : 1.39.1
commit: [e132316 : (https://github.com/Koenkk/zigbee2mqtt/commit/e132316a)
Type de coordinateur. : ConBee2/RaspBee2
Révision du coordinateur. : 0x26780700
Version de l'interface : 0.7.4
Version Zigbee-herdsman-converters : 19.72.0
Version Zigbee-herdsman : 0.55.3
Statistiques : Total 84
Beta Was this translation helpful? Give feedback.
All reactions