I have an issue with connections to NoteHub - relatively recently, in the last few days.
Running on RaspPi 4 running Debian 12 (bookworm). Running node-red v4.0.3, node v 20.18.0 - so pretty recent base layer. Prior to this it was probably running on older version of Debian and ran for months, interfacing to Notecard and updating NoteHub.
Node-red is running node-red-contrib-notcard 1.1.0 which I use to communicate with the card, sending req etc, pushing data to the card, synchin to Notehub.
I think the only element that changed is upgrade to the Bookworm layer.
I can successfully connect to the hub today, once, maybe twice in succession :
Notehub event : https://notehub.io/project/app:5f19fe61-0ed4-4465-9c41-2dee4c0d75de/event/a628b860-c188-85b7-9f2f-b621d8b9507a/info
then I get the following error:
nodered1 | 8 Oct 12:13:17 - [red] Uncaught Exception:
nodered1 | 8 Oct 12:13:17 - [error] Error: Timeout waiting for response bytes
nodered1 | at Timeout._onTimeout (/data/node_modules/node-red-contrib-notecard/notecard/i2c-connector.js:164:36)
nodered1 | at listOnTimeout (node:internal/timers:581:17)
nodered1 | at processTimers (node:internal/timers:519:7)
I’ve replaced and re-inserted the node in case it was corrupted, no improvement. I was running in docker, I moved to simple standalone, some issue. I’ve confirmed no errors on I2c in raspPi logs.
I;ve upgraded the card firmware
{“req”:“card.version”}
{
“version”: “notecard-6.2.5.16868”,
“device”: “dev:867648043579539”,
“name”: “Blues Wireless Notecard”,
“sku”: “NOTE-WBEX-500”,
“board”: “1.11”,
“cell”: true,
“gps”: true,
“api”: 6,
“body”: {
“org”: “Blues Wireless”,
“product”: “Notecard”,
“target”: “r5”,
“version”: “notecard-6.2.5”,
“ver_major”: 6,
“ver_minor”: 2,
“ver_patch”: 5,
“ver_build”: 16868,
“built”: “Aug 19 2024 17:18:38”
}
}
Any other troubleshoothing avenues I’m missing?
thanks