Releases: nobodyinperson/co2monitor
Idle interval between readings
This release adds a configurable idle interval between device readings to reduce file size.
Specify the amount of idle seconds in /etc/co2monitor/service.conf
:
interval = 30
The service needs restarting for this to take effect. One of:
sudo systemctl restart co2monitor
qdbus --system de.nobodyinperson.co2monitor /de/nobodyinperson/co2monitor de.nobodyinperson.co2monitor.quit
and then re-plugging the device should do it.
Easily show graph
fix: data file sorting by creation time in plot.R
Just a small fix that lets the plotscript /usr/share/doc/co2monitor/examples/plot.R
sort the data files by creation time, not just filename.
Known issues
Still, with this release, just don't unplug the device during warmup :-)
- The logging thread is not stopped when the device is unplugged during warmup. Instead, the thread does not exit at all, which is a problem. It also cannot be stopped from the dbus interface, co2monitor has to be stopped manually (call the
quit
method on dbus, or do asudo systemctl stop co2monitor
).
better hotplug handling
This release should fix some crashes when hotplugging all over the place.
Known issues
With this release, just don't unplug the device during warmup :-)
- The logging thread is not stopped when the device is unplugged during warmup. Instead, the thread does not exit at all, which is a problem. It also cannot be stopped from the dbus interface, co2monitor has to be stopped manually (call the
quit
method on dbus, or do asudo systemctl stop co2monitor
).
fix: co2monitor-service multiple invocation
improved structure
This release introduces an improved structure:
When a device in plugged in, udev
starts the co2monitor-invoker
who makes sure the co2monitor-service
is up and running (via systemd
if available) and then instructs it via dbus
to log from the attached device.
New Features:
- DBus integration
- handling multiple devices in parallel
- add French translation
Known Issues:
- On non-systemd systems, when plugging in multiple devices at once (e.g. at bootup), the
co2monitor-service
is started multiple times, because theco2monitor-invoker
does not check for other invoker instances. This is not tragic, because the services can only continue if the dbus busname is released again. But after shutting down theco2monitor-service
, the next instance kicks in. It does not influence usability.
systemd or non-systemd
From this release on, co2monitor decides automatically whether to use systemd or just udev RUN+=...
to start the logging service when plugging the device in. This enhances compatibility to a great deal.
- Tested on deprecated raspbian wheezy, which does not use systemd.
- In theory, co2monitor should now also be able to start individual logging services per device, if multiple are connected. I cannot test this, because I only have one (And still, the output file naming does not yet include the device name anyway...)
Update: There are indeed multiple services started if multiple devices are plugged in, but there are still bugs that make this not really useful. The next release will introduce a new structure that specifically addresses handling multiple devices in parallel.
Application icon
Add plotting script to application menu
rudimentary data visualization with R
This release adds an example R plotting script to get an overview of the measured data in the standard data logging folder /var/lib/co2monitor/data/
.
You may either view only the latest data since you last plugged in the device via
/usr/share/doc/co2monitor/examples/plot.R newest
or all the measured data via
/usr/share/doc/co2monitor/examples/plot.R all
This is for basic visualisation until the co2monitor-applet is ready.
An example output: