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?
Great stuff - almost can't believe it hadn't been thought of before!
Thanks for this Philippe
nickb's Profile: http://forums.slimdevices.com/member.php?userid=66261
View this thread:
meep wrote:
>
> Those B*std*rds at Amazon keep racing on making new languages available
> and adding features for US skills, but completely fail to extend those
> features to the other languages. There's a slot type available for US
> skills that make searching for album, artist and track
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
'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
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'
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
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:
l
(and not as fast) but it's working for me.
>
> Therefore, and until future notice, I guess I am out. Kudos however to
> meep and nickb for taking the plunge. Maybe someday old geezers like me
> can find our Alexa/Echoes useful.
Thanks :D
'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
: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
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
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
>
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
>
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
'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
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
'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
Aidem wrote:
> Unfortunately, I agree, this project seems to have stalled and I must
> thank you for providing a link to this alternative option: alexa-squeeze
> - DIY Alexa integration. I am trying to adapt the instructions provided
> to suit my Raspberry Pi environment.
> I have reached the
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
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
34 matches
Mail list logo
