Seeking Beta testers (Victron users especially) for Bluetooth sensor capable plugin for SignalK

[naugehyde]

Hi all. I'm looking for Beta testers for a substantially revised version of my bt-sensor-plugin-sk plugin. The latest revisions are here: https://github.com/naugehyde/bt-sensors-plugin-sk/tree/1.1.0 (Docs are NOT up to date as of this writing)

I'm looking for mariners with Victron equipment as well as Inkbird and Xiaomi sensors on their boats. If your boat has a Bluetooth-enabled sensor not currently supported by the plugin that you'd like integrated into the SK data model, just let me know and I'll do my best to code it for you.

Thanks.

Andrew Gerngross aka naugehyde

[Peter-Petrik]

In case of Victron devices, how does this plugin differ from https://github.com/stefanor/signalk-victron-ble?

[naugehyde]

The plug-in is a native nodejs app not a wrapper around a python process like the signalk-victron-ble. The plugin supports a wide variety of Bluetooth devices and is modular-- you can program your own sensor class and add support for previously unsupported devices. FWIW, several of the data constants were translated from the victron-ble python code into node-js. I also used the victron-ble python parse code as a partial guide for how to implement my own. Some credit is due to the creator of victron-ble (https://github.com/keshavdv).

…

On Mon, Oct 14, 2024, 12:37 PM Peter Petrik ***@***.***> wrote: In case of Victron devices, how does this plugin differ from https://github.com/stefanor/signalk-victron-ble? — Reply to this email directly, view it on GitHub <#140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRGJPCQRFECBMXMFP7DZ3QMPFAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJUGA2TOMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sberl]

I would like to give it a try if you need more testers.

[naugehyde]

Hi Steve. Plenty of untested Victron devices remaining to be tested. The more input the better.

1. What kind of BT sensors do you have on board?
2. Does your boat have any kind of remote internet access? (So I can ssh in and debug remotely)

Thanks!

[sberl]

We have a single BMV-712 and no Internet access.
Running signalk on a Raspberry PI.

[naugehyde]

With the latest firmware and encryption key in the config, you should be able to use the app and it should return good numbers. Latest beta is in the app store. Feel free to install and test.

…

On Thu, Nov 7, 2024, 2:44 PM Steve Berl ***@***.***> wrote: We have a single BMV-712 and no Internet access. Running signalk on a Raspberry PI. — Reply to this email directly, view it on GitHub <#140 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRGLHG3ORQHWDCWH4KLZ7PUOJAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJYGMYDKMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[superstar76]

Could you configure for Ruuvi tags? Ruuvi's communicate with Victron Cerbos and Signal K can be installed on the Cerbo. Would be nice if the Ruuvi data could easliy be migrated to the N2k network.

[naugehyde]

Yes, the plugin currently supports Ruuvi Tags.

…

On Sat, Apr 12, 2025 at 12:57 AM superstar76 ***@***.***> wrote: Could you configure for Ruuvi tags? Ruuvi's communicate with Victron Cerbos and Signal K can be installed on the Cerbo. Would be nice if the Ruuvi data could easliy be migrated to the N2k network. — Reply to this email directly, view it on GitHub <#140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRFVX77CIUEZ2NLWK3T2ZDBMXAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBRGA4TKNI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[superstar76]

Does it publish to N2K, or is the SK NMEA Plugin required?

[naugehyde]

No, the plug-in publishes SK paths that the end user configures. To publish an SK path onto the NMEA bus you need to use a plug-in like the SK to NMEA plug-in. If a path you create in the Bluetooth plug-in is supported by the NMEA plug-in (e.g. environment. outside.temperature) you should see the sensor data from your Bluetooth device on your NMEA display devices.

…

On Sat, Apr 12, 2025, 9:25 AM superstar76 ***@***.***> wrote: Does it publish to N2K, or is the SK NMEA Plugin required? — Reply to this email directly, view it on GitHub <#140 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRHFQGYDXG7BIW4YHRL2ZE46JAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBRGQ2TONA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bradharley]

This looks like a great project. Thank you. I have aboard:
Victron BMV 712. Several victron MPPT's. Cerbo (running on pi). A few ruuvi's. What would you like me to test?
I also have the overkill/JBD batteries, and configured those. The data as read is incorrect and it seems to be mapping cell voltage values into other fields. Screenshot attached. Let me know how I can help. Happy to provide remote access.

[bradharley]

Actually, disregard the jbd question. I disabled/re-enabled gatt and restarted and it's reading as it should.

Let me know what you want tested with other devices...

[bradharley]

I am continuing to test the plugin primarily with 3 JBD BMS'. I have three, and here is what I am seeing...
I can configure one battery using GATT and it seems to be ok. I configure a second battery, and sometimes it works with the signalk plugin config UI, but normally not. The data fields don't populate and the connection to the controller is erratic. IF I manually generate the .json file for the plugin it has sporatically worked with two controllers. It doesn't work at all with 3 controllers.
How would you like feedback and how would you like me to troubleshoot?
Bluetooth works in other ways, with the ruuvi plugin (disabled for this testing), bluetooth devices etc. Here is my latest config file.
[
bt-sensors-plugin-sk.json
](url)

[naugehyde]

Hmm. Very hard to say what the issue is. I don't have access to a JBDBMS myself. I remotely developed the sensor class through a VPN connection to a user who had JBD aboard. Your problem with 3 sensors could be coming from any number of issues.

1. Open an issue at https://github.com/naugehyde/bt-sensors-plugin-sk/issues

2. DM me on Discord (naugehyde in SK community) instructions to get remote access in to your system.

[KenAlbert47]

Thanks naugehyde,

I tried the BT Sensors plugin. Install was easy.
Config:
Raspberry Pi 5 running Signalk 2.13.5
I have been using Victron Instant Data over BLE for a while now and decided to give this new one a try.
After install I can see my Victron SmartSolar MPTT 100|30 and the one in the boat next to me...

I then mapped the Victron fields to Signalk paths and used the same encryption key as before.
I restarted Signalk and the fields came straight up in the UI.
But the values are not correct,

I'll do some digging but thought I'd drop a note here.
Cheers,
Ken

[KenAlbert47]

This is what is in the log

Apr 29 14:42:39 signalk-to-influxdb:Error: A 400 Bad Request error occurred: {"error":"partial write: unable to parse 'electrical.solar.Solitaire.chargingModeNum,context=vessels.urn:mrn:imo:mmsi:47474747,source=bt-sensors-plugin-sk jsonValue=undefined 1745901759898000000': invalid boolean dropped=0"}
Apr 29 14:42:39 Error: A 400 Bad Request error occurred: {"error":"partial write: unable to parse 'electrical.solar.Solitaire.chargingModeNum,context=vessels.urn:mrn:imo:mmsi:47474747,source=bt-sensors-plugin-sk jsonValue=undefined 1745901759898000000': invalid boolean dropped=0"} at IncomingMessage.<anonymous> (/home/home/.signalk/node_modules/signalk-to-influxdb/node_modules/influx/lib/src/pool.js:50:38) at IncomingMessage.emit (node:events:530:35) at endReadableNT (node:internal/streams/readable:1698:12) at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Apr 29 14:42:40 Delta is missing value in {"path":"electrical.solar.Solitaire.chargingModeNum"} from source "bt-sensors-plugin-sk"
Apr 29 14:42:41 Delta is missing value in {"path":"electrical.solar.Solitaire.chargingModeNum"} from source "bt-sensors-plugin-sk" 

[naugehyde]

Hi Ken, Thanks for the report. Can you double check the encryption key? If the key is the right length but not the exact right value you'll get bizarre data back like you received. Unfortunately, Victron doesn't supply any integrity checks on the decrypt. The error you're getting is a result of invalid data that the influxdb (different plugin) is rejecting. Guessing the encryption key in the config is not correct. Double check it and let me know how it goes. Best, Andy PS There's a new beta out there if you want to give it a try after we've solved the data issue. Install it by running npm i ***@***.*** from your signalk home (usually ~/.signalk).

…

On Mon, Apr 28, 2025 at 9:39 PM KenAlbert47 ***@***.***> wrote: Thanks naugehyde, I tried the BT Sensors plugin. Install was easy. Config: Raspberry Pi 5 running Signalk 2.13.5 I have been using Victron Instant Data over BLE for a while now and decided to give this new one a try. After install I can see my Victron SmartSolar MPTT 100|30 and the one in the boat next to me... Sensors.png (view on web) <https://github.com/user-attachments/assets/1c054e8e-ec88-4bb3-8ba5-3eb90384a4a1> I then mapped the Victron fields to Signalk paths and used the same encryption key as before. I restarted Signalk and the fields came straight up in the UI. But the values are not correct, SolitaireValues.png (view on web) <https://github.com/user-attachments/assets/83600a1c-31d4-411e-b356-f2d30c191c54> I'll do some digging but thought I'd drop a note here. Cheers, Ken — Reply to this email directly, view it on GitHub <#140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIREX2TV7UVSJ3FXYTWT23367TAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJXGY2TMMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[KenAlbert47]

Thanks Andy!
Yes your were correct - characters missing from my copy and paste of the encryption keys.

BTW I had a lot of trouble with the Victron Instant Data over BLE when running on a Raspberry Pi 3B. Turned out to be lack of flow control on the Pi 3B - I played with data rate and made it sort of better but it would fail every now and again and would need to restart the Pi. The Pi 5 has been flawless with the Victron Instant Data over BLE plugin. Happy to give this a try and report back.

Cheers,
Ken

[naugehyde]

Thanks for the update. There have been lots of problems with BLE on the pi. But BT on RPI is pretty stable these days. Poor RX signal strength was a big one on the 4b. Has it improved on the RPi 5?

…

On Mon, Apr 28, 2025 at 10:35 PM KenAlbert47 ***@***.***> wrote: Thanks Andy! Yes your were correct - characters missing from my copy and paste of the encryption keys. image.png (view on web) <https://github.com/user-attachments/assets/675ca854-2d46-4a80-a978-c3b93f511949> BTW I had a lot of trouble with the Victron Instant Data over BLE when running on a Raspberry Pi 3B. Turned out to be lack of flow control on the Pi 3B - I played with data rate and made it sort of better but it would fail every now and again and would need to restart the Pi. The Pi 5 has been flawless with the Victron Instant Data over BLE plugin. Happy to give this a try and report back. Cheers, Ken — Reply to this email directly, view it on GitHub <#140 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRGPAY6EY4KWGNIVQX3234FS7AVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJXGY4DEOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[KenAlbert47]

I've never had a pi 4 on the boat so I cannot compare. So far the pi 5 has been awesome. I've added another Victron MPTT 100|30 to the plugin that is my mates boat next to me in the marina - working perfectly.

[KenAlbert47]

I've installed 1.2.0-beta.0.0.10....
Cheers,
Ken

[KenAlbert47]

A very small thing I have noticed is that the Victron Instant Data over BLE returned a chargingMode field as lower case - possible modes were off, float, absorption and bulk. This plugin returns the fields as UpperCase OFF, FLOAT, ABSORPTION and BULK. I was using node-red to convert each of these states to a number so I could plot them in grafana to show the state changes on the same graph as the other parameters. Quick 1 minute change to fix it. :-)

