logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Bi-Directional meter for Solar with total Consumption and Export Energy counters (BL0942 based)

cdtdsilva 4365 55
Best answers

How can I add and enable extra energy counters such as export, today, yesterday, and hourly totals for BL0942-based devices in OpenBeken, and can this be done from the web interface?

Enable the extra energy statistics by updating `drv_bl_shared.c` (the statistics array) and its matching enumeration, then turn on NTP and run `SetupEnergyStats` so periodic counters like today, yesterday, and last hour are available [#21022822] There is no built-in toggle for this in the native web interface; the suggested approach is to add a console command and, if you want a button, wire it up in the JavaScript webapp instead of the device’s HTTP page [#21025418] For separate import/export handling, keep the energy value as a 32-bit float and split “taken” versus “given” later in the update path rather than adding a new variable unnecessarily [#21024952] If you need to store additional values, reuse reserved/retained storage rather than extending the flash structure, because adding fields breaks compatibility, while flashvars already writes in 64-byte blocks and only erases when a page fills [#21024952]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 21021021
    cdtdsilva
    Level 10  
    Just updating this to reflect the work done on this project.

    It's now possible to measure reverse and forward energy consumption on devices based on the BL0942.
    I have also implemented Netmetering, so that we know how much is self consumption and how much is actually exported to the grid.

    Netmetering is the sum of the consumed and produced balance. Say f you produced 1000W and used 500W, your balance will be 500W positive,
    Normally this would be exported to the grid to use later, but in recent tarifs, utilities have reduced the time you can do so, typically in between meter readings (15 to 60min). Any excess will be marked as 'Export@ and sold to the utility company for very little, compared with the purchase price.

    To better make use of this provision I added a feature to enable a remote relay when there is a certain ammount of positive balance. This allows diverting some of this energy to a water heater, a heating system or any other appliance.
    It can be used standalone or fed into home assistant to run automations.

    Further details as we go on...
    Now onto the original...

    On the other topic Link I have added support for forward and reverse energy on BL0942 based smart plus.

    OpenBecken has one global counter for energy - there is no way to display the aditional readings for energy exported.
    I would like to enable aditional ones, but i don't know how to do this - It's not really well documented like in tasmota. Are there any custom builds where this functionality is implemented?

    Something like this, which is enabled on the Shelly 3EM using ADE7880:
    Shelly EM user interface showing energy consumption data.

    I see that on the file drv_bl_shared.c there are stats for various statistics such as 'Energy today', 'Energy yesterday', 'Energy last hour', etc. Are these used on a particular device? Is there a way to enable them on the webinterface somehow?

    Thanks!
  • ADVERTISEMENT
  • #2 21022822
    p.kaczmarek2
    Moderator Smart Home  
    This is a very good idea.
    I think you need to edit this file:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/driver/drv_bl_shared.c
    Namely this array:
    Code: C / C++
    Log in, to see the code

    You also need to update the corresponding enumeration:
    Code: C / C++
    Log in, to see the code


    In order for extra counters like "energy today", etc, you need to enable NTP and setup energy counters. See our documentation for more details:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/commands.md
    Related command is SetupEnergyStats.
    You can check other threads for more information:
    https://www.elektroda.com/rtvforum/find.php?q=SetupEnergyStats


    Once you do the modification, I can merge in your changes. Let me know if you have any futher questions.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 21023986
    cdtdsilva
    Level 10  
    I was hoping you could assist me in enabling the additional statistics, as shown in my previous image (for now, let's disregard time statistics and solely focus on the totals). These statistics should be assigned to a variable, and that's where I'm encountering difficulties in comprehending the code.

    Based on my investigation, it seems that the correct function is

    Code: text Expand Select all Copy to clipboard
    void BL_ProcessUpdate(float voltage, float current, float power,
                      float frequency, float energyWh) {...}


    However, this function needs to be modified in order to display a few more elements on the webpage (such as total production, for instance) and somehow store it, similar to the consumption data.

    Storing wise, this function seems to be responsible for it,
    Code: text Expand Select all Copy to clipboard
    HAL_FlashVars_SaveTotalConsumption(sensors[OBK_CONSUMPTION_TOTAL].lastReading);

    but I'm not sure in which circunstances it saves, How do I ensure I don't write the memory too many times?

    It appears that this task may exceed my current abilities, despite my sincere efforts to assist.
  • #4 21024952
    p.kaczmarek2
    Moderator Smart Home  
    cdtdsilva wrote:
    I
    Code: text Expand Select all Copy to clipboard
    void BL_ProcessUpdate(float voltage, float current, float power,
                      float frequency, float energyWh) {...}


    If we assume that energyWh is negative when we have energy gain, then you don't need to add a variable there. You need to add a conditional statement later down the line to separate the "taken" from "given" values.


    cdtdsilva wrote:

    Storing wise, this function seems to be responsible for it,
    Code: text Expand Select all Copy to clipboard
    HAL_FlashVars_SaveTotalConsumption(sensors[OBK_CONSUMPTION_TOTAL].lastReading);


    I think you should be able to extend the structures there:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/hal/hal_flashVars.h#L20
    Update will break stats for all of the users but maybe we can live with that...
    Or maybe utilize the "reserved" 3-byte field?
    Or maybe store it in the last 4 bytes of:
    Code: text Expand Select all Copy to clipboard
    
	short savedValues[MAX_RETAIN_CHANNELS];

    No one ever retains more than 4 channels and MAX_RETAIN_CHANNELS is 12 so you could use that... if you need 4 bytes.

    cdtdsilva wrote:
    How do I ensure I don't write the memory too many times?

    The flashvars code works by writing 64 byte blocks many times to a single page and then erasing it only when the page is full. So, assuming page size 4096, then we get 4096/64 = 64 writes per erase cycle. Futhermore I think more pages are utilized. So it's many times more efficient and less prone to flash wear than a simple blind "erase+write" on each change.


    cdtdsilva wrote:

    It appears that this task may exceed my current abilities, despite my sincere efforts to assist.

    I am very happy with your activity so far. I can help more if it's required. Please tell me which new field of which type and size do you need and I can add them for you.
    I will most likely just use:
    Code: text Expand Select all Copy to clipboard
    
	short savedValues[MAX_RETAIN_CHANNELS];

    because, as I said earlier, I can't imagine a scenario where someones does energy metering and has 10 or so relay channels..
    Helpful post? Buy me a coffee.
  • #5 21025193
    cdtdsilva
    Level 10  
    p.kaczmarek2 wrote:
    cdtdsilva wrote:

    Code: text Expand Select all Copy to clipboard
    void BL_ProcessUpdate(float voltage, float current, float power,
                      float frequency, float energyWh) {...}


    If we assume that energyWh is negative when we have energy gain, then you don't need to add a variable there. You need to add a conditional statement later down the line to separate the "taken" from "given" values.

    Yes, doing that now.
    p.kaczmarek2 wrote:

    cdtdsilva wrote:

    Storing wise, this function seems to be responsible for it,
    Code: text Expand Select all Copy to clipboard
    HAL_FlashVars_SaveTotalConsumption(sensors[OBK_CONSUMPTION_TOTAL].lastReading);


    I think you should be able to extend the structures there:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/src/hal/hal_flashVars.h#L20
    Update will break stats for all of the users but maybe we can live with that...
    Or maybe utilize the "reserved" 3-byte field?
    Or maybe store it in the last 4 bytes of:
    Code: text Expand Select all Copy to clipboard
    
	short savedValues[MAX_RETAIN_CHANNELS];

    No one ever retains more than 4 channels and MAX_RETAIN_CHANNELS is 12 so you could use that... if you need 4 bytes.

    I've added it as such, Do you see any potential problems given the larger size?
    Will anything get overwritten if we use both?

    Code: text Expand Select all Copy to clipboard
    /* Fixed size 32 bytes */
typedef struct ENERGY_METERING_DATA {
	float TotalGeneration;
	float TotalConsumption;
	float TodayConsumpion;
	//float YesterdayConsumption;
	long save_counter;
	float ConsumptionHistory[2];
	time_t ConsumptionResetTime;
	unsigned char reseved[3];
	char actual_mday;
} ENERGY_METERING_DATA;


    p.kaczmarek2 wrote:

    cdtdsilva wrote:
    How do I ensure I don't write the memory too many times?

    The flashvars code works by writing 64 byte blocks many times to a single page and then erasing it only when the page is full. So, assuming page size 4096, then we get 4096/64 = 64 writes per erase cycle. Futhermore I think more pages are utilized. So it's many times more efficient and less prone to flash wear than a simple blind "erase+write" on each change.

    That's great, nothing will change then.

    p.kaczmarek2 wrote:
    cdtdsilva wrote:

    It appears that this task may exceed my current abilities, despite my sincere efforts to assist.

    I am very happy with your activity so far. I can help more if it's required. Please tell me which new field of which type and size do you need and I can add them for you.

    I will most likely just use:
    Code: text Expand Select all Copy to clipboard
    
	short savedValues[MAX_RETAIN_CHANNELS];

    because, as I said earlier, I can't imagine a scenario where someones does energy metering and has 10 or so relay channels..


    Well, we are moving :)

    Is there a system timer I can use without the need for NTP? I want to reset the absolute power variable every 15min / 60min.
    Where is the code for the webpage located? I want to add an extra button to reset the generation statistics, next to the one for the totals
  • #6 21025220
    Honsu
    Level 3  

    I have autoexec.bat entered in the file

    startDriver NTP
    ntp_timeZoneOfs 1
    SetupEnergyStats 1 60 60
    Screenshot showing energy consumption statistics with various measurement data.
  • #7 21025418
    p.kaczmarek2
    Moderator Smart Home  
    I am not sure if I missed it, but can you @cdtdsilva specify how much bytes do you need?

    cdtdsilva wrote:

    I've added it as such, Do you see any potential problems given the larger size?

    Adding new fields to this structure will cause all users to lose energy stats on reboot and cause faster flash wear.

    My suggestion currently is:

    p.kaczmarek2 wrote:

    Or maybe store it in the last 4 bytes of:
    Code: text Expand Select all Copy to clipboard
    
	short savedValues[MAX_RETAIN_CHANNELS];

    No one ever retains more than 4 channels and MAX_RETAIN_CHANNELS is 12 so you could use that... if you need 4 bytes.

    Please use those fields instead of adding new ones. Just get a pointer and cast it to integer or what kind of type do you want?

    cdtdsilva wrote:

    Is there a system timer I can use without the need for NTP? I want to reset the absolute power variable every 15min / 60min.

    Do you want to use it for testing purposes only or for production?
    There is addRepeatingEvent command that can be used for development testing.

    cdtdsilva wrote:

    Where is the code for the webpage located? I want to add an extra button to reset the generation statistics, next to the one for the totals

    Please do not add any special buttons to native HTTP page. We need to preserve flash memory. Some devices have only 1 MB. You only need to add console command like here:
    Snippet of a table with a command for resetting the energy counter and an optional new value.
    Screenshot of OpenBK7231T application source code in drv_bl_shared.c file.
    Then you can edit our Javascript web app code here:
    https://github.com/OpenBekenIOT/webapp
    in order to add a button to call this command, like I did here:
    Screenshot of a web app with tools for managing IoT devices.[/quote]
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #8 21025677
    cdtdsilva
    Level 10  
    p.kaczmarek2 wrote:
    I am not sure if I missed it, but can you @cdtdsilva specify how much bytes do you need?


    I need 8 bytes. The total counters are saved as a float - using a short, I'm guessing we only have 4 bits available, which would cause them to overflow somehow quicker.

    I was thinking in using the 'Yesterday Consumption' field or commenting it out, such as on the example, to give space to a variable of the same size. Technically then, that's the only field that would be broken, the other memory positions remain unchanged. That only saves last 24h consumption, so it would affect users minimally.

    p.kaczmarek2 wrote:

    Adding new fields to this structure will cause all users to lose energy stats on reboot and cause faster flash wear.

    See above.

    p.kaczmarek2 wrote:

    Do you want to use it for testing purposes only or for production?
    There is addRepeatingEvent command that can be used for development testing.


    I want to use it for production, without NTP. Is there a system tick counter used for non blocking delays?
  • #9 21025722
    p.kaczmarek2
    Moderator Smart Home  
    I can try to add two floating point fields for you in the place of last 4 retained channels, which no one is using. How should I name them? Two 32-bit floats, so 2*4 = 8 bytes.

    How precise timing do you need?
    Helpful post? Buy me a coffee.
  • #10 21025744
    cdtdsilva
    Level 10  
    p.kaczmarek2 wrote:
    I can try to add two floating point fields for you in the place of last 4 retained channels, which no one is using. How should I name them? Two 32-bit floats, so 2*4 = 8 bytes.


    Thanks. I only need one variable called TotalGeneration. It should be a 64bit / 8 byte float.

    p.kaczmarek2 wrote:
    How precise timing do you need?

    The timing doesn't need to be very precise, just roughly 15min or 60min options, as those are the standard net metering times offered by utilities.

    I said I didn't want to use NTP... For clarification - I don't mind using it - But I want to be able to use it without the internet. So would the driver still run, with the time not synced (ie starting to count from 1900)? I will be doing is getting the number of seconds and schedulling the next clear of the absolute energy counter to 15 or 60 min ahead in time. This would ideally be synced to the start of the hour, if the device was connected to the internet, but correct timezone, day, week, etc is not required.

    Energy metering is now working, just neet to add the net metering feature and change the 'TotalGeneration' to the new variable you will be creating plus some tidy up of the code
    Screenshot showing energy consumption statistics with values such as frequency, voltage, current, and other electrical parameters.
  • #11 21025789
    p.kaczmarek2
    Moderator Smart Home  
    All our math is done on 32-bit floats and 32-bit float is used to store power consumption, why do you suddenly want to use 64-bit double for power generation? How much power do you expect to generate that you think it will overflow the 32-bit type?

    If you are worried about floating point precision, you could also settle on 32 bit unsigned integer and assume that it's a value in Wh or something, depending on how much precision you need.

    Regarding timing - maybe just do:
    Code: C / C++
    Log in, to see the code

    in the driver code? In the "on every second" tick update...

    Added after 1 [minutes]:

    Also - can you respect Flag 25 in your changes?
    Fragment of a software feature list with a highlighted row in orange.
    To be more precise - only run your changes when this flag is set?

    I am asking becaus we had reports saying that some power metering chips are reporting negative values randomly...
    Helpful post? Buy me a coffee.
  • #12 21025841
    cdtdsilva
    Level 10  
    p.kaczmarek2 wrote:
    All our math is done on 32-bit floats and 32-bit float is used to store power consumption, why do you suddenly want to use 64-bit double for power generation? How much power do you expect to generate that you think it will overflow the 32-bit type?


    I was making a number of assumptions, but I see your point now. 4 bytes is OK.

    Would it be enough to initialize it as
    Code: text Expand Select all Copy to clipboard
    #define MAX_RETAIN_CHANNELS 10
    and then add our new variable on the top of
    Code: text Expand Select all Copy to clipboard
    typedef struct ENERGY_METERING_DATA {float TotalGeneration; ...}
    so it ocupies those first 4 bytes?

    p.kaczmarek2 wrote:

    Regarding timing - maybe just do:
    Code: C / C++
    Log in, to see the code

    in the driver code? In the "on every second" tick update...


    Ill try that for a first go.

    p.kaczmarek2 wrote:

    Also - can you respect Flag 25 in your changes?
    Fragment of a software feature list with a highlighted row in orange.
    To be more precise - only run your changes when this flag is set?
    I am asking becaus we had reports saying that some power metering chips are reporting negative values randomly...


    Yes, that shouldn't be a problem.
  • ADVERTISEMENT
  • #13 21025864
    p.kaczmarek2
    Moderator Smart Home  
    cdtdsilva wrote:
    p.kaczmarek2 wrote:
    All our math is done on 32-bit floats and 32-bit float is used to store power consumption, why do you suddenly want to use 64-bit double for power generation? How much power do you expect to generate that you think it will overflow the 32-bit type?


    I was making a number of assumptions, but I see your point now. 4 bit is OK.

    Ok ok, but it's 4 byte, not bit. It's just two letters but it matters.

    cdtdsilva wrote:

    Would it be enough to initialize it as
    Code: text Expand Select all Copy to clipboard
    #define MAX_RETAIN_CHANNELS 10
    and then add our new variable on the top of
    Code: text Expand Select all Copy to clipboard
    typedef struct ENERGY_METERING_DATA {float TotalGeneration; ...}
    so it ocupies those first 4 bytes?

    Your solution may be more elegant but I'd still opt for a bit more "hacky" approach that keeps MAX_RETAIN_CHANNELS at 12 but still allows you to overwrite last two values (2 * 2 bytes = 4 bytes) with your value.
    This is because I think there is almost no chance of conflict between those two usages so we can keep both those features, just I will document that they occupy the same space.

    Ok, so, now, can I add that function to store a 4-byte float for you? I will add it to the main tree already, but it won't be called anywhere, I will leave it up to you.
    Helpful post? Buy me a coffee.
  • #14 21025906
    cdtdsilva
    Level 10  
    p.kaczmarek2 wrote:
    cdtdsilva wrote:
    p.kaczmarek2 wrote:
    All our math is done on 32-bit floats and 32-bit float is used to store power consumption, why do you suddenly want to use 64-bit double for power generation? How much power do you expect to generate that you think it will overflow the 32-bit type?


    I was making a number of assumptions, but I see your point now. 4 bit is OK.

    Ok ok, but it's 4 byte, not bit. It's just two letters but it matters.

    Ups... Corrected!

    p.kaczmarek2 wrote:
    cdtdsilva wrote:

    Would it be enough to initialize it as
    Code: text Expand Select all Copy to clipboard
    #define MAX_RETAIN_CHANNELS 10
    and then add our new variable on the top of
    Code: text Expand Select all Copy to clipboard
    typedef struct ENERGY_METERING_DATA {float TotalGeneration; ...}
    so it ocupies those first 4 bytes?


    Your solution may be more elegant but I'd still opt for a bit more "hacky" approach that keeps MAX_RETAIN_CHANNELS at 12 but still allows you to overwrite last two values (2 * 2 bytes = 4 bytes) with your value.
    This is because I think there is almost no chance of conflict between those two usages so we can keep both those features, just I will document that they occupy the same space.

    Ok, so, now, can I add that function to store a 4-byte float for you? I will add it to the main tree already, but it won't be called anywhere, I will leave it up to you.


    Yes, please go ahead.
    I was thinking to write the bytes in a loop to the memory locations, but then I was worried that a power loss might increase the risk of data corruption. I'm sure you'll have a better idea ;)

    Added after 10 [hours] 18 [minutes]:

    Ok - Changes are complete.

    I did the changes I proposed earlier, and then we can use this new function, once it's complete.
    src/hal/hal_flashVars.h
    Code: text Expand Select all Copy to clipboard
    #define MAX_RETAIN_CHANNELS 10
