I’m experiencing an entity count mismatch with my VZM31-SN switches in Home Assistant/ZHA:
The Issue:
Older switches (added several months ago): 51 entities each
Newly added switches (added this week): 30 entities each
Same model, same firmware, different entity counts
I’m running the latest updates to HA. I do see the inovelli clusters when managing the Zigbee Device. I’ve reset the re-added the device multiple times. Also, it’s running the 3.04 firmware.
Root Cause (?I think?):
After investigating, this appears to be related to the migration to Quirks V2, specifically PR #3232.
The VZM31-SN quirk was converted to use QuirkBuilder, but unlike the VZM32-SN quirk (which explicitly declares all entities using .number(), .switch(), etc.), the VZM31-SN quirk relies on ZHA’s automatic entity creation heuristics. I’m guessing that these heuristics are more conservative in V2, resulting in fewer entities being created.
What’s Missing:
Notably, the LED color control entities are missing on the new switches, which breaks several of my existing automations.
Are there plans to update the VZM31-SN quirk to explicitly declare all entities (similar to the VZM32-SN custom quirk)?
If I have time this weekend, I’ll probably mimic what’s in the VZM32 quirk and see if I can get things set up the way that I like.
I am seeing the same behaviour. My existing VZM31-SN switches show all 51 entities in HA, but a newly installed switches are only showing 30. Notably missing are all the entities regarding LEDs and multi-tap control.
Can someone point me to more details regarding the quirks?
I know that my new mm wave switch also does this, so will this be fixed in that quirk that we are waiting for for it? Or is this a separate issue for just this one?
I spent some time this weekend trying to update the quirk to manually add the entities like in the VZM36 example. Unfortunately, I now end up with a bunch of duplicate entries. The previously added switches have a total of 81 entities and the newly added switches have 61 entities.
I’m definitely missing something about how ZHA decides when to and when not to create entities based on the cluster data. I’ll continue to experiment.
I am having the same issue. I have the four of the first batch that I just got around to updating the bootloader on. The two switches I reset and repaired are seeing the same behavior. I do have the custom one for VZM32-SN.
@chrisdfw , I did not have the custom quirk installed for VZM32-SN and was having the issue, so I don’t think it is related to that. If you look at the bug report link I previously posted, it looks like there was a change elsewhere in ZHA in how attributes are processed, which exposed an error in the inovelli quirk. A PR to fix the issue has already been posted and is pending merge, but would require an update.
I believe you are correct on this as the device was moved to V2 via a community member. The original entities were created based on code in the ZHA repo and not the zha-device-handlers. As part of the switch to V2 quirks, are the entities supposed to be moved over to the zha-device-handlers repo? This makes more sense and will be better in the long run I believe.
As a side note, you should be able to edit settings via “Manage Zigbee Device” menu in the device as a workaround until it can get figured out:
