Core 200S-P

[fuccimain]

Just FYI

I mentioned here https://github.com/tuct/levoit/discussions/54 that the Core 200S-P works with the Core 200S yaml (w/ yaml flipped Tx/Rx pins,) but one thing that is not working (so far) is the filter % sensor.

Just Letting it be known. Curious if there is anything I can try.

Thanks ✌️

[tuct]

Hi,
do you have an extra ESP32, or did you flash the original ESP32?
The remaining filter life time is calculated in the esp based on runtime, ...
What exactly is not working? you see nothing or what is wrong?

[tuct]

It might be that the P reports speeds differently. Do the speeds display correctly in ha for the 200p?

if you have an extra esp or even if you have flashed the original one, we can try to capture some uart traffic to check if something in the speeds is different for the P, it has a pet mode that might not be covered by the s implementation.

[rebpdx]

I just did the same Tx/Rx thing for mine. The filter light on the device is light up now that I'm connected, I tried a reset and no luck it just pushed the percentage in Home Assistant back to 100%

Everything else seems to be working. I flashed the original ESP32 and managed to read the chip into a backup before flashing it.

[tcouey]

I actually came here to open this same issue. I flashed the original ESP that it came with (about 6 months ago) and I've been waiting (plus I got busy) to see if the percentage would ever go down, but it never did, it's still at 100%.

Funny thing is that the filter light on the control panel came on tonight, so I cleaned the filter and reset it with the timer butter (like the manual says to do) and that worked, so I'm thinking that the main microcontroller on the PCB has its own timer for the filter? In any case, I can confirm that the filter percentage doesn't work on the 200S-P and the reset button doesn't clear the filter light either.

Update: I have to work for the next four days and don't have any free time on work days but maybe on my next weekend I'll crack her open and throw a serial probe on the bus between the microcontrollers to see what they're saying. Any Linux software recommendations for analyzing the captured traffic? Or has someone hacked together a tool for decoding it? I haven't looked at the project here very much beyond just getting the firmware installed.

[fuccimain]

Hi, do you have an extra ESP32, or did you flash the original ESP32? The remaining filter life time is calculated in the esp based on runtime, ... What exactly is not working? you see nothing or what is wrong?

flashed the original

It might be that the P reports speeds differently. Do the speeds display correctly in ha for the 200p?

yes the speeds work perfect (33%, 66% &100%)

I actually came here to open this same issue. I flashed the original ESP that it came with (about 6 months ago) and I've been waiting (plus I got busy) to see if the percentage would ever go down, but it never did, it's still at 100%.

ok so update. I've let it run and it took quite a few days for the 100% filter life to start to go down. It might be how the filter life is calculated because it took a REALLY long time to go from 100% to 99.4% (see pic.) Guess I'm used to how the graph looks with my 400S-P is a steady downward slope. This one is a downward staircase so might take a while to go below 100%

I also had the red filter light go on on the unit, so I hit the filter reset esp control, thats why the filter went back to 100%
(I forgot about the timer button action)

[tuct]

Hi, I will check on my Core 200 again; it might be that this one handles the filter a bit differently than the other - need to check if the mcu has filter control on this unit, which might be the case based on your reports.

[tuct]

About uart capture, check this part here:
https://github.com/tuct/levoit#capturing-a-uart-dump
i am using logic2, cheap fake hardware works abolutly good enough, i am using an original salae (quite expensive)

[tuct]

i think i found the issue:
the core200 uses mcu not esp32 for filter lifetime,
my unit has 100%, so i can't 100% verify ;)
but i found the byte that most likly has filter life in the MCU response and firmware with required changes is currently beeing build.

Would be cool if one of you could test and check that we get the correct value if filter is not 100%!

[tuct]

1.5.0 released, it should fix the issue! But as my unit has 100% i can only verify in a day or so after my filter drops to 99%!
If your unit is below 100% filter lifetime, the new fw should show the correct value now!

[tcouey]

I installed the new version on one of my two units to test it. Now it always shows 0.0% on the "Filter %" and "Filter Low" shows as "Problem".