-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot setup DHT22 Room Humidity Sensor, but setup as Chamber Humidity Sensor works #423
Comments
I missed a few lines of code for Room humidity sensor which I never tested. Sorry for that. |
Confirmed fixed at my end; thanks! 🙏 |
I was too quick! Adding DHT22 as room sensor now works, except it is still being reported within MQTT as Before this fix using the workaround it was reporting a value via MQTT, even through the topic was incorrect. Now it is reporting random single keyboard symbols (eg ,*-.). Nearly there! |
Yeah, the tag was wrong. However, I don't get it how the value was wrong. |
Hi; is the latest commit (b05b25a) ready for testing? I'm getting an error when compiling
|
I fixed it in the following way: I have fixed some of the issues already in my forked version of this repo (for which I might prepare a PR for in the future if @vitotai is up for that, but I will reach out when I have the time to do so), check the following: https://github.com/koekie/BrewPiLess/blob/master/src/MqttRemoteControl.cpp#L162-L171 |
Hi; I've noticed on the device setup page (http://brewpiless.local/setup.htm) that I cannot setup a DHT22 as a Room Humidity Sensor in the first instance. The device stays when I hit "apply", but the sensor value shows 255 continiously, and the temperature sensor does not show up when devices are refreshed.
I am able to work around this by setting the DHT22 as a Chamber Humidity Sensor first, and then change it to a Room Humidity Sensor. This then works okay, but the sensor continues to be reported in MQTT as
fridgeHumidity
notroomHumidity
.I'm compiling version 4.4 ce14288 using the
esp32-oled
default build environment and config.Thanks for your work on this!
The text was updated successfully, but these errors were encountered: