Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add CCTFR6700 * Add schneider_pilot_mode * Add Schneider Electric CCTFR6700 * File already exists * Add schneider_pilot_mode to CCTFR6700 * Update toZigbee.js * Added fromZigbee for schneider_pilot_mode * Udpated toZigbee for schneider_pilot_mode * Added fromZigbee pilot mode and fixed expose for energy/power * Removed configureKey * Update schneider_electric.js * Added measured temperature SET for CCTFR6700 * Added measured temperature SET for CCTFR6700 Requires 'report' capability merged into herdsman. * Added push/pop to global store Used for deferred writes * Added toZigbee for CCTFR6400 * Added CCTFR6400 thermostat * Added from zigbee for CCTFR6400 Also forced local_temperature othewise Home assistant is not happy * Improved CCTFR6400 and 6700 * Added UI temperature update of CCTFR6400 * Updated using ClusterAttributeValue * Updated using ClusterAttributeValue * Updated using ClusterAttributeValue * Removed legacy support for schneider_thermostat_system_mode * Removed temperature expose Temperature is exposed as local_temperature only * CCTFR6400 tempreature exposed as local_temperature * Used sendWhenActive for keypadLockout * Used sendWhenActive for keypadLockout and added defaults * Fixed schneider_ui_action convert * Simplified schneider_thermostat_control_sequence_of_operation * Reverted Push/pop value * Update toZigbee.js * Update toZigbee.js * Update schneider_electric.js * Update fromZigbee.js * Update schneider_electric.js * Update schneider_electric.js * Fix' Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
- Loading branch information
Showing
3 changed files
with
125 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this to work, a hacked firmware is needed so that read to hvac cluster on enpoint 3 are seen by the coordinator.
Do you plan to publish that firmware?
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@H3buss yes, I will include these changes in the next fw updates. (cc2652/cc1352 will come first)
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, that's the dongle I use in production env.
I'll update the doc, maybe tomorrow
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry to come back on that issue, but I installed my production environnement and the the thermostat no longer take the readResponses into account. I think I messed-up when I tested with the hacked firmware a while ago.
After some troubleshooting, the readResponses are sent from coordinator endpoint 3, and the sent attributes are correct, however the profile is incorrect: should be 0x0104 for Home Automation, and is 0x0105.
How can I set the profile for the read responses?
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a bit troublesome because the profileID cannot be send via the API. I think the firmware uses the profileID of the endpoint, but changing the profileID is not possible since this could potentially break other devices.
We can try to set the profile id to the wildcard one
0xFFFF
. Could you try to set that, reflash your stick and see what happens?d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with a CC2652R (offcial firmware) and modified to 0xFFFF the profile of endpoint 3 https://github.com/Koenkk/zigbee-herdsman/blob/fbe8b70e7ec7f540b0749adcd82922564f858ef2/src/adapter/z-stack/adapter/endpoints.ts#L25
Unfortunately, the read on endpoint 3 profile 0x0105 are not forwarded to herdsman. Should I try with the hacked firware on CC2531? (this is my production adapter, so I need to migrate everything before testing)
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes you will need the hacker cc2531 firmware, I will update the CC2652R with this hack later.
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested with profile 0xFFFF.
The coordinator does respond with 0xFFFF as profile id, but unfortunately the response is ignored by the device.
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So maybe the only option would be a configuration option in the main conf that makes the adapter compatible with that device, loosing compatibility with other devices along the way.
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@H3buss yes, but this also would require a reset of your network, I need to think of an acceptable solution.
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Koenkk Hello! Sorry to bother you on this issue. Did you think of a solution yet?
d0fb06c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@H3buss I've checked the api, but the profileID is set in the closed source part of the firmware. I've changed the profileID in zigbee-herdsman now, fingers crossed that it doesn't introduce any other problems :)