Was working great and now won't authorise on 3456

[plasterer41]

Any thoughts or any similar experiences?

thanks,

Irwin

[saviothecnic]

ok i removed node-red-contrib-alexa-cakebaked 4.0.2 and installed node-red-contrib-alexa-remote2-v2 and modified as you suggested it now works again Only that at every restart it always asks me to re-authenticate but only if I restart raspberry my cookie path is this /home/pi/cookie/alexa.cookie

[bwims]

It might be

/usr/local/addons/redmatic/var/node_modules/node-red-contrib-opcua/node_modules

I did Google Redmatic "path" to "node-red" modules (Did you try that?)

and found this

https://github.com/mikakaraila/node-red-contrib-opcua/issues/193

Can't help you otherwise.

On Sat, 5 Jun 2021 at 16:25, andesse @.***> wrote:

I am to stupid to find the file. My system is Raspberrymatic based Redmatic. Can someone help me and comment the path that I need to use in ssh to find It? Thanks in advance

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855255298, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENIQ2JM4WNTC2PPMHZMLITTRI6VNANCNFSM45ACHLFQ .

[bbindreiter]

@cakebake hasn't been active since the beginning of February. I'm not sure if he's still using this node at all otherwise he'd have written something in here 🤷‍♂️

Even though I want to avoid it if somehow possible, maybe it's time to fork this node once again. I'm sure there are people out there not finding their way to github and are getting frustrated.

[bwims]

@cakebake hasn't been active since the beginning of February. I'm not sure if he's still using this node at all otherwise he'd have written something in here 🤷‍♂️

Even though I want to avoid it if somehow possible, maybe it's time to fork this node once again. I'm sure there are people out there not finding their way to github and are getting frustrated.

I already said you were a hero! 🙂

[andesse]

@bwims thanks, found it at the end... Not the best in console using 🤣

[andesse]

@bbindreiter just fork it. I personally, as an "end consumer" am just happy when I have a contrib that runs stable and gets a new update if not so :)

[peterchs]

Sad to say but it needs to be forked (again).

It needs a maintainer who has the time/attention to up version when the key dependency (alexa-remote) gets updates.

Unfortunately @cakebake mustn't have this time/attention, evidenced by the multiple releases of alexa-remote since 18 April v3.7.2 with no version update here. I'd really rather be getting updates via the node red palette manager than hacking at node modules.

[bwims]

ditto!

On Sat, 5 Jun 2021 at 21:19, Peter Stevenson @.***> wrote:

Sad to say but it needs to be forked (again).

It needs a maintainer who has the time/attention to up version when the key dependency (alexa-remote) gets updates.

Unfortunately @cakebake https://github.com/cakebake mustn't have this time/attention, evidenced by the multiple releases of alexa-remote since 18 April v3.7.2 with no version update here. I'd really rather be getting updates via the node red palette manager than hacking at node modules.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855290713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENIQ2KKB3LFGW4SAALOES3TRKBGLANCNFSM45ACHLFQ .

[saviothecnic]

And it is true there are 4 versions that are photocopies of each other and it just creates confusion I see that some are updated for 11 months others for 4 months others for 2 months another for 1 month we all automation enthusiasts have alexa and being able to plagiarize it for our purposes thanks to the red knot is very nice but you need a knot that always stays in step with adj by Amazon Alexa

[team-tech-works-uk]

this is pretty much one of the most-important (for me - and others?) node-red modules - alexa has gained imho dominance as an intelligent UI for smart-homes and hence strong and reliable integration with node-red is essential. I'd be happy to pay a suitable maintainer (or even offer my services if all else fails!!!)

[Chris380]

@bbindreiter Vielen Dank Bernd, tolle Arbeit!! I've added the accept property in line 797 and restarted node-red, everything works fine again. I wish I had found this issue and your solution a bit earlier. I was getting frustrated, because redeploying, reinitializing, restarting did not help since a few day.

[Matten-Matten]

Maybe we should then create a community node together.

Because many are very attentive here and also able to create a development like this. In my opinion it is always difficult for one person to keep the node up to date (time, implementation, etc.)

Recently, the most common cause of bugs is the cookie thing, because of that I have subscribed the topic "alexa-remote / releases" by @Apollon77, so I can implement innovations in my system.

At this point I have to say, that @Apollon77 does a first class job. Biggest thanks!

[bbindreiter]

Good, I'll fork it. Maintainers and contributors welcome. Will post the link here shortly.

[cakebake]

