Jacopo Scazzosi

> I would be interested as long as we keep on a node level and do not add additional topics to the spec on mqtt level. My initial idea was...

> Say I have 2 devices, they both have a power switch and a level control. One is a dimmable light, the other a variable-speed pump. How would I tell...

> I think we can create PR's against the readme document: https://github.com/homieiot/homie5-device-profiles @Tieske sounds good to me, we can keep profile-oriented work in that repo. Feel free to close this...

I agree @Tieske . Feel free to close this issue or move it to either an issue or discussion in that repo.

For research purposes, the BACnet protocol is very profile-driven and the spec makes for some interesting reading.

@Tieske I'm still working on Homie implementations which will require profiles at some point. However, work is happening more slowly than I had anticipated due to other priorities. I've also...

> That said, I’ve been revisiting an idea related to general semantic information for devices, in the context of a potential Homie MCP server project. The goal would be to...

> Are you seeing any (negative) impact when running the perf script? From `main`: ``` 20,000,000 elems 20 maps 3672.3449579999997 20,000,000 elems 20 maps 20 filter 2590.885416 100,000 iterators each...

@RubenVerborgh I couldn't find a way to spy on `tiny-set-immediate`'s exports directly so I explicitly split the tests into two different sub-suites: one for the no-op spy, whose callback must...

@rubensworks @RubenVerborgh just checkin in on this PR. I have not addressed all of the comments above as I wasn't able to find a way to spy on `tiny-set-immediate`'s exports,...