-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WXCJKG12LM, WXCJKG11LM, WXCJKG13LM - all action entities are now showing as Unknown, although all functionality is still working #24266
Comments
Same issue as #24195 |
Could you provide the debug log when the action goes to unknown? See this on how to enable debug logging. |
Is this sufficient? The device I am testing with is 0x54ef441000179f97 [2024-10-09 18:08:59] debug: zh:zstack:unpi:parser: --- parseNext [254,5,69,196,3,203,1,223,236,126] |
Does it go from |
Yes, it goes from None to Unknown. But since these are legacy and will be
replaced by event, then leave it. No need to spend time fixing something
that will be removed eventually. I have excluded these entities from
alerting.
Many thanks!
…On Thu, 10 Oct 2024 at 14:22, Koen Kanters ***@***.***> wrote:
Does it go from None to Unknown in HA with this? Because I still see
"action":"". Note that the action sensor will be removed in Z2M 2.0.0:
#24198 <#24198>
—
Reply to this email directly, view it on GitHub
<#24266 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONHCL4B7PPCIVSEWKD3D6LZ2Z5TDAVCNFSM6AAAAABPSVEJDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVGA4DGNZUHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days |
What happened?
Upgraded to 1.40.2-1 and now core to 2024.10.1 and all my *action entities for these Aqara switches have changed their default status to Unknown which is triggering my automation to alert on Unknown, offline entities/devices. I can exclude them from the automation but I wonder what's changed? I can't find any changes but again, this happened after the Core update.
What did you expect to happen?
When idle, the action state should be None
How to reproduce it (minimal and precise)
Core 2024.10.1 and z2m 1.40.2-1
Zigbee2MQTT version
1.40.2-1
Adapter firmware version
20230507
Adapter
zzh!
Setup
Home Assistant Blue (ODROID N2+)
Debug log
nothing in the log but this is a screenshot from before the Core upgrade and after.The text was updated successfully, but these errors were encountered: