I am trying to edit the friendly name for these sensors, but it always puts the ble_temperature/ble_humidity in front.
Can the friendly name be fully configurable, please?
This was the solution Map new sensor to old sensor name
Updated the Raspbian this system works on and I noted a bug whereby if there is an external dongle, the internal BT sensor does not work. - Pi-bluetooth bug external and internal devices. I did revert the fix (as I have a local dongle and a remote one).
However, I am seeing these errors that eventually results in the HCI interface going down. I saw the errors before I applied the fix, after I applied the fix and again once I reverted back to the up to date version.
Feb 05 11:23:38 hassio kernel: Bluetooth: hci0: Received unexpected HCI Event 00000000
Feb 05 11:23:38 hassio kernel: Bluetooth: hci0: Received unexpected HCI Event 00000000
Feb 05 11:23:39 hassio kernel: Bluetooth: hci0: command 0x040c tx timeout
Feb 05 11:23:40 hassio kernel: Bluetooth: hci0: hardware error 0x00
Feb 05 11:23:40 hassio kernel: debugfs: File 'force_bredr_smp' in directory 'hci0' already present!
Feb 05 11:25:09 hassio kernel: Bluetooth: hci1: hardware error 0x03
Feb 05 11:25:09 hassio kernel: debugfs: File 'force_bredr_smp' in directory 'hci1' already present!
Feb 05 11:25:26 hassio kernel: Bluetooth: hci0: advertising data len corrected 28 -> 4
Feb 05 11:25:26 hassio kernel: Bluetooth: hci0: Received unexpected HCI Event 00000000
Feb 05 11:25:36 hassio kernel: Bluetooth: hci1: hardware error 0x0e
Feb 05 11:25:36 hassio kernel: debugfs: File 'force_bredr_smp' in directory 'hci1' already present!
These errors are repeated over and over in the syslog.
While migrating between the old BLE integration and the new one (so no BLE activity) no errors were seen.
[edit]
I’ll add that the data received is significantly worse than the old mitemp_bt passive system I had running. Where I used to get 10 or so readings in a 60s period, I now see a max of 5.