-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement OTA #1696
Comments
Could you grab such a message with sniffing? |
Will check and report. From what i know that some of my devices now shown the own Maybe our Default EndPoint from zigbee-shepherd dont allow them or maybe we need special init the needing genOta Cluster Part ? |
@Koenkk got some more logging messages: After i add Maybe we should move the Cluster Init to Default EP or move them to seperate ZAPP ?
|
I prefer to move them into the default ep as I want to get rid of ZAPP |
How we could do this? |
Eventually I want to integrate this into zigbee-herdsman (same goes for e.g. the ias zone enrolment, so we can completely remove it from the |
@Koenkk Doesn´t we could add simple our Clusters to the |
I havent' checked that, but if it's that easy, why not? |
Yes: Modify some Parts: Comment out the complete Part of https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/zigbee.js#L151 After Restarting the Z2M the new Coordinator Entrys in the db File looks like this: Endpoint#1 now include the needing Clusters in the List. Now we doesn´t need the EndPoint:11 from our own ZAPP no more. |
Now my DEBUG Output look like this:
|
I test this with the Bitron Device
|
@Koenkk The only difference between our own build clusterlist from #1696 (comment) and using a ZAPP with the Mount Option via https://github.com/zigbeer/zigbee-shepherd/blob/master/lib/shepherd.js#L243 would be the Part of this: https://github.com/zigbeer/zigbee-shepherd/blob/master/lib/shepherd.js#L288-L301 |
Probably, but before we change old shepherd code, I'm currently refactoring the complete zigbee-shepherd library and will take this into account to make such things much more easy. |
@splitice What type of Modification on zigbee-shepherd themselve it need to get the broadcast passed or to interact with the request and responses ? I build up the needing steps for the OTA Statemachine but doesn´t could pass the needing traffic. |
Added more
|
@tb-killa For the OTA you must setup a OTA server, and then activate OTA update process on the devices, not just change in zigbee-shepherd , I think this document helpful for you because our solution base on TI API: http://dev.ti.com/tirex/content/simplelink_zigbee_sdk_plugin_1_60_01_09/docs/zigbee_user_guide/html/zigbee/developing_zigbee_applications/ota_upgrade/ota_upgrade.html. Before build OTA server yourself, try TI close sourced one first. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Close this Issue Post and move to Koenkk/zigbee-herdsman#60 |
As part of further preparations to implement a basic OTA server, a first OTA implementation based on the zcl-id cluster definition is required.
This is followed by a general implementation of the discovery process:
I thought we could just use @Koenkk's responder to intercept first requests, but apparently none are sent at all.
Possibly broadcasts are not forwarded ?
Maybe @Koenkk could say something about this ?
The text was updated successfully, but these errors were encountered: