Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embedded Web application #16

Open
kelsos opened this issue Aug 8, 2014 · 8 comments
Open

Embedded Web application #16

kelsos opened this issue Aug 8, 2014 · 8 comments

Comments

@kelsos
Copy link
Collaborator

kelsos commented Aug 8, 2014

Add an embedded web application that will use Websockets to implement the notification protocol.
The web application will be used in systems where a native application is not available (iOS/Windows Phone etc).

@Erimus-Koo
Copy link

It sounds great.

I'm a rookie user of home assistant. Maybe some open API can make musicbee be remote by home assistant. And home assistant merged "home bridge", so maybe can use Home App(iOS/apple TV/mac) to remote control musicbee.

Integrations - Home Assistant

@kelsos
Copy link
Collaborator Author

kelsos commented Jan 1, 2020

Hi @Erimus-Koo I will have a look to see how possible it is to use something like this. Currently, the problem with the API is that it's a pure TCP socket implementation that doesn't talk any standard protocol so it is harder to interface with anything.

@Erimus-Koo
Copy link

Thanks for your time. I've tried to read some docs like: Creating your first integration · Home Assistant dev docs, but still many problems.

So I wrote a little service to receive 'key' from computer in LAN, and 'replay' the keys on local, utility/remote_key_service.py. I can remote control the player by media keys now, and home assistant can use command line as buttons. Just some basic feature, play/pause/next/prev. I still look forward to your full-featured web app.

@nitzanbueno
Copy link

Hi @Erimus-Koo I will have a look to see how possible it is to use something like this. Currently, the problem with the API is that it's a pure TCP socket implementation that doesn't talk any standard protocol so it is harder to interface with anything.

Hey, are you planning on changing the protocol to WebSocket anytime soon?
If not, it might be possible to write a WebSocket server that proxies to the TCP socket.

@kelsos
Copy link
Collaborator Author

kelsos commented Nov 29, 2020

Hey @nitzanbueno at the moment I am not directly planning to do that. I need to get an initial version of v2.0.0 of the application ready and then I will deal with that.

@nitzanbueno
Copy link

OK.
At the moment, I'm working on a websocket proxy server and web client, if you're interested.

@nitzanbueno
Copy link

I forked your project and switched SocketServer for a WebSocket server written with Fleck.
I also made a web client to go along with it, if you'd like to take a look.
Thanks for the great work!

@kelsos
Copy link
Collaborator Author

kelsos commented Dec 6, 2020

Fleck is what I had in mind too. I will take a look when I find time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants