ilpork / vahti Goto Github PK

App.config can't be accessed because PCLAppConfig and link to App.config hasn't been added to iOS project. Because App.config can't be read, the app fails on start-up.

When Vahti.Server is configured to publish history data to Firebase database, the calculated measurements of a SensorDevice are not included in published history data. No graph is shown in mobile/web app respectively.

Expected behavior is that calculated measurements get history data in same way as "regular" measurement data gets.

A home screen widget would provide a quick overview of values selected sensors. I had a simple widget in first version of the app, but it wasn't configurable, so I removed it from the project. The target is now to make a widget, which can show values from three sensors, and those sensors can be selected in the app.

It also requires different approach in selecting the items to be shown in overview tab in app (now it's done on location details page. Options page could provide means to define visibility in both use cases (overview page and widget).

I've noticed with my Raspberry Pi 4 (using Raspbian Buster and BlueZ 5.50) that Vahti.Collector runs fine for a couple of days or so, but then starts to get random errors from D-Bus like org.freedesktop.DBus.Error.UnknownObject: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist.

While Vahti.Collector continues to run despite of random errors, they get more and more frequent as time goes on. Vahti.Collector uses BleReader.Net, which uses DotNet-BlueZ, which uses the D-Bus. Those components seem also to be affected by these issues too.

Workaround to this problem is to restart the Bluetooth and Vahti services periodically.
Add RuntimeMaxSec=86400 line in Service section of /etc/systemd/system/bluetooth.target.wants/bluetooth.service. The number is the time (in seconds) to pass before service is restarted (86400 is one day).

Respectively Vahti itself can be restarted periodically in same way. See Setting Up Raspberry Pi for details on how to run it as service.

Fixing this problem is likely not easy as it seems to originate from Bluez/D-Bus. I'll go with the workaround for now and investigate this more later, especially if someone else encounters these issues too.

Currently BluetoothGw project is meant to collect data from Bluetooth LE devices. It'd be good to be provide general support for reading other type of sensor data too (like System.Device.Gpio and Iot.Device.Bindings.

If sensor history values have no variance (like a movement counter of a sensor which is not moved), showing the graph fails and error is shown instead of the graph:
OxyPlot exception: Step cannot be zero or negative

Expected behavior is that graph should be shown even if graph is straight line.

I noticed when testing against my documentation that alerts are not sent if publishing to cloud database is not enabled. Alerts should be sent regardless of if cloud publishing is enabled or not.