09-16-2025, 04:06 PM
Is that the 'usual suspect' when this error presents itself? I'm confused but - anyways, no; I did not buy a RF433Mhz receiver to go with the A16 board.
I find it very hard to accumulate/digest a ton of different how-to's that each will touch on the subject from very different angles and all seem to arrive at the goal (Home Assistant integration) more or less with out any issues at all ?
I know, criticism does not offer any way forward - but I really would like the A16 'family' to succeed because it's such an obvious complementary product to Home Assistant (HA), and the Smart Home market is certainly booming. One way to make this happen would be to present the integration in an easy to follow YouTube (series if necessary) covering at least 2 "camps" (at least) one being the HAOS camp running HA directly on the hardware/OS, and the other being the VM camp running HA as a (cluster of) container(s) mostly in Docker or like environments.
I'm in the Docker camp and I'm trying a gazillion different things to get to integrate this stuff (I originally thought the hard part would come when I had to solder wires from my IHC 'buttons' in order to have A16 emit either MQTT messages or somehow otherwise tell HA that this or that button had gone 'high' and now HA was expected to send a signal to some Zigbee device flicking the on/off on a relay in effect turning on/off the light in my bathroom - but no; I guess I'm still weeks if not months away from that).
So - checklist time:
1: flash the KC868 A16 with the version 2 software
2: find it in HA as an integration (nope - not happening)
3: flash a yaml with HA config to the board from a container running esphome (nope - see above error)
4: ehh i'm out of ideas (and chatgpt spent all my tokens telling me what "it" thought was a good idea) ?
I find it very hard to accumulate/digest a ton of different how-to's that each will touch on the subject from very different angles and all seem to arrive at the goal (Home Assistant integration) more or less with out any issues at all ?
I know, criticism does not offer any way forward - but I really would like the A16 'family' to succeed because it's such an obvious complementary product to Home Assistant (HA), and the Smart Home market is certainly booming. One way to make this happen would be to present the integration in an easy to follow YouTube (series if necessary) covering at least 2 "camps" (at least) one being the HAOS camp running HA directly on the hardware/OS, and the other being the VM camp running HA as a (cluster of) container(s) mostly in Docker or like environments.
I'm in the Docker camp and I'm trying a gazillion different things to get to integrate this stuff (I originally thought the hard part would come when I had to solder wires from my IHC 'buttons' in order to have A16 emit either MQTT messages or somehow otherwise tell HA that this or that button had gone 'high' and now HA was expected to send a signal to some Zigbee device flicking the on/off on a relay in effect turning on/off the light in my bathroom - but no; I guess I'm still weeks if not months away from that).
So - checklist time:
1: flash the KC868 A16 with the version 2 software
2: find it in HA as an integration (nope - not happening)
3: flash a yaml with HA config to the board from a container running esphome (nope - see above error)
4: ehh i'm out of ideas (and chatgpt spent all my tokens telling me what "it" thought was a good idea) ?