Raspberry Pi Zero compatibility

[DamienVT]

Hi,

I received new hardware for my integration.
A Raspberry Pi Zero W.
I try to launch the installation but I had an issue with NodeJS installation.
Here is the error message:

## Installing the NodeSource Node.js 14.x repo...
## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js 4 and later.

I try to finish installation manually...

I follow this to install de good version of NodeJs:
https://hassancorrigan.com/blog/install-nodejs-on-a-raspberry-pi-zero/

In file install.sh:
cp install/config.js config/ need sudo

Then after a complete installation, the application don't start.

I try to start manually, and have this issue:

pi@raspberrypi:/opt/openrowingmonitor $ sudo npm start

> [email protected] start /opt/openrowingmonitor
> node app/server.js

==== Open Rowing Monitor 0.7.1 ====

bluetooth profile: FTMS Rower
webserver running on port 80
(node:2149) UnhandledPromiseRejectionWarning: Error: ENODEV, No such device
    at Hci.init (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/hci-socket/hci.js:110:35)
    at BlenoBindings.init (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/hci-socket/bindings.js:97:13)
    at Bleno.<anonymous> (/opt/openrowingmonitor/node_modules/@abandonware/bleno/lib/bleno.js:49:22)
    at Bleno.emit (events.js:315:20)
    at _addListener (events.js:358:14)
    at Bleno.addListener (events.js:406:10)
    at createFtmsPeripheral (file:///opt/openrowingmonitor/app/ble/FtmsPeripheral.js:25:9)
    at createPeripheral (file:///opt/openrowingmonitor/app/ble/PeripheralManager.js:63:20)
    at createPeripheralManager (file:///opt/openrowingmonitor/app/ble/PeripheralManager.js:20:3)
    at file:///opt/openrowingmonitor/app/server.js:32:27
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2149) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2149) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
file:///opt/openrowingmonitor/app/ble/PeripheralManager.js:39
    peripheral.notifyData(type, metrics)
               ^

TypeError: Cannot read property 'notifyData' of undefined
    at EventEmitter.notifyMetrics (file:///opt/openrowingmonitor/app/ble/PeripheralManager.js:39:16)
    at EventEmitter.<anonymous> (file:///opt/openrowingmonitor/app/server.js:103:21)
    at EventEmitter.emit (events.js:315:20)
    at Timeout.emitMetrics [as _onTimeout] (file:///opt/openrowingmonitor/app/engine/RowingStatistics.js:42:15)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node app/server.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-05-02T16_04_14_961Z-debug.log
pi@raspberrypi:/opt/openrowingmonitor $ /opt/openrowingmonitor/node_modules/@abandonware/noble/lib/hci-socket/hci.js:120
    this._socket.bindRaw(this._deviceId);
                 ^

Error: ENODEV, No such device
    at Hci.init (/opt/openrowingmonitor/node_modules/@abandonware/noble/lib/hci-socket/hci.js:120:18)
    at NobleBindings.init (/opt/openrowingmonitor/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:93:13)
    at /opt/openrowingmonitor/node_modules/@abandonware/noble/lib/noble.js:61:24
    at processTicksAndRejections (internal/process/task_queues.js:75:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}

[laberning]

Seems like the official support for ARMv6 was stopped with Node.js 12. However the core team still automatically creates those unofficial builds form ARMv6 that may still work.

Thanks for the hint, I'll add a routine to install those automatically on ARMv6 devices, once we're sure that the rest of Open Rowing Monitor supports Raspberry Pi Zero W. I assume it could work, but we'll have to see how performant a Node.js application will run on this single core device.

The permission issue in the install script should now be fixed, thanks for reporting.

That error when launching Open Rowing Monitor looks like it has some problem to communicate with the Bluetooth Module of the device.
Did you run the bluetooth reconfiguration part of the install script? It's basically these commands:

sudo systemctl disable bluetooth
sudo apt-get -y install bluetooth bluez libbluetooth-dev libudev-dev git

[DamienVT]

Hi again Lars,
Too quick answer...
I have error on GPIO binding:

fs.js:711
  handleErrorFromBinding(ctx);
  ^

Error: EBUSY: resource busy or locked, write
    at Object.writeSync (fs.js:711:3)
    at Object.writeFileSync (fs.js:1473:26)
    at exportGpio (/opt/openrowingmonitor/node_modules/onoff/onoff.js:18:8)
    at new Gpio (/opt/openrowingmonitor/node_modules/onoff/onoff.js:172:36)
    at createGpioTimerService (file:///opt/openrowingmonitor/app/gpio/GpioTimerService.js:31:20)
    at file:///opt/openrowingmonitor/app/gpio/GpioTimerService.js:51:1
    at <anonymous> (<anonymous>) {
  errno: -16,
  syscall: 'write',
  code: 'EBUSY'
}

[DamienVT]

Hi again Lars,
It's my mistake... ^^
I wrote like you put in the discussion:
gpioPin: 16
Instead of
gpioPin: 16,

I have to learn more about java langage :)

[laberning]

Cool that it works 🎉
Those Waveshare screens look pretty nice. From your link I'm not 100% sure what resolution it does (the wiki states 800×480, but https://www.waveshare.com/3.5inch-RPi-LCD-B.htm lists it as 480x320).
I guess it is 480x320, but 800x480 would give a pretty sweet ppi on that size...

The Open Rowing Monitor UI is quite responsive to different resolutions, but there was a small aspect ratio where those buttons would not fit into two rows... Should be fixed now with the latest version.

I think I'll add a special kiosk mode with one of the next changes that will get rid of the fullscreen button in favour of something that would make more sense in a kiosk environment.

There is already a standalone mode that gets automatically enabled when you add Open Rowing Monitor to the home screen on a mobile device (http://localhost/#:standalone:).

For kiosk mode we can maybe add a button to trigger a shutdown of the system...

To update you can use the script sudo /opt/openrowingmonitor/install/update.sh

[DamienVT]

Hi Lars,
As I read, the hardware resolution is 800x480, but in configuration, it is set to 480x320 except for Retropie that it is set to 640x480... I don't know why.
I did some modification on the html to have all information more readable on my small screen.
I use the standalone option to have the stop button, and I try to add the shutdown system with the help of ShellJS, but I did not success...
I read the code for automatic adaptation of the kDamp, but I think that an update of the distance per revolution is missing.

[laberning]

You are right - re-evaluation for the distance was missing when doing the automatic adaption. The latest version fixes that.

To trigger a shutdown you could probably just exec something like halt (see here for an example on how to exec a child process).

I'll add some functionality like that in future, but it will take some time as I want it to have at least a confirmation dialog (so one does not shut down the rower by mistake) and also some feedback once the shutdown was successful. So that will happen after reworking the UI from the current prototype into a proper Web Application...