Hi! Sorry for the late reply. I had forked the project mainly for myself and hadn't used it in the last few weeks. I think it's great that the community proves itself here once again and that people help each other. If I can help with the new fork, please let me know. Otherwise I can also include other developers here. That would save many having to reinstall the node. I'm happy to report. I am subscribed.

[bbindreiter]

Hi @cakebake. Glad you're back! I absolutely agree that it would be best if we can just keep this fork here alive. Reinstalling is a pain. But eventually, that'd still mean that you're the one who has to do the builds and uploads to npmjs and nodered. Do you have the time and energy for it?

[cakebake]

But eventually, that'd still mean that you're the one who has to do the builds and uploads to npmjs and nodered. Do you have the time and energy for it?

Hi @bbindreiter,

That's right ... time is always a problem for me...

It would be incredibly helpful if you would check the functionality and if you can also resolve the merge requests. In terms of quality, it generally makes sense for one or two persons to do the "final acceptance" and publish the release. I can also hand over / share this process after a short time.

I am currently no longer using the node myself. But that can change again. :)

So if I have support on GitHub, I would be very helpful. This concerns issues, upstream keep an eye on, merge requests...

[andesse]

@bbindreiter @cakebake Jens, if you don't use the node anymore and time is short, hand it directly over to Bernd, he can create a new name for the contrib and is able to publish new releases.

You can still participate if time is available, or helping with the final acceptance.

Changing the contrib in node red isn't that complicated at all.

Just came into my mind. Good idea?

[fmarzocca]

@andesse, but this would imply that all users will have to remove cakebaked module, reinstall and configure a new one.

On Mon, Jun 7, 2021 at 11:23 AM andesse @.***> wrote:

@bbindreiter https://github.com/bbindreiter @cakebake https://github.com/cakebake Jens, if you don't use the node anymore and time is short, hand it directly over to Bernd, he can create a new name for the contrib and is able to publish new releases.

You can still participate if time is available, or helping with the final acceptance.

Changing the contrib in node red isn't that complicated at all.

Just came into my mind. Good idea?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855765030, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACBCQ3XV4XVOV3K37364KBLTRSFZ3ANCNFSM45ACHLFQ .

[andesse]

@fmarzocca thats so easy. Backup all flows, delete everything, delete the contrib, install the new one, import everything. Takes 3 minutes.

But you are right, I get your point, it might be annoying for some users.

[bwims]

Don't forget the little wrinkle where deleting and reimporting a flow loses the authentication unless you fiddle with credential encryption etc.   

I'd much rather keep the same fork if at all possible, but also happy to move to another if necessary.

This is the missing software that Amazon should provide. It turns a pretty useless voice automation system into something really powerful.

[bbindreiter]

Now that users can update cakebaked and find a working environment again there's no need to fork and migrate all users to a new node. I did create a fork here https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel which I intend to use for myself, as I'm eager to add more functionality, e.g. https://github.com/586837r/node-red-contrib-alexa-remote2/pull/181 . If something breaks I will always try to fix it upstream and support @cakebake, so everyone benefits from it.

Cheers!

[ammawel]

hmmm... of course first of all thank you very much for your efforts!

You write "as I'm eager to add more functionality" - and how will the rest of us users get this new functionality? Wouldn't it make more sense to have several developers like you working together on just one fork? Maybe also with a new name for the common project?

Maybe it would also be possible to work together to fix bugs that have been there for a long time. For example, Alexa still stops talking after some time (only for some users? Why?). In the meantime, the error can be detected and the module reinitialized; other software that works similarly (FHEM) or even uses the same module from Apollon77 (iobroker) do not have this error.

In its current form, despite the updates, this module is not reliable and actually not usable. We still hope...

Thanks and regards Achim

[bbindreiter]

I've been using this node for quite a while and found it very reliable actually. The only problem we all had was that it stopped working a while ago due to the authentication error, which is fixed now.

We all depend from alexa-remote2 and @Apollon77 is responsive. It was a matter of 24 hours to get the fix merged and published. Then it's up to the maintainers. Like previously pointed out, it doesn't help having multiple developers when only the owner is able to publish a new version to the repository. @cakebake stated that he's currently not using the node, therefore I have forked his repository so I can add new functionality and can independently publish to npmjs. The latter is important to me as I'm using this node heavily and rely on it (Doorbell, etc.. ). If there's something to fix I'll be the first to open a PR so users of cakebaked won't be left out.

[ohrenweide]

therefore I have forked his repository so I can add new functionality and can independently publish to npmjs

