Closed biddster closed 2 years ago
That's definitely not normal. Just checked my PI and I don't have this behavior. Have you used this node before and it's happening since the last update?
Thanks!
I'm a new user to this node. I was using the mattl0 fork for a few days before switching to your fork. I think it started when the latest alexa-remote package was pulled in, but I can't be sure. I started using mattl0 around the 11th of July.
I reported this on the mattl0 fork https://github.com/MattL0/node-red-contrib-alexa-remote2-mattl0/issues/3
This afternoon I removed all alexa nodes. I created a new alexa account and one by one added the alexa nodes I need back in. I added one node per half-hour so I could check the effect on the DNS lookups. The upshot is that it's fine.
I'll monitor over the next few days and close this.
I'm using the latest version 5.0.11 and I'm seeing a lot of DNS lookups to eu-api-alexa.amazon.co.uk. It's roughly about 4 per second. I noticed this as I use pihole and it was making so many calls that pihole eventually rate limited the client. Nothing is being blocked by pihole. Functionally, this node is brilliant and is just what I need.
I've enabled trace and this is what's happening in the debug log (over and over again):
It's my first time using this node so I'm not sure this is normal?
I've got events disabled in the account configuration as I thought that might be the issue but it's not.
Happy to help debug if this is a bug.