-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Incorrect CO2 Sensor Selected #16720
Comments
My experience with the S8 is that seeing "Kx0" means trouble communicating with the sensor, circumstances including things like bad connections or not enough power available. Easy way of getting "Kx0" is to disconnect the sensor..... Your pin selections may not be a good plan, preferred is to use the hardware serial pins, gpio 1/3. |
{"GPIO0":{"1600":"SAir Tx"}, "GPIO2":{"1632":"SAir Rx"} 2 software serial on the same ESP8266 is calling for problems |
I'm really new to this whole ESP thing. What about this configuration do you think is causing this problem? Is the problem something that can alleviated by tweaking some settings? Idk, maybe polling the sensors less frequently? |
Using software serial means bit banging, which is a high load on the processor to monitor pins to measure timing. That's why I made the suggestion of using hardware serial, probably on the one with most traffic. Hardware serial is when the MCU chip has electronics to do it very efficiently. Using an ESP32 would mean that you have at least two hardware serial available, meaning no bit banging at all, which is optimal. I'd suggest first trying if it works out on ESP8266 using hardware serial for one of them. That would be TX on gpio1 and RX on gpio3. Do note that there could also be other potential explanations for the communications breakdown, like I mentioned already. |
Thanks for the assistance. I'll look into the hardware configuration further. |
The detection of Senseair sensors doesn't handle error situations always correctly. Although a more stable sensor connection is preferable, PR #22487 will won't have the issue that a S8 suddenly is regarded as a Kx0 anymore. Still WIP. |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
I have an air quality sensor that uses a Senseair S8 CO2 sensor. The sensor is detected correctly when the device it initially flashed with the Tasmota-Sensors build. However, after some time, Tasmota changes the device to a Kx0 CO2 sensor. I'm unable to get it to switch back without re-flashing the device entirely
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
Compile Tasmota using the Tasmota-Sensors template and the USE_PROMETHEUS option.
Flash device.
Wait a day or two.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expected it to continue detecting the Senseair S8 and not switch devices to the Kx0
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
Incorrect Device:
![image](https://user-images.githubusercontent.com/1363971/193832633-e5aac79d-9547-487b-b54a-c7ab328140f9.png)
ADDITIONAL CONTEXT
Add any other context about the problem here.
I compiled this myself using the Tasmota-Sensors as a base and included USE_PROMETHEUS.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: