Is anyone interested in a challenge?

Third party integrations
, , ,
1

This is my 2nd day ever using home assistant .

(Before I continue, I shall preface that I am a novice, I have no desire to learn how to code, Or how the code works.)

(Before ever using home assistant)
I was trying to figure out how to send multiple sources of audio to a single zone/group of zones… microphone + airplay/spotify

I was told I needed a mixer… ok

So I went on a quest to find a mixer that I can control with my phone… there were a lot of options… but then I came across the Motu ultra-lite avb… it’s an audio interface that can act as a standalone mixer.

I also found out that it has an open api… which I didn’t put much thought to at the time…

Today after finally getting home assistant to work with
a control4 amp, it dawned on me if this would work.

Would it be possible to make an integration that uses the Motu avb api to control it via home assistant?
(Feel free to answer)

My thoughts were if there was a way to make a simple audio matrix template that interfaces with the Motu with the ability to control which input goes to what output. Because there are many outputs, and the I/O is expandable, I would be able to control more zones simultaneously with less hardware… I could also send multiple inputs to one output…etc…

Because it’s a full fledged mixer, in theory I should be able control the volume, equalizer, effects, etc… using HA via the api…

So the question is who’s open to that challenge of creating the template/integration for home assistant…?

It should be a simple easy to use card that has layout similar to the juke audio app…

Link to api…: https://cdn-data.motu.com/downloads/audio/AVB/docs/MOTU%20AVB%20Web%20API.pdf

Thank you,

2

Make you a deal, send me the hardware and I’ll work on the software :wink:

All jokes aside, don’t even need an integration. Use rest commands and stuff to get things working custom. Could even use an external python or bash script to do it. Wouldn’t be all that hard if they expose a lot of functionality via the API.

Edit: seems like everything is exposed via API for read and write. Wouldn’t be hard to get this working.

3

With that statement it’s highly unlikely that you’re going to get many takers on this.

It’s like asking “I don’t want to put any effort into this and I’m not going to even try so I want someone else to do all the work for me. who’s willing to do it for me? Oh and if I have another thing I want to do later since I have no interest in learning to do it myself in the future I’ll probably be coming back again asking you to do that for me as well”.

Not trying to be mean but just keeping it real.

2 Likes
4

Ok, I’ll add to the challenge…

Can this: (GitHub - Drumfix/avb4linux) be modified and implemented into home assistant?

it should be able to run multiple instances of the driver/integration simultaneously.

Each instance should have a maximum 128 audio inputs(send), and 128 audio outputs(receive)

Each output can be one speaker/channel in a stereo/surround sound environment, or mono audio.

There can be a maximum of 64 stereo streams per instance of the driver.

To further complicate things, there should be an airplay/spotify connect integration that allows one to patch each instance of airplay/spotifyC to the inputs(send) (minimum 2 required for stereo) of the avb driver integration…

All outputs(receive) can be used to stream/upload to other sources/HA servers…

There should be an option to isolate/confine each instance of airplay/SpotifyC to a separate vLan on a network…

5

You’re absolutely right….

I have no desire to learn to code, or to learn how the code works.

That being said, anyone can say: hey! I’m interested in getting involved, but I don’t wanna do this for free… Let’s come up with an arrangement that will suit us both….

And there are those who just like the challenge of it all… = free

I may be lazy, but I’m not an a-hole…:wink:

6

I’ve made my offer, balls in your court.

Search baudneo on GitHub for my resume.

7

Thank you,

I’ll think about that.

I’ll have to find a piece of hardware I’m willing to invest in without much of a loss factor…

As well as a method to recoup the investment…

Also, if I do go through with it, and you do design/code a functional integration/Implementation for me that I approve of, I’ll own all rights to that integration/Implementation and you wouldn’t be allowed to publish it publicly, or to share or with anyone else; Both privately and publicly… you would also be barred from designing/coding/making/sharing anything similar to it…

8

From a quick look, that repo is an alsa driver and facilities to integrate with a Linux machine.

It depends what you want to do. Do you just want control and status? API will be fine. Do you want deep userland access to it’s audio interface through alsa? Implement the repo you linked.

Edit: I’m going to nope right out of this after that last blurb.

Also, if I do go through with it, and you do design/code a functional integration/Implementation for me that I approve of, I’ll own all rights to that integration/Implementation and you wouldn’t be allowed to publish it publicly, or to share or with anyone else; Both privately and publicly… you would also be barred from designing/coding/making/sharing anything similar to it…

#1 read the license of the repo you linked.

#2 if I create an API wrapper, there’s no chance in hell I’d follow those absurd statements.

Edit 2: long live OSS

Edit 3: witaf just went on here? Wild.

9

If I’m sending you a piece of hardware, in exchange for writing software, I’m in essence paying you to do work for me. correct?

If I’m paying you to do work for me, then I should be the only one to benefit from that work, unless I see it fit that others benefit as well in exchange for $$

Yes it is an audio driver. It uses avb iEEE protocol .
The way that avb is integrated by Motu allows for 16 x 8 streams of audio. Or a maximum of 128 streams in and 128 out. Some Motu avb interfaces allow 2 x 16 x 8 streams of audio.

Also as far as I’m aware Motu is only using the layer2 implementation of avb so it might further complicate things…

I want to eliminate as many pieces of hardware that I can in order to achieve this…

Just a PC 2 Ethernet ports only running HAOS + AVB switch + ubiquity network + motu avb interface + amplifier/speakers…

Thank you,

10

Actually, I think this is an important thing to point out about the absolute arrogance and absurdity of this post…

You came onto the forum of an open source project to request that someone who uses this open source software create a proprietary integration and sign an NDA to never develop anything related to the device? or the technology? Break OSS licensing? For free? So you can ‘recoup’ your cost of free labour?

Am I missing anything there?

Edit: FAQ - Home Assistant Community

1 Like
11

If something is being done for free, then it should be available for the public.

But if I have to send in a piece of hardware, then it’s not free anymore.

If the hardware were to be returned, then sure publish it as much as you want.

BTW. making a “custom” implementation of something that is open source, that Implementation in and of itself is not open source, and can be charged for.

12

Do you realise how many pieces of hardware people have purchased in order to create the free and open source Home Assistant?

If you don’t want to contribute respectfully to the enhancement of FREE Home Assistant and it’s Integrations then go elsewhere.

2 Likes
13

wow this thread took a weird hard turn pretty quickly.

I might have to challenge this assertion:

:laughing:

1 Like
14

BSD is pretty permissive, but GPLv2 requires access to the source code for derivative works shared in binary or executable form. Using the included kernel modules would put that work in that category. An API wrapper would be different. So, yes, your demands would be breaking OSS licensing. I could care less about money and greed, I’m talking about sharing things with others who have already put work into the platform you are asking an integration be made, a platform that is free itself.

My point still stands on coming to an open source project and requesting some of the most out of pocket crap I’ve heard in a while.

I’m done with replying and wasting my time here. Good luck.

15

That’s being rather generous! :rofl: I can’t say I’d go that far.