Events not firing again 12Oct #152
Comments
|
Can confirm my events are becoming spotty again |
|
Same here again :-( |
|
Same here |
|
+1 |
|
Same here, sorry. |
|
Same here in UK |
|
same here - Thailand |
|
hey all, already tested That worked for me greeting |
|
That didn't work for me
Are you sure you are able to listen to events?
…On Sat, 14 Oct 2023 at 08:52, Matten-Matten ***@***.***> wrote:
hey all,
already tested "reset" -> "Fresh Authentication" -> Proxy login via "open
... in your Browser"?
That worked for me
gruß
matten matten
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR7RNC2AWMJTIAP4CZB7BDX7JADNANCNFSM6AAAAAA56DZ3JY>
.
You are receiving this because you authored the thread.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/152/1762705209
@github.com>
|
|
Reset / Fresh Auth wont work here as well (Germany) |
|
Not work for me (Italy) |
|
sorry, I got confused. Alexa states arrive, but no device activity |
|
Same here- UK. |
|
Same here in Brazil |
|
same here Spain |
|
Same here in Catalonia |
|
+1 Germany |
|
will this be left like this??? won't events ever work again? |
|
I will probably remove the event node. People are building their home automation based on it and then we have issues like this one, where all weight is on one man's shoulders |
|
I hope you don't do that, it's really useful. If it fails every now and then it's ok, it's way worse to remove it.... |
|
TBH with you the event node was quite a mess when cakebaked was the owner. It would fail every other month and it was still valuable to have it. Ever since you took it over it's been almost rock solid, like night and day different. I really hope you can find the heart to keep on with this and keep the event node alive. I'm really thankful for everything you've done during this last couple of years. Kind regards |
|
It's all @Apollon77, I'm just integrating his lib but thank you very much. I would happily keep this event node but some users rely on it apparently. I just want to avoid a situation where someone locks themselves out or something. |
|
I have some ideas to at least workaround a bit. Will potentially not that perfect as before. We will see. Needs some days ... not at home currently that often so no Alexa test devices with me. |
Please dont remove this functionality! True - some people use this to build their smart home on it (like me) but it is currently the only way how i can use voice control to my smarthome. if you remove it, i dont have any possibility to use voice control... so better havent it some times than havent it any time :-) Is there anything we can do to support you please let us now. And no worrys if fixing issues can not be done just in time - i think, no one of us here will expect this. Unfortunatly i am not an js coder, but if i can assist with testing or anything else let me know. Stay motivated - we count on you 2 (@bbindreiter and @Apollon77 ) Ans many many thanks for your tireless effort Martin (Berlin) |
|
I can only agree, it would be a real pity if this functionality would no longer exist. |
|
Is there a document or some blog post or other resources that explain what changes in the behaviour of the alexa system that brakes the alexa-remote functionality? And since it's (correct me if I'm wrong) a "virtual" echo device, how those kind of devices still work after these changes occour? |
|
First of all, thank you to those who contribute to the project! |
|
@gattokotatsu Because these are all inofficial "Alexa App and internal API" related topics ... indeed no there is nothing oficially available :-) In fact they do not send a push information anymore they were sending before. any the functionality relied in this information. So we now need to find things around this. |
|
I too am eagerly watching and hoping for this to be fixed. thanks so much for your work so far. I don't even need to know the words that are spoken, but other than that Alexa doesn't do anything. At the moment i just listen for what Alexa asks to decode and send that into node red along with the name of that Alexa from there i trigger nod red commands but i send it to the room name of said Alexa command so bedroom tv for example. I assume many of you are doing the same, but i was thinking since we all coming her for same answer someone, or one of the amazing dev's fixing this, my have or come up with a solution so if we can't listen to the words said anymore in order to get the name of the device sending the command, is there a way to do a different action and grab the name? If i set Alexa to toggle on and off an Alexa routine/dummy light/switch does anyone know of any way to find out what device did the action? |
Hi Apollon77 can you remind us all, how we can access the Thanks |
I understand you, but I can't pin it down to any specific activity that I can control. For example, I got some "too many" errors recorded at 3:32am this morning. Nothing scheduled happens at that time, I don't have any regular polling automations or flows or anything like that. It has gone through periods of chucking these errors out for a long time (at random times) but not seen it for some months before now. I only have one event node so I can save anything said or heard, so it can be repeated if I ask for it. I have restored back to 5.0.46 (mostly out of curiosity) and it is, apparently, still working. |
|
I'm in the UK and still on 5.0.48 and still seems to be working ok. |
Please can someone (@Apollon77 / @bbindreiter / anyone else) let us know how to access the logs? I keep seeing this in Node-red and would like to understand why:
I suspect this is the reason for mine being intermittent. Thanks! |
|
To @Apollon77 or @bbindreiter I agree, as most of us would like to help if we knew how ? 👍 Just a polite request, thanks |
|
If there is nothing personal on your flows I would love to import your flows, as I think I could learn from them. The Thanks 😃 |
|
debug log |
|
The log shows (you can also have a look) ...
So the question is now why the library did not determine the volume/eq change for G0922H0725030MM4 as an activity. So please let the logging enabled that way and try some more such actions on this device so that I can see if the values change or not and such ... because if they change then I might need to adjust the logic on how to detect an activity |
|
Thanks Apollon77, I did wonder about this - The command issued was "Alexa, what's the living room temperature" I'll get some more logs uploaded |
|
@ziggycatuk |
Yes sometimes Amazazon devices seems to sync the current settings to the server and this is that ... so yes in this case we also might consider it as an activity and simply find nothing ... it is as it is t´with such "assumptions" |
I run NR in docker and use Portainer to manage containers. The logs are easily accessible in Portainer. |
Hi thanks for that will have a look as I run Node-RED in Docker as well. |
The NodeRED forum is a much better place to discuss flows than here :) |
|
Is anyone still having issues with events not firing, it plays up every single day for me. Three attempts # "Alexa, whats the living room temperature" Three attempts # "Alexa, what's the kitchen temperature" |
|
I only use device activity to save last things heard and said so I can say "pardon" and get them repeated, but it's working for me whenever I look... I'm in UK, and still on 5.0.46 |
Yep, mine is still disconnecting, waiting a minute then reconnecting: |
|
I still do not get the reason why it discoinnects for you that often ... for me it works "rock stable" .... |
|
For me, 90% of the time don't work (On Device Activity) node.. I do not receive anything (debug node empty). |
Any chance you can let me know how to get the debug logs? |
|
your issue is unrelated to this topic, look at your port mappings or open a new thread |
Same problem for me for 2 weeks. The events no longer trigger or very rarely... I am in France. |
|
@poupiote Your log looks like "You did not enabed the settings option to automatically get the activity data" that you need to enable since some versions |
|
This issue is stale because it has been open for 30 days with no activity. |
|
This issue was closed because it has been inactive for 14 days since being marked as stale. |
|
This is still an open issue |
and others
Several of us on the Node-RED forum have noticed that events are not being received
From my own logs - this started after 14:33 GMT
Stopping/starting NR doesn't make it work again :(
The text was updated successfully, but these errors were encountered: