sensor.goveetemp_bt_hci VS linux

For those who are interested, the Passive BLE monitor Home Assistant integration supports quite a few thermometers. The Govee support is based on a component I wrote, Home-Is-Where-You-Hang-Your-Hack/sensor.goveetemp_bt_hci/. If you are looking for just the decoder, check out Thrilleratplay/GoveeWatcher.

If you run Home Assistant, (or want to), the driver to pick these signals up, and get the values into Home Assistant, you will add this package: https://github.com/Home-Is-Where-You-Hang-Your-Hack/sensor.goveetemp_bt_hci

I'm running ubuntu 20 on a Raspberry Pi 4. I'm running Home Assistant in a docker container, instead of running their HassOS. I followed the instructions on github for installing HACS and the goveetemp sensor. I couldn't see the sensor showing up in Home Assistant. I chased a lot of stuff, including this bug report that makes it sound like bluetooth isn't all that reliable on the Raspberry Pi. I also found this thread in this subreddit, but that wasn't my problem.

I'm reading the bluetooth sensor with a raspberry also used for the webcam, found this library, reimplemented the parser in nodejs, this is the relevant part:

I'm going to make some tests with this library that I found that seems to support this device, I'll let you know if it works well !

Govee Temperature/Humidity BLE Home Assistant Component

Fan control generally involves hysteresis. This means a cooling fan turns on at one temperature, and then turns off once temperature has fallen to another lower temperature. This avoids cycling the fan on and off too much. The difference between those two temperatures is hysteresis. The default hysteresis is 10°C and maybe the fan never manages to cool the CPU to 45°C. A parameter has been added to change hysteresis: https://github.com/raspberrypi/linux/commit/fa390133fd17f2cc6aa5a7d2e472c073a1115fe1

I see that the PR against the Raspberry Pi linux repo is out [0]. Interestingly they are introducing a BCM2712 defconfig with a 64k default page size.

[0] - https://github.com/raspberrypi/linux/pull/5618

and can grab their patched kernel source here ( use the dtbs and overlays and kernel from your compiled version)

Also was your pi issue related to this? https://github.com/raspberrypi/linux/issues/3381 or what do you mean jittery, unstable?

Could be related to the driver load order/blacklisting (https://github.com/raspberrypi/linux/issues/435) Or couple of people report configuring the dtoverlay=imx477 in the boot config helped (https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README)

thanks, I also found this: https://github.com/raspberrypi/linux/issues/5398

And ready! :)

> It is the most basic task for Linux computer...

Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited:

https://github.com/raspberrypi/linux/issues/3010

Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless.

https://www.discomp.eu/wireless-minipci-cards_c14501412.html