Device support: 'Nue' / '3A Smarthome' smart switch range #176
Labels
Comments
|
Can you:
// Nue
{
zigbeeModel: ['FB56+ZSW1HKJ2.5', 'FB56+ZSW1HKJ1.7'],
model: 'TODO',
vendor: 'Nue',
description: 'Smart light switch - 2 gang',
supports: 'TODO',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const device = shepherd.find(ieeeAddr, 1);
execute(device, [(cb) => device.bind('genOnOff', coordinator, cb)], callback);
},
}, |
|
Thanks @Koenkk I will try this tonight and let you know how I get on, and will gather all the other model details I can for the other devices |
|
@Koenkk , This is the database.db contents. Below I will post the shepherd results, but there were not any "no converter available" messages. I hope this helps and appreciate your time. SHEPHERD DUMP: (I have tried pairing, keeping pairing alive, and also switch presses during this dump but no response was noted to switches again) |
|
Thanks, can you check with this code: // Nue
{
zigbeeModel: ['FB56+ZSW1HKJ2.5', 'FB56+ZSW1HKJ1.7'],
model: 'TODO',
vendor: 'Nue',
description: 'Smart light switch - 2 gang',
supports: 'TODO',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep16 = shepherd.find(ieeeAddr, 16);
execute(ep16, [(cb) => ep16.bind('genOnOff', coordinator, cb)], () => {
const ep17 = shepherd.find(ieeeAddr, 17);
execute(ep17, [(cb) => ep17.bind('genOnOff', coordinator, cb)], callback);
});
},
}, |
|
Thanks @Koenkk again for your help. I've tried the new code, debug below. I still cannot detect any messages coming through with state changes from the switch. Is there something else I should be doing? For info, I am running the dongle on a laptop with Debian, which is connecting back to the Hass.io MQTT server on my Pi okay. Here's the latest log: DATABASE.db |
|
Can you try with this code: // Nue
{
zigbeeModel: ['FB56+ZSW1HKJ2.5', 'FB56+ZSW1HKJ1.7'],
model: 'TODO',
vendor: 'Nue',
description: 'Smart light switch - 2 gang',
supports: 'TODO',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep16 = shepherd.find(ieeeAddr, 16);
const ep17 = shepherd.find(ieeeAddr, 17);
const actions = [
(cb) => ep16.bind('genOnOff', coordinator, cb),
(cb) => ep17.bind('genOnOff', coordinator, cb),
(cb) => ep16.report('genOnOff', 'onOff', 0, 1000, 0, cb),
(cb) => ep17.report('genOnOff', 'onOff', 0, 1000, 0, cb),
];
execute(ep16, actions, callback);
},
}, |
|
Dump below (just Shepherd in debug, let me know if you need all debugged). Still no movement when switches triggered, though the board itself looks like it is probably universal between 1, 2 and 3 gang models, this one is just missing the resistors and switches in the other position (e.g. this 2 gang has positions 1 and 3 populated). Thanks @Koenkk |
|
Can you try with: // Nue
{
zigbeeModel: ['FB56+ZSW1HKJ2.5', 'FB56+ZSW1HKJ1.7'],
model: 'TODO',
vendor: 'Nue',
description: 'Smart light switch - 2 gang',
supports: 'TODO',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep16 = shepherd.find(ieeeAddr, 16);
const ep17 = shepherd.find(ieeeAddr, 17);
const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 10, repChange: 0};
const actions = [
(cb) => ep16.bind('genOnOff', coordinator, cb),
(cb) => ep16.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
(cb) => ep17.bind('genOnOff', coordinator, cb),
(cb) => ep17.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
];
execute(ep16, actions, callback);
},
}, |
|
Hi @Koenkk , I have tried the new code, below is a debug log. Again I did not see any new messages when cycling the switches, and I also have a MQTT sniffer subscribed to the topic in case something was missed, but no luck. Could it be something I'm doing wrong? Thanks for you continuing efforts in helping! Much appreciated. |
|
Strange that still nothing is reported. In the meantime somebody got a different Nue model working: Koenkk/zigbee-herdsman-converters#29 (comment) |
|
Hi @Koenkk , I haven't given up... yet! But I'm getting close I'm afraid, as this is all a bit beyond my skill level getting this far. I would really like this to work however as a lot of my plans for the smart side of our renovation rely on this, and I mistakenly thought this would be easy (hah!). I figured that if Alexa can do it then I could too! I'm wondering though if this will be of benefit: The SmartThings guys seem to have most of this figured out for HomeAssistant/MQTT and utilising the Smart Things hub - I'm just hoping that the device handlers for that hub may in fact be ported over to Zigbee2MQTT easily in this case? As always, your help and great interface is very much appreciated! |
|
Could you try the following code? According to the smartthings docs these are the commands that are executed in the configure method: // Nue
{
zigbeeModel: ['FB56+ZSW1HKJ2.5', 'FB56+ZSW1HKJ1.7'],
model: 'TODO',
vendor: 'Nue',
description: 'Smart light switch - 2 gang',
supports: 'TODO',
fromZigbee: [],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep16 = shepherd.find(ieeeAddr, 16);
const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 10, repChange: 0};
const actions = [
(cb) => ep16.read('genOnOff', 'onOff', cb),
(cb) => ep16.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
];
execute(ep16, actions, callback);
},
}, |
|
Hi @Koenkk , sorry for the delay in trying this, and thanks again for continuing to help. I decided to try reflashing the firmware on the CC2531 first to see if that made a difference (I'm currently using your latest with the large buffer - let me know if that's a bad idea!) I have used the above code you provided for the devices.js file. The good news is that I've noticed some new lines in the log - but at this time cycling the switches does not result in immediate messages, however I have seen them appear once seemingly out of the blue: Log.txt file: This is a segment from the debug terminal: This is now populated into the database.db: I feel like I'm getting close!!! Does this look like it's going in the right direction now? Once I get one working, I'll be happy to find and properly format the settings data for the 5 or so related devices I have and create a PR, so hopefully this will help others also. Any further steps forward would be great!! Thank you again. |
|
After |
|
No, that was the first time I've ever seen the "no converter available" message appear, and the associated payloads, eg.: 2018-8-16 11:47:32 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"onOff":1}} Toggling the switch does not produce any messages that I can see on the debug output or the log. Is this due to needing to further setup (Sorry closed issue by accident on my phone) |
|
The one report is because of the read in the configure method. Somehow, the device just refuses to report it's state change :(. Could you try pairing your |
|
@Koenkk sure thing. I just need to find which switch it is in the house! For the time being, I also added a Nue "FB56-ZSW05HG1.2" in-line switch whilst debugging, before I forever sealed it in plasterboard tomorrow. This device is that referred to in Nue in wall switch #29 Log below - I'll try some other model switches now. Thanks again. |
|
I believe this is the same FB56+ZSW1HKJ2.5, Debug output: Log.txt: This is my devices.js entry: |
|
The configure failed: Can you try repairing? |
|
Sorry I'm currently away with work - the device might be difficult to get to now but I can try. Is there any chance this is related to the sniffer, and/or firmware? I'm holding out for some changes to Zigbee2MQTT that allow modification of the .js files, as this will make the process much easier to debug. Something else (a little off topic) that I've been wondering about for a while now is if/when I get this up and running, is how to continue to utilise Alexa integration. The supplied usb hub I assume will become redundant, but therefore so will the links to the hub via the app, which is the Alexa link. Is it possible to utilise the CC2531 as a repeater, rather than a coordinator, but still to pass/receive messages to HASS.io? |
|
You could try updating to: https://github.com/Koenkk/Z-Stack-firmware/tree/increased_buffer/coordinator/CC2531/bin No this is not possible, as zigbee2mqtt has to be the coordinator. (and you cannot have more than one coordinator in a zigbee network). |
|
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. |
|
@highground88 how did you go in the end. As, seemingly, the only AU approved switches there should be interest. |
|
No problem, thanks for fixing it - any ideas on how to fix the 2 way feedback? |
|
Also, using the latest dev build (30/3/19), I'm experiencing more binding issues. I can bind the '4scene' to the '2gang' switches, but not the other way around (irrespective of using friendly names etc). If I do bind the '4scene' to the '2gang' , the source switch actuates as expected, but no Z2M message is produced whenever a bound source key is pressed. Pressing the target key does initiate a message. These 'click' buttons produce messages okay before they're bound, and when 'un-binded'. operate again as expected. Happy to move this into another issue/binding issue if you'd prefer? Cheers |
|
To start with, we first make sure that this mapping is OK: Do the correct switches turn on off when sending to |
|
You might be on to something... thank you for your daily message :-) I have noticed that all switches are always set ON. The 'click' message when physically pressing the button shows this, e.g. Each botton (top-left etc) sends its own 'click' endpoint as intended, however the entire message before this does not change independant on whether switches are on or off, it always shows ON for each switch state. This switch only momentarily lights up for about 1 sec when pressed, therefore isn't 'ON' constantly I imagine (however outside Z2M on its own network & hub, the light stays active if the paired device remains on). zigbee2mqtt/4scene/top_left/set ON result The message above results in the following MQTT message: It seems as though there might be a problem with the handler? EDIT: I'm now using the below handler which I pasted together from other devices... not sure if correct, but the switches now light up and remain lit. Switch 4 isn't on there yet... This results in: I then added:
I might leave it to an expert to advise what I need to do and what I've done wrong perhaps :-) |
|
Can you use the following 2 HGZB_045_cmdOn: {
cid: 'genOnOff',
type: 'cmdOn',
convert: (model, msg, publish, options) => {
const ep = msg.endpoints[0];
const button = getKey(model.ep(ep.device), ep.epId);
const payload = {};
payload[`state_${button}`] = 'ON';
return payload
},
},
HGZB_045_cmdOff: {
cid: 'genOnOff',
type: 'cmdOff',
convert: (model, msg, publish, options) => {
const ep = msg.endpoints[0];
const button = getKey(model.ep(ep.device), ep.epId);
const payload = {};
payload[`state_${button}`] = 'OFF';
return payload
},
}, |
|
Utilising this handler: on a fresh install with the FromZigbee changes made, I am getting this response from
"state_left" should probably be "state_bottom_left" perhaps? I am also not getting any changes to the states of any switches; all remain ON. Only the 'click' value changes dependant on switch, otherwise these are the same messages. |
|
These values are probably cached, please remove |
|
Sorry was away for work again. Thanks for the reply, here is where I am at:
Using this handler still: #176 (comment) Sending: Pressing this top_left switch results: The log shows: Can you confirm the device handler I'm using is currently accurate? Thank you!! |
|
I expect that this device is stateless, I just provides one message if the one of the button is pressed. If my reasoning is correct, the converter should be changed to produce |
|
Thanks Koen. It might well be. On its standard hub I've done some testing using a binded pair of devices to try to determine the natural behaviour (below). It would be great to be able to utilise the state light as I was hoping to setup a 4 gang scene switch next to the bed and have a 'night time' alarm button which would show the state of the HA alarm dependant on switch LED colour for the wife. This would therefore be outside of the switches ecosystem. (all off state) (all off state) If this is the case as you expected and no state is forwarded,, is there a need to add the I'm still not sure how best to format the converter I'm sorry to produce Much appreciation as always for your help. |
|
Can you try these handlers: HGZB_045_cmdOn: {
cid: 'genOnOff',
type: 'cmdOn',
convert: (model, msg, publish, options) => {
const ep = msg.endpoints[0];
const button = getKey(model.ep(ep.device), ep.epId);
return {click: `${button}_on`};
},
},
HGZB_045_cmdOff: {
cid: 'genOnOff',
type: 'cmdOff',
convert: (model, msg, publish, options) => {
const ep = msg.endpoints[0];
const button = getKey(model.ep(ep.device), ep.epId);
return {click: `${button}_off`};
},
}, |
|
Hi @Koenkk , still not having much luck with this device unfortunately... I'm using this device config (is this still correct?): ... with the handlers you last posted above, on a fresh build. I have MQTT connection, but am not receiving MQTT messages, and appear to be getting these errors : This is current verion info: |
|
Can you provide the complete debug log? |
|
DEBUG LOG -- Error at bottom highlighted. Thanks Koen. I have a fresh 1.4.0 dev version now, and I changed over to my second CC2531, and are receiving MQTT messages again (e.g. This error though seems to still appear on it's own eventually without any button presses. I'm not sure of the nature or effect it has. |
highground88
changed the title
|
@highground88 can you add to https://github.com/Koenkk/cc-znp/blob/master/lib/zpiObject.js#L19 |
|
@Koenkk , thanks for your help. I've made the changes to the zipObject.js file - I imagine the above line is just for logging? In any case, the error isn't returning - I dont think anything else has change and can't reproduce this again... sorry if that's unhelpful. As I'm only getting to spend a little bit of time on this project now compared to previously, I'm probably not understanding where I am up to with regard to finishing off the scene switch support (finally). I still want to support the state change via led on the scene switches - this appears possible as per my experiences in comments above - but I don't have the knowledge to understand what parts of the device config I changed which make this work, and which parts break the 'click' and state changes on MQTT.
Based on my tests and trials above - is there anything you can suggest I try? Thanks mate - I know you have a lot of other people asking for help and other projects going on. |
|
|
Once both target (switch) and source (scene switch) are bound in both directions, I do not get MQTT messages or Z2M logs when the source is switched - however, if switched seperately, or if I press any of the unbound scene switches, MQTT messages and logs are produced. Further, I still have the same issue - state is only one direction (bound in both directions). Switching the target switch to off leaves the source in the on state - though there is Z2M activity when the target is switched, unlike in reverse. If the source/scene switch is showing on, and I send " Let me know if this doesn't make sense or further tests you need me to do. Could the device config below be the issue?: |
|
The device config looks good, I'm wondering if the scene LED can be turned off remotely at all. |
|
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. |
wilmardo
pushed a commit
to wilmardo/zigbee2mqtt
that referenced
this issue
Sep 26, 2019
wilmardo
pushed a commit
to wilmardo/zigbee2mqtt
that referenced
this issue
Sep 26, 2019
wilmardo
pushed a commit
to wilmardo/zigbee2mqtt
that referenced
this issue
Sep 26, 2019
wilmardo
pushed a commit
to wilmardo/zigbee2mqtt
that referenced
this issue
Sep 26, 2019
Koenkk
added a commit
to Koenkk/zigbee-herdsman-converters
that referenced
this issue
Dec 23, 2019
…BT-A19-CCT-Bulb (#826) * 7.0.10 * Add Support for EcoSmart Bright White Bulbs (#200) * Update devices.js * Update devices.js * update * Bitron-Video Wall Thermostat (#199) * added Bitron Wall Thermostat * added Bitron fromZigbee convertes bitron_battery (should be usefull for all bitron battery powered devices) bitron_thermostat_att_report bitron_thermostat_dev_change * Update fromZigbee.js * Update devices.js * Update devices.js * Update devices.js * Update fromZigbee.js * Update toZigbee.js i changed the calculation of the input values so that you can also set half degrees. before: 21.3 -> 21.0 21.4 -> 21.0 21.5 -> 22.0 now: 21.3 -> 21.5 21.4 -> 21.5 21.5 -> 21.5 * Update fromZigbee.js * added temperature_display_mode + running_state * Update devices.js * Trailing spaces * Update fromZigbee.js * Update fromZigbee.js * Update fromZigbee.js * Update devices.js * Update devices.js * FB56-ZCW11HG1.2 (#202) * GLEDOPTO GL-B-008Z * HGZB-20-DE https://www.amazon.de/Intelligente-Steckdose-kompatibel-SmartThings-Steuerung/dp/B07GYG5GRP * Update devices.js * Update devices.js * Update devices.js * FB56-ZCW11HG1.2 https://uploads.tapatalk-cdn.com/20190106/dcf0f59343233342d004319d05c04bc0.jpg * FB56-ZCW11HG1.2 * FB56-ZCW11HG1.2 i miss this device * rebase * Update devices.js * Filter non-realistic WSDCGQ11LM and WSDCGQ01LM temperature reports. Koenkk/zigbee2mqtt#798 * Filter non-realistic WSDCGQ11LM and WSDCGQ01LM humidity reports. Koenkk/zigbee2mqtt#798 * 7.0.11 * Support E1524. Koenkk/zigbee2mqtt#102 * 7.0.12 * Update devices.js to include Nue HGZB-01A (#203) * Update device.js to include Nue HGZB-01A Device is a mains inline zigbee light controller with brightness. Amazon link: https://www.amazon.com/gp/product/B07FBD96DG/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 Added and tested device per: https://koenkk.github.io/zigbee2mqtt/how_tos/how_to_support_new_devices.html * remove extranious tab that fails check * Fixed the rest of the tabs - still figuring this out... sorry. * adding space back... * Update devices.js * Add RTCGQ11LM illuminance interval report. Koenkk/zigbee2mqtt#827 * 7.0.13 * Support TRADFRI wireless dimmer battery. Koenkk/zigbee2mqtt#792 * 7.0.14 * Add support for Gledopto Zigbee LED controller WW/CW Dimmer (GL-C-006) (#204) * Support 100.424.11. Koenkk/zigbee2mqtt#803 * Add device support for iCasa Zigbee 3.0 Dimmer (#206) * Add device support for iCasa Zigbee 3.0 Dimmer * Update devices.js * Refactors (#207) * Add Iris 3326-L motion and temperature sensor * Use scoped zcl-id * Only package needed files * refactor: Use a Map for findByZigbeeModel * Add `extend` attribute The attribute shallow-merges the model object, with the explicitly defined properties taking precidence Converted all uses of `generic` to `extend` format. * Fix missing color temperature from #207 * Hue power-on behavior (#209) * added Hue Power-on Converter tested with GU10. needs Firmware 1.46 hue_power_on_behavior // default / enable / disable / configure hue_power_on_behavior, // default = 1 // on - lamps on after power loss with configured brightness, color temperature, color // off - lamps off after power loss // recover - lamps on after power loss with last state hue_power_on_brightness // brightness when hue_power_on_behavior = on, same settings as brightness converter // default = 255 hue_power_on_color_temperature // color temperature when hue_power_on_behavior = on, same settings as colortemp converter // default = 366 to-do: hue_power_on_color (must be added by someone with appropriate bulb) * Update toZigbee.js * Hue specific settings generic hue settings with power-on converter * Update toZigbee.js * fixed 'null' values as discussed here: Koenkk/zigbee2mqtt#848 * Update fromZigbee.js * Update fromZigbee.js * Update toZigbee.js * Update devices.js * Update devices.js * fixed 'null' values in thermostat converters. (#210) * fixed 'null' values in thermostat converters. as discussed here: Koenkk/zigbee2mqtt#848 * Update fromZigbee.js * Update fromZigbee.js * Update fromZigbee.js * Update fromZigbee.js * Update fromZigbee.js * Update fromZigbee.js * 7.0.15 * Add devices.js to files. * 7.0.16 * Trim null characters on spaces when searching for zigbee model. Koenkk/zigbee2mqtt#810 * 7.0.17 * Fix linting error. * 7.0.18 * Update battery cfg for TRADFRI wireless dimmer. Koenkk/zigbee2mqtt#792 * 7.0.19 * Fix documentation for Xiaomi Wireless Wall Switch (#211) * Fix documentation for Xiaomi Wireless Wall Switch * Update devices.js * TRADFRI Driver 10W (#214) same device as TRADFRI transformer 10W but other name * ToZigbee onoff; don’t crash on wrong value type. #212 * Fix tradfri wireless dimmer report interval. Koenkk/zigbee2mqtt#792 * 7.0.20 * Add support for Sengled model E1A-AC2 (#215) * Add support for Sengled model E1A-AC2 Adding support for Sengled downlights (https://www.sengled.com.au/shop/element-downlight-single/) * Update devices.js * Trust Contact Sensor (CSW_ADUROLIGHT) invert logic (#221) Fixed an issue where contact ON on the device resulted contact:false MQTT-payload and vice versa. * Fix for: No converter available for 4713407 with cid genOnOff, type attReport and data {"cid":"genOnOff","data":{"onOff":0}} (#218) * Add support for OSRAM/Lightify Switch Mini (#219) * Added Support for OSRAM Smart Switch Mini AC0251100NJ * Lightify Switch Mini Support * CODE Tidy * Fixed comma dangle * Removed trailing space * Update fromZigbee.js * Update fromZigbee.js * Update devices.js * Update devices.js * Update devices.js * 7.0.21 * Fix crash when model null. Koenkk/zigbee2mqtt#887 * 7.0.22 * Fix xiaomi lock (#223) * feat(xiaomi_lock_report): recover reporting of error case 0x1107ffffffffffff This error message is sent by the Xiaomi / Vima smart lock when an unknown object (e.g. a lock pick) is introduced into the cylinder. * chore(xiaomi_lock_report): uniformize code comments * Support for Sylvania 71831, Adjustable White A19 Bulb (#224) * Support for RGB Mueller Licht: tint (#225) * added tint from Mueller Licht * Update devices.js * Added Müller Licht white bulbs (#229) * New devices: Heiman Water Sensor, Heiman Door Sensor * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * Improved support for HEIMAN devices * Fixed ; and style * Style fix * Updates * Fixed wrong bitshift * Added Müller Licht white bulbs * Added Müller Licht white bulbs * Refactor transtime to readAfterWriteTime (#227) * refactor transition times * Increased thermostat_system_mode readAfterWriteTime * Implemented thermostat enums (#226) * Implemented thermostat enums * Fixed linting issues * Hopefully no more linting problems * Fixed review comments * Fixed more uppercase * Update toZigbee.js * 7.0.23 * Fix for systemMode runningState enum implementation. (#234) * corrected runningStates * added runningMode added runningMode edited runningState * Update toZigbee.js removed comments that are described at documentation added runningMode (get) * Update common.js * Update fromZigbee.js * Update common.js * Update fromZigbee.js * Switch zcl-id to tarball * 7.0.24 * fixed var name. (#235) * NodeJS 4.* compatibility fix (#236) * Fix max interval (#237) Changed the maximum interval time. * Support HS1DS-E. Koenkk/zigbee2mqtt#911 * added Gledopto Smart RGBW GU10 (GL-S-003Z) (#240) * Update devices.js added Gledopto Smart RGBW GU10 (GL-S-003Z) * Update devices.js * Update devices.js * Enum fixes (#241) * Fixed reference to undefined enum objects. * Fixed issue with setting system_mode to "off". The key for "off" is 0 which would fool getKeyByValue into returning the "off" string as fallback value. * add hue/saturation support to light_color (#239) * add hue/saturation support to light_color * add hue/saturation support to light_color_colortemp * fix hue/saturation support to light_color_colortemp * Keep nodejs 4 support. * 7.0.25 * FLS-CT (#243) * ZBT-ExtendedColor * FLS-CT * Update devices.js * Update devices.js * added SLP2b Hive Active Plug (#245) * added SLP2b * tidy spacing * Update devices.js * Update devices.js * HS1SA fixes (#247) * Added fix for bad iasCieAddr registration * Added battery measurement converter * Added battery measurement registration * Added support for Salus SP600 Smart Plug (#248) * Add support for Hive HALIGHTDIMWWB22 (Bayonet mount) * Update devices.js * Added support for Salus SP600 Smart Plug * Salus SP600: Fix indentation * Rename EDP_power to generic_power * Add support for Gledopto devices with multiple lights in one controller (#249) * Add support for Gledopto devices with multiple lights in one controller * Add support for Gledopto devices with multiple lights in one controller - fix eslint error * 7.0.26 * Added support for Gledopto GL-B-007Z bulb (#251) * Add support for AduroSmart ERIA White and Color bulbs. (#250) * Add support for AduroSmart ERIA White and Color bulbs. * Update devices.js * 7.0.27 * Q-FLAG LED Panel, Smart-Home RGBW (#252) https://www.paul-neuhaus.de/shop/de/led-panel-smart-home-alexa-tauglich-100-110-39.html * Hs1 sa battery (#253) * Fixed battery calculation. Zigbee standard states that 200 = 100% * Added enrollment and ZoneID detection * add report handling to generic light_onoff_brightness (#258) * add report handling to generic light_onoff_brightness * Update devices.js * Update devices.js * Update devices.js * 7.0.28 * Simplify/cleanup some converters. * Add color color_temp report converter. * 7.0.29 * Fix typo * 7.0.30 * Fix state get converter. * 7.0.31 * Added handlers for Livolo (#256) * Added handlers for Livolo * Formatting corrections * Update fromZigbee.js * Update devices.js * Updates handlers for Livolo * Fixes * Update devices.js * Updates. * 7.1.0 * Add combined toZigbee color and colortemp converter. (#260) * Add support for AduroSmart ERIA White and Color bulbs. * Update devices.js * Add combined toZigbee color and colortemp convertor. This convertor is a combination of light_color and light_colortemp and can be used instead of the two individual convertors. When used to set, it actually calls out to light_color or light_colortemp to get the return value. When used to get, it gets both color and colorTemp in one call. The reason for the existence of this somewhat peculiar converter is that some lights don't report their state when changed. To fix this, we query the state after we set it. We want to query color and colorTemp both when setting either, because both change when setting one. This converter is used to do just that. We're using this convertor by default now in generic.light_onoff_brightness_colortemp_colorxy because it can't hurt. * Typos. * Added Eurotronic Spirit Zigbee thermostat (#254) * Added Eurotronic Spirit Zigbee thermostat * adjust Spirit Zigbee thermostat binding due to pr comments * fix linter errors * renamed specific attributes with eurotronic prefix, cleanup converters * update model and description to match convention for documentation * remove trailing space * remove trailing space * added postfix parameter to eurotronic converters * 7.1.1 * Fix Xiaomi Gas sensor density json attr (#263) * 7.1.2 * Introduce Ninja Smart plug to devices.js (#262) * Update devices.js * Intro-Ninja-Plug Introduced device entry for Ninja Smart plug from Ninja Block inc, including power metering and on/off support * Update devices.js * Ignore genGroups devChange. Koenkk/zigbee2mqtt#764 * Add support for AduroSmart ERIA Smart Wireless Dimming Switch (#264) * Add support for AduroSmart ERIA Smart Wireless Dimming Switch Switch returns event on button release. Hold not supported. Implemented as action sensor, returning actions on, off, up, down. Proprietary cluster PRs in zcl-id and zcl-packet need to be merged first. URL: https://adurosmart.com/products/adurosmart-eria-smart-dimming-switch-hub-required Image: https://static1.squarespace.com/static/5b73cad4aa49a1238f3c98ab/5b74eb9fb8a045d2f8b7d562/5b764e90562fa74310b76949/1534480018645/81825-Dimmng-switch-3.jpg?format=2500w * Update devices.js * HS3CG - Heiman gas sensor #257 (#265) * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * 7.1.3 * Update toZigbee.js (#266) Bugfix: Eurotronic zigbee thermostat support: localTemperatureCalibration was not written correctly to the device. * Immax LED E14/230V C35 5W TB 440LM ZIGBEE DIM (#268) * Add support for BOSCH RADON TriTech ZB Motion Sensor Model RFDL-ZB-MS (#267) * Update devices.js Add support for BOSCH RADON TriTech ZB Motion Sensor Model RFDL-ZB-MS * Update fromZigbee.js Add support for BOSCH motion sensor RADON TriTech ZB bit 0 is used to detect motion bit temper contact and bit 3 battery low * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * Update devices.js * Add support for Hue white ambiance suspension Fair (#269) * More custom attributes for Eurotronic SPZB0001 (#270) * Added Eurotronic Spirit Zigbee thermostat * adjust Spirit Zigbee thermostat binding due to pr comments * fix linter errors * renamed specific attributes with eurotronic prefix, cleanup converters * update model and description to match convention for documentation * remove trailing space * remove trailing space * added postfix parameter to eurotronic converters * Eurotronic SPZB0001: more custom attribtes, listen to devChange instead of attReport, rename eurotronic_16386 * Update ikea tradfri remote setup link. * Lock zcl-id. * 7.1.4 * Multiple Gledopto transition by 3.3. Koenkk/zigbee2mqtt#1047 * 7.1.5 * LED1624G9 doesn't support color temperature. Koenkk/zigbee2mqtt#678 * Added support for Innr RS 225 bulb (#271) * Add E1746. Koenkk/zigbee2mqtt#832 * 7.1.6 * Fix gledopto color and color_temp converter. Koenkk/zigbee2mqtt#1064 (comment) * 7.1.7 * Add E1743 Koenkk/zigbee2mqtt#997 (#273) * Experimental support E1743. Koenkk/zigbee2mqtt#997 * Add battery support and fix model. Koenkk/zigbee2mqtt#997 * Add missing battery converter. Koenkk/zigbee2mqtt#997 * Add ignore_power_change. Koenkk/zigbee2mqtt#997 * Increase WXKG01LM long click delay. This makes detecting long clicks more reliable. Sometimes a `long` is detected when it's actually a `single`. * Support YRD426NRSC. Koenkk/zigbee2mqtt#1032 (#274) * Experimental support YRD426NRSC. Koenkk/zigbee2mqtt#1032 * Update fromZigbee.js * 7.1.8 * Add Osram BR30 RGBW LED to HA * Add support for TRADFRI bulb E27 WS opal 1000lm light LED1732G11 (#277) * SmokeSensor-EM (#272) * tint remote, 3 keys (#279) * tint remote, 3 keys activated On-Off and brightness up/down * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * Update links. * 7.1.9 * Innr RB 265 E27 Bulb support (#280) * Fixed HS1SA battery report (#282) * 7.1.10 * Updated devices.js with support for ELKO Dimmer 316 GLED RF. (#283) * Updated devices.js with support for ELKO Dimmer 316 GLED RF. * Update devices.js * Update devices.js * Update devices.js * Additional setup is not required anymore. * Decoupled mode for Xiaomi wired wall switches (#287) * Added LivingWise ZigBee Smart dimmer Switch. Model#: LVS-ZB500D (#288) * Added LivingWise ZigBee Smart dimmer Switch. Model#: LVS-ZB500D * Update devices.js * Update devices.js * Update fromZigbee.js * added samsung smartthings plug (#286) * added samsung smartthings plug * Update fromZigbee.js * Update devices.js * Update toZigbee.js * Update toZigbee.js * didn't need custom toZigbee converter * didn't need custom toZigbee converter * tint remote (ZBT-Remote) Color keys (#284) * tint remote, 3 keys activated On-Off and brightness up/down * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * tint remote (ZBT-Remote) Color keys Implementation of color wheel and color temp, brightness with stesize and transition-time * syntax power-key * Update fromZigbee.js change on/off-button to action:'on' and 'off' * Update fromZigbee.js * Update devices.js * Update fromZigbee.js * Update devices.js * [Xiaomi wired switch] Parse operation mode response (#290) * Add GL-FL-004TZ. #293 * Added support for new Philips Hue Outdoor Motion Sensor (#294) * Update devices.js Added support for the new Philips Hue Outdoor Motion Sensor * Update devices.js * Add ST218. #295 * Add ' generic_state_multi_ep' to support Nue branded switches (#298) * Update devices.js with support for Nue 'FB56+ZSW1HKJ1.7' (#297) * Fix problem with FB56+ZSW05HG1.2' (HGZB-01A) handler (#299) * Fix problem with FB56+ZSW05HG1.2' (HGZB-01A) handler FB56+ZSW05HG1.2' (HGZB-01A) This device was already supported and works, however error message below. I've added "fz.ignore_onoff_change" to the device handler and this fixes the problem (if it is a problem?), but wanted to check with you @Koenkk that it's okay to ignore the 'genOnOff' message? ```zigbee2mqtt:debug 2/23/2019, 1:31:59 AM Received zigbee message of type 'devChange' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'FB56+ZSW05HG1.2' (0x00124b000ae5fa3e) zigbee2mqtt:warn 2/23/2019, 1:31:59 AM No converter available for 'FB56+ZSW05HG1.2' with cid 'genOnOff', type 'devChange' and data '{"cid":"genOnOff","data":{"onOff":0}}' zigbee2mqtt:warn 2/23/2019, 1:31:59 AM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:debug 2/23/2019, 1:32:23 AM Received MQTT message on 'zigbee2mqtt/0x00124b000ae5fa3e/set' with data 'ON' zigbee2mqtt:info 2/23/2019, 1:32:23 AM Zigbee publish to device '0x00124b000ae5fa3e', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - null``` I also moved the " // Smart Home Pty" devices below // Nue as I believe they are probably the same and before long you might get double ups. * Update devices.js * Update devices.js * Update devices.js * Update devices.js * Update devices.js * Update devices.js * Add support for Keen Home smart vent (#276) * - added support for Keen Home smart vent * - added more from-zigbee handler for keen vent - added more model# for keen vent * Update devices.js * - updated reporting interval and only handle attReport and ignore devChange on temperature and pressure * - added cover_position handler * - added cover_position to keen home toZigbee * - added transtime to cover_position.set - changed key to state for cover_position * Update toZigbee.js * Update devices.js * - added cover_state and cover_position fromZigbee handler - made changes to cover_open_close toZigbee handler so it'd work correctly * - added devChange fromZigbee handler for keen home pressure, temperature and battery - updated cover_position and cover_position_report fromZigbee handler to return both position and state (state is determined by position now) - updated cover_open_close to only change currentLevel - adjusted attReport interval for kee home vent * - removed reporting config * - fixed lint errors * 7.1.11 * Add device to support Trust Remote control ZYCT-202 (#300) * Add device to support Trust Remote control ZYCT-202 Koenkk/zigbee2mqtt#635 * Add the concerters for the Trust Remote control ZYCT-202 The groupid has been processed in the button press. So you have the action and the selector mode in 1 state value and can easily be used in a Home Assistant Automation state rule. * Add the concerters for the Trust Remote control ZYCT-202 The groupid has been processed in the button press. So you have the action and the selector mode in 1 state value and can easily be used in a Home Assistant Automation state rule. (Koenkk/zigbee2mqtt#635) * Update devices.js Fixed spaces line 1941 * Update devices.js Fixed the maximum line length of 120 max-len * Separated the action and groupid in the return rules Have separated the action and groupid in the return rules... * Update fromZigbee.js * Support TRADFRI wirelessm motion sensor E1525. Koenkk/zigbee2mqtt#247 * 7.1.12 * Add support for AXIS Gear window shade motor (#301) * - added support for AXIS Gear window shade motor * - updated AXIS Gear model * Update devices.js * Support HGZB-42-UK. #278 * 7.1.13 * Change up and down in Ikea Outlet Switch (#302) * TRADFRI dimmer change maximum response time. (#305) * Update action color wheel structure. * tint remote, 3 keys activated On-Off and brightness up/down * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * tint remote (ZBT-Remote) Color keys Implementation of color wheel and color temp, brightness with stesize and transition-time * syntax power-key * Update fromZigbee.js change on/off-button to action:'on' and 'off' * Update fromZigbee.js * Update devices.js * Update fromZigbee.js * Update devices.js * tint remote, changed to standard return values, changed calculations of color to franctions. * adopt to master * adopt master changes * Update fromZigbee.js * Update fromZigbee.js * fixed thermostat_setpoint_raise_lower (#308) setpoint_raise_lower is client-to-server only. There is no need for a "get". To get the setpoint use: occupied_heating_setpoint or unoccupied_heating_setpoint * Added illuminance measurement for SML002 (#307) * Added illuminance measurement Added illuminance measurement for Philips outdoor sensor SML002. * Update devices.js * new: Hue Flourish ceiling light (#309) * new: Hue Flourish ceiling light * Update devices.js * Cosmetic updates. * Separate moveToLevelWithOnOff and moveToLevel converters. Koenkk/zigbee2mqtt#176 * 7.2.0 * updated reporting confg for Keen Vent and AXIS Gear (#310) * - updated reporting configuration for Keen Vent - updated AXIS Gear to start report its position and battery level * Update devices.js * Update zcl-id. * Add philips cluster for hue dimmer (#311) * Add philips cluster for hue dimmer * Modify philips hue dimmer * Modify philips hue dimmer * Modify philips hue dimmer * Update fromZigbee.js * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * 7.2.1 * Check if message has onOff for state converters. Koenkk/zigbee2mqtt#1176 * 7.2.2 * Additional model name for Osram LIGHTIFY Flex RGBW (#314) * Update devices.js (#315) * Support ISW-ZPR1-WP13. Koenkk/zigbee2mqtt#768 * 7.2.3 * Also check for realistic values in WSDCGQ01LM_WSDCGQ11LM_interval. Koenkk/zigbee2mqtt#798 * 7.2.4 * Add support for Philips Hue Sana (#316) Signed-off-by: markus1540 <markus1540@gmail.com> * Update fromZigbee.js with ignore_light_brightness_change (#318) Updated to support Nue Dimmer Switch (FB56+ZSC05HG1.0) * Support HGZB-02A. Koenkk/zigbee2mqtt#1179 * Update devices.js with FB56+ZSC05HG1.0 (Nue Smart Dimmer Switch) (#317) * Update devices.js with FB56+ZSC05HG1.0 (Nue Smart Dimmer Switch) * Renamed FB56+ZSC05HG1.0 model ID to correct ID. * Update devices.js * Add action for ICTC-G-1. Koenkk/zigbee2mqtt#1191 * 7.2.5 * Clarify that the GE Link bulb could be BR30 or A19 (#320) I noticed that my A19 GE Link bulbs are sharing the BR30 description. From what I can tell, they both share same model number: Koenkk/zigbee2mqtt#1161 * Update devices.js for 'FB56+ZSW1HKJ1.7' with new button decriptions (top/bottom) (#321) * Support for 'FB56+ZSW1IKJ1.7' 3-gang Nue Smart Switch (#319) * Support for 'FB56+ZSW1IKJ1.7' 3-gang Nue Smart Switch Confirmed working, but please check my parentheses etc @Koenkk .... I get double MQTT feedback. It would also be great if you could support 'top' and 'bottom' in https://github.com/Koenkk/zigbee2mqtt/blob/master/lib/extension/devicePublish.js#L8 - is this a possibility? This would make more sense for countries like Australia where switches are mounted vertically, and give the option for the handler to match the local orientation of the device. * Changed FB56+ZSW1IKJ1.7 to include new button descriptors (top/bottom) * Fix missing converters for philips hue dimmer (#322) * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * re-pair fix and add multiple clicks for hue dimmer (#323) * added multiple (single/double etc) click for hue dimmer * fix re-pair issue for hue dimmer * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * Fix gledopto converter crash. Koenkk/zigbee2mqtt#1209 * 7.2.6 * Ignore basic dev change for all lights. Koenkk/zigbee2mqtt#1064 * Check if data has currentLevel attribute in brightness converters. Koenkk/zigbee2mqtt#1212 * Update devices.js for Nue HGZB-41 (#325) The Nue 1 gang smart switch model 'HGZB-41' identifies as 'FNB56-ZSW01LX2.0', the same as previously listed 'HGZB-42-UK' 2 gang switch. Updated model / description to allow for both. * add Nyce-3043 and additional Smartthings devices (#324) * add Nyce-3043 and additional Smartthings devices * Update devices.js * Update fromZigbee.js * 7.2.7 * Improve AC0251100NJ actions consistency Improve AC0251100NJ actions consistency * extend E1524 with genPowerCfg reporting (#326) * extend E1524 with genPowerCfg reporting * Add Whitespace to fix failured travis check * Update devices.js * Update devices.js * Update README.md (#327) Link to zigbee2mqtt. * Bitron av2010/34 (#328) * AV2010/34 devices.js Part * add AV2010_34_click + generic ignore_power_report * Update devices.js * Add extra guard to xiaomi_contact_interval. Koenkk/zigbee2mqtt#1219 * Update dependencies. * 7.2.8 * Update devices.js to support FNB56-ZSW03LX2.0 - Nue 3 gang smart switch v2.0 (#330) * Update devices.js to support FNB56-ZSW03LX2.0 - Nue 3 gang smart switch v2.0 Endpoints changed between versions. Possibly using newer Zigbee protocol now also * Update devices.js * Add Securifi Peanut Smart Plug (#331) * Add Securifi Peanut Smart Plug Measurements not supported/tested as they require a firmware upgrade (?). Switch works though. See Koenkk/zigbee2mqtt#809 * Update devices.js * Update fromZigbee.js to support Nue Scene Switches (#332) * Add 'FTB56+ZSN15HG1.0' & 'FB56+ZSN08KJ2.3' Nue Scene Switches (#333) * Add 'FTB56+ZSN15HG1.0' & 'FB56+ZSN08KJ2.3' Nue Scene Switches * Update devices.js * Update devices.js to support FB56+ZSW1HKJ2.5 2 gang Nue smart switch (#334) * Update devices.js to support FB56+ZSW1HKJ2.5 2 gang Nue smart switch This has the same model number HGZB-042 as FB56+ZSW1HKJ1.7 * Update devices.js * Add support for Visonic MCT-350 contact sensor. (#336) * Add support for Visonic MCT-350 contact sensor. * Update devices.js * Update fromZigbee.js * Add support for OJB-CR701-YZ Gas and CO sensor (#338) * Add statuschange converter for OJB-CR701-YZ * Add OJB-CR701-YZ to devices.js * Fix eslint * amend * fix: Set proper vendor for OJB-CR701-YZ * Update devices.js * Update fromZigbee.js * Update devices.js * Update devices.js * Update fromZigbee.js * Add more ignore converters. * Changed to correct external model details (#335) * Changed to correct external model details * Fix model numbers * Update devices.js * Add support for Sengled E12-N14 (BR30) Light * Add support for Sengled E12-N14 (BR30) Light * Update devices.js * Update devices.js * Allow type to be an array. * 8.0.0 * Don’t convert readRsp for ZNLDP12LM. Koenkk/zigbee2mqtt#1240 * 8.0.1 * Add alias for 4058075036185. Koenkk/zigbee2mqtt#1245 * Ignore false ZNCZ02LM and ZNLDP12LM messages. * 8.0.2 * Add Support SwannOne Key Fob SWO-KEF1PA * Modify payload to be more compatible with Home Assistant * Sunricher (#340) * Sunricher * Update devices.js * Update devices.js (#341) * Adding `wireless mode` support for Xiaomi Switches QBKB11LM/QBKG12LM (#342) * Update fromZigbee.js rename methods for xiaomi aqara switch wireless mode * Update devices.js wireless mode for aqara wired switches * Update devices.js * Add 2 additional Nue models FB56+ZSW1GKJ2.5 & FTB56+ZSN16HG1.0 (#348) Again .. another overlap of model but with different Zigbee ID. Entered differently per device. Tidied up descriptions further. * Added Smartthings devices (#344) * add Nyce-3043 and additional Smartthings devices * Update devices.js * Update fromZigbee.js * additional Smartthings devices * added converters * updated 3315-S * added st_leak_change * updated 3305-S, ignore change on genpower * Update devices.js * Update devices.js * Update devices.js * Update fromZigbee.js * Add Support SwannOne Key Fob SWO-KEF1PA (#346) * Add support for Sengled E12-N14 (BR30) Light * Add Osram BR30 RGBW LED to HA * Update devices.js * Add Support SwannOne Key Fob SWO-KEF1PA * Modify payload to be more compatible with Home Assistant * Update devices.js * Update fromZigbee.js * Update fromZigbee.js * 8.0.3 * Add converters for ignoring 'diagnostic' and 'genscenes' dev changes * Implement no_occupancy_since for RTCGQ01LM and RTCGQ11LM. Koenkk/zigbee2mqtt#1195 * 8.0.4 * Add converters for ignoring 'diagnostic' and 'genscenes' dev changes (#350) * Add support for Sengled E12-N14 (BR30) Light * Add Osram BR30 RGBW LED to HA * Update devices.js * Add support for Sengled E12-N14 (BR30) Light * Update devices.js * Add Support SwannOne Key Fob SWO-KEF1PA * Modify payload to be more compatible with Home Assistant * Add support for Sengled E12-N14 (BR30) Light * Update devices.js * Add Support SwannOne Key Fob SWO-KEF1PA * Modify payload to be more compatible with Home Assistant * Add converters for ignoring 'diagnostic' and 'genscenes' dev changes * Sengled: Add configure feature for reporting 'genOnOff' and 'genLevelCtrl' Wireshark reported Sengled's own hub configured the bulbs for reporting on/off states and brightness. * Osram/Sylvania: Add vendor specific functions NOTE: Will require updated zcl-id and zcl-packet defs: qosmio/zcl-id@859d657 qosmio/zcl-packet@f74d92c Two new functions: * osram_set_transition: Allows setting a default transition time whenever lights are turned back on manually. * osram_remember_state: Allows the end device to remember its last brightness/hue/color/etc state when light is turned on manually. Currently it resets to default. Also adding options to the ignore list. - fz.ignore_genIdentify_change - fz.ignore_diagnostic_change - fz.ignore_genscenes_change * Fixing eslinting issues. * Sylvania/Osram: Configure BR30, A19, A19 RGBW to report on/off * Revert 'configure' options for reporting. Being worked on upstream Koenkk/zigbee2mqtt#1064 * FIX: Key was incorrectly defined as a list of options. * Revert 'configure' options for reporting. Being worked on upstream See: Koenkk/zigbee2mqtt#1064 * FIX: duplicate keys that were already merged. * FIX: Remove duplicate keys that were already merged. * eslinting fixes * Enhancements to ZBT-CCTSwitch-D0001 + add new device Ecosmart-ZBT-A19-CCT-Bulb * eslint fixes * Add color_temp hold/release ZBT-CCTSwitch-D0001 Also updates the brightness hold/release logic. * FIX devices.js Fixes the following error FAIL test/index.test.js index.js ✓ Find device by model ID (6ms) ✓ Find device by model ID with strange characters 1 (1ms) ✓ Find device by model ID with strange characters 2 ✓ Find device by model ID with strange characters 3 (1ms) ✓ Find device by model ID without strange characters (1ms) ✓ Find device by model ID null (1ms) ✕ Verify devices.js definitions (132ms) ● index.js › Verify devices.js definitions TypeError: Cannot convert undefined or null to object at Function.keys (<anonymous>) 63 | const converter = device.fromZigbee[converterKey]; 64 | > 65 | const keys = Object.keys(converter); | ^ 66 | verifyKeys(['cluster', 'type', 'convert'], keys, converterKey); 67 | 68 | if (4 != converter.convert.length) { at keys (test/index.test.js:65:37) at Array.forEach (<anonymous>) at forEach (test/index.test.js:62:44) at Array.forEach (<anonymous>) at Object.forEach (test/index.test.js:47:17) * Rename 'color_temp' to 'colortemp' for consistency Many automations in HA are set up to split '_' based on `attribute`, `direction`, `action`. Trying to keep the splits consistent. * Tidy up code and logic for CCTSwitch * FIX: Change 'button' to 'click' for HA compatibility * Update devices.js * Update devices.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com> Co-authored-by: boojew <boojew@gmail.com> Co-authored-by: Chrischi- <Chrischi-@users.noreply.github.com> Co-authored-by: arteck <6681528+arteck@users.noreply.github.com> Co-authored-by: mkventure <42322917+mkventure@users.noreply.github.com> Co-authored-by: netztrip <dave-pbqr@netztrip.de> Co-authored-by: Sander <3908728+sheyden@users.noreply.github.com> Co-authored-by: Mihail Malo <qm3ster@gmail.com> Co-authored-by: Paul Tiedtke <PaulTiedtke@web.de> Co-authored-by: pnewnam <register.pn@gmail.com> Co-authored-by: Kryzek <dr.drake@gmail.com> Co-authored-by: James Tutton <github@comexe.co.uk> Co-authored-by: Adán SDPC <adan@stampery.com> Co-authored-by: Daniel Lashua <daniel@inklog.net> Co-authored-by: Niklas <Gurkengewuerz@users.noreply.github.com> Co-authored-by: Merlin Schumacher <merlin.schumacher@gmail.com> Co-authored-by: Simon Rasmussen <zetlon@gmail.com> Co-authored-by: Ilya Kirov <kirovilya@gmail.com> Co-authored-by: Andrey <pck.forex@gmail.com> Co-authored-by: KernSani <oli.merten@gmail.com> Co-authored-by: Sebastian Raff <hobbyquaker@gmail.com> Co-authored-by: simonses1 <45721550+simonses1@users.noreply.github.com> Co-authored-by: Gustav Johansson <gustav@neer.se> Co-authored-by: MarkAdamson <markadamson83@gmail.com> Co-authored-by: zipbee <46903217+zipbee@users.noreply.github.com> Co-authored-by: Maxim Milakov <maxim.milakov@gmail.com> Co-authored-by: Giel de Nijs <gi-el@users.noreply.github.com> Co-authored-by: jbmbn <47156243+jbmbn@users.noreply.github.com> Co-authored-by: ptvo <33662022+ptvoinfo@users.noreply.github.com> Co-authored-by: Martin Helff <martin@helff.net> Co-authored-by: Roman Zhukov <bag4spam@gmail.com> Co-authored-by: asgothian <45667167+asgothian@users.noreply.github.com> Co-authored-by: Mad-Andy <47221633+Mad-Andy@users.noreply.github.com> Co-authored-by: pfischbach <3976786+pfischbach@users.noreply.github.com> Co-authored-by: way2many <40859898+way2many@users.noreply.github.com> Co-authored-by: Russell Joyce <russell@russellj.co.uk> Co-authored-by: Daniël Kluivingh <dkluivingh@gmail.com> Co-authored-by: MoskitoHorst <horst.wessel@moskito-gis.de> Co-authored-by: Srdan Suka <srdan.suka@gmail.com> Co-authored-by: fredrikgk <46903952+fredrikgk@users.noreply.github.com> Co-authored-by: Ruslan Sayfutdinov <ruslan@sayfutdinov.com> Co-authored-by: Aleksey <26031505+dev-abo@users.noreply.github.com> Co-authored-by: Marc <marc-gist@users.noreply.github.com> Co-authored-by: jonnycastaway <jonny.castaway@gmx.net> Co-authored-by: highground88 <emaillj@hotmail.com> Co-authored-by: Joe Lu <snjoetw@gmail.com> Co-authored-by: hwijers <45356188+hwijers@users.noreply.github.com> Co-authored-by: papanirual <46861405+papanirual@users.noreply.github.com> Co-authored-by: Torsten <github@kryger.de> Co-authored-by: Gergely Markics <5822419+ugrug@users.noreply.github.com> Co-authored-by: Cameron Bulock <cameron@bulock.com> Co-authored-by: Andreas Seiderer <22220407+andreas-seiderer@users.noreply.github.com> Co-authored-by: Markus Goy <markus1540@users.noreply.github.com> Co-authored-by: Marc Seeger <mail@marc-seeger.de> Co-authored-by: Rene <renehonig@gmail.com> Co-authored-by: Oliver <932481+tb-killa@users.noreply.github.com> Co-authored-by: pixel::doc <pixeldoc2000@users.noreply.github.com> Co-authored-by: Roger D <roger-@users.noreply.github.com> Co-authored-by: jace <jace.wiseman@gmail.com> Co-authored-by: Frank Wammes <FrankZZ@users.noreply.github.com> Co-authored-by: Eduardo <eduardo@edubox.org> Co-authored-by: Hai Phan <pataha@users.noreply.github.com>
qosmio
pushed a commit
to qosmio/zigbee-herdsman-converters
that referenced
this issue
Dec 25, 2019
|
Hi, I would like some help with some of my Feibit Zigbee switches. I have setup Home Assistant 0.117.6 on Raspberry Pi 4b 4gb and have installed zigbee2mqtt 1.16.1 and mosqito broker 5.1. I am using Phoscon Raspbee II as my zigbee receiver with the latest firmware 26660700. I have got the following Feibit devices and they all install correctly but the device is not refreshing the state automatically. i,e if I physically switch on the switch the state in zigbee2mwtt and HA will still show as off. can someone please help me to get this working properly. I have aslo got some 3A Neu dswitched and they seem to work properly. Also the dimmer switch above will crash when trying to change the brightness. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
I think I've hit a snag and would appreciate some tips if someone could? It's been quite a mission just to get this far, I'm not very experienced in linux and even getting a machine up and running wasn't much fun.
I've taken two " 'Nue' 2 gang smart switches " off the supplied 'Nue' hub, and believe I have updated the 'devices.js' appropriately as they are being detected (copy of terminal below). Here's the model info lines from both entries in the 'devices' file:
zigbeeModel: ['FB56+ZSW1HKJ2.5']and
zigbeeModel: ['FB56+ZSW1HKJ1.7']Funnily enough I think these are the same model 2 switch devices.. Perhaps one is a later revision? Regardless, this is the two switch model. I am yet to test on the 1 switch, 3 switch, dimmer and also the 1 and four button 'scene' switches I have just installed. PRODUCT LINK
Once the 'devices.js' file is updated, and zigbee2mqtt is restarted, I'm struggling to see any immediate messages when the switches are turned on and off - there doesn't seem to be anything coming through, and no sort of pattern reflecting how I've switched them on/off.
Where should I go next?
I don't know if this is helpful or not, but others seem to have been attaching these switches to the SmartThigns hub, via a similar detection method which is supplied by the distributor - would this be useful? LINK TO PDF
Thanks!
PASTEBIN DUMP
The text was updated successfully, but these errors were encountered: