Devices build on linux

[michaelgneff-lgtm]

I'm currently trying to get the app to build on linux. I made a change to webble to just accept my exercise bike name, and that works just fine. However, no changes to any of the .ts files in the devices files seem to show up in the running code. I run the build command and can confirm that test strings show up when I grep the appimage. However, they don't appear in the log dump. I tried changing 'BLE-FM' to another string, and it always just dumps as BLE-FM. Apparently, it is ignoring whatever I link in and loading from the web.

I'm not really familiar with this development environment, I mostly did compiled c/c++ code. Can anyone help me get a local clone of devices to work within the app?

[gdoumen]

The desktop app and the web bundle are distributed seperately.

The desktop app is basically just a Chromium browser with some additional logic ( to enable functionality a normal web page would not have - exposed via IPC)

The web bundle is the one that has the UI (web-ui repo) and busines logic (services repo - which imports devices repo)
At the start of the app, the app check if there is a "pageUrl" configured in the settings.json,

• if it is: it will load the web bundle from there ( I use this for local debugging)
• if not: it will try to download/unzip the web.bundle from my server, but if this fails will use the locally cached version

So if you want to test your local changes you will have to checkout web-ui, services and devices repo. Your folder structure should have all in the same main folder

/
/services
/devices
/web-ui

run npm run dev in both the devices and services folder (which will re-build the libs on every code change)
then run npm run dev in web-ui. This will run the web bundle in localhost:3000 and will hot-reload on any changes in the web-ui or if any of the libs are changing

now add "pageUrl": "http://localhost:3000", to your settings.json and launch the app. It now should show your changes.

One note: In the latest commit to the webble code, I also have included a "auto-approve" for "good" devices (i.e. Smart Trainers, Power-Meters, Cadence Sensors,...) and an "auto-reject" for devices that don't have to correct BLE services ( e.g. speakers, TVs, ....), supported by a local device cache on app level. Maybe this would already address

You also need to understand that I'm slightly mis-using WebBLE. In the spec of Web-BLE, the user has to accept a BLE device in the "DeviceList", which is a component that the Browser has to provide. WebBLE will only allow communication to approved devices. The approval request is signalled by the Web-BLE stack via messages. I'm hiding this "DeviceList" and silently approve(or reject) the device in the background. The devices-lib will ony see "approved" devices (via peripheral announcement).

[michaelgneff-lgtm]

Thank you for such a thorough response!
I just enjoyed a nice workout this morning running on linux & bluetooth with Incyclist.

I'll try the latest build without my hack.

The only other hack I was trying is that my Schwinn 130 quits broadcasting if I 'coast' and the app panics on health check and disconnects, so I was going to always return 'ok' in the health check.