Decommissioning the EnOcean switch

RE: Decommissioning the EnOcean switch

Terutaka Takeuji — Thu, 09 Nov 2023 07:32:21 GMT

I mistakenly continued on with another ticket, so I will only write the conclusion in this ticket.

First of all, the "bt_enocean_foreach()" function is not a function for removing a commissioned EnOcean switch.
This function executes the callback function associated with "bt_enocean_foreach()" for the number of commissioned devices (valid devices only).

Therefore, the function that removes the EnOcean switch is the "bt_enocean_decommission()" function.

I built it based on the "EnOcean" sample, and was able to decommission all commissioned EnOcean switches simply by editing "main.c".

■Delete all EnOcean switches (described in main.c)
static void find_and_decommission(struct bt_enocean_device *dev, void *user_data)
{
　　bt_enocean_decommission(dev);
}
bt_enocean_foreach(find_and_decommission, NULL);

You can remove all EnOcean switches with the above code.
"bt_enocean_foreach()" can be called anywhere in main.c where you want to perform processing.

I had a problem with the button interrupt processing description and was repeatedly failing, but the problem was resolved by writing the button interrupt processing as below.

■Button interrupt processing code
static void button_changed(uint32_t button_state, uint32_t has_changed)
{
　　Processing content…
}
err = dk_buttons_init(button_changed);

For more details, please check the following questions in Case ID: 317215.

thank you very much.

RE: Decommissioning the EnOcean switch

Terutaka Takeuji — Wed, 01 Nov 2023 08:03:04 GMT

Sorry for the late reply.
I have an additional question for Mr. Taesuk.

I would like to use the bt_enocean_foreach function to erase everything, but I don't know what to specify as an argument.

"bt_enocean_foreach syntax"
bt_enocean_foreach(bt_enocean_foreach_cb_t cb, void *user_data)

question)
bt_enocean_foreach has two arguments, but what should I specify for each?
Please tell me the program code in detail.

RE: Decommissioning the EnOcean switch

tesc — Tue, 17 Oct 2023 13:09:42 GMT

Hi,

[quote user="Terutaka Takeuji"]While checking the answers, I understood that there is no way to decommission EnOcean switches individually, but is my understanding correct?[/quote]

It is possible to decommission EnOcean switches individually through the use of bt_enocean_decommission() if you have the bt_enocean_device structure for the EnOcean switch.

Regards,
Terje

RE: Decommissioning the EnOcean switch

Terutaka Takeuji — Fri, 13 Oct 2023 23:33:59 GMT

Thank you for your reply tesc.

The answer was to use "bt_enocean_foreach()" if you want to decommission all EnOcean switches, so I'll try that.

While checking the answers, I understood that there is no way to decommission EnOcean switches individually, but is my understanding correct?

Also, am I correct in understanding that there is no way to send a decommission signal from the EnOcean switch?

Please give me an answer.

RE: Decommissioning the EnOcean switch

tesc — Fri, 13 Oct 2023 13:21:16 GMT

Hi,

The Bluetooth EnOcean library is only capable of observing the output of the EnOcean devices, and does not send anything back. The decommissioning is only for a device to remove the details of a (separate) switch. For instance, if you have a Bluetooth mesh bridge for bridging EnOcean switch messages into a Bluetooth mesh network, decommissioning can be used to make that bridge not bridging messages from that EnOcean switch into the mesh network anymore.

If you want to decommission all switches, you can use bt_enocean_foreach(), which calls a callback for all commissioned EnOcean devices. Decommission the device in the callback, and decommissioning will be done for all commissioned devices.

Regards,
Terje