This also seems to me to be the best solution. Thank you for your good work and help here @bbindreiter . I am very much looking forward to the fact that with the help of your project the textCommand will be available soon. This will allow any dynamic requests to be made to Alexa - this will be the biggest step forward in a long time in my eyes.

Edit: Just installed node-red-contrib-alexa-remote2-applestrudel .... and the text command works like a charm! Thanks! 😊

[Matten-Matten]

Text_to_command is even a problem solver for me. Because I also set the alarm clock via the node, but unfortunately I have not yet succeeded, no matter how I format the input, to set an alarm clock longer than 24 hours and I think that is still a bug in the node. Since I manually inserted the text_to_command in my system, I was already able to test it and also solve my problem with the alarm clock.

[andesse]

@Matten-Matten is there a documentation how text-to-command is used?

[Matten-Matten]

is there a documentation how text-to-command is used?

to operate? that's easy you can enter what you can ask alexa too.

if you want to add the function in your node you have to do this manually in the files or wait until it appears here as an update.

greeting

[andesse]

@Matten-Matten gotcha! There is a workaround for doing this already. In the alexa app you can define a routine, where the trigger is what you actually would have asked alexa.

[cakebake]

I've been using this node for quite a while and found it very reliable actually. The only problem we all had was that it stopped working a while ago due to the authentication error, which is fixed now.

We all depend from alexa-remote2 and @Apollon77 is responsive. It was a matter of 24 hours to get the fix merged and published. Then it's up to the maintainers. Like previously pointed out, it doesn't help having multiple developers when only the owner is able to publish a new version to the repository. @cakebake stated that he's currently not using the node, therefore I have forked his repository so I can add new functionality and can independently publish to npmjs. The latter is important to me as I'm using this node heavily and rely on it (Doorbell, etc.. ). If there's something to fix I'll be the first to open a PR so users of cakebaked won't be left out.

Hi @bbindreiter,

I think you misunderstood me. I wanted to share this project with other developers so that "normal users" don't have to put in a lot of effort to redo their flow. That was very difficult for many of them the last time they made the switch.

If you have now made the decision to continue the project in a different repo, then syncing both projects makes absolutely no sense, as I then no longer see the purpose of keeping this project alive. Or am I seeing something wrong here? Nobody can benefit from it.

I can then rather write a simple guide on how everyone can "simply" create their fork in order to be able to be independent. The basic idea of ​​community is then no longer really given. Although it would certainly be instructive for many to know the code in connection with their Amazon account. No NPM repos or the Node-Red repository are required to install a node. This can also be done "simply" via the package.json of the Node-Red installation via Git.

Your decision. I'll just have a look here again soon and I'm happy to give authorizations to the source code or support another project if there is time and help is needed.

[bdydrp]

I have updated to the latest version, but still encounter a 'unexpected end of JSON input' I believe this is because i use an Australian account

[vbenhur]

The problem came back to me. The fault Authentication Failure: "no body" appears after I restart the NR. When I log into amazon everything looks OK but after deploy or restart NR the error message appears. I'm already using the latest version.

[andesse]

@vbenhur after a restart it's always necessary to make a fresh auth. Don't deploy full Flows, is that maybe the problem? If the auth and Init nodes get deployed, they cause the problems. I changed my deploys to changed nodes, and never had a problem since.

important is also that you run all automations in a routine node. There choose the option "node" and Run all stuff that you need. you can choose serial to run several automations after another.

if you trigger two alexa nodes in a flow simultaneously, the no json error usually appears in one or both.

can these tips solve your issue?

maybe you're right and we have another problem yet, since when did it appear? I played with big automation today, used the routine nodes like described and had zero issues. I can't reproduce.

Greetings

[andesse]

@vbenhur sorry, I use the applestrudel contrib, not the cakebaked anymore.

maybe it helps to switch to this one. but try the tips I recommend first. maybe it works for you

[vbenhur]

@andesse thanks for the tips! I didn't know the fact after a restart it's always necessary to make the authentication. It is a problem for me because I have a system running in a customer's house, then yesterday he had an energy fault and the system didn't come back. About node deploy, I just did it. It's a very interesting approach. In my case, I am not triggering two Alexa nodes in a flow.

I installed the applestrudel contrib just to check if the error persists and the behavior remains the same.

But maybe there's nothing wrong with contrib if this authentication condition is always required on system reboot. Is there some other solution to auto auth with cookie? I thought the cookie was for that.

[Matten-Matten]

