Hi Aditya,
BLE_ROLE_BROADCASTER should not have an impact on this. There is only one
place in the code where this is used:
include/nimble/nimble_opt_auto.h:37:#define NIMBLE_BLE_ADVERTISE
\
(MYNEWT_VAL(BLE_ROLE_BROADCASTER) || MYNEWT_VAL(BLE_ROLE_PERIPHERAL))
Best regards
Hi,
On Thursday, 8 February 2018 00:32:34 CEST aditi hilbert wrote:
> Hi all,
>
> There has been a lot of feature additions and bug fixes since our last
> release on Dec 13, 2018. I’d like to propose we try to get a release out in
> two weeks (Feb 21st). Below are some of the things we have
Hi Michał,
Yes, that is what you should be seeing, because the message is being sent to
the GROUP; originator receives it as well.
If you change it to the destination / target address, you wouldn’t see Received.
To test this, you would require two devices.
Assuming Device A and B.
With all
Hi Aditya,
I enabled these flags:
BLE_ROLE_BROADCASTER: 1
BLE_ROLE_PERIPHERAL: 1
BLE_EXT_ADV: 1
And this is what i see after pushing the button a few times:
045120 #mesh-onoff STATUS
045121 #mesh-onoff STATUS: Sent !
045123 Received
045263 #mesh-onoff STATUS
045264
Hi Łukasz,
Disabling only the following flags in syscfg.yml allows the device to receive
but not send mesh messages.
BLE_ROLE_BROADCASTER: 1
BLE_ROLE_PERIPHERAL: 1
Disabling BLE_EXT_ADV: 1, flag allows the device to send and receive mesh
messages.
And as I said earlier
Hi Łukasz,
Am actually sending it to the Group Address.
In main.c :- Line 27
void button_cb(struct os_event *ev)
{
mesh_msg_send(MODEL_ID_CBOR_ACTION, GROUP_ADDR, "HELLO WORLD", 12);
}
And its relevant method :-
In mesh_init.c :- Line 138.
void mesh_msg_send(uint16_t model_id,
