matterbridge with z2m - issues with device recognition and matter descriptors.

[jpadie]

Discussed in https://github.com/Luligu/matterbridge/discussions/16

^{Originally posted by jpadie April 26, 2024} z2m configured and working fine for ages. matterbridge installs ok. idem the plugin. plugin configured with mqtt details.
however in the matterbridge front end the z2m plugin is showing zero devices, although two are registered on the z2m front end. messages come in via mqtt and are shown in the logs as warnings.

took a few minutes for the devices in z2m to be found by matterbridge. in the meantime mqtt messages showed in the logs as warning.

the two devices on the coordinator are a sonoff temp and humidity sensor and a 2-gang dimmer module.

the temp and humidity module correctly shows its data on the matterbridge front end. but alexa only sees the temperature. despite alexa docs there is a good device ui available for atmospheric information sensors since this module can be paired directly to alexa and is represented on a reasonable gui rather than as two separate devices.

the coordinator appears to be shown in alexa and in the matterbridge front end as a door lock. clearly this is not correct. there is no reason for the coordinator to be published in alexa at all, imo.

the 2 gang dimmer module is exposed to alexa as two lights; one responsive device that has no dimmer capability and one device that is unresponsive. matterbridge describes the module as a "bridgedevice-0x00013" and shows no useful information in the cluster column. both gangs work perfectly with Z2M. this is a TuYa device, by the way.

so there are two devices in Z2M. matterbridge records 3 and reports to alexa that there are 5. that probably makes sense if the matterbridge is reporting the temp and humidity sensor as two separate clusters rather than combined (alexa does support combined devices now, from memory).

happy to provide more material if that is helpful in debugging. will try to convert this to an issue.