Node-red-pushsafer 1.0.4 Crash

General
1

Hi, I have been using node-red-pushsafer 1.0.4 for several years from Node-Red within Home Assistant without problem, with messages going to both my Android phone and my Windows 10 PC.

Yesterday I added a guest account to Pushsafer to also receive my messages on her iPhone.

This seems to have resulted in node-red-pushsafer 1.0.4 crashing Node-Red with the following log message:

6 Oct 08:08:03 - [info] Node-RED version: v4.0.9
6 Oct 08:08:03 - [info] Node.js  version: v22.16.0
6 Oct 08:08:03 - [info] Linux 6.12.34-haos-raspi arm64 LE
6 Oct 08:08:03 - [info] Loading palette nodes
6 Oct 08:08:04 - [info] Node-RED Contrib Theme Collection version: v4.1.0
6 Oct 08:08:08 - [info] Dashboard version 3.6.6 started at /endpoint/ui
6 Oct 08:08:10 - [info] node-red-contrib-home-assistant-websocket v0.77.2 nodes initialized
6 Oct 08:08:11 - [info] Settings file  : /etc/node-red/config.js
6 Oct 08:08:11 - [info] Context store  : 'default' [module=memory]
6 Oct 08:08:11 - [info] User directory : /config/
6 Oct 08:08:11 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Oct 08:08:11 - [info] Flows file     : /config/flows.json
6 Oct 08:08:11 - [info] Server now running at http://127.0.0.1:46836/
6 Oct 08:08:11 - [info] Starting flows
[08:08:11] INFO: Starting NGinx...
6 Oct 08:08:12 - [info] Started flows
6 Oct 08:08:12 - [info] [server:Home Assistant] Connecting to http://supervisor/core
6 Oct 08:08:12 - [info] [mqtt-broker:4e6a8af2.56ed74] Connected to broker: mqtt://192.168.0.216:1883
6 Oct 08:08:12 - [info] [mqtt-broker:Archview MQTT Broker] Connected to broker: HomeAssistant@mqtt://192.168.0.216:1883
6 Oct 08:08:12 - [info] [server:Home Assistant] Connected to http://supervisor/core
Cannot parse error: {"reason":"BadDeviceToken"}{"status":1,"success":"message transmitted","available":39849,"message_ids":"62416432:59380,62416434:97455"}
6 Oct 08:08:14 - [red] Uncaught Exception:
**6 Oct 08:08:14 - [error] SyntaxError: Unexpected non-whitespace character after JSON at position 27 (line 1 column 28)**
    at JSON.parse (<anonymous>)
    at /config/node_modules/node-red-pushsafer/pushsafer/pushsafer.js:155:45
    at IncomingMessage.<anonymous> (/config/node_modules/pushsafer-notifications/lib/pushsafer.js:78:6)
    at IncomingMessage.emit (node:events:530:35)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at processTicksAndRejections (node:internal/process/task_queues:90:21)
[08:08:14] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[08:08:14] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping

Does anyone know who if anyone I report this bug to? Thanks

2

I had many issues with pushsafer from Home Assistant. I moved to Pushbullet which works like a charm. I don't even need a Node-red node for it on Home Assistant, just sending a simple HTML request with the device notification.