Writing this post to see if there’s interest in using and possibly supporting the development of an app dedicated to the Devialet speakers.
I have a proof of concept already running locally (volumeUp, volumeDown, mute), using default Homey widgets, but development is slow for the moment since I can only combine a Homey Pro with a Devialet speaker (a Dione) only for a few hours every week, to test stuff. I know that the API is dedicated to the Phantom but most of the API calls seem to be similar.
I will gather feedback and report on roadblocks and hopefully on progress in this thread.
I am also thinking about contacting Devialet and see if they would be interested in providing a device (any device that supports their published API would be fine) so I can speed up development, so if someone is closer to their dev or mkt team, drop me a message.
And since I mentioned roadblocks, dropping here a reference to how the devices “could” notify homey about changes (volume change, playback change, playback position etc) but don’t.
In the API it is mentioned that:
In order to show up to date information, the client application may subscribe to or perform regular polling on the following endpoints:
● /groups/current/sources (the list of all available sources)
● /groups/current/sources/current (the current playback state)
● /systems/current/sources/current/soundControl/volume (the current volume for the system)
● /groups/current/sources/current/playback/position (the position within the current track)
Unfortunately, none of the obvious methods to subscribe to those SSE (server side events) works, so if anyone has any idea what they meant and how we could subscribe to those SSE’s I could use that help.