[naugehyde]

Hmm. That's a tough one. Other users might be dependent on the case in their node-red flows (Operation Mode as Victron calls it is used by other device types as well). Can't change it now without the potential for breaking someone else's downstream code. In javascript, "OFF" != "off" but users like you can normalize and prettify case easily (toLowerCase()) FWIW, here's the full list of OperationModes: ``OperationMode: new Map([ [0, 'OFF'], [1, 'LOW_POWER'], [2, 'FAULT'], [3, 'BULK'], [4, 'ABSORPTION'], [5, 'FLOAT'], [6, 'STORAGE'], [7, 'EQUALIZE_MANUAL'], [9, 'INVERTING'], [11, 'POWER_SUPPLY'], [245, 'STARTING_UP'], [246, 'REPEATED_ABSORPTION'], [247, 'RECONDITION'], [248, 'BATTERY_SAFE'], [252, 'EXTERNAL_CONTROL'] ])`` Also, feel free to include the Victron Constants in your node-red flows. The file is located in the plugin directory at Victron/VictronConstants.js I'm not certain how best for a node-red flow to ascertain SignalK's plugin directory but I suspect there's a reliable mechanism. Check the node-red plugin docs.

…

On Mon, Apr 28, 2025 at 11:37 PM KenAlbert47 ***@***.***> wrote: A very small thing I have noticed is that the Victron Instant Data over BLE returned a chargingMode field as lower case - possible modes were off, float, absorption and bulk. This plugin returns the fields as UpperCase OFF, FLOAT, ABSORPTION and BULK. I was using node-red to convert each of these states to a number so I could plot them in grafana to show the state changes on the same graph as the other parameters. Quick 1 minute change to fix it. :-) — Reply to this email directly, view it on GitHub <#140 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALTAIRHWOOOYRQITYZLACEL234M4LAVCNFSM6AAAAABO7UO4LSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJXG4ZDIMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>