Anyone with experience in these? How do you like it. What is your use case? Any other recommendations make/model wise?
I have it and I was pretty happy with it in regards to accuracy and the frequency of the reporting... Until I realized that it is one of the ***** devices that was congesting my Z-wave network, threatening my WAF to become dangerously low...
It may be my Z-wave network specific issue, but at the moment I have it excluded and turned off. Unfortunately, I can't find Zigbee equivalent for the moment.
1 Like
What about this?
1 Like
In Europe, a company called bleBox makes a wifi sensor. There is a community-developed (me) Hubitat driver with LAN control of the sensor as well as published API documents supporting further development, if necessary. I used one for a while, but my air quality was so good, I stopped (unless I took the unit to my garage, it was always green).
3 Likes
Is the integration cloud or local?
Local (LAN) integration.
2 Likes
I found that Eurotronics device on Vesternet here in the UK and wouldn't mind one myself. I've no idea what FLiRS is, but if it's going to be bad for my mesh then I'll maybe give it a miss. How do you know whether a device is FLiRS or not before purchase, as it's not mentioned in the specs? (I notice that it will show in in the Z Wave Mesh Details app)
Also on Vesternet I found the below but it's far more expensive than the Eurotronics model:
1 Like
You are right, The Eurotronic Air Quality sensor is 5V DC powered and I may have been mistaken on what type of Z-wave device it is, so I edited my post to avoid any inaccurate information.
1 Like
@kkossev Can you do anything with the Frient air quality monitor ?
sys:12022-05-08 08:51:48.731 am Zigbee Discovery Stopped
sys:12022-05-08 08:51:47.735 am Zigbee Discovery Running
sys:12022-05-08 08:51:47.541 am Zigbee Discovery Stopped
dev:16272022-05-08 08:51:36.202 am infoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 B6E4 00 00 0000 00 00 090000040100012000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[09, 00, 00, 04, 01, 00, 01, 20, 00]]
dev:16272022-05-08 08:51:26.192 am infoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 B6E4 00 00 0000 00 00 0800000401010A0000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[08, 00, 00, 04, 01, 01, 0A, 00, 00]]
dev:16272022-05-08 08:51:14.549 am infoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 B6E4 00 00 0000 00 00 040000040100012000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[04, 00, 00, 04, 01, 00, 01, 20, 00]]
dev:16272022-05-08 08:51:04.541 am infoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 B6E4 00 00 0000 00 00 03FDFF040101190000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[03, FD, FF, 04, 01, 01, 19, 00, 00]]
dev:16272022-05-08 08:50:54.527 am infoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 B6E4 00 00 0000 00 00 0200000401010A0000, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, 00, 00, 04, 01, 01, 0A, 00, 00]]
dev:16272022-05-08 08:50:54.364 am debuggetting info for unknown Zigbee device...
dev:16272022-05-08 08:50:52.899 am infoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 B6E4 00 00 0000 00 00 00E4B69816003600BC150000, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B6E4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, E4, B6, 98, 16, 00, 36, 00, BC, 15, 00, 00]]
Sure, I love riddles! 
Can you try to get the fingerprint (from the 'device' driver)? You will need to wake up the device when pressing the Info button... If for any reason the fingerprint is not received, remove the device, pair it as a new one and copy the detailed endpoints information from the 'More' link.
Outside of above I'm not getting any other info from the device even when pairing new.
I click get info and get the above stuff back 10 mins later
No, when the Air Quality is paired as a new device, you should have a 'More' link (before you type in the device name and press Save). The 'More' link appears only for new devices, that's why you need to 'REMOVE device' from its current page first.
I'll triple check but I don't think that showed up... let me try again
This is a complex device and probably has multi endpoints, that for some reason are not discovered by HE...
Is there a particular Frient product ID / number that is printed on the box or in the leaflet?
Frient AQSZB-110 is supported in zigbee2mqtt (HomeAssistant), so it should be possible to make it work in HE as well.
I propose that you start a new thread (as this one was initially about Eurotronic) and probably first check whether there are any plans for supporting Frient products natively in HE?
