As announced in the post
https://forums.slimdevices.com/showthread.php?111016-Announce-MediaServer-*certified*-Alexa-skill-for-LMS,
I have created a certified skill for controlling LMS via the JSONRPC
interface. The installation instructions provided in the section -server
configuration- of the
Nice I didn't expect this to be possible.
I'm running LMS already on a SYnology, and it seems to allow python
3.5.2 to be installed using package manager.
Has anyone else installed this on an older Synology or is something more
modern like a Rpi recommended?
Thanks. With that link, I found some options on the "Always Free" tier.
They list "Database AWS DynamoDB" "Compute AWS Lambda" "Mobile Amazon
SNS" "Developer Tools Amazon Cloudwatch" "Business Productivity Amazon
Chime" and a few others. I don't know which I should choose.
Nice to see there is
NFLnut wrote:
> I thought I might try (again) to wrap my head around this project but I
> have a maybe naive question: If I decide to try to do the MQTT set up,
> and since I really have no knowledge about AWS, what does it cost to use
> that service with Amazon? Is there a cost? Monthly?
I thought I might try (again) to wrap my head around this project but I
have a maybe naive question: If I decide to try to do the MQTT set up,
and since I really have no knowledge about AWS, what does it cost to use
that service with Amazon? Is there a cost? Monthly? Annually?
Thanks for
Freddy wrote:
> Been away for a while and now I see that there has been some great
> progress here, nice work.
>
Thanks!
>
> I´m running the version from July (not MQTT), is there any point of
> upgrading and if so, what are the steps?
>
Probably not much point yet if you've got it working
Been away for a while and now I see that there has been some great
progress here, nice work.
I´m running the version from July (not MQTT), is there any point of
upgrading and if so, what are the steps?
A bit afraid to break my setup:eek:
Hisma wrote:
> There's too much manual intervention required to do a fully automated
> installation from what I could follow, particularly on the AWS side. I
> would say a lot of the complexity is just knowing how to navigate your
> way around AWS and get everything "prepped" to ultimately run
sharper9 wrote:
> Wow thanks nickb
>
> I think this a little above my tech level.
> Shame I would love to get this working.
> Are there any future plans for an installer for any of the server side?
There's too much manual intervention required to do a fully automated
installation from what I
+1 !!
sharper9 wrote:
> Wow thanks nickb
>
> I think this a little above my tech level.
> Shame I would love to get this working.
> Are there any future plans for an installer for any of the server side?
gegen's
nickb wrote:
> If you're technical, we've got an extensive 'squeeze-alexa HOWTO'
> (https://github.com/declension/squeeze-alexa/blob/master/docs/HOWTO.md).
> It's not easy (but I'm automating more and more), and quite a few people
> have got this set up now.
Wow thanks nickb
I think this a
'squeeze-alexa 2.4'
(https://github.com/declension/squeeze-alexa/releases/tag/v2.4) is now
out.
- Handle old and disconnected players properly
- Handle now playing for tracks / streams with no artist
- Friendly error responses if transport is broken
- Update requests
sharper9 wrote:
> Just ordered echo 2nd Gen and a dot 3rd gen.
> I have a couple of squeeze V3 running wonderfully using my QNAP NAS as
> storage with Flac and MP3 format.
> Would like to get them hooked up.
>
> What do I do next?
>
If you're technical, we've got an extensive 'squeeze-alexa
Just ordered echo 2nd Gen and a dot 3rd gen.
I have a couple of squeeze V3 running wonderfully using my QNAP NAS as
storage with Flac and MP3 format.
Would like to get them hooked up.
What do I do next?
also posted here
Hisma wrote:
>
> But I exported my wiki page into a word doc, see here -
> edit: send me a PM if you want it, just in case there's too much private
> info I didn't want to make it public
>
Done, thanks.
>
> Note that I COULD NOT get this working with stunnel. I think your
> instrunctions
Hisma wrote:
>
> Thanks for your hard work on this. This clearly took a lot of time and
> effort. I will say though it is definitely a "techie only" setup for
> sure. I'm fairly savvie and it took me about 8 hours to finally get it
> working! It was mostly due to the quality of
'squeeze-alexa 2.3'
(https://github.com/declension/squeeze-alexa/releases/tag/v2.3) is now
out.
- Stop transport better (#52) and unsubscribe in MQTT on
disconnect
- Improve long ValueError Alexa reponse when transport goes
wrong.
- Now Playing: Support multiple artists if
Prog wrote:
> I'll maybe have another go at the weekend when I have more time.
> Thanks. If I get properly stuck then I'll ask for help in the places you
> suggested. I'm probably missing something obvious when it comes to
> configuring mqtt-squeeze.
I've just updated the 'MQTT HOWTO'
nickb wrote:
> It's not -too- hard, I promise, it just takes a lot of time and reading.
I'll maybe have another go at the weekend when I have more time.
> Not currently. A few people have asked (and succeeded?). I'll try to add
> a few pointers. If you get really stuck try the chatroom or post
Prog wrote:
> I think I'm getting too old for all this techie stuff as I've come
> unstuck following the HOWTO guide. :o
>
It's not -too- hard, I promise, it just takes a lot of time and
reading.
>
> Is there a step-by-step guide anywhere to getting this all working on a
> Raspbian-based
I think I'm getting too old for all this techie stuff as I've come
unstuck following the HOWTO guide. :o
Is there a step-by-step guide anywhere to getting this all working on a
Raspbian-based server? I'd prefer the MQTT bridge option as I'm actually
familiar with MQTT.
Many thanks in advance.
htcheng wrote:
>
> I now have a working skill that can select players, change volume, play
> genres, etc. EXCEPT when I ask it to play a Playlist, it acknowledges
> the playlist but it loads an empty playlist. Once it does this, the
> skill forgets all of the players, genres, etc. for a few
'squeeze-alexa 2.2'
(https://github.com/declension/squeeze-alexa/releases/tag/v2.2) is now
out.
- Huge performance improvement for MQTT transport mode (possibly SSL
too, untested)
- Use Amazon native Genre
- Documentation improvements
- Testing improvements
reinholdk wrote:
> There's a typo in the link above. Should be without "t" before "alexa":
> https://github.com/declension/squeeze-alexa/blob/master/docs/MQTT.md
Fixed now. Thanks!
nickb's Profile:
nickb wrote:
> Sure, understood. Good news then - this isn't necessary now - you can
> use 'the new MQTT transport'
> (https://github.com/declension/squeeze-talexa/blob/master/docs/MQTT.md)
> instead if that takes your fancy. This requires no ports to be opened,
> no LMS plugins to be
nickb wrote:
> Sure, understood. Good news then - this isn't necessary now - you can
> use 'the new MQTT transport'
> (https://github.com/declension/squeeze-talexa/blob/master/docs/MQTT.md)
> instead if that takes your fancy. This requires no ports to be opened,
> no LMS plugins to be
NFLnut wrote:
>
>
> Main reason being, I don't want to accidentally and unsecurely blow open
> a port on the innerwebz for every script kiddie on the planet to play
> with.
>
Sure, understood. Good news then - this isn't necessary now - you can
use 'the new MQTT transport'
I would love to try this as Alexa/Echo seems fairly useless to me (I
recently purchased a Show and a Dot to experiment with, the latter which
I really needed to connect directly to my Denon receiver, and I'm pretty
nonplussed by the whole experience). I have no interest in listening to
Amazon
'squeeze-alexa 2.1'
(https://github.com/declension/squeeze-alexa/releases/tag/v2.1) is now
out:
- AWS setup automation (BETA)
- MQTT transport improvements
- SSL hardening
- Nginx / Dockerised nginx tunnel examples
- Various setup / documentation improvements
slartibartfast wrote:
> As of tonight Peter Mee's Alexa implementation is working again.
> [emoji3]
>
> Sent from my SM-G900F using Tapatalk
Yes!
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8
speaker; Pioneer
As of tonight Peter Mee's Alexa implementation is working again.
[emoji3]castalla wrote:
> Same here
Sent from my SM-G900F using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
Freddy wrote:
> Its not that much that needs to be confed locally actually.
>
> If you are running NGINX I can share my config.
No idea what nginx does ... thanks anyway
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony
Its not that much that needs to be confed locally actually.
If you are running NGINX I can share my config.
Freddy's Profile: http://forums.slimdevices.com/member.php?userid=41055
View this thread:
slartibartfast wrote:
> I don't suppose there are step by step instructions for installing this
> on a Raspberry Pi (Debian Stretch). Or are there? I don't really want to
> screw up a working server.
>
> Sent from my SM-G900F using Tapatalk
Same here
Touch, Logitech Radio, Logitech UE
I don't suppose there are step by step instructions for installing this
on a Raspberry Pi (Debian Stretch). Or are there? I don't really want to
screw up a working server.
Sent from my SM-G900F using Tapatalk
:cool:
nickb's Profile: http://forums.slimdevices.com/member.php?userid=66261
View this thread: http://forums.slimdevices.com/showthread.php?t=107009
___
plugins mailing list
I´m happy to say that I´ve got this up and running now, with _a lot_ of
help from Nick. Thank You!
I ended up using NGINX SSL as my transporter which was for me optimal
since I already got NGINX running.
Only thing was that I couldn´t use my Lets Encrypt certs but thats no
biggie and it also
FYI
I tried and documented a 'proof-of-concept with Nginx inside Docker'
(https://github.com/declension/squeeze-alexa/blob/https://github.com/declension/squeeze-alexa/blob/master/docs/SSL.md#with-nginx-19aster/docs/SSL.md)
to work. :)
Freddy wrote:
> I´ve now managed to create the certs for MQTT IOT using the cli.
>
> Stuck on next step though
> -
> Set up permissions for MQTT
> Go to the AWS IoT section (make sure to select the right region), and
> you start the setup.
>
> You'll need an IAM policy to grant MQTT access to
nickb wrote:
> In which case personally I'd just leave that as is, 'generate new cert
> pairs just for stunnel'
> (https://github.com/declension/squeeze-alexa/blob/master/docs/SSL.md#create-certificates)
> which you can set to be 10 years or whatever. So long as you keep these
> safe of course.
Freddy wrote:
> So your plan is to share the same Letsencrypt certs with stunnel in
> docker and use this container only for squeeze-alexa?
> If you succeed please share, I run my NGINX with Letsencrypt on a nuc
> but Docker on a QNAP NAS. So it might be possible for me to use the same
>
I´ve now managed to create the certs for MQTT IOT using the cli.
Stuck on next step though
-
Set up permissions for MQTT
Go to the AWS IoT section (make sure to select the right region), and
you start the setup.
You'll need an IAM policy to grant MQTT access to the squeeze-alexa
Lambda.
Use
nickb wrote:
> Great, please give it a go. Sorry you're finding it difficult - it is
> definitely a complex setup. I've been adding to the docs more and more,
> but sometimes think the extra detail is making it -more- complicated.
>
> Definitely the fact there are entirely different networking
caplam wrote:
> I'll probably go with stunnel in docker container on synology nas. But
> i'll have to dig a bit more as, for now, i don't really understand
> network management with docker and particularly synology's
> implementation.
>
> edit: my concern is to make easy reverting changes on my
I'll probably go with stunnel in docker container on synology nas. But
i'll have to dig a bit more as, for now, i don't really understand
network management with docker and particularly synology's
implementation.
LMS 7.9.1 on a debian jessie vm (esxi 5.5)
1xboom, 1x sq3, 2x sonos play1,
caplam wrote:
> thank you for your answer.
> For now my concern is to find out how to treat the incoming traffic from
> amazon. If my understanding is right, it's not http traffic so i can't
> use synology reverse proxy.
> (I have several servers like jeedom which i can join on
>
nickb wrote:
>
> Sounds perfect - ignore MQTT for now, I'd go for SSL with your existing
> certificate, and get stunnel working - it's old but rock-solid and very
> lightweight.
>
> The diagnostics (local_test.py) and FAQ should provide quite a lot of
> help with this route, just make sure
Featuring MQTT support, new settings system, French language, and
various fixes:
'squeeze-alexa 2.0'
(https://github.com/declension/squeeze-alexa/releases/tag/v2.0)
nickb's Profile:
caplam wrote:
> Hi,
> My lms is installed in a esxi5.5 debian8 vm. I'd like to use alexa to
> control lms but i'd also like to have echo seen as a regular lms player
> (not with squeeze-alexia i think).
>
No, but see https://github.com/declension/squeeze-alexa/issues/25
>
> I already have a
Freddy wrote:
>
> I also run LetsEncrypt, NGINX and a MQTT broker but to my understanding
> the latter is of no use for this setup since we must use Amazons IOT
> broker?
That's right, at least for now.
Conceptually you've still got an unsolved problem if you use your own
broker - of how to
Freddy wrote:
> Hi,
> I was about to give this another try since it seems amazing. But I have
> a really hard time to follow the README/HOWTO from start -> finish.
>
Great, please give it a go. Sorry you're finding it difficult - it is
definitely a complex setup. I've been adding to the docs
caplam wrote:
> don't be happy too soon i'm not very skilled especially in security. :(
No worries, would be amazing to get this to work
I wonder if 2.0 will have a setup-script :)
Freddy's Profile:
don't be happy too soon i'm not very skilled especially in security. :(
LMS 7.9.1 on a debian jessie vm (esxi 5.5)
1xboom, 1x sq3, 2x sonos play1, foobar 2000, zettaly
spotify family
ipeng
plugins: spotty, upnpbridge, airplay bridge, shairtunes2W, youtube,
soundcloud
caplam wrote:
> Hi,
>
> I'm also interested in giving it a try and i'm also struggling to
> understand how it works. I've not started for now but i'm thinking on
> how to do it.
> My lms is installed in a esxi5.5 debian8 vm. I'd like to use alexa to
> control lms but i'd also like to have echo
Hi,
I'm also interested in giving it a try and i'm also struggling to
understand how it works. I've not started for now but i'm thinking on
how to do it.
My lms is installed in a esxi5.5 debian8 vm. I'd like to use alexa to
control lms but i'd also like to have echo seen as a regular lms player
Hi,
I was about to give this another try since it seems amazing. But I have
a really hard time to follow the README/HOWTO from start -> finish. I
would like to use alexa-squeeze with the MQTT transporter.
Is it worth waiting for 2.0? Will that one be easier to setup?
'squeeze-alexa 1.3'
(https://github.com/declension/squeeze-alexa/releases/tag/v1.3) is now
out with various internal improvements. It's now Python 3.x only, for
what it's worth. :)
Also... a 2.0 version is coming soon, with better networking support
using switchable transports depending on what
'Squeeze Alexa 1.2'
(https://github.com/declension/squeeze-alexa/releases/tag/v1.2) is now
out.
- The skill is now internationalised with en_GB as default, and
German (de_DE). American English (en_US) is supported by default now
too.
- Better timeout handling
- Errors with
Aidem wrote:
> Hi nickb, sorry, I realised I was on the wrong thread and felt
> discussion should be switched this thread.
> Thank you your reply.
>
> In your installation guide, after *clone the repo* the guide has the
> sentence. Note you will have to run a release process now to get the
>
nickb wrote:
> Stunnel is recommended, or at least documented and tested in detailed.
>
>
> Good news though - on searching just now it looks like 'nginx R6
> supports SSL termination for TCP protocols'
> (https://docs.nginx.com/nginx/admin-guide/security-controls/terminating-ssl-tcp/)
> , in
Freddy wrote:
> Great to see an own thread about this, I totally missed that before.
>
> I have a question.
> I'm currently running NGINX for connecting secure to Home-Assistant
> (HTTP) and connecting to my MQTT broker (stream)
> Alexa integration works fine with HA using HAASKA + let´s
Great to see an own thread about this, I totally missed that before.
I have a question.
I´m currently running NGINX for connecting secure to Home-Assistant
(HTTP) and connecting to my MQTT broker (stream)
Alexa integration works fine with HA using HAASKA + let´s encrypt cert
I´m a bit confused
'squeeze alexa 1.1'
(https://github.com/declension/squeeze-alexa/releases/tag/v1.1) was
released a while ago.
Includes various fixes and minor improvements, plus improved guides and
HOWTOs.
Also, the development version is now internationalised, with UK English
and German as the two
Oh, is latency a problem with MQTT?
I'd primarily thought websockets might be much simpler to integrate
---
learn more about iPeng, the iPhone and iPad remote for the Squeezebox
and
Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
at penguinlovesmusic.com
*New: iPeng 9, the
pippin wrote:
> MQTT is nice and fine but why not just use websockets or something like
> that? Plenty of implementations readily available and simple to
> integrate.
Probably because I have some familiarity with MQTT and understand how
I'd design a solution for the multi-user requirements.
MQTT is nice and fine but why not just use websockets or something like
that? Plenty of implementations readily available and simple to
integrate.
---
learn more about iPeng, the iPhone and iPad remote for the Squeezebox
and
Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
nickb wrote:
> Hi Meep. Interesting. I've played with MQTT and seemed simple / good -
> let us know how it goes. Got a bit worried when starting to read 'this
> very detailed review'
> (http://vasters.com/archive/MQTT-An-Implementers-Perspective.html)
> (though biased I guess) pointed out -so-
nickb wrote:
>
> I agree - patches are important, and yes for OpenSSL, as a key piece of
> internet infrastructure it's scary and definitely in the firing line &
> press often. To an extent that's why I'm advocating using -any- TLS TCP
> proxy most suited to your server (if you can get one
meep wrote:
>
> The next stage of development for me is to implement pseudo-polling by
> implementing MQTT. This will hopefully eliminate the requirement for an
> open port, though I have some concerns about latency. And of course this
> will only be as secure as mqtt over https can be.
>
Hi
pippin wrote:
> Hm, how is this more secure than what Meep is doing?
>
Hi Pippin. Great to open up this discussion. It's not intended as a
replacement / comparison to Meep's... more that there are some (other)
solutions out there which simply open up LMS directly (or use HTTP basic
auth) which
pippin wrote:
> Hm, how is this more secure than what Meep is doing?
> I mean... TLS and everything but this still requires you to open up your
> server machine to the internet and as security issues are this should at
> least involve staying up to date with known security issues in e.g. your
>
Hm, how is this more secure than what Meep is doing?
I mean... TLS and everything but this still requires you to open up your
server machine to the internet and as security issues are this should at
least involve staying up to date with known security issues in e.g. your
TLS client on a daily
Unfortunately, I'm probably not techie enough for it.
Regards,
Jim
Kyle's Profile: http://forums.slimdevices.com/member.php?userid=2541
View this thread: http://forums.slimdevices.com/showthread.php?t=107009
As mentioned a while ago, I've been developing (on and off) a DIY Alexa
Skill for Squeezebox integration and been using it successfully at home
for a while now.
Anyway - it's now improved and open-sourced on Github:
HTTPS://GITHUB.COM/DECLENSION/SQUEEZE-ALEXA
This is a separate approach from
74 matches
Mail list logo
