Comments
Harvey Specter
Posted at 03:19 January 14, 2022
Ilya Rakhlin
Reply
Author

Do you happen to have any experience or examples of getting any builds of your firmware working in ZHA (home assistant ZHA). All is working well with the z2m converter but I have a few friends I was hoping to use for beta testing a device who are on ZHA. I’ve previously written a few z2m converters but have very little experience with ZHA quirks. As I start to play around with it I just wanted to see if you had any examples or samples I could use as a jumping off point. Would be especially helpful if it uses the TemperatureMeasurementCluster or Humidity.

Thank you

    Harvey Specter
    Posted at 04:34 January 14, 2022
    Owner
    Reply
    Author

    Sorry, but I don’t have examples for ZHA.

Harvey Specter
Posted at 18:49 January 8, 2022
Tube
Reply
Author

What are the child and route table sizes for the cc2652?

    Harvey Specter
    Posted at 03:48 January 10, 2022
    Owner
    Reply
    Author

    The child table was compiled with the following key value:
    MAX_DEVICE_TABLE_ENTRIES=50

Harvey Specter
Posted at 01:29 January 7, 2022
Philip
Reply
Author

Hello any chance to integrate HX711 Load Cell Amplifier to sensor list?

    Harvey Specter
    Posted at 07:33 January 7, 2022
    Owner
    Reply
    Author

    Hello, Sorry, but I didn’t plan to add this sensor.

Harvey Specter
Posted at 23:28 December 18, 2021
Ilya Rakhlin
Reply
Author

Just curious about sensor compatibility, I understand you may not have tested these but do you know if there are any reasons why the HDC2XXX line of sensors would work (https://www.ti.com/product/HDC1080 listed under similar on this page). According to a TI forum post they are firmware identical, https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/861532/hdc2010-technical-differences-among-hdc2080-hdc2010-hdc1080

In that same line of questions, SHT30 is listed as supported, it would seem the SHT31 and SHT35 are also firmware identical and differences are around accuracy, voltage, ect. I understand they may not be tested but is there any reason they would not work? With the current shortage of parts sometimes it easier to be flexible.

Harvey Specter
Posted at 06:27 December 17, 2021
Paul
Reply
Author

Description of Zigbee2MQTT-Commands need a note on the required Zigbee2MQTT version. In Zigbee2MQTT 1.17.0 a new API was introduced. Using the format of the current documented commands will not work with Zigbee2MQTT versions >1.16. It would be helpful to get a hint about this circumstance.

    Harvey Specter
    Posted at 07:07 December 17, 2021
    Owner
    Reply
    Author

    I use v1.18 and these commands work. Could you please describe the format in your case?

      Harvey Specter
      Posted at 15:36 December 17, 2021
      Paul
      Reply
      Author

      The following zigbee2mqtt command is working fine in version 1.12.
      -t zigbee2mqtt/garage/l3/set -m {\”trigger\”:800}
      after upgrading to version 1.22. it’s no longer working. I played a bit with the new command syntax e.q -t zigbee2mqtt/garage/set -m {\”state_l3\”:800} but without success. So what is the correct format to initiate a trigger?

Harvey Specter
Posted at 00:57 August 7, 2021
Shonn
Reply
Author

The problem report:
I have an old power plug with a cc2530(external 32.00MHZ oscillator) and FM24C02C eeprom. Sometimes the plug cannot boot, the led keep the dim light state(the normal state is off or light).
I try to fix this problem with the configure of cc2530(without oscillator).

« Older Comments

Leave a Reply to Shonn
Cancel Reply