Wenn du den Cookie in einer datei auf dem speicher speicherst und in der Konfiguration von node angibst. Ist nach einem Neustart keine Notwendigkeit das ganze zu Authentifizieren.

EN: If you save the cookie in a file on the memory and specify it in the configuration of node. After a restart there is no need to authenticate the whole thing.

Gruß matten matten

[andesse]

@Matten-Matten @vbenhur oh sorry, I meant an initialize after reboot, my bad.

but all main problems disappeared not deploying the nodes anymore. deploying just changed nodes was a lifechanger.

and important, don't trigger two nodes at the same time.

fun fact: as I use Spotify in my bathroom, when the door closes, I had it on one Spotify account all the time. so the music everywhere else stopped when in use. first I contacted Amazon, asked if it's fine to make a second account on my name for the automation reason, they said: you can create as much accounts as you want. then I contacted Spotify, explained the reason, they said it's ok to run family accounts on different Echos in the same apartment and upgraded to a family account. now I have two Amazon account, feedet with different Spotify accounts. I can trigger these two account simultaneously in node red. no issue :) I have one Spotify connected to the bathroom, one to the Livingroom. bathroom runs completely on its own play my Playlist, that have really Stange names, so the dot can find it and I can add new songs when I want. the second my Echo-dot, that is normally connected to my main account can be controlled with my ipad when it plays music. all very conviniet.

[bbindreiter]

In addition to Auto-Init with the cookie file I am running the Initialize node every hour because I also had issues in the past.

I let Alexa tell me the time on every full hour during the day and it maybe didn't work once in the last 2 months.

[saviothecnic]

Guys to me for a few days is not working is it just my problem or is it not working for you too?

[andesse]

Guys to me for a few days is not working

is it just my problem or is it not working for you too?

This contrib isn't updated anymore when I am right. You can use the Applestrudel one. This works fine. it's a fork from the cakebaked. BACKUP your flows, delete your flows, deinstall cakebaked, reboot, install Applestrudel, Import your flows

[saviothecnic]

Thanks I didn't know about the new fork I switched to Applestrude but I still have it the same problem ie it works to feel but it doesn't work for me to talk about alexa

[andesse]

Thanks I didn't know about the new fork

I switched to Applestrude but I still have it

the same problem ie it works to feel

but it doesn't work for me to talk about alexa

can you describe your problem a little bit more detailed?

[andesse]

In addition to Auto-Init with the cookie file I am running the Initialize node every hour because I also had issues in the past.

I let Alexa tell me the time on every full hour during the day and it maybe didn't work once in the last 2 months.

@bbindreiter Hey, I just figured recently out that I only have problems when 2 Alexa Nodes are running simultaneously. Since I am using the Node Alexa Routine, in the settings "Node" with the setting "serial" and add any Number of requests inside, I have no problems at all. Changed some flows using this rule and everything works perfect. Also I asked Amazon, it's ok to run several Accounts just for using Alexa. Some rooms also have a different Account. I just initialize after Node-Red reboot.

[Chris380]

Some minutes ago I switched from node-red-contrib-alexa-remote-cakebaked to node-red-contrib-alexa-remote2-applestrudel with the ui migration (deleting and reimporting the flows). I can confirm that applestrudel works fine. Glad to see now that I can use Device Activity again. Danke @bbindreiter für Deinen Einsatz :-)

[saviothecnic]

can you describe your problem a little bit more detailed?

Example in this node I ask alexa the temepratura alexa hears the request but it doesn't tell me the temperature on the device I know that the request is heard because the answer that I also send on telegram I find it but I am not speaking from the paired echo device

[andesse]

can you describe your problem a little bit more detailed?

Example in this node I ask

alexa the temepratura alexa hears the request

but it doesn't tell me the temperature on the device

I know that the request is heard because the answer

that I also send on telegram I find it

but I am not speaking from the paired echo device

@saviothecnic try to use a delay node with 1 second before the routine speak node. did you debug what comes out of the first function node? does the format fit for the alexa node?

[saviothecnic]

I'm sorry I'm not very experienced can you give me an example on how to delay?

[saviothecnic]

I did this but it doesn't work

[bbindreiter]

Does it work when you trigger Routine Speak directly with some hardcoded text?

[saviothecnic]

I have never used this option you can post me an example so I try

[bbindreiter]

Add Inject Node and connect it to another Routine Speak node in which you've set some static text for Alexa to speak (Hello or something). If it works it's your flow, if not some Alexa/Node-Red config ain't working.