homebridge/to/get {"name": "*"} - output

The output format of homebridge/to/get {"name": "*"} is a bit strange to parse.

Would this not make more sense to output :

[LaborEtArs]

@cflurin I’m thinking about ESP8266 clients, that could do a ‘self-register’ to homebridge(-mqtt). To do so, they should be able to find out, if they have been already registered, which would be possible by calling ‘homebridge/to/get’ and lookup the accessory/service name. Of course, this may be possible based on the current response, too. I developed a ESP-based HAP client (but had to find out, after it is running, that the ESP8266 is just a bit to slow for HAP communication…). Therefore I’m already in HAP a bit deeper… When registering a new accessory to homekit, the new HAP device has to send it’s ‘Accessory Attribute Database (AAD)’ to homekit. This AAD is structured hierarchically, therefore I’m used to this format and think it would feel more ‘native’, if the mqtt plugin would deliver the same format. You can find the HAP spec here HAP spec R2, look at 6.6.4. If such a format (the hierarchical style) would be interesting to you, maybe I can deliver a PR 😃

[LaborEtArs]

I also stumbled across this, but may I’d like to have it even a bit more complicated… As an accessory may have several services, and every service may have several characteristics, wouldn’t it make sense to copy this hierarchical structure to the JSON response also: name: “Light Hub”, services: [ …{ …name: “Light 1”, …characteristics: [ …{ On: true }, …{ Brightness: 75}]} …{ …name: “Light 2”, …characteristics: [ …{ On: false }, …{ Brightness: 75}]}]