grimmace92 wrote:
> When I type in the command docker exec -it home-assistant bash it goes
> to /usr/src/app
>
> from there I can type cd /config where I found shell and the scripts.
> It looks to me like its /config/shell but I have to be logged in as root
> though. Does this pic help?
>
>
ynot1234567890 wrote:
> Open a terminal to your HA installation, go to your shell directory
> which is usually (supposed to be) just under the config directory
> /config/shell (where you put your shell script files (ie: qry_alb.sh,
> etc..)) and type pwd. This will give you the full path. The f
grimmace92 wrote:
> Still no luck. The play, restart and advance buttons work. In my
> docker details I see the file folder as web/docker/homeassistant and the
> mount as /config
> Under environment variables I see this
> /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/
ynot1234567890 wrote:
> Does pause, play, volume work on the player?
>
> If the only one working is artist for music source lms (this action does
> not require a shell script file at this time), then the shell files are
> not being called properly and the likely cause of that is path to the
> s
grimmace92 wrote:
> Ok I've tested from the Home Assistant GUI and the only thing I can get
> to work is populating Artist name with the music source as LMS and then
> choosing play artist. Nothing else works. Nothing from Spotify. I've
> checked all of the shell scripts to see if they work f
ynot1234567890 wrote:
> The toggle on the traditional interface for LMS Music Player Controls
> serves no purpose. See post 105 for how to remove. (control: hidden)
>
> Ynot.
Ok I've tested from the Home Assistant GUI and the only thing I can get
to work is populating Artist name with the m
grimmace92 wrote:
> Awesome. This is now fixed as well after creating the scripts directory
> and placing the files in there. Thanks again. One more thing I noticed
> I used to have a toggle button next to LMS Music Player Controls in the
> pic I posted in post # 118. I don't now and not sur
ynot1234567890 wrote:
> Based on the GUI view, looks like your script entities are not being
> found (ie: contents of script_lms_controls.yaml is not being found in
> the scripts section). So, in your configuration.yaml file, look for the
> line:
> >
Code:
> > script:
grimmace92 wrote:
> Oh man. I am such a fool. I went way to far down the rabbit hole on
> this one. Obviously that song wasn't in my LMS database. I picked one
> that was and got the expected results. I will investigate the spotify
> query when I am home later. Also I am still having issue
ynot1234567890 wrote:
> Hi, Indeed it looks like you are getting much closer. My http section
> reads as follows:
> >
Code:
> > http:
> base_url: https://mydomain.duckdns.org
> ssl_certificate: /ssl/fullchain.pem
> ssl_key: /ssl/privkey.pem
> trusted_networks:
grimmace92 wrote:
> Hi Ynot,
>
> I've made some progress I think. I've fixed the certificate issue but
> I'm not getting the expected results. Is there anything else I can try?
> I haven't entered anything in my confirguration.yaml file for the http
> section. If I do I get an error trying t
You can also change notepad++ config on order to use unix type end of
line character:
https://stackoverflow.com/questions/8195839/choose-newline-character-in-notepad
kalimeroo's Profile: http://forums.slimdevices.com/membe
kalimeroo wrote:
> @grimmace92
> How did you edit the Bash files ?
> If this wad done under Windows, you can run the utility dos2unix on the
> files.
> Lightning also be a folder rights issue
>
> @ynot
> You're welcome
Hi Kalimeroo,
Yes I am using windows to edit the files using notepad++ ya
@grimmace92
How did you edit the Bash files ?
If this wad done under Windows, you can run the utility dos2unix on the
files.
Lightning also be a folder rights issue
@ynot
You're welcome
kalimeroo's Profile: http://forums
Hi Ynot,
I've made some progress I think. I've fixed the certificate issue but
I'm not getting the expected results. Is there anything else I can try?
I haven't entered anything in my confirguration.yaml file for the http
section. If I do I get an error trying to login into home assistant.
W
kalimeroo wrote:
> If it is working in Dialogflow then you have to click integration and
> choose Google Assistant. With your android device you start by saying
> "Talk to LMS control" and then issue command like "Play artist Pink
> Floyd in the kitchen"
@samoth Glad to hear it's working for yo
samoth wrote:
> @ynot1234567890: Absolutely great gadget and nice work. With Dialogflow
> it is working perfect.:o
> Could you please describe how you can use LMS Controls from Google
> Assistant directly or perhaps I have missed something ?
>
> Best regards,
> Samoth
If it is working in Dialo
In order to install secured certificates on a rpi with Hassbian, I
logged in as homeassistant user (sudo -u homeassistant -H -s) and then
followed the instructions detailed here:
https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt
In order to generate a token for Home As
ynot1234567890 wrote:
> So now when you run the shell script it executes a call against lms does
> it return the artist, album but fails posting the result? You can send
> me a copy of one your script files (say qry_alb.sh) and I will check it
> out to ensure the format is correct. I assume yo
grimmace92 wrote:
> Ok. I did the symlink from nc to ncat and that fixed the 'nc' issue. I
> still can't figure out the certificate issue. I've created it
> successfully in synology using let's encrypt but for some reason its not
> using it properly.
So now when you run the shell script it e
ynot1234567890 wrote:
> Thanks I will consider that. In the next release, *nc* will be replaced
> with *socat* in order to handle lms connections that require username
> and passwords.
>
FYI: I'm running HA in a Docker container (on my QNAP NAS) - the docker
image doesn't have socat either.
ColH wrote:
> I'm still not entirely sure about all the cert stuff either - I've got
> mine working, but tried so many things!
> I do notice thought that your script is failing to find 'nc'. Following
> suggestions I saw somewhere, I made a symlink from nc to ncat.
> @ynot: another suggestion fo
ColH wrote:
> I'm still not entirely sure about all the cert stuff either - I've got
> mine working, but tried so many things!
> I do notice thought that your script is failing to find 'nc'. Following
> suggestions I saw somewhere, I made a symlink from nc to ncat.
> @ynot: another suggestion fo
I'm still not entirely sure about all the cert stuff either - I've got
mine working, but tried so many things!
I do notice thought that your script is failing to find 'nc'. Following
suggestions I saw somewhere, I made a symlink from nc to ncat.
@ynot: another suggestion for the scripts - do a 'w
grimmace92 wrote:
> Im using the using the home assistant package available on synology
> diskstation through docker not HASSIO. I just add duckdns to my
> configuration.yaml file. Do I need HASSIO for this to work?
Sorry but I don't know anything about the HA package for synology
diskstation
ynot1234567890 wrote:
> The line is supposed to be this:
> https://mynameused.duckdns.org/api/states/sensor.art_ID? -H
> "Authorization: Bearer $HA_Token"
> The second line of the shell script files (ie: qry_alb.sh) should read
> *HA_Token=Your_Long_Lived_Token_Here*. Replace
> "Your_Long_Lived
grimmace92 wrote:
> Here is what I'm doing in putty and what I see. Something with my
> certificate is causing an issue. I just have no idea what else to
> check. Port 443 is forwarded to 8123. For this line is it supposed to
> stay like this or is the whole thing supposed to be replaced wit
ynot1234567890 wrote:
> Hi,
>
> > > >
- The HA_Link is to be replaced with your domain line name. So mine
> might be (but isn't) ynotmylink.duckdns.org
- The HA Token needs to be generated for your application. It is a
> long lived access token and allows other applications (shel
grimmace92 wrote:
> Thanks. Progress but following error
>
> Getting closer. I created a cert via lets encrpyt and then exported
> them and placed them in my homeassistant folder where my
> configuration.yaml file is. I can access home assistant via https.
> This query is giving me the fol
grimmace92 wrote:
> I'm pretty close to getting this working.
> Update https://HA_Link.duckdns.org/api/states/sensor.art_ID? -H
> "Authorization Bearer $HA_Token" with you're HA_Link (must be accessible
> from the internet)
>
> I assumed this meant to change "HA_Link" to what you created in d
ColH wrote:
> What is the toggle switch at the top of this pane? I assumed it was
> going to be power on/off on the player selected below, but it doesn't
> seem to do anything, or react to on/off done in any other ways (even
> through voice control).
It should not be there at all. Serves no pu
CypherMK wrote:
> Try: bash qry_alb.sh _supertramp _breakfast_in_america
Thanks. Progress but following error
Getting closer. I created a cert via lets encrpyt and then exported
them and placed them in my homeassistant folder where my
configuration.yaml file is. I can access home assistant
grimmace92 wrote:
> I'm pretty close to getting this working. I've got everything in Home
> Assistant and I can change songs, pause, etc. However the shell scripts
> aren't working I don't think. I have home assistant installed on a
> synology NAS using docker. The home assistant folder is a
ynot1234567890 wrote:
> I guess so if that's how your system is configured. I am using docker
> and in that install it's simply /config/shell. You may need to update
> the path to the shell files in configuration.yaml file to ensure they
> get executed. For the next revision I will try to use
What is the toggle switch at the top of this pane? I assumed it was
going to be power on/off on the player selected below, but it doesn't
seem to do anything, or react to on/off done in any other ways (even
through voice control).
ColH wrote:
> How to I get the client ID and secret for the Spotify scripts?
Sign up for a Spotify developers account here:
https://developer.spotify.com/dashboard/
Create an app and you will get a client id and client secret. These are
used for security purposes to run queries against the s
How to I get the client ID and secret for the Spotify scripts?
ColH's Profile: http://forums.slimdevices.com/member.php?userid=30377
View this thread: http://forums.slimdevices.com/showthread.php?t=109273
CypherMK wrote:
> Ok, I will send you an email.
> Another thing I see you mention. I don't see any HA sensors anywhere
> posting my results.
That would be the case if the shell scripts were not running properly.
It is supposed to post the query results to sensors for use inside HA.
sensor.ar
Ok, I will send you an email.
Another thing I see you mention. I don't see any HA sensors anywhere
posting my results.
CypherMK's Profile: http://forums.slimdevices.com/member.php?userid=62798
View this thread: http://f
CypherMK wrote:
> This is also different from your example:
> 26408
> And I don't have those player controls like your example.
Hi, sounds like the shell scripts are not executing or executing
properly. That is why you're not getting anything queued up. So to
test open a shell in your HA inst
This is also different from your example:
26408
And I don't have those player controls like your example.
+---+
|Filename: Knipsel3.JPG |
|Download: http://forums.slimdevices.com/attachme
ynot1234567890 wrote:
> I guess so if that's how your system is configured. I am using docker
> and in that install it's simply /config/shell. You may need to update
> the path to the shell files in configuration.yaml file to ensure they
> get executed. For the next revision I will try to use
CypherMK wrote:
> So it should be: /home/homeassistant/. homeassistant/config/shell.
>
> Thanks for helping!
I guess so if that's how your system is configured. I am using docker
and in that install it's simply /config/shell. You may need to update
the path to the shell files in configuratio
ynot1234567890 wrote:
> The shell files go in the config/shell directory as indicated in the
> configuration.yaml file. Ynot.So it should be: /home/homeassistant/.
> homeassistant/config/shell.
Thanks for helping!
Cy
CypherMK wrote:
> I did, but did I put the "shell" files in the correct directory? I put
> them in: /home/homeassistant/.homeassistant/shell
> Is that correct?
The shell files go in the config/shell directory as indicated int he
configuration.yaml file. Ynot.
*software* - logitech media ser
CypherMK wrote:
> Putting an artist or song etc in the HA GUI doesn't add songs to the
> playlist...
Hi, sorry for the late reply, been on holidays with little time or
access. But I see Hopeful has been helping out nicely, thank you. How
did you make out. I assume you got the shell scripts r
Putting an artist or song etc in the HA GUI doesn't add songs to the
playlist...
CypherMK's Profile: http://forums.slimdevices.com/member.php?userid=62798
View this thread: http://forums.slimdevices.com/showthread.php?t=10
CypherMK wrote:
> Managed to run it, and this is the outcome:
>
> >
Code:
> > osmc@osmc:/home/homeassistant/.homeassistant/shell$ bash qry_alb.sh
_supertramp _breakfast_in_america
Managed to run it, and this is the outcome:
Code:
osmc@osmc:/home/homeassistant/.homeassistant/shell$ bash qry_alb.sh
_supertramp
_breakfast_in_america
nc: c
hopeful wrote:
> Did you change directories before running the command?
> cd config/shell
I did, but did I put the "shell" files in the correct directory? I put
them in: /home/homeassistant/.homeassistant/shell
Is that correct?
-
Did you change directories before running the command?
cd config/shell
hopeful's Profile: http://forums.slimdevices.com/member.php?userid=65059
View this thread: http://forums.slimdevices.com/showthread.php?t=109273
_
Hi ynot,
Finally got some time to get this running. Thanks for the guide.
But I'm running into some problems with setting this up. I think I have
done everything right, but I can't use the artist, song etc fields in HA
GUI as explained in the troubleshooting guide.
> If that works then fill ou
dclbas wrote:
> While setting up the fulfillment section under dialogflow, I had another
> question for the Webhooks instruction:
>
> "In the Headers section, replace insert_your_long_lived_token_here with
> your long lived access token ID generated by Home Assistant."
>
> What do I put in for
ynot1234567890 wrote:
> Hi dclbas:
>
> For those starting from scratch, as Hopeful mentioned, step 1 is to
> ensure your HA instance is fully accessible from the internet using
> https://mydomain.duckdns.org, Hopefuls instructions should help you
> there.
>
> Step 2: Is setup the HA access lo
hopeful wrote:
> It's documented here:
>
> https://www.home-assistant.io/docs/authentication/providers/
>
> The final zero in the IP address is a wildcard. It means that any device
> with an IP address beginning with 192.68.0 connecting to your HA server
> is trusted and you shouldn't have to
dclbas wrote:
> Thanks Colin for your instructions, what does the last lines do?
>
> trusted_networks:
> - 192.168.0.0/24
>
> What IP address do I use for the trusted_networks, my raspberrypi
> address?
>
> Thanks
It's documented here:
https://www.home-assistant.io/docs/authentication/provid
hopeful wrote:
> Is your HA server accessible from the internet, e.g. from a mobile
> 'phone using 4G and not the local wi-fi network? You need to be able to
> get to it externally using 'mydomain.duckdns.org'
>
> If not, here's what I had to do:
> 1. In the DuckDNS add-in, configure your DuckD
ynot1234567890 wrote:
> Hi dclbas:
>
> For those starting from scratch, as Hopeful mentioned, step 1 is to
> ensure your HA instance is fully accessible from the internet using
> https://mydomain.duckdns.org, Hopefuls instructions should help you
> there.
>
> Step 2: Is setup the HA access lo
Hi dclbas:
For those starting from scratch, as Hopeful mentioned, step 1 is to
ensure your HA instance is fully accessible from the internet using
https://mydomain.duckdns.org, Hopefuls instructions should help you
there.
Step 2: Is setup the HA access long lived access tokens
Step 3: Modify
Is your HA server accessible from the internet, e.g. from a mobile
'phone using 4G and not the local wi-fi network? You need to be able to
get to it externally using 'mydomain.duckdns.org'
If not, here's what I had to do:
1. In the DuckDNS add-in, configure your DuckDNS token and domain name
and
Thanks ynot123 for creating the Google Assistant voice control for LMS.
I'm a newbie setting up Hassio and have been following your instructions
on how to get Google Voice working. I did have a question regarding how
to setup the Webhooks, you mention:
"Fill in the URL field with
"https://hom
hopeful wrote:
> Bearing in mind that this is all new to me, are my following assumptions
> correct ...
> 1. Following your complete set of instructions, provided that I'm happy
> to use the phrase 'LMS Controls', I wouldn't need to create an Action
> from https://console.actions.google.com/ , b
Good news, the LMS Controls project (see 'here'
(https://github.com/ynot123/LMS_Controls)) has been updated to
incorporate the new Home Assistant authentication system. This project
now uses Long Lived Access Tokens to authenticate between Google
DialogFlow and Home Assistant.
In addition, chang
Bearing in mind that this is all new to me, are my following assumptions
correct ...
1. Following your complete set of instructions, provided that I'm happy
to use the phrase 'LMS Controls', I wouldn't need to create an Action
from https://console.actions.google.com/ , because the DialogFlow part
hopeful wrote:
> If you haven't published an action to be available to all and I haven't
> created an action from the console, how does Google Assistant recognize
> the phrase 'LMS Control'?
Hum, not sure. I did indeed publish it as an alpha action only which
should only appear to those I inv
If you haven't published the action as an available app to all users and
I haven't created an action, how does Google Assistant recognise the
phrase 'LMS Controls' at the moment?
hopeful's Profile: http://forums.slimdevice
If you haven't published an action to be available to all and I haven't
created an action from the console, how does Google Assistant recognise
the phrase 'LMS Control'?
hopeful's Profile: http://forums.slimdevices.com/mem
hopeful wrote:
> But I haven't created the LMS Controls action, ynot has, hasn't he? If I
> log on to that URL, there is no action to select.
>
> Sorry if I'm being dumb.
You will need to create your own action, calling your own url, with your
webhook, etc.. You can name it whatever you want
kalimeroo wrote:
> You log on to your https://console.actions.google.com/ and you select
> your action. On the left panel you'll get the "Invocation" menu where
> you can change your trigger phrase.
But I haven't created the LMS Controls action, ynot has, hasn't he? If I
log on to that URL, the
You log on to your https://console.actions.google.com/ and you select
your action. On the left panel you'll get the "Invocation" menu where
you can change your trigger phrase.
kalimeroo's Profile: http://forums.slimdevices
kalimeroo wrote:
> You can decide the way your action is triggered. It requires two words .
So where is that string and can it be edited after the application has
been created?
hopeful's Profile: http://forums.slimdevices
When you create a google application you create an action (in this case
it will be Dialogflow). You can decide the way your action is triggered.
It requires two words (Vortexbox won't work but Vortex box will) so you
can use "Ok google, tell Vortex Box to play nirvana in the kitchen".
-
I'm curious to know how the Google Assistant recognises the intent 'LMS
Controls' in order to start the app. If I wanted to change the name,
could I do that and, if so, where? So, for example, I could say 'Hey
google ask Vortexbox to play album Dog and Butterfly by Heart in the
kitchen with shuff
@kalimeroo, That is exactly the issue. As mentioned above, in order to
make this work now, the dialogflow method has to be implemented properly
using HA intents, returning a valid JSON to Google Assistant. I will
likely create a short term patch to make it work as it was, then do a
better job
I probably experience the same issue.
I went on and created an action on google console and then created a new
project and then an action in Dialogflow.
When testing the app in Dialogflow in works fine but if I then integrate
it to google assistant and run the test I get the error "LMS control
i
ynot1234567890 wrote:
>
> I will try to solve it fairly soon, but integrating 3 pieces of software
> I have little control over is proving a bigger task than I hoped for.
> If you have time, give it a shot and let me know how you make out. I
> will post if I make significant progress in this
kalimeroo wrote:
> Thanks a lot for your time and efforts. The authentification with the
> long lasting token (generetad in
> https://your_server.duckdns.org/profile) works like a charm. I just had
> to specify the 8123 port as my router does not handle port forwarding
> correctly.
>
> I can no
Thanks a lot for your time and efforts. The authentification with the
long lasting token (generetad in
https://your_server.duckdns.org/profile) works like a charm. I just had
to specify the 8123 port as my router does not handle port forwarding
correctly.
I can now move on with the Google part.
kalimeroo wrote:
> Hi,
>
> I am running Hassbian with Home Assistant v0.83.2.
>
> When running the qry_alb.sh script it returns successfully the ID number
> of the artist and album (LMS server is not secured as far as I know).
>
> The issue is on the curl POST request which returns the error
Hi,
I am running Hassbian with Home Assistant v0.83.2.
When running the qry_alb.sh script it returns successfully the ID number
of the artist and album (LMS server is not secured as far as I know).
The issue is on the curl POST request which returns the error 401.
I tested :
$ curl -X POST
kalimeroo wrote:
> Concerning the end of line character if using windows to edit the files,
> it can also be fixed whith the dos2unix tool.
>
> I added the following lines in order to force API password usage:
>
> homeassistant:
> auth_providers:
> - type: legacy_api_password
>
> http:
> api_
Concerning the end of line character if using windows to edit the files,
it can also be fixed whith the dos2unix tool.
I added the following lines in order to force API password usage:
homeassistant:
auth_providers:
- type: legacy_api_password
http:
api_password: !secret http_password
The se
Please note if you upgrade your Home Assistant installation to version
0.83.2 the use of api_password is no longer supported (as pointed out by
@kalimeroo) and your webhooks and shell script authentication will need
to change to use long-lived tokens.
I will provide an update on the methods in t
hopeful wrote:
> Doh! As I was preparing to send you my script and replacing the IP
> address and DuckDNS ID with asterisks, I noticed that I'd missed
> replacing a 'localhost' entry in the original file. It works now - sorry
> about that.
>
> One thing that may help others is the problem I had
Doh! As I was preparing to send you my script and replacing the IP
address and DuckDNS ID with asterisks, I noticed that I'd missed
replacing a 'localhost' entry in the original file. It works now - sorry
about that.
One thing that may help others is the problem I had before this. If
using Windo
hopeful wrote:
> The result of running the qry_alb.sh script directly:
>
> bash-4.4# bash qry_alb.sh _supertramp _crisis_what_crisis?
>
>
> Artist ID is:
> Album ID is: 0
> now Posting results
>
> {"attributes": {}, "context": {"id": "e2b25b8b1eb1469e9948916ad73d9d49",
> "user_id": null}, "e
The result of running the qry_alb.sh script directly:
bash-4.4# bash qry_alb.sh _supertramp _crisis_what_crisis?
Artists are:
Artist check zero is:
qry_alb.sh: line 14: [: ==: unary operator expected
Artist found so moving on to albums
Album check zero is: 0
Albums are:
albums 0 20 ar
hopeful wrote:
> Following the guide troubleshooting.md I can successfully fill out the
> source and artist fields and select the play artist function and the
> player starts playing. However, the same doesn't work for play album or
> play playlist?
>
> Colin
For the album issue, I assume you
Following the guide troubleshooting.md I can successfully fill out the
source and artist fields and select the play artist function and the
player starts playing. However, the same doesn't work for play album or
play playlist.
I notice that some of the shell script files include the 'login usern
kalimeroo wrote:
> @Hopeful Sorry, I misunderstood your issue.
>
> Setting a Legacy PI password works fine but will indeed be dropped
> (https://www.home-assistant.io/docs/authentication/providers/).
>
> @ynot
>
> I think I have set up the Home Assistant (Hassbian) and LMS fine on my
> Rpi. Y
@Hopeful Sorry, I misunderstood your issue.
Setting a Legacy PI password works fine but will indeed be dropped
(https://www.home-assistant.io/docs/authentication/providers/).
@ynot
I think I have set up the Home Assistant (Hassbian) and LMS fine on my
Rpi. You state that you created a playlist
hopeful wrote:
> I am struggling to work out how to specify an API password. I installed
> Home Assistant using a Pi image and have a password to enter on the web
> page when I go to http://hassio.local:8123
> This isn't the same password as the API password is it? Also, isn't the
> API passwor
kalimeroo wrote:
> Hi,
>
> When you first login to Home assistant, it will prompt you with a login
> ans password. This is not an authentification step. Indeed here you can
> create a new home assistant user ans its password. You will then use
> this login/password to effectively login.
Maybe
Hi,
When you first login to Home assistant, it will prompt you with a login
ans password. This is not an authentification step. Indeed here you can
create a new home assistant user ans its password. You will then use
this login/password to effectively login.
---
I am struggling to work out how to specify an API password. I installed
Home Assistant using a Pi image and have a password to enter on the web
page when I go to http://hassio.local:8123
This isn't the same password as the API password is it? Also, isn't the
API password feature is now deprecate
kalimeroo wrote:
> Thanks for your suggestion. I currently have a rpi with Digiamp hat
> running picoreplayer and LMS server.
> In the future (when I move home) I will go for a NAS running both LMS
> and Hassio in containers (or an old PC running this).
> I will go for two rpi at the moment (on
Thanks for your suggestion. I currently have a rpi with Digiamp hat
running picoreplayer and LMS server.
In the future (when I move home) I will go for a NAS running both LMS
and Hassio in containers (or an old PC running this).
I will go for two rpi at the moment (one for Homass and the other f
kalimeroo wrote:
> Really great job you did !
>
> Also I am a complete beginner with Hass.io and DialgFlow I will try and
> reproduce your setup with all the informations/files you kindly
> provided.
>
> I have one rpi, a google home mini and a squeezebox touch. I would thus
> need a second r
Really great job you did !
Also I am a complete beginner with Hass.io and DialgFlow I will try and
reproduce your setup with all the informations/files you kindly
provided.
I have one rpi, a google home mini and a squeezebox touch. I would thus
need a second rpi in order ro run LMS server or m
Great job you did ynot !
I was looking for such a solution as I own a google home mini and an rpi
based audio system. I will thus try and proceed with the setup
described...which can take a bit of time as I am completely new to
homass.io and Dialogflow.
Thanks
101 - 200 of 230 matches
Mail list logo