There is a protocol typically used with mid range to professional sound devices like qsys control and other products called OSC. Some DJs use this as well since its a way to use a hardware interface (like a mixer) to control the software on their PC acting as a DJ. This protocol is very simple and is a little bit simliiar to mqtt.
I guess i am not sure what is meant by missing capabilities. Any new feature is something that is missing, thats added to fill in a gap or that someone needs to make something work. In this case its a protocol like SMNP or DMX. There are a few control surfaces out that speak this protocol that would be very nice to have part of HA. This does include qsys, which I have a processer in my home that manages audio routing. It would be much easier for me to use OSC to control the levels for each room. It would also allow me to do some basic tunings like setting equalizers, gains and such. HA runs most of my audio sources but qsys deals with the routing and level setting, so having them more combined would be ideal. Also this protocol is extremely simple and basic, but I am not a coder. This protocol would allow for more integrations and solve some problems for other users. I dont want to elaborate more on specific use cases, so I will just say that having this protocol would be another useful aspect of HA.
I honestly didnt expect to get such a negative reply. This is very surprising. I am in the control industry and I deal with protocols all the time, but I understand there is not normally a place for these in the home environment, although some larger homes may require some amount of it.
Just trying to help you here. I’m not being negative, just looking for what you want to change.
I take it from your comment that you are looking for some new integrations that currently are not there.
Is there something filling these needs already written by someone as a Custom Integration or Add-on? Perhaps follow that up and help that move along. If this new function is not already part of Core’s thousands of built in Integrations or one of the multi-thousands of custom Integrations, well, I’m shocked there could be anything missing like that, honestly if it will be useful to a group of people using the project.
Remember, this is an Open source project. MOST new integrations are born as Custom Integrations built by the community first, they get bugs cleared and grow in popularity, and then they get pulled into Core.
Alternatively if you are looking to add this functionality to an existing Core function, please let us know which one(s) and what you would like to see changed so the owner can be identified to work it. Simply asking for protocol’s to be implemented in core has little or no chance of going anywhere.
So just trying to help you out here. Take it as you will, however it is meant to be positive.
I guess i am not sure how that works on the HA side. This is a network protocol very similiar to mqtt, and raw socket comms. You have to configure both sides to communicate. In my world this is actually a bit more like modbus TCP. Having the infrastructure and code to take values and have them be recognized by HA is what I am looking for in terms of an integration. Again as an example modbus TCP is just a protocol and you can use whatever hardware is supported and similiarly on HA side do whatever you want with the two way data. If I want to turn on a coil or read a sensor, I can do that now. I would be looking for the same type configuration for this OSC protocol.
I see the goal of this being something similar to the command line or RESTful command integration, however since the payload is likely to be very varied it would be good to be able to customize that. Maybe a notifier action?
Basically I’d like to be able to set up OSC receiver devices as integrations, then use action.send_OSC_my_receiving_device, with the payload “/eos/cue/13/go/” (this example targets ETC Eos lighting cues).
It seems like for somebody with the right skills, this shouldn’t be too big a deal - set up each OSC destination and then throw payloads at it from automations or buttons. I was frankly amazed it doesn’t already exist, given how prevalent OSC is in more and more control environments.