Support MQTT or Home Assistant

[runty]

This would also make it easy to import into other home platforms

[babldev]

also requested by @glenrobertson

[babldev]

I hear Home Assistant has some time series features as well so maybe that will also help with #3

[runty]

yes, automatically with graphing, many ways to show data, etc

[dogshapedangel]

This would be an extremely powerful addition. +1

[dogshapedangel]

It might be worth taking a look at the Aranet4's HA implementation as it actually uses Bluetooth (I think BLE specifically), granted this is only the HA half of that.

https://github.com/home-assistant/core/tree/dev/homeassistant/components/aranet
https://www.home-assistant.io/integrations/aranet/

It would be ideal to have this data accessible via both Wi-Fi and Bluetooth but I can understand if pursuing one option first would be simpler.

[dogshapedangel]

@runty @glenrobertson If you are OK with forgoing display support in the interim, I have crafted an ESPHome config that allows you to run Bitclock with ESPHome firmware, sending data straight to Home Assistant.

https://github.com/manedfolf/bitclock/blob/esphome/bitclock-esphome/bitclock-esphome.yaml

It does not support the included display at this time since ESPHome doesn't have component support for the 2.71in Pervasive Displays E2271KS0C1 e-ink display. It would be possible to craft a custom component/driver for ESPHome, but that is admittedly not something I readily know how to do. It would still be very cool to be able to do custom screens directly within ESPHome. Granted, all of that is well outside of the scope of this project/repo so I have no expectation of support on this unless it piques the developer's interest.

[babldev]

@manedfolf nice work!

Pretty amazing you can do that with just a few lines in a YAML file

[babldev]

@manedfolf One thing to note is if you use direct sensor readings I assume you'll lose the "fudge factors" to correct temp + humidity.

bitclock/bitclock-fw/main/tasks/sht4x.c

Lines 148 to 164 in d957f64

	// SHT4x is supposed to be "factory calibrated" but at least
	// in my testing it reads overly hot by 4 deg C.
	//
	// This could be from various factors:
	// - Self-heating via sensor / PCB
	// - Bad enclosure ventilation
	// - PCBA manufacturing errors
	// - Sensor not meeting specification
	//
	// So let's modify it in a linear fashion based on a reference thermometer
	// at 2 points.
	//
	// Linear calibration based on semi-scientific testing with the rev5
	// enclosure Observations: 29.06 deg C should be 25.61
	// 7.59 deg C should be 3.67
	degCEnclosureOffset = degC * 0.022 - 4.08;
	degC = degC + degCEnclosureOffset;

bitclock/bitclock-fw/main/tasks/sht4x.c

Lines 178 to 192 in d957f64

	// Because are temperature is offset by PCB/Enclosure heating
	// We need to compensate the RH too. See
	// "App Notes Humidity at a Glance" for the source of this equation:
	//
	// RH2 = RH1*exp(4283.78*(T1-T2)/(243.12+T1)/(243.12+T2));
	//
	// T1 = degC - degCEnclosureOffset
	// T2 = degC
	//
	// It's ~1.22x at 26deg C compensated temp
	//
	relativeHumidityEnclosureMultiplier =
	exp((4283.78 * -degCEnclosureOffset) /
	((243.12 + degC - degCEnclosureOffset) * (243.12 + degC)));
	rh_pRH *= relativeHumidityEnclosureMultiplier;

[dogshapedangel]

@babldev I can’t speak to the actual code behind it, but I believe the library does include configuration options for some kind of compensations

https://esphome.io/components/sensor/sht4x.html

[glenrobertson]

@dogshapedangel I like the esphome solution you have! Before I discovered that, I put together these changes that will report data over MQTT in the homeassistant discovery message format: #13

It would just need some changes to the web UI as well to accept an MQTT url.