bmd-videohub sources/destinations not getting recognized

[dominik-ruoff]

I'm having an issue where on two different Videohub 40x40 not all inputs/outputs are recognized (notification at the top says "device active with 7 sources and 12 destinations).
Ist there a known issue about illegal characters or something like that? The module log doesn't say anything about it at all.

[geoffhouse]

How odd. Is the device on a different network (ie with high latency to the BUG service)?

[dominik-ruoff]

Pretty odd indeed.
No, the server is in the same layer2 net and a second Videohub (same net, same switch one IP ahead) (edit:) sometimes initializes correctly with 40 sources and 40 destinations.

That's the faulty one - at this time (videohub restart and bug panel restart):

Also quite irritating, that destinations 13-20 are just skipped.
I can't see anything that might cause this in the labels:

After restart of the panel again, I'm left again with 7 sources and 12 destinations.

[dominik-ruoff]

I don't know, if that helps, but in the logfiles I found a message on the restart event:

npm error path /home/node/module
npm error command failed
npm error signal SIGTERM
npm error command sh -c node ./api/server
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-23T18_14_28_853Z-debug-0.log

so I looked up the debug logfile:

0 verbose cli /usr/local/bin/node /usr/local/bin/npm
1 info using npm@10.9.4
2 info using node@v22.22.1
3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc
4 silly config load:file:/home/node/module/.npmrc
5 silly config load:file:/root/.npmrc
6 silly config load:file:/usr/local/etc/npmrc
7 verbose title npm run production
8 verbose argv "run" "production"
9 verbose logfile logs-max:10 dir:/root/.npm/_logs/2026-03-23T18_14_28_853Z-
10 verbose logfile /root/.npm/_logs/2026-03-23T18_14_28_853Z-debug-0.log
11 silly logfile done cleaning log files
12 verbose stack Error: command failed
12 verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22)
12 verbose stack at spawnWithShell (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10)
12 verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12)
12 verbose stack at runScriptPkg (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:79:13)
12 verbose stack at runScript (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12)
12 verbose stack at #run (/usr/local/lib/node_modules/npm/lib/commands/run-script.js:131:13)
12 verbose stack at async RunScript.exec (/usr/local/lib/node_modules/npm/lib/commands/run-script.js:40:7)
12 verbose stack at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:207:9)
12 verbose stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli/entry.js:74:5)
13 error path /home/node/module
14 error command failed
15 error signal SIGTERM
16 error command sh -c node ./api/server
17 verbose cwd /home/node/module
18 verbose os Linux 6.8.0-60-generic
19 verbose node v22.22.1
20 verbose npm v10.9.4
21 verbose exit 1
22 verbose code 1
23 error A complete log of this run can be found in: /root/.npm/_logs/2026-03-23T18_14_28_853Z-debug-0.log

[geoffhouse]

Thanks dominik. I think those logs are just the panel restarting - nothing to do with this error, sadly.
The only last thing to check is the panel config - have you accidentally excluded any of the sources/destinations?