It has always worked for me until I upgraded to 2022.2.2.
Battery_low has a “false” state.
However linkquality and smoke is “null”. Thats why both binary sensors are “Unknown” is HA.
Do you know how to test the smoke detectors? Never tried it before 
SHoul dbe a good idea to check it it’s really working in HA in case of fire.
Seems all was working well. However in the last update the binary sensor got an additional “unknown” state.
After putting the smoke sensor in test all states changed correctly. And afterwards it returned to off instead of null. Something to do with settimg an initial state I guess. Problem solved 
Hi Guys,
I’m fairly new in home assistant and I’m playing around with it for a couple of weeks now and liking it a lot.
Because my smoke detectors needed to be replaced I thought why not replace them with smart ones. I allready have a conbee II stick so zigbee smoke detectors would be nice.
Also based on this thread I bought a woox R7049 to do some tests, installed the zigbee2mqtt addon.
I put the smoke detector in “pair mode” ( the red light on top is flashing)
But whatever I do, I can’t pair the smoke detector with zigbee2mqtt. nothing is discovered, noting in debug log. To see if zigbee2mqtt was working at all I also paired a smart plug and that was discovered without issues.
Could you please help me, figure this out?
Did you putt zigbee2mqtt in pairing mode also (clicking on the right top of the zigbee2mqtt addon : “Allow all”?
Hi Tim,
Yes in zigbee2mqtt pairing mode was on, the smart plug paired with zigbee2mqtt in just a few seconds.
BIG WARNING!!
I implemented the fire alarm woox R7049 in Home Assistant and the pairing worked fine. I could trigger the alarm with the test button on the device and I could automate what would happen if they were triggered.
Then one evening we forgot to open the damper on the fireplace and filled the room with smoke. The alarm did not react. It turned out that you have to activate the alarm while connected to the woox zigbee hub, with the woox app, otherwise they won’t react to fire.
So I returned them to get my money back. I don’t want to think about what would happen in case of a real fire.
So make sure that your alarms are initiated properly or claim your money back! I would never trust them. A fire alarm shall not have the option not to react on fire. Even if you have initiated it, It could be set to no reaction by mistake without anyone knowing about it.
That is a very interesting tale. Thanks.
Thanks for this experience! Can anybody else confirm this or could this be a defect? As the smoke detector is EN 14604 certified I would assume it should work without any registration or activation.
Hi all, I recently bought a few R7049 units and this post triggerd me, Thanks for that
I am very interested what the experiences are from others with this device.
Initially everything seems to work fine during adoptation into the network.
Now I am trying to setup advance features like proper status reporting in the UI, linking of devices (if one goes off trigger the rest), silencing etc…
while playing around with them setting the actions “test_alarm” and “silence_alarm” seem to work fine, but not tested with real smoke yet.
Also not statuses are reported properly, also not after activating all possible actions, will investigate a bit further and report back here.
My setup is
P.S. looked up the website and there they state that device can be connected to most gateways, implying that it should work with our setups. (About Us). Contacted them with the request to share detailed instructions.
You say a lot but give no detail or logs.
Hi,
This is the output in MQTT, my conclusion is that the device itself does not report back the statuses that are now defined as null, all these values are read-only properties and must be set by the device.
“battery_level”, “test_alarm_result” and “linkquality” seem to be reported correctly.
The “alarm”, “silence_alarm” and test_alarm" seem to work also properly.
{
"alarm":false,
"battery_level":"high",
"battery_low":null,
"fault_alarm":null,
"linkquality":184,
"silence_siren":false,
"smoke":null,
"test_alarm":false,
"test_alarm_result":"check_success"
}
Any of you have the same device? What is reported for “smoke”, “battery_low” and “fault_alarm”?
Seems OTA is not supported so unable to check on FW version of the devices.
I guess,
“smoke”: null, indicates that there is no smoke now;
“battery low”: null, indicates that it is self-checking if the battery is low, and if so, it will send a reminder;
“fault alarm”: null, indicates that it is self-checking whether there is a fault alarm.
I also bought the Woox-R7049 and this evening I installed it in Home Assistant.
It is connected with the Zigbee-2-Mqtt addon.
Everything is working fine. I even simulated a real fire alarm, by burning a piece of newspaper.
You have the option “silence_siren”, and when you choose this, then the smoke sensor is quiet and you have to do something with an automation to warn and alarm. But of course it is better not to silence the sensor.
I couldn’t find any info about Woox R7063 Smart Wall Light Switch, so I bought it. It is recognized as TuYa TS0001 in zigbee2mqtt and works as expected! Automations, here we go!
The On/Off status and button is shown, one can set power_on_behavior with values “off”, “previous”, “on”.
I am using mine with home HVAC (Aldes ES300-HE, it said it needed “2A Inductif”, “5A Resistif”), this one should be up to 800W = 3.63A via 220V, enough power.
Just got the WOOX R6079 Smart two-way garden socket.
The manual states; Ensure the smart garden socket is quickly flashing (2 times per second). If the (WTF) SMART CEILING LIGHT isn’t flashing: press ON/OFF until the smart garden socheth starts to flash…
What ceiling light and which socket+h?
It has a kind of WiFi button on the top, but whatever way I press, no flashing at all and no auto-discovery in any way…
Has someone got this item and got it to work?
Are they still working? Can’t get my Woox R7049 (smoke detectors ) to work with ZHA , tried numerous Quirks with no success. Pairing always works, after pairing nothing else will be received …
Unit reports as _TZE200_aycxwiau
There are numerous devices described in this thread, and I am not sure everyone is talking about the same device.
They are still working fine. Switched to Zigbee2mqtt a couple of weeks ago, that works fine as well. Actually triggered the alarm on ZHA a couple times while cooking, automations ran fine. Om Z2M you get a couple more options as well, like testing the alarm. It shows up under the same modelname as yours, should work fine with ZHA without any quirks…