Announcement

Collapse
No announcement yet.

Alexa TTS that works better (IMHO) than the solution for Home Assistant.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • zimmer62
    replied
    "no csrf found"
    I had this today as well... I restarted nodered and went to the cookie refresh page again.

    I haven't been able to keep this running for more than a few weeks without having to intervene. I wish it was more stable.

    Leave a comment:


  • MFULLER
    replied
    Thought I would give this a shot as I had a spare Pi sitting around.

    I've got node red installed (never used it before and have limited pi knowledge).
    I've followed this thread as best I can but am stuck on the Refresh Cookie part. I open the proxy page and enter my username/password for Amazon. I then switch back to node-red and it gives a "no csrf found" error. Debug shows:
    Code:
    18/02/2020, 16:35:40node: MyAlexamsg : string[13]
    "no csrf found"
    Any layman's help appreciated.

    Leave a comment:


  • alphatech
    replied
    Thank you, looking forward to it.

    Leave a comment:


  • AZweimiller
    replied
    Originally posted by alphatech View Post
    Sorry but I'm very unfamiliar with all these tools and I need some guidance since from what I read, there are many different platforms and tools that someone can use. I have HS3 on a Windows 7. Does anyone have a step by step process to install these tools on this platform.

    Thanks
    I can give you a hand on something like Google Hangouts if you want to shoot me a PM. I don't have anything written up as I just worked through this myself.

    Leave a comment:


  • alphatech
    replied
    Sorry but I'm very unfamiliar with all these tools and I need some guidance since from what I read, there are many different platforms and tools that someone can use. I have HS3 on a Windows 7. Does anyone have a step by step process to install these tools on this platform.

    Thanks

    Leave a comment:


  • AZweimiller
    replied
    Originally posted by mr.Magoo View Post
    Thanks - glad you like it !
    Another Node that you may want to look into is "Alexa Local" - https://flows.nodered.org/node/node-...ib-alexa-local
    This allows you to set up a "virtual" device in Node Red that is recognized by Alexa as a smart home device and you can either have it trigger things directly - or - when you combine the two (Alexa Local and Alexa Event) you can use it to make the triggering room sensitive in a way not too different from Alexa's own Group/Lights function (but more powerful / flexible).

    i.e. you combine the room from Events with the device from Local and let that control whatever it is you'd like to control
    This sounds interesting but I'm not fully following. Can you elaborate or post an example? I am currently up and running with the TTS using a tweaked version of your original Flow so thanks for that.

    EDIT:

    Thanks, figured it out.

    Leave a comment:


  • mjolsen
    replied
    Originally posted by mjolsen View Post


    oh yeah.. sorry, I didn't do the file method I copied the cookie from the debug window. So I went back and used the proxy method and dumped it to the file and copied that cookie. Hopefully it sticks. will see in a few days.

    thanks again,
    mike
    Still working since the 29th! Looks like the cookie in the file method works great! Super simple and great solution! Seems like someone could wrap all of this up into a plugin and a clean interface.

    m

    Leave a comment:


  • mjolsen
    replied
    Originally posted by mterry63 View Post

    I'm assuming you're using Node-Red and the flows posted in this thread.

    If you open Node-Red in you web browser and select the Alexa-Init flow, in the right hand pane is an arrow pointing down. Click that and select "Configuration Nodes". You should see a button under alexa-remote-account. Double click that and it should open "Edit Alexa Account node". I have the method "Proxy" with "127.0.0.1" and port "3456". Right under that is the file path used for the stored cookie which will be used if the flow is restarted. The path will depend on your OS, for me I have /home/user/tempfilename. Once you capture the cookie with a proxy browser login you can look for the file and show the contents.

    Hope that helps.

    oh yeah.. sorry, I didn't do the file method I copied the cookie from the debug window. So I went back and used the proxy method and dumped it to the file and copied that cookie. Hopefully it sticks. will see in a few days.

    thanks again,
    mike

    Leave a comment:


  • mterry63
    replied
    Originally posted by mjolsen View Post

    didn't see any instructions on that nor did I find such options?
    I'm assuming you're using Node-Red and the flows posted in this thread.

    If you open Node-Red in you web browser and select the Alexa-Init flow, in the right hand pane is an arrow pointing down. Click that and select "Configuration Nodes". You should see a button under alexa-remote-account. Double click that and it should open "Edit Alexa Account node". I have the method "Proxy" with "127.0.0.1" and port "3456". Right under that is the file path used for the stored cookie which will be used if the flow is restarted. The path will depend on your OS, for me I have /home/user/tempfilename. Once you capture the cookie with a proxy browser login you can look for the file and show the contents.

    Hope that helps.

    Leave a comment:


  • mjolsen
    replied
    Originally posted by mterry63 View Post
    Do you have the cookie mode set to write to a valid file?

    Sent from my Pixel 2 using Tapatalk
    didn't see any instructions on that nor did I find such options?

    Leave a comment:


  • mterry63
    replied
    Originally posted by mjolsen View Post
    Looks like I have to re-auth every few days. I've tried cookie mode and account mode. Is this a current limitation or did I do something wrong?

    thx,
    mike
    Do you have the cookie mode set to write to a valid file?

    Sent from my Pixel 2 using Tapatalk

    Leave a comment:


  • mjolsen
    replied
    Looks like I have to re-auth every few days. I've tried cookie mode and account mode. Is this a current limitation or did I do something wrong?

    thx,
    mike

    Leave a comment:


  • Statikk
    replied
    Originally posted by mterry63 View Post
    You'll thank me later.
    You're right! Thank you!! I'll still do the set up to bypass geo-blocking for those random things here and there but that service is amazing and totally hassle free! I had been looking for something like that for awhile now so my in laws have more German stuff to watch than just NDR and the few things that aren't blocked on some of the mediatheks. Plus it has the added bonus of having a nice easy to use interface.

    Leave a comment:


  • mterry63
    replied
    Originally posted by Statikk View Post
    Sounds like something I was going to attempt with pfSense and pfblocker. I haven't got around to it yet but the idea was to tunnel traffic based on destination to get around geoblocking so my wife could watch German content from some of their networks without forcing all of the streaming traffic from that device through the tunnel. Is there some kind of guide or write up you found useful when you were implementing you current solution?
    Sign up for YouTV on a PC, Roku, or FireTV and watch any German programming you want without hassle. You'll thank me later.


    Sent from my Pixel 2 using Tapatalk

    Leave a comment:


  • mr.Magoo
    replied
    Not to scare people away too much as there's no hacking involved if you rather just run windows, I'm running my whole setup on a W2016 server
    i.e. NodeRed, Mosquitto (for MQTT) and HS3 (plus Grafana and InfluxDB for logging / graphs). should work just fine on 2012 server or 2010

    Somehow Pi's feel sketchier (lets not turn this into a windows joke thread, OK so I try to keep them on semi single duties.
    One is my 1W controller, one is my doorbell and then the two ZNet's

    Leave a comment:

Working...
X