Closed AndreKR closed 3 years ago
It turns out USE_ADC_VCC
is not the culprit.
I have just flashed the affected device with a firmware that doesn't have USE_ADC_VCC
enabled and now the analog input is shown as expected, but the bogus energy monitoring is still shown:
Not sure what is going on.
Please, do a reset 6
on that device.
Done, this is the result:
Please, try to update that device to latest Tasmota of the development branch:
In the console type:
OTAurl http://ota.tasmota.com/tasmota/tasmota.bin.gz
Upgrade 1
Then do a reset 6
again please
Also, after all that, please, set weblog to 4 and then restart the device. Please, copy the content of the console. Thanks.
The problem doesn't happen with the official development image. It does not happen with the official release image (9.5.0) either.
It only happens with my image from TasmoCompiler. Here's my user_config_override.h
:
Ok
In your custom build you are enabling:
So that is why you have that.
Don't define that and you won't get the dummy energy consumption.
Closing this issue as it has been answered.
See Docs for more information. See Chat for more user experience. See Code of Conduct
I don't think I have control over that in TasmoCompiler, I have opened https://github.com/benzino77/tasmocompiler/issues/219.
I have tested on Tasmocompiler with selecting use_vcc and without selecting energy_monitoring and the resulting firmware is ok. It doesn't have energy dummy sensor.
For this device, you should compile without adding energy monitoring due to your device don't have that and you don't want that either.
When selecting ENERGY MEASUREMENTS, Tasmocompiler adds also ENERGY DUMMY SENSOR. This is expected and correct. If you don't need and you don't want energy measurements (neither with a power measurement chip or by a dummy sensor) you should not select energy measurements in Tasmocompiler.
Energy Dummy will count power consumption using a fixed voltage value + a fixed current value and the time the relay is ON. Those values are configured in the same way as the calibration of the power measurement chip (please, see the docs for that).
So, this is neither a Tasmota bug nor a Tasmocompiler bug. Just disable what you don't need. Thanks.
I see. My intention was to have a firmware that can do everything I need, but it will only actually do it when it is configured to do so.
In that case, In Tasmocompiler select ENERGY MONITORING and then add the following in the CUSTOM PARAMETER section:
PROBLEM DESCRIPTION
I have two Shelly 1 devices, both with Tasmota 9.5.0, but one is compiled with
USE_ADC_VCC
and uses this template:and the other one is compiled without
USE_ADC_VCC
and uses this template:The one without
USE_ADC_VCC
shows the ADC input, as expected:But the other one shows energy measurements, which of course are all 0 because the Shelly 1 does not have energy monitoring nor is it enabled:
It is also discovered as an energy monitoring device in Home Assistant.
I think the only difference between the two devices is the value of
USE_ADC_VCC
.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
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log: