chshu
commented
1 year ago @lbuque Could you try again with the latest IDF master, we just fixed a bug in commit: https://github.com/espressif/esp-idf/commit/897b9700c41fed603c61cadc205cc11f972ee7b4
Closed lbuque closed 1 year ago
chshu
commented
1 year ago @lbuque Could you try again with the latest IDF master, we just fixed a bug in commit: https://github.com/espressif/esp-idf/commit/897b9700c41fed603c61cadc205cc11f972ee7b4
lbuque
commented
1 year ago @chshu Using the commit you suggested, I tried the HA_on_off_light example. Still can't catch any messages in ubiqua.
Could it be that the Beacon Request is only initiated for certain channels? If yes, which channels are used in the code? I simply checked the code, but I didn't see the channel information.
likunqiao097304
commented
1 year ago @lbuque the default channel is 13. If you want to change to different one, please refer to the esp_zigbee_core.h: esp_zb_set_network_channel(uint8_t channel); BTW, it seems like on-off switch didn't formed network successfully. Try to erase the NVRAM first, before flash the code. Please refer to the README.md under HA_on_off_switch.
lbuque
commented
1 year ago @likunqiao097304 It works! ! !
Make two suggestions:
likunqiao097304
commented
1 year ago @lbuque zigbee light example is not a router is for the demonstration of zigbee-end device purpose. primary channel and secondary channel by default make them the same. So does your suggestion mean that on the monitor log side to show which channel we are sending beacon request to? both on primary channel and secondary channel?
lbuque
commented
1 year ago @likunqiao097304 As a sub-device, it sends a Beacon Request to each channel during Network steering to find a suitable zigbee network to join as soon as possible.
Just like the Network steering procedure in the figure below:
I didn't find an api to set vScanChannels or bdbPrimaryChannelSet.
u236
commented
1 year ago Same problem using v5.1-dev-3066-g236fa5e669 but network successfully formed and joined with v5.1-dev-3101-g1195b6cb2bz, thanks for the fix!
likunqiao097304
commented
1 year ago bdbPrimaryChannelSet
@lbuque This api hasn't provided yet. We will add them in the next round release
momo1
commented
1 year ago I am having a similar issue with the example. I flashed HA_on_off_switch and HA_on_off_light on two ESP32 C6s. I am using IDF v5.1-dev-3213-gd29e53dc0c on both and I also tried multiple older versions. I've erased NVRAM on both and clean built before each trial. The coordinator seems to work fine:
I (365) main_task: Started on CPU0
I (365) main_task: Calling app_main()
I (375) gpio: GPIO[9]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:2
I (375) phy_init: phy_version 101,061a19e,Jan 11 2023,18:48:18
I (455) main_task: Returned from app_main()
I (465) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 23, status: -1
I (465) ESP_ZB_ON_OFF_SWITCH: Zigbee stack initialized
I (465) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 54, status: 0
I (465) ESP_ZB_ON_OFF_SWITCH: Start network formation
I (475) ESP_ZB_ON_OFF_SWITCH: Formed network successfully (Extended PAN ID: 00:00:94:21:f6:f9:55:60, PAN ID: 0x6d44)
I (945) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 54, status: 0
I (945) ESP_ZB_ON_OFF_SWITCH: Network steering started
I (1565) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 18, status: 0
I (2075) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 48, status: 0
I (3655) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 18, status: 0
I (7405) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 18, status: 0
I (7915) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 48, status: 0
I (9495) ESP_ZB_ON_OFF_SWITCH: ZDO signal: 18, status: 0But the light end device fails to join the network:
I (345) main_task: Started on CPU0
I (345) main_task: Calling app_main()
I (355) gpio: GPIO[8]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (355) phy_init: phy_version 101,061a19e,Jan 11 2023,18:48:18
W (365) phy_init: failed to load RF calibration data (0x1102), falling back to full calibration
I (455) main_task: Returned from app_main()
I (635) ESP_ZB_ON_OFF_LIGHT: ZDO signal: 23, status: -1
I (635) ESP_ZB_ON_OFF_LIGHT: Zigbee stack initialized
I (635) ESP_ZB_ON_OFF_LIGHT: Start network steering
I (3295) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (6965) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (10635) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (14305) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (17975) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (21645) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)
I (25315) ESP_ZB_ON_OFF_LIGHT: Network steering was not successful (status: -1)Thanks
lbuque
commented
1 year ago @momo1 It is recommended that you buy a zigbee sniffer, which can capture zigbee data packets, making it easier to locate problems.
likunqiao097304
commented
1 year ago v5.1-dev-3213-gd29e53dc0c
I used the same commit of esp-idf. It works fine on both examples from my side. From the log you provided, it did look like failed to join the network. Some suggestions you could try, firstly when you checkout to different esp-idf commit, do a git submodule update --init --recursive. Secondly, make sure you do erase-flash on the both examples.
Could you checkout what version of the esp-zboss-lib and esp-zigbee-lib? It is under each examples/management_components a file called idf_component.yml. They should be 0.3.1 and 0.5.0.
momo1
commented
1 year ago @likunqiao097304 Thank you for the quick response! It worked!
I had already erased the flash and recursively updated all git modules before posting but the thing that I missed was that the library versions changed across commits in the main/idf_component.yml. Both zboss and zigbee libs were at a lower version. Once I corrected that it worked. Nice catch and thanks again.
likunqiao097304
commented
1 year ago @likunqiao097304 Thank you for the quick response! It worked!
I had already erased the flash and recursively updated all git modules before posting but the thing that I missed was that the library versions changed across commits in the
main/idf_component.yml. Both zboss and zigbee libs were at a lower version. Once I corrected that it worked. Nice catch and thanks again.
Good to hear that. Again, the Zigbee sdk is still under 1.0.0 version, there are still some known / unknown issues need to fix from our side, so feel free to give us more feedback. Also you could check this repo for more example:esp-zigbee-sdk. Have fun with ESP32C6
bouvrais
commented
1 year ago bdbPrimaryChannelSet
@lbuque This api hasn't provided yet. We will add them in the next round release
@likunqiao097304 therefore I suppose there is currently no way to connect an ESP32 End Device to a standard Coordinator network (i.e. a network that is not created by another ESP32)? Is the a list of features yet to be implemented I could look at?
swkim01
commented
1 year ago @likunqiao097304 Thank you!
After setting the channel number, I could make the device to be registered to home assistant via zigbee2mqtt addon with zigbee 3.0 usb dongle.
I used HA_on_off_switch example that was modified to include manufname and modelid attributes in basic cluster, refered by this custom example.
...
char modelid[] = {13, 'E', 'S', 'P', '3', '2', 'C', '6', '.', 'L', 'i', 'g', 'h', 't'};
char manufname[] = {9, 'E', 's', 'p', 'r', 'e', 's', 's', 'i', 'f'};
...
esp_zb_init(&zb_nwk_cfg);
esp_zb_set_network_channel(23);
...
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, &modelid[0]);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, &manufname[0]);
...Then, I added the following switch converter to HA repository as to this procedure.
const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
zigbeeModel: ['ESP32C6.Light'],
model: 'ESP32C6.Light',
vendor: 'Espressif',
description: 'light_bulb',
fromZigbee: [fz.on_off],
toZigbee: [tz.on_off],
exposes: [e.switch()],
// The configure method below is needed to make the device reports on/off state changes
// when the device is controlled manually through the button on it.
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff']);
await reporting.onOff(endpoint);
},
};
module.exports = definition;screenshot of z2m device list on HA.
screenshot of z2m dashboard on HA.
lbuque
commented
1 year ago @swkim01 Can you show your code in detail?
According to your modification, I can't get the value of ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID using read attrib.
swkim01
commented
1 year ago @lbuque My esp_zb_task function is as follows. That's all.
static void esp_zb_task(void *pvParameters)
{
/* initialize Zigbee stack with Zigbee end-device config */
esp_zb_cfg_t zb_nwk_cfg = ESP_ZB_ZED_CONFIG();
esp_zb_init(&zb_nwk_cfg);
esp_zb_set_network_channel(23);
/* set the on-off light device config */
uint8_t test_attr, test_attr2;
test_attr = 0;
test_attr2 = 4;
/* basic cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_basic_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_BASIC);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_ZCL_VERSION_ID, &test_attr);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_POWER_SOURCE_ID, &test_attr2);
esp_zb_cluster_update_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_ZCL_VERSION_ID, &test_attr2);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, &modelid[0]);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, &manufname[0]);
/* identify cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_identify_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_IDENTIFY);
esp_zb_identify_cluster_add_attr(esp_zb_identify_cluster, ESP_ZB_ZCL_ATTR_IDENTIFY_IDENTIFY_TIME_ID, &test_attr);
/* group cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_groups_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_GROUPS);
esp_zb_groups_cluster_add_attr(esp_zb_groups_cluster, ESP_ZB_ZCL_ATTR_GROUPS_NAME_SUPPORT_ID, &test_attr);
/* scenes cluster create with standard cluster + customized */
esp_zb_attribute_list_t *esp_zb_scenes_cluster = esp_zb_scenes_cluster_create(NULL);
esp_zb_cluster_update_attr(esp_zb_scenes_cluster, ESP_ZB_ZCL_ATTR_SCENES_NAME_SUPPORT_ID, &test_attr);
/* on-off cluster create with standard cluster config*/
esp_zb_on_off_cluster_cfg_t on_off_cfg;
on_off_cfg.on_off = ESP_ZB_ZCL_ON_OFF_ON_OFF_DEFAULT_VALUE;
esp_zb_attribute_list_t *esp_zb_on_off_cluster = esp_zb_on_off_cluster_create(&on_off_cfg);
/* create cluster lists for this endpoint */
esp_zb_cluster_list_t *esp_zb_cluster_list = esp_zb_zcl_cluster_list_create();
esp_zb_cluster_list_add_basic_cluster(esp_zb_cluster_list, esp_zb_basic_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
/* update basic cluster in the existed cluster list */
//esp_zb_cluster_list_update_basic_cluster(esp_zb_cluster_list, esp_zb_basic_cluster_create(NULL), ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_identify_cluster(esp_zb_cluster_list, esp_zb_identify_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_groups_cluster(esp_zb_cluster_list, esp_zb_groups_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_scenes_cluster(esp_zb_cluster_list, esp_zb_scenes_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_on_off_cluster(esp_zb_cluster_list, esp_zb_on_off_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_ep_list_t *esp_zb_ep_list = esp_zb_ep_list_create();
/* add created endpoint (cluster_list) to endpoint list */
esp_zb_ep_list_add_ep(esp_zb_ep_list, esp_zb_cluster_list, HA_ESP_LIGHT_ENDPOINT, ESP_ZB_AF_HA_PROFILE_ID, ESP_ZB_HA_ON_OFF_OUTPUT_DEVICE_ID);
esp_zb_device_register(esp_zb_ep_list);
esp_zb_device_add_set_attr_value_cb(attr_cb);
ESP_ERROR_CHECK(esp_zb_start(false));
esp_zb_main_loop_iteration();
}bdbPrimaryChannelSet
@lbuque This api hasn't provided yet. We will add them in the next round release
@likunqiao097304 therefore I suppose there is currently no way to connect an ESP32 End Device to a standard Coordinator network (i.e. a network that is not created by another ESP32)? Is the a list of features yet to be implemented I could look at?
I think you can, by calling esp_zb_set_network_channel, you could switch to other channel that your Zigbee coordinator formed. Just a note here, we will provide esp_zb_set_primary_network_channel_set and esp_zb_set_secondary_network_channel_set API pretty soon.
bouvrais
commented
1 year ago Thank you @likunqiao097304, I can confirm that forcing the channel to the one used by the coordinator does indeed allow joining the network. Also @swkim01's example works sufficiently well on my end by changing the channel.
likunqiao097304
commented
1 year ago bdbPrimaryChannelSet
@lbuque This api hasn't provided yet. We will add them in the next round release
@lbuque The API for primary/secondary channel set has been provided in the latest version of lib file. Please take a look and close the issue if fixed it
lbuque
commented
1 year ago @likunqiao097304 thank you for your support! ! ! It works.
swkim01
commented
8 months ago I tested the code with esp-idf 5.1.2(esp-zigbee-lib: 0.9.5, esp-zboss-lib: 0.7.2). No problem! The device are set to that right model id and manufacturer name on zigbee2mqtt.
2023년 11월 30일 (목) 오후 8:46, pcurt @.***>님이 작성:
Does someone test this following code with the last esp-idf version (ESP-IDF) 5.1.2 ?
... char modelid[] = {13, 'E', 'S', 'P', '3', '2', 'C', '6', '.', 'L', 'i', 'g', 'h', 't'}; char manufname[] = {9, 'E', 's', 'p', 'r', 'e', 's', 's', 'i', 'f'}; ... esp_zb_init(&zb_nwk_cfg); esp_zb_set_network_channel(23); ... esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, &modelid[0]); esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, &manufname[0]); ...
It uses the following versions for zigbee and zboss libraries
esp-zigbee-lib: "0.9.0" esp-zboss-lib: "0.7.0"
With 5.1.2 esp-idf, Zigbee model and manufacturer name are set to 'undefined' It was working with previous version 5.1.1 (esp-zigbee-lib: 0.7.0, espressif/esp-zboss-lib: 0.5.0) So I don't know who to set model and manufacturer with last esp-idf.
— Reply to this email directly, view it on GitHub https://github.com/espressif/esp-idf/issues/10662#issuecomment-1833609270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANLS2RQYTO37WBBAOOX32DYHBWYNAVCNFSM6AAAAAAUMDAKYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGYYDSMRXGA . You are receiving this because you were mentioned.Message ID: @.***>
pcurt
commented
8 months ago I tested the code with esp-idf 5.1.2(esp-zigbee-lib: 0.9.5, esp-zboss-lib: 0.7.2). No problem! The device are set to that right model id and manufacturer name on zigbee2mqtt. 2023년 11월 30일 (목) 오후 8:46, pcurt @.>님이 작성: … Does someone test this following code with the last esp-idf version (ESP-IDF) 5.1.2 ? ... char modelid[] = {13, 'E', 'S', 'P', '3', '2', 'C', '6', '.', 'L', 'i', 'g', 'h', 't'}; char manufname[] = {9, 'E', 's', 'p', 'r', 'e', 's', 's', 'i', 'f'}; ... esp_zb_init(&zb_nwk_cfg); esp_zb_set_network_channel(23); ... esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, &modelid[0]); esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, &manufname[0]); ... It uses the following versions for zigbee and zboss libraries esp-zigbee-lib: "0.9.0" esp-zboss-lib: "0.7.0" With 5.1.2 esp-idf, Zigbee model and manufacturer name are set to 'undefined' It was working with previous version 5.1.1 (esp-zigbee-lib: 0.7.0, espressif/esp-zboss-lib: 0.5.0) So I don't know who to set model and manufacturer with last esp-idf. — Reply to this email directly, view it on GitHub <#10662 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANLS2RQYTO37WBBAOOX32DYHBWYNAVCNFSM6AAAAAAUMDAKYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGYYDSMRXGA . You are receiving this because you were mentioned.Message ID: @.>
Thanks, it is now working
Tokn59
commented
7 months ago @swkim01 swkim01
char modelid[] = {13, 'E', 'S', 'P', '3', '2', 'C', '6', '.', 'L', 'i', 'g', 'h', 't'}; char manufname[] = {9, 'E', 's', 'p', 'r', 'e', 's', 's', 'i', 'f'};
Could you please share your full example or indicate clearly where you defined and added these in the source code ? Thank you !!!!
swkim01
commented
7 months ago @Tokn59 Within esp_zb_light.c of HA_on_off_light example, replace esp_zb_task function with the following code, that's all.
char modelid[] = {13, 'E', 'S', 'P', '3', '2', 'C', '6', '.', 'L', 'i', 'g', 'h', 't'};
char manufname[] = {9, 'E', 's', 'p', 'r', 'e', 's', 's', 'i', 'f'};
static void esp_zb_task(void *pvParameters)
{
/* initialize Zigbee stack with Zigbee end-device config */
esp_zb_cfg_t zb_nwk_cfg = ESP_ZB_ZED_CONFIG();
esp_zb_init(&zb_nwk_cfg);
esp_zb_set_primary_network_channel_set(ESP_ZB_PRIMARY_CHANNEL_MASK);
/* set the on-off light device config */
uint8_t test_attr, test_attr2;
test_attr = 0;
test_attr2 = 4;
/* basic cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_basic_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_BASIC);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_ZCL_VERSION_ID, &test_attr);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_POWER_SOURCE_ID, &test_attr2);
esp_zb_cluster_update_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_ZCL_VERSION_ID, &test_attr2);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, &modelid[0]);
esp_zb_basic_cluster_add_attr(esp_zb_basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, &manufname[0]);
/* identify cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_identify_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_IDENTIFY);
esp_zb_identify_cluster_add_attr(esp_zb_identify_cluster, ESP_ZB_ZCL_ATTR_IDENTIFY_IDENTIFY_TIME_ID, &test_attr);
/* group cluster create with fully customized */
esp_zb_attribute_list_t *esp_zb_groups_cluster = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_GROUPS);
esp_zb_groups_cluster_add_attr(esp_zb_groups_cluster, ESP_ZB_ZCL_ATTR_GROUPS_NAME_SUPPORT_ID, &test_attr);
/* scenes cluster create with standard cluster + customized */
esp_zb_attribute_list_t *esp_zb_scenes_cluster = esp_zb_scenes_cluster_create(NULL);
esp_zb_cluster_update_attr(esp_zb_scenes_cluster, ESP_ZB_ZCL_ATTR_SCENES_NAME_SUPPORT_ID, &test_attr);
/* on-off cluster create with standard cluster config*/
esp_zb_on_off_cluster_cfg_t on_off_cfg;
on_off_cfg.on_off = ESP_ZB_ZCL_ON_OFF_ON_OFF_DEFAULT_VALUE;
esp_zb_attribute_list_t *esp_zb_on_off_cluster = esp_zb_on_off_cluster_create(&on_off_cfg);
/* create cluster lists for this endpoint */
esp_zb_cluster_list_t *esp_zb_cluster_list = esp_zb_zcl_cluster_list_create();
esp_zb_cluster_list_add_basic_cluster(esp_zb_cluster_list, esp_zb_basic_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
/* update basic cluster in the existed cluster list */
//esp_zb_cluster_list_update_basic_cluster(esp_zb_cluster_list, esp_zb_basic_cluster_create(NULL), ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_identify_cluster(esp_zb_cluster_list, esp_zb_identify_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_groups_cluster(esp_zb_cluster_list, esp_zb_groups_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_scenes_cluster(esp_zb_cluster_list, esp_zb_scenes_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_cluster_list_add_on_off_cluster(esp_zb_cluster_list, esp_zb_on_off_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
esp_zb_ep_list_t *esp_zb_ep_list = esp_zb_ep_list_create();
/* add created endpoint (cluster_list) to endpoint list */
esp_zb_ep_list_add_ep(esp_zb_ep_list, esp_zb_cluster_list, HA_ESP_LIGHT_ENDPOINT, ESP_ZB_AF_HA_PROFILE_ID, ESP_ZB_HA_ON_OFF_OUTPUT_DEVICE_ID);
esp_zb_device_register(esp_zb_ep_list);
esp_zb_core_action_handler_register(zb_action_handler);
ESP_ERROR_CHECK(esp_zb_start(false));
esp_zb_main_loop_iteration();
}@swkim01 swkim01
I owe you a BIG thanks !!!!! Got it working after some fiddling around and creating the right converter file for Zigbee2MQTT. The switch works !!!!! Having the possibility now to build custom Zigbee devices is just great after years of Wifi only ! :-)
SCiunczyk
commented
3 months ago Hi,
I'm trying to connect ESP32-H2/C6 Espressif HA Light on/off to my HA (Conbee III - distance to device 50cm) using @swkim01 example. I got error:
error 2024-04-21 11:00:36Interview failed for '0x744dbdfffe600a54 with error 'Error: Interview failed because can not get node descriptor ('0x744dbdfffe600a54')'
error 2024-04-21 11:00:36Failed to interview '0x744dbdfffe600a54', device has not successfully been pairedBut with ZHA integration the board is connecting without any problems (successful screen below):
I have H2 and C6 boards - same problem. What steps should I perform to diagnose the bugs/misconfiguration. Any suggestions very appreciated.
chshu
commented
3 months ago @SCiunczyk Could you please file a new issue here: https://github.com/espressif/esp-zigbee-sdk/issues.
But with ZHA integration the board is connecting without any problems (successful screen below):
Could you also describe a bit more about this step in the new issue, what's the difference between 'ZHA integration' and my HA (Conbee III - distance to device 50cm)?
SCiunczyk
commented
3 months ago @chshu sure, just give me few minutes.
Answers checklist.
IDF version.
v5.1-dev-3066-g236fa5e669
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-C6-DevKitC-1
Power Supply used.
USB
What is the expected behavior?
I have two boards, run HA_on_off_light and HA_on_off_switch respectively, and then I use zigbee sniffer to get their incoming packets, but I can't get anything.
What is the actual behavior?
I can't get the Beacon Request message when I use Ubiqua.
Steps to reproduce.
Debug Logs.
More Information.
No response