More > JRiver Media Center 32 for Windows

Make MC compatible with Home Assistant

<< < (5/6) > >>

mattkhan:
related HA github issue -> https://github.com/StevenLooman/home-assistant-dlna-dmr/issues/13#issuecomment-752015900

MasterC:
Another vote for JRiver control in HA. I have HA running almost everything in my house - and it integrates nicely with everything. Having the JRiver integration would complete my setup!

BillT:
I use HomeSeer (tried Home Assistant but at the time I tried it in order to do anything much you had to use YAML - way too difficult). HomeSeer used to have a JRiver add on years ago, but JRiver changed so often that the HS integration kept failing so eventually it was dropped.

The solution that I came up with was to use MCWS. Send http strings. In HomeSeer &hs.GetURL("http://192.168.0.6:52199/MCWS/v1/Playback/Stop?Zone=-1&ZoneType=ID","", True, 80) sends the stop command. All the transport functions are available and you can change views (and probably a lot more functions that I don't use).

I use a web browser running Panel in a HSTouch window (http://192.168.0.6:52199/Panel/). The HS main interface isn't generally used.

I would think that a similar approach would work with HA. If I can do it it cant be that difficult!

mattkhan:
it's what I do atm, define a few restful commands and call them via buttons, e.g.


--- Code: ---cmdserver_mc_stopall:
  url: "http://1.2.3.4:12345/MCWS/v1/Playback/StopAll"
  username: !secret mc_user
  password: !secret mc_pass

--- End code ---

eve:

--- Quote from: mattkhan on January 07, 2024, 03:28:46 am ---it's what I do atm, define a few restful commands and call them via buttons, e.g.


--- Code: ---cmdserver_mc_stopall:
  url: "http://1.2.3.4:12345/MCWS/v1/Playback/StopAll"
  username: !secret mc_user
  password: !secret mc_pass

--- End code ---

--- End quote ---

See for me, I have multiple JRiver clients and it seemed impractical to juggle them and their IPs so the way I set up my layer between MCWS (plus a few functions that run locally on the systems) is that the IPs are generated based upon my config in a database (this config system makes up the backbone of how all my AES67 crap works too). This way, if I spin up a new JRiver instance or need to change an IP of a device, I just update the database and everything works. Furthermore it simplifies accessing specific JRiver instances by name / identifier and their respective zones. This also gives me the benefit of like helper functions and longer macros? So for example since I run OLEDs, pausing a movie in an ideal world means not leaving a static image displayed, there's a function that handles hiding / showing JRiver correctly (which requires not only JRiver MCC commands but some OS things) + a whole thing for like, swapping to an 'idle' zone that provides automatically generated background material (think trailers and featurettes and 'retro ephemera' stuff) to display instead of just going to black.
More complex functions are easy too, all that queuing and queue generation stuff can happen in that service which then provides the queued items to JRiver (without JRiver needing to manage them in it's library database or anything).

Navigation

[0] Message Index

[#] Next page

[*] Previous page