Koenkk / zigbee-herdsman

A Node.js Zigbee library
MIT License
456 stars 277 forks source link

zigbee-herdsman migration #23

Closed hobbyquaker closed 4 years ago

hobbyquaker commented 4 years ago

Hi Koenkk! First of all: Thanks for your awesome work! I have questions about the herdsman:

Regards, Sebastian

Ref: https://github.com/hobbyquaker/node-red-contrib-zigbee/issues/44

Koenkk commented 4 years ago

Hey Sebastian!

hobbyquaker commented 4 years ago

Thanks for the answer and the API hints! Will try to move my project to 0.6 asap ;)

Koenkk commented 4 years ago

Great, feel free to ask any questions here.

hobbyquaker commented 4 years ago

@Koenkk I would like to offer my help with documentation: adding jsdoc comments in the source, configure jsdoc&jsdoc2markdown to create an API.md file documenting all methods/properties/events. What do you think about that? Would you accept PRs?

Koenkk commented 4 years ago

Yes definitely! Let me know if something is unclear.

I would recommend starting with the things I mentioned here: https://github.com/Koenkk/zigbee-herdsman/issues/23#issuecomment-528857240

hobbyquaker commented 4 years ago

Have to get some more jsdoc(2md) knowledge, this is the first time I'm using it on Typescript and with Async/Await/Promises... This is just a first example so you get some impression on how this could look like ;-)

Koenkk commented 4 years ago

That looks like a good start :smile:

hobbyquaker commented 4 years ago

Hi @Koenkk
I managed it to adapt node-red-contrib-zigbee to zigbee-herdsman@0.7.0 and on my test system everything runs fine. I'm very excited about the herdsman, pairing works much better, until now everything works stable and consuming the api is much more pleasant than working with the shepherd :-) Thank you so much for your work!

Now i tried to upgrade my production system, but I was facing a problem. There are no messages incoming from my sensors, trying to control bulbs always ends in no network route (205). Do I see that right that this migration should just work (starting with already paired devices and a device db that was created by the shepherd)?

hobbyquaker commented 4 years ago

ah, nevermind, got it working 🎉 Made a little mistake leading to another panID: https://github.com/hobbyquaker/node-red-contrib-zigbee/commit/85883110ecc6ac0e67e3e43db9cd30fd1a6d52f7 :-)

Koenkk commented 4 years ago

Good to hear :smile:

hobbyquaker commented 4 years ago

Another Question: I'm keeping track of binds in the device.meta to offer a nice ui for binding: image What do you think about the suggestion to integrate that mechanism in the herdsman? Right now binds made by the configure extensions aren't tracked because it seemed to complicated to hook oh these, that's something I'd like to have in future... If you want I could try to prepare a PR, but most likely I will need some hands-holding and pushes into the right direction ;-)

hobbyquaker commented 4 years ago

And one more question: I also have a ui to select which devices should report: image But I have no clue how to "un-report". Removing the bind isn't enough I guess, can I remove them completely by some special configuration on endpoint.configureReporting(cluster, configuration)?

Koenkk commented 4 years ago
bohtho commented 4 years ago

This is exemplary complementary development! And with such quality! I’m ditching my current zigbee system and migrating it all to zigbee-herdsman/node-red-contrib-node-zigbee based on reputation, documentation and what I see here alone.