For Pete's sake! Now it's back to 1.75!!!
No change after rebooting HE
Yes, I just checked on mine.
The log file on the Environment Sensor will show the following when you click on/off
Do you use this module? If you like, you can send it back. I will give you a new one. I am very curious on what is going on with that module.
I'm not seeing anything under Current States like you are.
Not really. It's the one with your BT board connected to it and I've only used it for trying to find BT devices (no love there) so I can easily send it back.
I only used this module because it's handy, right here on my desk. I'll try another one and let you know what happens with it. But first I'm going to re-install the switch driver code... Nope, no change.
Since I also have a BT device connected to the Environment Sensor, I test the switch on that device.
Going into the switch device...
BTW, if you like to get it replaced, please PM me. I am interested to see what is going on with your module. I can try to help you setup with the switch there.
I grabbed the module from the garage since it's the one I'll be hooking the relay to. After I added the Switch child driver it was acting the same as the other one except the device page showed info under Current States.
I pulled the module from the USB, waited a few seconds, plugged it back in and got a successful switch to ON with the event logged and the DO at 3.3V but then it stopped switching so I again pulled the USB power, waited, re-plugged and now it's working as you said it should... 0V off, 3.3V on and events are logged.
Yes, please. I'll PM in a moment.
@iharyadi, this morning my Zigbee mesh stopped working. I found this in the HE logs every 30 seconds: errorjava.lang.IllegalStateException: Queue full (refresh) from one of your environment sensors.
I found nothing in the Zigbee log and there was some other strangeness like the /hub/zigbee/getChildAndRouteInfo link showed the html instead of the expected info. I suspect this is the result of the hub being trashed and not directly related to your sensor.
I guess I don't know that it was your sensor that started this and maybe it was just the first victim of the situation. 
I had to reboot the HE to restore normalcy.
I believe that if you are seeing this page, the zigbee is offline. Since my dth sensor depend on a working zigbee radio on the hub, the queue error above may happen. I personally have not seen this happen. My zigbee has been working just fine so far.
Which version of hub and hubitat firmware version do you use? Has it changed recently? I am curious whether there is something lurking that bring down the hub zigbee.
No, it's been 3-4 months since I updated to 135 and I've had no problems with it until now. It's been the best release to date for me. I'm not aware of any place I can look on HE to see when the update was applied. BTW, I don't plan to upgrade again until there is a stable version to go to. 
Yeah, I really don't know what started the Queue Full problem but there was a much earlier report of a similar experience: Hubitat with Homemade Temperature, Humidity, Pressure and Light sensor - #85 by veeceeoh I guess it could be something entirely unrelated to your device or even the Zigbee radio/mesh and they just happened to be front and center when the issue came up. 
As far as full queue error, it looks like common errors. When things go bad on the hub, one of the error that may come up is queue full. It did happen with my sensor to veechoo in 2018. I believe the error is also report recently in the community forum with other sensors or even applications. It is not specifc to this dth. I think this error is aftermath of something bad had happened. It is not the true root cause of the issue.
The concern that I have is actually more to why your Zigbee become offline. I did search this forum. I would not link the result here. There are a few of them. I also am not finding anything specific to a hub or firmware version. Yes... there are some zigbee issue is reported in the community recently.
I think the zigbee offline could be the start of your issue. If it happens again, I would be interested to know the root cause of it.
1 Like
Me, too.
1 Like
I read not all of the zigbee offline threads. Some of them happen similar to you interm of timing. Waking up in the morning and finding out that zigbee stopped working.
There are some members stated like you that rebooting the hub get their zigbee back to work.
I wonder that something that happened overnight may cause this. This is speculation on my part because I do not have extensive data. It is just my observation from reading a few posting here.
2 Likes
@iharyadi, any thoughts on making a batch of these using the BME680 so we could get some indoor air quality (bVOC, Co2) reading?
5 Likes
@parish99 & @douglaspitman I had request to make BME680 version. Thank you for bring this up.
I certainly am looking to find a way to get it integrated. There is a major issue that I need to overcome today. The BME680 cost $10 to $13 for my kind of size. We can bring the sensor to $5 ish if we are making 1000+ sensors. If we can get such demand here, this should be do able.
There are some technical issue. However, they are minor issues. They are something that I can handle.
It is just basically come down to the cost of the BME680. The only solution at the moment is to purchase it at 1000+ quantity to make it viable.
ps. Here some reference to the cost of BME680.
https://www.digikey.com/en/products/detail/bosch-sensortec/BME680/7401317?utm_adgroup=Sensors%20%26%20Transducers&utm_source=google&utm_medium=cpc&utm_campaign=Dynamic%20Search_RLSA_Cart&utm_term=&utm_content=Sensors%20%26%20Transducers&gclid=Cj0KCQiAzZL-BRDnARIsAPCJs71qYz9htbMGWj7Iw9M6Ih68sGL-CZ_RQi8mhX22Ue8RrMHHuEB4ajgaAnpAEALw_wcB
2 Likes
Put me down for at least 2. After I have those for a few weeks I'll likely want 2-5 more.
1 Like
I'm in for a couple. I would be willing to pay the difference also.
1 Like
I would be willing to pay the difference between the lower and higher quantity purchase. In other words, I think I am seeing the whole device would be maybe $5 more if made in smaller quantities, like make 200 instead of 1000? That $5 would be worth having this sooner rather than wait for 1000 other people to commit to purchasing.
(hope that makes sense)
That said, I would be in for at least 1, maybe 2.
1 Like
Hello Iman - Put me down for 2, even at the higher price.
1 Like
The higher price is fine for me as well. I’d do 3 or 4.
1 Like
@aaiyar, @neonturbo, @leeonestop, @LosinIt, @douglaspitman
It will be hard to ask the manufacturer to switch a part for just small batch in the middle of assembly. It could translate to much higher total price of the sensor. This custom request is a way for contract manufacturer to charge premium fee. It is just much easier to negotiate and deal with contract manufacturer on a simple plain uniform parts assembly.
I really like to have BME680 for all of us. It is make sense to have the additional sensor.
I will try what I can do to get the BME680 on the Environment Sensor. BME680 and BME280 is pin compatible. In the next batch, I will ask the manufacture not to populate the BME280 on some of the boards. I will solder the BME680 once they got here. I hope this is easy enough for them to follow. I cannot promise you when this will happen. But, I will try.
Meanwhile, If anyone else would like one with BEM680, please let me know here or PM. If I do get a sense that we have a demand close to 1K unit, we can just jump right to make the Environment Sensor with BME680. So far the "want" count is around 10 ish, we have 990 to go. 
Thanks
Iman
3 Likes