...
typedef struct ENERGY_METERING_DATA {float TotalGeneration; ...}


    NTP works fine witout internet, so I used the minute variable, after enabling it. This does not break compatibility with existing stats (Example PowerSave 1; startDriver NTP; SetupEnergyStats 1 60 60) - These work as they did. They measure consumption and remain 0'd with generation.

    Flag 25 disables the netmetering statistics and generation counter. Active energy is 0 and the consumption counter is not incremented.
    Current, Voltage and var are still displayed, but nothing to do with my code changes - They probably always were, as if you attach a capacitor to the load (lots of current/var, nil consumption).

    It seems like the total generation is not saved very often. A restart does save it - but pulling the plug out doesn't. Consumption typically saves it in 0.01 or 0.02KW intervals.

    For the net metering functionality I would like to be able to set a variable to define the actual time (15min, 60min, etc.) - Can I do this using the console? Or can it be added on the webpage? The variable is called
    Code: text Expand Select all Copy to clipboard
    net_metring_interval


    Is it possible to run a command based on the value of a given variable, for example, close the relay, when generation is above a certain threshold? Any examples of this, I can refer to?
  • #15 21026479
    p.kaczmarek2
    Moderator Smart Home  
    cdtdsilva wrote:

    I did the changes I proposed earlier, and then we can use this new function, once it's complete.
    Code: text Expand Select all Copy to clipboard
    #define MAX_RETAIN_CHANNELS 10
