I’m aware of the ESP Home component. Not sure how that relates to my Matter based repo. Could you elaborate?
Well, as far as I’ve seen, you had to implement the full workflow, including parsing and so on.
All of that is already done/validated with the emontx component from ESPHome.
The component itself does not send anything, but it creates all the available sensors.
When setting up a yaml file to create a firmware, you specify all what you need (at minimum the emontx component) and then add the “communication layers”. That could be wifi/thread/zigbee and you can add other things like http (to send to an emoncms, local or remote), mqtt, …
So I think, it should be quite easy to reuse everything that already exists in ESPHome and make emonWifi be a matter/thread device.
It would then show up in Home Assistant, your Home Energy Manager, … as a matter device.
ESPHome is somehow designed to work with Home Assistant, but it also works as a standalone device.
Findings: only the matter component is missing in ESPHome. It might be a (very) good idea to make some research, and create a matter component out of what you’ve already implemented.
Ah, I see what you mean.
My goal was to take away as much of the technical stuff as possible. No YAML, no ESPHome, no Home Assistant. I want my Home Energy Manager to only Matter, so this firmware let me use my emonTx data by simply scanning a QR code.
As for ESPHome, it doesn’t support Matter and, given the complexity of the CHiP SDK, I’m not sure it ever will. There is plenty of discussion about it. Personally, I don’t know that it makes much sense given the existing ecosystem. If you’re using HomeAssistant, ESPHome is already well integrated, so using Matter doesn’t make much sense as you don’t gain anything.
As for handling the data, it’s just a CSV string that comes in over UART. Parsing and exposing the values is done by a few lines of code.
New findings…
Well, I think I know now why there’s no matter component in ESPHome.
There’s a huge problem! The DAC infrastructure !
It seems to be somehow impossible to define your self a unique id, it must come from a CSA-approved PKI, or it won’t work with Apple Home, nor Google Home.
With HA, it would work since it doesn’t enforce DAC validation. Aqara app accepts test certs too.
Not strictly true. Apple Home and Google Home both allow uncertified devices. I have more than dozen custom devices in my home that use the test attestation certificates. I’ve never had an issue with iOS Home, beyond its limited support of Matter.
probably a setting that you can enable or not.
But ok, that’s fine, and in fact a good point.
When you try and commission an uncertified device, iOS Home just prompts you that it’s uncertified and asks if you wish to continue. This was the always the case with iOS Home, even back to their own HomeKit protocol.
They could always decide to prevent you from adding your uncertified devices, but I can’t see that happening.
that’s pretty cool… I think I’ll start soon to implement some matter component for ESPHome 
If you need help navigating esp-matter or connectedhomeip, get in touch. I’m not an expert, but I’ve made plenty of mistakes 