-
Notifications
You must be signed in to change notification settings - Fork 636
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
BW-SHP2 (BLITZWOLF_BWSHPX) some measurements are zero #1823
Comments
Can you decode the stack trace? Or you can upload the .pio/build/env/firmware.elf Can't comment on 0 energy values yet, don't see any obvious issues running SHPX_V23 firmware. |
Interesting @mcspr! I didn't know the root cause for it but it's exactly that - if I keep refreshing the page, eventually it crashes. Do you want to close this one as duplicate? What's the right way to decode the stack trace? |
If you do actively use web, it does look like a duplicate. Do you use Chrome too, like #1824? I will add this to the wiki eventually... One recent crash problem with thingspeak involved decoding:
One problem discovered was that code lines may be incorrect for some of the addresses, not really sure about the reason. To mitigate that, one can use the current toolchain files from https://github.com/earlephilhower/esp-quick-toolchain/releases/tag/2.5.0-4 |
@mcspr this is what I got:
|
No experience with that, really. (continuing #1038? and i thought that was related to the relay-on) We do see half of the values though, filtering may still be a problem? If you can, this espurna/code/espurna/sensor.ino Line 1508 in 4469ec8
HLW8012 adaptation for SHP chip may be wrong, maybe? Logic flow sometimes resets values to 0 https://github.com/xoseperez/hlw8012 One interesting problem that #1802 mentioned regarding ESP in general / board design - could it be EM interference? |
@ruimarinho have you had any chance to check the raw output values? and have you tried this with ESPEasy or Tasmota? (i think espeasy uses Xose's library and tasmota uses it's own custom module) What are you using to test the output values? As I mentioned above, hwl library sometimes resets output values to 0. One of those conditions is pulse-timeout after switching to the current measurement mode (cf1 pin measures both current and voltage, depending on which digital signal we send to the sel pin; |
@mcspr can I use espurna's web interface to upload Tasmota's firmware? I tried using a halogen bulb as well as a LED bulb. |
Yes, this was already tried before and seems to be working ok. Might briefly break setting, but reboot will fix things. Just make sure that you use the same SDK / Core versions
|
Tasmota is already on 2.5.x but I was able to compile with 2.3.0. Thanks for the tip - the upgrade worked. The sensor still reads 0 power even with a custom HLW8012 implementation. At this point I am convinced I have a faulty power sensing chip. |
Weird. And the same thing happens with something like laptop power adapter? Referencing HLW source again, it counts CF pin pulses to calculate energy value (as it seemingly changes from time to time?) |
Question
The device is crashing sometime after boot and sensor information is not available (always 0W).
Already tried factory reset with no change.
Device information
The text was updated successfully, but these errors were encountered: