I’m completely new to Home Assistant and have no prior experience with it. I recently purchased a Tuya TS0601_TZE200_7bztmfm1 CO detector (Tuya TS0601_smart_CO_air_box control via MQTT | Zigbee2MQTT) and connected it via Zigbee2MQTT. To test its functionality, I placed it in a sealed container and used incense sticks to simulate smoke. However, the ppm value remained at 0ppm and did not change.
Now I’m wondering whether the CO detector is defective or if I made a mistake during the integration with Home Assistant. Do I need to configure anything else in Home Assistant to get the CO detector working properly?
does your device expose entities in z2m? (it’s the tab to the right from where you took your screenshot)
Tuya devices: they use zigbee but that doesn’t mean they play nice with the standard
next time you buy a device, check if it works/is supported
Apparently, TS0601 doesn’t specify the device itself and if you do a search here on the forum, you will get multiple threads with issues related to that ID.
Many users steer away from Tuya because of difficulty to integrate them in HA.
Most CO detectors don’t go off unless it’s so many ppm for so long(alarm only). This device appear to be level reporting but id still recommend leaving it near a large co-source for over an hour to see what happens.
after a quick skim read of a git issue with this ( #12622) I fear it may be an alarm only and ha just created the 0ppm entity because.
Have you tried watching it directly from an mqtt client?
Also I urge everyone to test their home fire, gas, and co detectors including the battery(power outages happen, sensors are only rated for 5 years!)!
Thank you for your help. I have now ordered a Fibaro CO detector with Z-Wave. This is DIN EN 50291 certified. I hope it will deliver the desired result. I’ll let you know as soon as I have news.
Did you conduct a search here on the forum (or elsewhere) because I have seen topics about devices that just don’t live up to what is expected from an environmental sensor.
I recently received the Fibaro CO detector and connected it to Home Assistant via Z-Wave. It provides a lot of entities, but unfortunately, I don’t fully understand their meanings yet.
I’ve set up an automation that turns off the smart plug for the range hood when 50 ppm is detected. During my test with an enclosed box and incense sticks, everything worked well. However, I have the feeling that the update interval for the values is too long. Does anyone know if it’s possible to set a shorter update interval?
Additionally, when the CO detector triggers, Home Assistant only shows the ppm value, but not that the CO detector has been triggered. Perhaps some of you have more experience and could assist me with the configuration.
Hi glad to hear you got another one that works better.
Can you share the entities it does create, possibly a photo of it in the states of dev tools?
Update Interval
Z-Wave devices often have a configurable polling interval, but this depends on:
Device Configuration Options: Some devices allow adjusting the frequency of updates (e.g., thresholds for reporting ppm changes).
Z-Wave Polling Settings: Home Assistant’s Z-Wave integration lets you manually set polling for devices, though this can increase network traffic.
Steps to Adjust Update Interval:
Check Configuration Parameters:
Go to Settings > Devices & Services > Z-Wave > Manage Nodes.
Select your Fibaro CO detector and look for configuration parameters related to reporting intervals or thresholds.
Adjust these values if available (e.g., lowering the ppm change threshold for quicker reporting).
Enable Polling (If Parameters Are Unavailable):
Navigate to your Z-Wave device configuration in Home Assistant.
Set a polling interval for the sensor.co_detector_co_level entity. For example, you might poll every 30 seconds, but use this sparingly as it can increase Z-Wave network traffic.
Alarm Indication
Use a Binary Sensor:
Look for a binary_sensor entity associated with the CO detector.
If none exists, you can create a template binary sensor based on the sensor.co_detector_co_level value:
Use this new binary sensor to trigger actions when the CO level exceeds your threshold:
yaml
Copy code
automation:
- alias: "Turn Off Range Hood When CO Detected"
trigger:
- platform: state
entity_id: binary_sensor.co_alarm_triggered
to: 'on'
action:
- service: switch.turn_off
target:
entity_id: switch.range_hood
I realize this was some time ago, my apologies…but sometimes those cheap CO2 detectors aren’t actually what they claim. Chinese manufacturers like to use a generic alcohol sensor in these, and either report random reads or nothing at all. Those multi-gas sensors that were on the market earlier this year were nothing more than a cheap ethanol sensor.
Alcohol sensors tend to be larger devices with a mesh top, whereas CO2 sensors are smaller units encased in metal that do not have a mesh top. May be worth opening your original device to see what’s inside, if you weren’t able to get it working.
