Brian Gix

The loop-back mechanism should allow local Config Clients to provision local "pre-nodes". It used to work, so I will investigate if and why it may not be working now. The...

I thought you had created a fix for this and would submit it for inclusion. If you have a fix please submit it, and it will most likely be applied...

A patch-set has been submitted to the reflector to fix this issue.

> I figured out the cause of the problem. I used the latest version of the bluetooth-meshd, but the network configuration (/var/lib/bluetooth/mesh/) already existed and was generated by the old...

I will look at it this evening to see if I can see where it is failing, and perhaps tell you what other debugging you can turn on. In the...

First off, meshctl is deprecated and no longer supported. The proper set of tools to use are the bluetooth-meshd daemon, and tools/mesh-cfgclient. As far as the provisioning message "Push 1...

What kind of advertisements are the glucose meters sending? Are they LE or are they BR/EDR? Are the advertisements sent with a specific AD type? Also: What kernel version are...

The latest Raspberry PI OS kernel is v6.1. There is no way to filter in the BT Controller for multiple MAC addresses. With the Bluetooth Mesh changes added to v6.1,...

I would upgrade the entire Raspberry PI OS. kernel v4.19 is old enough that there will almost certainly be incompatibulities with user space pieces between it and v6.1

The immediate cause of the non-send is that mesh-io-generic thinks we are in the middle of a pre-existing send operation, and queuing the new packet to be sent after the...