...
typedef struct ENERGY_METERING_DATA {float TotalGeneration; ...}


    As I said, I'd prefer to keep MAX_RETAIN_CHANNELS at 12 and just use last two retain channels as a float with a cast, but I will add a sample of this for you later.

    cdtdsilva wrote:

    It seems like the total generation is not saved very often. A restart does save it - but pulling the plug out doesn't. Consumption typically saves it in 0.01 or 0.02KW intervals.

    I am not currently sure, I need to check the bl_shared.c code.

    cdtdsilva wrote:

    For the net metering functionality I would like to be able to set a variable to define the actual time (15min, 60min, etc.) - Can I do this using the console? Or can it be added on the webpage? The variable is called
    Code: text Expand Select all Copy to clipboard
    net_metring_interval

    This must be done via console command and later you can use our Vue/JS page to create a button for that.

    cdtdsilva wrote:

    Is it possible to run a command based on the value of a given variable, for example, close the relay, when generation is above a certain threshold? Any examples of this, I can refer to?

    I think you can use addChangeHandler for that:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/autoexecExamples.md

    Added after 5 [hours] 36 [minutes]:

    @cdtdsilva I have a little update. I have checked the code and I now know where the data is saved. The following feature was added by our contributor so I couldn't just figure it out from the memory.
    You need to search for BL09XX_SaveEmeteringStatistics
    See: https://github.com/search?q=repo%3Aopenshwpro...pp%20BL09XX_SaveEmeteringStatistics&type=code
    There is a conditional statement in the bl_shared.c which determines the frequency of power metering data saving.
    Helpful post? Buy me a coffee.
  • Helpful post
    #16 21031005
    cdtdsilva
    Level 10  
    Hi p.kaczmarek2!

    The piece of code I used to save the generation variable is for development purposes. I will use your code, once you're finished. For now i just made sure the correct memory positions were used, so it's backwards compatible with the final code.

    I may need some help to sync your repo to mine - last time it just over-wrote all my changes (good thing I had a backup). This time, too many files were changed to do it by hand. I'm not a daily github user, so not sure on all the perks there...

    I noticed power data is saved in 10Wh intervals. That's probably usefull to document.
    10Wh increments is probably fine for a smart plug, for whole house power consumption, it will likelly write the flash 1000+ times a day.
    I sugest users change the default value to 100W and have added a small indicator showing the set value.

    The variable that writes the flash is the one below, inside src/driver/drv_bl_shared.c. I have re-written it to save whenever either of the values goes above the threshold set by 'changeSavedThresholdEnergy'.

    Code: text Expand Select all Copy to clipboard
    if (((sensors[OBK_CONSUMPTION_TOTAL].lastReading - lastSavedEnergyCounterValue) >= changeSavedThresholdEnergy) ||
        ((xTaskGetTickCount() - lastConsumptionSaveStamp) >= (6 * 3600 * 1000 / portTICK_PERIOD_MS)) 


    I modified the Periodic statistics feature to fit the needs of Netmetering (the balance between consumption and generation), as currently implemented by power companies.
    Because both the period and time zone will vary across the globe, the user will need to enable NTP and statistics manually.
    My start command looks like this, for reference:
    Code: text Expand Select all Copy to clipboard
    backlog Powersave 1; startDriver BL0942; startDriver NTP; ntp_timeZoneOfs 1; SetupEnergyStats 1 60 15


    Energy stats sets the period offered by the utility company. 60 seconds and x minutes. The rest should be self-explanatory.
    The statistics themselves, show the results for consumption, just as before. Netmetering balance is shown in a separate entry. A positive value indicates excess production and negative indicates consumption from the grid.

    Where there is excess production, I made provision to turn on a remote smart plug. This can be used to turn on an immersion heater or command a heat pump. In Poland, the present regulations offer 60min netmetering period, which is very generous. The relay goes off if either the solar array is not producing above a minimun value or we drop below a certain ammount of excess production, otherwise it remains on. The turn on and off thresholds are different, to accomodate some hysteresis, plus the relay only changes states every 2 minutes.

    Right now the default values are:
    > 50W (instant) and >10Wh excess production to turn on the relay,
    <50W (instant) and <5Wh excess production turns off the relay.
    2 minutes for changing states

    These values may need to be adjusted, based on the power of the instalation.
    Presently the IP address of the remote plug is hard coded.

    NTP was enabled and used to sync the readings. Where the device is connected to internet and able to sync, NTP is also used to sync the internal time at the start of every hour (HH:00min). This ensures the start of the metering period matches the one used by the utility company. The status of this relay is displayed on the webpage.

    These features are all enabled using Flag 25.

    I didn't check the MTTQ features as I don't have HA by hand. In principle everything should work, but I didn't test to see if the generation readings are reported correctly.

    I leave it up to you what features you want to keep for the final version. It would be nice if the webpage was able to accomodate customization of these parameters by the end user. I can help document those.

    For reference, here's a screenshot. For anyone wanting to try the binaries, they are added as an attachment to this post.
    Screenshot of an energy monitoring interface displaying various electrical parameters.
    Attachments:
    • OpenBK7231T_App_main_3368c80d8dbc.zip (10.21 MB) You must be logged in to download this attachment.
  • #17 21031759
    p.kaczmarek2
    Moderator Smart Home  
    Here is my proposal of save function:
    https://github.com/openshwprojects/OpenBK7231...mmit/9003bc67d12c16749c7d59ae5b4709d57560f522
    You can sync changes from mains to get my changes on your fork.

    Merge conflicts can be indeed hard to resolve. Did you use Github gui? Maybe try using a dedicated diff/merge tool?
    I think there may be some online tutorials for conflicts resolve:
    https://www.youtube.com/results?search_query=how+to+merge+git+conflicts
    Alternatively you can just rewrite/copy paste your changes to the main tree....

    It would be a bit difficult for me to do that with your fork, as I don't have a good understanding of your code and I am also not the main contributor of power metering features, as far as I know they were introduces by @valeklubomir and later some other user improved them.

    This is very good if it's all enabled by flag 25.

    I am not sure about that "diversion relay" part. I will need to check this once it's in PR. My main question is - how much flash space it takes and why not just use script with addChangeHandler? But again, maybe if it's not taking much space, then it's a good idea... or we can just #ifdef it and allow users to enable it in obk_config.h so we can save flash space when it's not needed...

    I want to keep all your features, just as I said, I have only few requirements:
    - the energy export must be enabled by flag 25 or similiar (and this is already implemented, right?)
    - if you add some features that requires a lot of flash memory/space, consider adding option to disable them to obk_config.h
    - you can't break too much compatbility with older versions
    - and as you said, we need some basic docs

    I will do a final code review once you manage to get the conflicts resolved. I can also do some basic testing with @DeDaMrAz and maybe @divadiow before merging.

    Added after 1 [minutes]:

    EDIT: The energy step for save could be made configurable via console command
    Helpful post? Buy me a coffee.
  • #18 21032447
    cdtdsilva
    Level 10  
    Hi p.kaczmarek2

    I don't have any conflicts, just last time I tried to merge, it somehow overwritten my changes.
    I don't use these tools on an everyday basis, so I find it extremely time consuming to figure it all out. Now that the easter holidays are over I'm not so easy on time, so I will have to review at a later time.

    The 'diversion relay' part of the code is an if loop with conditional statements, which calls out the Send Get command to send an HTTP request to turn on or off a remote plug. All the code is contained inside That's makes use of the already included code inside selftest_http_client.c, example:

    Code: text Expand Select all Copy to clipboard
    ///CMD_ExecuteCommand("SendGet http://192.168.0.103/cm?cmnd=POWER%20TOGGLE", 0);

    You might have a good idea of the memory use of that feature. The rest, I think it's negligible. A few more variables and loops.

    90% of the aditions are inside src/driver/drv_bl_shared.c.
    I did some previous changes on how metering data is obtained from the BL0942 inside /src/driver/drv_bl0942.c

    The rest is adition of variables here and there. I'm pretty confident no backwards compatibility was lost, but due to the memory structure, the generation data is probably sent via MQTT regardless of flag 25 (As a 0 value). That needs to be tested, to ensure nothing goes out of place on HA, etc.

    I know all of the variables can be changed via the console. Are you kindly telling me there is no space to make the changes? I would find it more user friendly to have them on the webinterface, but understand if space is an issue. We could also make a separate version, a bit like tasmota (with an #ifdef) specific for users that require reverse metering. It's quite a niche application, after all.

    Either way I will prepare some details covering the various variables of interest. I will probably forget them in a few weeks, so better have them documented :-)

    Meanwhile, these work fine via MQTT on home assistant.
    Energy monitoring panel displaying graphs and tables. Home Assistant user interface displaying various home statistics.
  • #19 21032496
    p.kaczmarek2
    Moderator Smart Home  
    @cdtdsilva are you using Github GUI? If there are no conflicts, I could just merge your changes on my site, but then you won't be present in Github history as a contributor, and I think your presence there is deserved as you did good work. It's up to you. If you think you can reasonably test this things on your side then I can open PR for you once you send me your code...

    cdtdsilva wrote:

    The 'diversion relay' part of the code is an if loop with conditional statements, which calls out the Send Get command to send an HTTP request to turn on or off a remote plug. That's makes use of the already included code inside selftest_http_client.c, example:

    Code: text Expand Select all Copy to clipboard
    ///CMD_ExecuteCommand("SendGet http://192.168.0.103/cm?cmnd=POWER%20TOGGLE", 0);


    I think it should be scripted, we can't have that in code, but you can leave it commented out in the code as example.



    cdtdsilva wrote:

    I know all of the variables can be changed via the console. Is that your way of telling me there is no space to make the changes? I would find it more user friendly to have them on the webinterface, but understand if space is an issue.

    Solution is very simple:
    1. make a console command
    2. add interface to our web app:
    https://github.com/OpenBekenIOT/webapp
    for example like:
    Screenshot of a web app interface with configuration tools.

    cdtdsilva wrote:

    but understand if space is an issue.

    BL602 is very close to OTA size limit. Futhermore, BK7231s have issue because OTA file is growing and it's sometimes reaching LFS size and overwrites LFS on OTA

    cdtdsilva wrote:

    We could also make a separate version, a bit like tasmota (with an #ifdef) specific for users that require reverse metering. It's quite a niche application, after all.

    If possible and easy, yes.



    cdtdsilva wrote:

    Meanwhile, these work fine via MQTT on home assistant.
    Energy monitoring panel displaying graphs and tables. Home Assistant user interface displaying various home statistics.

    That looks very good and promising!
    Helpful post? Buy me a coffee.
  • #20 21034035
    cdtdsilva
    Level 10  
    @p.kaczmarek2

    I'm compiling using the github web page.

    I have absolutelly no problem it not having my name there as a contributor. I'm happy enough that others make use of this code. More and more, it seems one needs to have a doctorate degree to understand the power bill, let alone all the solar stuff and it's rules!

    That actually reminds me that the home assistant implementation of 'net energy' is probably useless for most people, because under current schemes, there is a grace period one can consume the produced energy, after which is sold or given away to the grid. And so, when I look at the figures, at the end of the day, I can see what was exported, but I don't know how much of it was during the netmetering period or outside.

    I may add another counter to diferentiate between energy consumed within the netmetering period and energy outside, which was either exported or sold to the grid. I think there is a serious gap on the market to offer something that allows people to understand exactly how they are being billed and how to better make use of their own generated energy...

    I also realized, that I need a way to override the netmering for my diversion load. For example, if it is a water cylinder or a heat pump, I may want it to run on a timer, if there is no production at the end of the day. So this needs to override the energy based rules. With that, I was trying to find out how to read the button presses. Would you be able to tell me where is this function? And also, how to toggle the status LED? I have played arround with "setChannel x 'state'" but I can't get consistent results with that. So any guidance to the relevant documentation would be great.

    I will ditch the 2 minute histerysis to turn the diversion load on and off, and instead rely on the net accumulated energy... Using a 1000W load, as an example, translates to roughly 17W per minute Setting a 40W 'reserve' before the relay turns on provides satisfactory results, without unnecessary delays. I'm presently working with 15min net times, which are the most challenging, but those in poland can choose higher values as they have a whole hour to use any leftovers!

    Now Back to the code...
    Quote:
    I think it should be scripted, we can't have that in code, but you can leave it commented out in the code as example.


    Can you tell me how this scripting works? Is it the autoexec.bat?

    I'm thinking that even if flag 25 is left out, the code will still be in the memory. The only true way to save space is to comment the lines at compilation time? But we would need an easy way to generate the binaries. Maybe a separate compilation with some rules changed?

    Quote:
    Solution is very simple:
    1. make a console command
    2. add interface to our web app:
    https://github.com/OpenBekenIOT/webapp
    for example like:


    That's interesting. So is this webapp pointing to an outside page, instead of being stored on the flash? That would explain why I can't acess it when connected to the Becken hotspot ;)

    I'm going to do some more fine tuning to the code over the next few days, or whenever we have some sun. It would be great if you could clarify how to read the button presses and toggle the status LED.
  • #21 21051414
    cdtdsilva
    Level 10  
    @p.kaczmarek2

    With the aim of making the code as compatible as possible to different devices, can you please add a new flag to invert direction of AC power?
    That's because some devices measure consumption as positive or negative.

    I have have repurposed flag 40 on my tests and that works well, but need one to add to the final code. Something like: 'Invert direction of AC power Flow'

    Thanks
  • #22 21053679
    p.kaczmarek2
    Moderator Smart Home  
    Sure, here is the flag you requested:
    https://github.com/openshwprojects/OpenBK7231...mmit/9b85615336fa44096d3d2620137296c487faa6a1
    Please merge your changes and it's ready to use.

    I am very happy with the recent progress, when do you expect to be ready for the final PR merge?
    Helpful post? Buy me a coffee.
  • #23 21054935
    cdtdsilva
    Level 10  
    Thanks for your help.
    Possibly this weekend. I'm logging data on two units and need to compare it with supplier data to check accuracy.

    Everything seems to be working OK.

    Out of curiosity - Looking at the flag code, with the current flash alocation - How many more flags can we add?
  • #24 21054964
    p.kaczmarek2
    Moderator Smart Home  
    Flags are currently stored as two 32 bit values, so there is a maximum of 64 flags I guess.
    Helpful post? Buy me a coffee.
  • #25 21058515
    cdtdsilva
    Level 10  
    Ok. Would it be acceptable for me to use a few more on some future release?

    I'm thinking as such:
    Enable cooling Fan (When power generation greater than setpoint)
    Remote Relay (The flag would enable or disable a storage heater or heat pump based on excess generation)
    Storage system: When there is no consumption, at the end of the netmetering period, it enables a battery storage, to ofset consumption.
    Disable net meteing: Shows Import and Export exactly as metered.

    If not, I will probably run a separate variant with them.

    On another point, I've been having issues compiling to the BL602. the error messages are rather confusing do you have an idea what the problem might be? Link
  • #26 21058799
    miegapele
    Level 16  

    That strange error might be due to conflicting bool definition. Try replacing bool definition with stdbool as I've done here
  • #27 21058992
    cdtdsilva
    Level 10  
    Screenshot of a GitHub commit showing changes to the new_common.h file with three additions and one deletion. That didn’t work.
  • #28 21059123
    miegapele
    Level 16  

    new_cfg.h needs to be included as it is in many other drivers. bl602 build seems strict on implicit function declarations
  • #29 21060367
    cdtdsilva
    Level 10  
    miegapele wrote:

    new_cfg.h needs to be included as it is in many other drivers. bl602 build seems strict on implicit function declarations


    Thanks, that did the trick!
  • #30 21060386
    p.kaczmarek2
    Moderator Smart Home  
    cdtdsilva wrote:
    Ok. Would it be acceptable for me to use a few more on some future release?
    Enable cooling Fan (When power generation greater than setpoint)
    Remote Relay (The flag would enable or disable a storage heater or heat pump based on excess generation)
    Storage system: When there is no consumption, at the end of the netmetering period, it enables a battery storage, to ofset consumption.
    Disable net meteing: Shows Import and Export exactly as metered.

    This is a lot of flags. Maybe we should consider just giving you an extra byte for "power flags" in config struct?

    That would give you 8 flags.

    But I am not sure, I would need to think about it.

    Futhermore... are those strictly related to power metering? SHouldn't be the "enable cooling fan" be in external driver?
    The same goes for remote relay. Hmm
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around the implementation of a bi-directional energy meter based on the BL0942 chip, which now allows for the measurement of both energy consumption and export to the grid. Key features include net metering capabilities that track self-consumption versus exported energy, and the addition of a remote relay to divert excess energy to appliances like water heaters. Participants discuss code modifications to enhance functionality, including the management of energy statistics, memory allocation, and the introduction of flags for various operational modes. Concerns about flash memory wear and the need for efficient data handling are also addressed, alongside suggestions for improving user interaction with the system through console commands and web interface enhancements.
Generated by the language model.
Today's popular

FAQ

TL;DR: BL0942 meters can now log both import and export, cut flash writes from ~1 000 to <30 per day, and even trigger 7 MQTT updates s⁻¹ at 4 kW if left un-tuned [Elektroda, cdtdsilva, post #21084669] “Flags are currently stored as two 32-bit values” [Elektroda, p.kaczmarek2, post #21054964] Why it matters: Accurate bi-directional data lets you bill, automate and protect flash on cheap Wi-Fi plugs.

Quick Facts

• Default flash page: 4 096 B; log block: 64 B ⇒ 64 writes before erase [Elektroda, p.kaczmarek2, post #21024952] • Energy save threshold ships at 10 Wh; users cut writes to 100 Wh for whole-house metering [Elektroda, cdtdsilva, post #21065687] • BL0942 net-metering tested at 15- and 60-min windows via SetupEnergyStats 1 60 15|60 [Elektroda, cdtdsilva, post #21066744] • Total available flags: 64; two longs hold them [Elektroda, p.kaczmarek2, post #21054964] • One command enables NTP, BL0942 and power-save: backlog Powersave 1; startDriver BL0942; startDriver NTP; ntp_timeZoneOfs <ofs> [Elektroda, cdtdsilva, post #21070093]

How do I enable forward and reverse (import/export) energy counting on a BL0942 plug?

  1. Flash the recent OpenBeken build that includes bi-directional code. 2. Run backlog Powersave 1; startDriver BL0942; startDriver NTP; ntp_timeZoneOfs <ofs> to start the driver. 3. Set flag 25 (SetFlag 25 1) to allow negative readings. 4. If your device reports export as positive, also set flag 48 (SetFlag 48 1) to invert the sign [Elektroda, cdtdsilva, #21070093; #21025841].

Where are the extra energy counters defined and can I add more?

Counters live in drv_bl_shared.c inside the sensors[OBK__NUM_SENSORS] array. Add new entries and update the energySensor_e enum to match the order [Elektroda, p.kaczmarek2, post #21022822] Compile after enabling NTP and running SetupEnergyStats so daily statistics work.

What does the `SetupEnergyStats` command do?

SetupEnergyStats <enable> <sampleSec> <samplesPerSum> sets up circular RAM logging. Example SetupEnergyStats 1 60 60 records 60 values (1 h) at 60 s intervals, letting the firmware compute net-metered energy every hour [Elektroda, p.kaczmarek2, post #21022822]

Can I choose any net-metering period, not just 15 or 60 min?

Yes. Omit the old flag pair and instead set SetupEnergyStats 1 60 <periodMin> in autoexec.bat. The firmware will average import and export over that many minutes, e.g., SetupEnergyStats 1 60 30 for a 30-minute window [Elektroda, p.kaczmarek2, post #21068748]

How do I divert surplus solar to a water heater or battery charger?

Use change-handlers: 1. addChangeHandler NetMetering > 40 SendGet http://192.168.0.69/cm?cmnd=Power%20ON 2. addChangeHandler NetMetering < 5 SendGet http://192.168.0.69/cm?cmnd=Power%20OFF [Elektroda, p.kaczmarek2, post #21060974] "Scripts keep firmware small and flexible."

Edge case: Wi-Fi drops make the module reboot—why?

Long MQTT bursts (up to 7 messages s⁻¹ at 4 kW) can swamp LWIP when Wi-Fi links flap, triggering the watchdog [Elektroda, cdtdsilva, post #21084669] Increase changeSendThreshold or disable HA auto-discovery during testing.

How many configuration flags are left?

The structure holds two 32-bit words, providing 64 flags total. Unused count equals 64 − current usage (≈50 after this patch) [Elektroda, p.kaczmarek2, post #21054964]

I get a BL602 compile error about ‘bool’. Fix?

new_cfg.h must precede other headers and define #include <stdbool.h>. Adding it resolved implicit-function errors in BL602 builds [Elektroda, miegapele, post #21059123]

How do I move TotalGeneration without breaking existing flash layout?

Cast the last two savedValues (4 bytes) in ENERGY_METERING_DATA to a float instead of enlarging the struct. The helper HAL_FlashVars_SaveFloatGeneration() added in commit 9003bc6 handles read/write [Elektroda, p.kaczmarek2, post #21025864]

Does Home Assistant auto-discovery still work after these changes?

Yes. Sensors energycounter, energy_export, and net_metering publish via MQTT and appear under HA Energy Dashboard automatically in testing builds [Elektroda, cdtdsilva, post #21070093]

Quick 3-step: add a cooling-fan relay based on inverter power

  1. Flash firmware and set up BL0942 driver.
  2. addChangeHandler Power > 250 SendGet http://fan-ip/cm?cmnd=Power%20ON.
  3. addChangeHandler Power < 240 SendGet http://fan-ip/cm?cmnd=Power%20OFF [Elektroda, p.kaczmarek2, post #21060974]
Generated by the language model.
ADVERTISEMENT