Alexa-remote2 not supplying all requests reliably and other issues with it

[E1cid]

1 Tplink vr400 router

wired - all pc, android boxes(1 running node-red and openluup on debian VM), veraplus (z-wave and zigbee)

wifi 3 dots, 4 phones and 2tabs 1 tv(all others use android boxes, printer.

2 wifi access points ( one ethernet and one wifi bridged) with all other smart devices about 20

I do not run 5g wifi as do not feel the need for it.

[cymplecy]

Well (touch wood) its been totally reliable for the past few days

And I MAY have found a reason!

One of my Pi occasionally drops off my network and needs rebooting but recently this has become more and more frequent and a few days ago - I unplugged it and brought it back to computer room to investigate it a bit closer.

I haven't got round to doing it - but ever since I removed it from the network - I've had no problems with the remote2 node

So, COULD be a big co-incidence but I won't know until I get the dodgy PiZero setup on its own monitor (need to find a mini-HDMI adaptor)

[kenkoknz]

Just a thought, some routers is defaulted to handle 32 wireless devices (setable to more), so may be worth a check. I came across that as sometimes some devices drop for no reasons.

[cymplecy]

Googling suggests mine can do 64 - but theory and practice can of course not match in reality

[kenkoknz]

You be surprise how quickly devices addup or the extra phones or tablets, especially when your daughter's friends visiting n join your network!

[cymplecy]

Yep - eldest move back in on Friday - that's 2 iphones, 1 apple watch and 1 laptop (and another one streaming Netflix!)

[cymplecy]

Current status
All requests being received from into Node-RED reliably since last post.

The not speaking issue

Alexa-remote2 not supplying all requests reliably and other issues with it

And tonight's continuning saga is that Alexa has stopped speaking when I send custom commands to the Alexa Routine node [image] Not changed anything (honest) and all working last night when I used it for my door locking stuff - tonight neither my main LivingRoom Dot nor my working android phone will speak Object looks fine (same as yesterday) - node reports sucess - just no sound comes out at all I'm not very lucky with this set of nodes.....

continues.

It repeatably happens after I stop/restart Node-RED (say after updating a contrib node)

Then - no speak requests come out of my dots (no errors show up - debugging looks fine - just no speech is read out)

However, if I then stop/restart Node-RED again - it starts working again

[ghayne]

Hi Simon, I had this yesterday after restarting node red. I tried opening the Alexa account node and pressing "update" and it worked again! Not a very stable node regarding restarts!

[cymplecy]

@ghayne

I tried opening the Alexa account node and pressing "update" and it worked again!

Hallejluhah that its not just me

I'll try that out next time it hiccups as it would be muich less disruptive than stopping/restarting Node-Red again

[cymplecy]

It stopped speaking again today and I did your technique of opening up account info and pressing update then deploy and it started speaking again

So at least I avoid restarting Node-RED

[kenkoknz]

My node not speaking sometimes also, all I did was just to redeploy nr and it works again, hope a new release will fix reliability problem.
On this note, for short term fix, is there a node I can use to redeploy nr with a flow? Then I can redeploy nr at regular intervals depending on reliability.