search

ptvoinfo / zigbee-configurable-firmware

PTVO firmware for CC2530, CC2531, and CC2652 Zigbee chips
https://ptvo.info/zigbee-configurable-firmware-features/
MIT License
192 stars 22 forks source link

E-Byte E72 interview fails with zigbee2mqtt #253

Closed u20p17 closed 5 months ago

u20p17 commented 7 months ago

Hello, I have a E-Byte E72 want to flash a ptvo firmware with the following settings: image image image

I flashed it with openocd via jtag and tried to pair it with zigbee2mqtt. There the sensor gets recognized, but the interview fails, why?

image

ptvoinfo commented 7 months ago

Hi.

  1. Disable all inputs and outputs, and enable only one GPIO output. It is the simplest configuration.
  2. Reset the device using the power on/off sequence. https://ptvo.info/zigbee-configurable-firmware-features/general-info/
  3. Delete the device in Z2M. Stop Z2M. Delete coordinator_backup.json in the "data" folder. Start Z2M again.
  4. Try to re-join your device again.

Note: You can ignore the first error. It is a bug in Z2M.

u20p17 commented 7 months ago

Hi, I tried it and now I could again add it to zigbee2mqtt... Nevertheless, I do only get a mqtt message at startup (even I have set a periodic signal transmission of 60s), following this error:

image

Afterwards, sometimes I get another message, but couldn't figure out what influences this behaviour... what could be my problem?

u20p17 commented 7 months ago

after setting the following specific settings it seems to work (at least when I change the state of the GPIO input it sends a action message- not sure if it does not send periodic messages because it is configures as end device?): image

seems that the legacy parameter must be set to false... (default is true)...

u20p17 commented 6 months ago

@ptvoinfo : any idea why it does not send mqtt messages via zigbee2mqtt in regular intervals as specified in the Expert settings tab of ptvo?

ptvoinfo commented 6 months ago

@u20p17 The firmware does not send periodic reports for inputs and UART because the firmware waits for an event from the corresponding pin. For example, if you add a GPIO output, you will receive periodic reports for it.