Is everyone (with a Pushover account) else getting this error from node-red-node-pushover?

General
1

I have tested the Pushover Website and recreted a new node for node-red-node-pushover but keep getting (debug from pushover node):


name: "AggregateError"
message: "AggregateError"
code: "ETIMEDOUT"
stack: string
AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1122:18)
    at internalConnectMultiple (node:net:1190:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1716:5)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7)

Am I doing something wrong or have Pushover changed their API 10 days ago? Searched the forum. Maybe it is just me.

2

Are you saying that you are creating a new contrib node that does the same/similar thing as node-red-node-pushover? Or that you are creating a new flow that uses node-red-node-pushover but it doesn't work?

I use node-red-node-pushover, and it's still working ok.

3

No just using the standard palette and dropping a new node. From the lack of posts in the forum about this it seemed just like me. I wonder why mine has stopped working. I send all my IoT over Wireguard to China (HK) but it doesn’t fit temporally when this stopped working. Besides my laptop on the Home VLAN is tunnelled to Russia and works.

4

Have realised it isn’t just Node Red. I have some direct Home Assistant scenes that go to pushover that have stopped working even though the devices themselves can access the internet. Must be something to with tunnelling to China (HK). Maybe China have a thing against pushover. Wrote to Pushover asking for address and port so I can bypass the VPN with a Policy Based Routing rule but no reply. Guessing it is api.pushover.net and port 443. Does that sound reasonable?