Think about using the Homebridge Speaker/SmartSpeaker instead of light source characteristics

[dotWee]

I think defining the accessory as a Speaker or even a SmartSpeaker and applying its characteristics would be more intuitive instead of declaring it as a light source.

It requires a functioning mute action and optional volume settings.

Related documentation:

• https://developers.homebridge.io/#/service/Speaker
• https://developers.homebridge.io/#/service/SmartSpeaker

[scholtzan]

One problem with Speaker or SmartSpeaker is that the type is not supported by HomeKit. When I set the type to Speaker, HomeKit says "This accessory is not certified and may not work reliably with HomeKit" and the accessory becomes unresponsive.

I could, however, add an accessoryType option to the config that determines whether accessories are registered as light accessories or speaker accessories.

[dotWee]

Would you mind sharing your modifications as a branch? I'd love to debug & dig into it!

[scholtzan]

Sure, I added a service_type option to the config that determines whether the Lightbulb or Speaker service is used for Spotify accessories. You can find the changes in this PR: #12

I also found some issues related to HomeKit not supporting Speaker and SmartSpeaker services in the Homebridge repository:

• SmartSpeaker Service homebridge/homebridge#2553
• Speaker not supported arachnetech/homebridge-mqttthing#233