PV / Solar Excess Optimizer: Auto-control appliances (wallbox, dish washer, heatpump, ...) based on excess solar power

nukleuz80 · May 27, 2024, 7:05am

Hi there,

i´m testing this pretty cool Blueprint and have a question to understand the logic of it.
I have a standard micro-converter. 1600W IN / 600W/800W out…

When will the appliances start?

My appliance “Schreibtischlampe” is starting when the LOAD POWER (Grid) is 180W / EXPORT-POWER = 0W and the PV-POWER is 120-200W.

It´s own consumption in Watt is 8W. I don´t have EXCESS!

I use this configuration without battery.

alias: pv_excess_schreibtischlampe
description: ""
use_blueprint:
  path: inventocasa/pv_excess_control.yaml
  input:
    automation_id: pv_excess_schreibtischlampe
    pv_power: sensor.pv_power_gesamt_bkw_1_und_2
    appliance_switch: light.schreibtischlampe_buro
    appliance_switch_interval: 1
    actual_power: sensor.schreibtischlampe_buro_power
    min_home_battery_level: 0
    load_power: sensor.power_vom_netz_watt
    export_power: sensor.power_ins_netz_watt
    defined_current: 6
    appliance_priority: 2

Do i need the Combined Import/Export Power for my setup or is the behavior normal?

What i expected: Only start the appliances (ON…) when there is Excess.

Thanks!

cypresss · May 27, 2024, 12:43pm

Hello everyone,

is there a way to stop pyscript from spamming my logbook?
It creates entries every 10 seconds!

Jmoos · May 27, 2024, 2:33pm

Thank you for this Blueprint!
I have been testing with a simple smartplug and this works as expected.
However when i want to add my smart dishwasher using the Home Connect ALT integration it does not work as expected. I see the following errors in the logging

This error originated from a custom integration.

Logger: custom_components.pyscript.file.pv_excess_control.on_time
Source: custom_components/pyscript/eval.py:1941
integration: Pyscript Python scripting (documentation, issues)
First occurred: May 26, 2024 at 13:34:16 (3391 occurrences)
Last logged: 16:22:17

[button.011090388881000357_start_pause (Prio 1)] Appliance state (=2024-05-25T15:10:11.931062+00:00) is neither ON nor OFF. Assuming OFF state.
Cannot switch on appliance: Service "button.turn_on" does not exist.
[button.011090388881000357_start_pause (Prio 1)] Appliance state (=unavailable) is neither ON nor OFF. Assuming OFF state.
num=unavailable is not a valid number between 0 and 1000000: could not convert string to float: 'unavailable'
Could not update Export/PV history!: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

The entity i use in the blueprint is:
button.011090388881000357_start_pause
This entity becomes available when i enable remote start on the dishwasher. This is as expected. And is a safety feature of the manufacturer.

I suspect i need a switch entity in the blueprint. Is there a way to “convert” the button to a switch? Or am i missing something in the configuratoin of the blueprint?
Any help is appreciated

cypresss · May 28, 2024, 6:11am

I can’t be the only one annoyed by this

nukleuz80 · May 28, 2024, 6:41am

Hey, it seems that i needed the import/export combined power sensor.
Everything works like a charm…

nukleuz80 · May 28, 2024, 6:42am

Hi, isn´t it possible to remove the logger in configuration.yaml?

cypresss · May 28, 2024, 7:08am

The entries in the logbook are generated by the pyscript integration:

github.com/custom-components/pyscript

Logbook Functionality

custom-components:master ← dlashua:logbook

opened 10:57AM - 29 Oct 20 UTC

dlashua

+102 -8

There might be a better way to do this instead of using `Function` like I have. …However, it works. A few things to note. * The event fired before the function runs can be named anything we want. I chose "pyscript_running" and then realized Home Assistant uses "automation_triggered". This can be renamed by changing it in both `trigger.py` and `logbook.py`. * While I have confirmed that `state.set()` is sending the correct context to the best of my knowledge, it seems that states set in this manner don't show up in the log book at all. The state still "sets" as expected, but there is no logbook entry. Therefore, all of the "context" code can be removed from `state.set()` if desired. * I've left the original context as part of the trigger function kwargs. This way, pyscript users can still look at `user_id` to determine who did something. Unfortunately, determining if **pyscript** did something would mean climbing the context tree, which is tedious. * I've also left context as an optional kwarg to `service.call` and `event.fire`. If a users passes a context, it'll use that. If they don't and we have one from the `pyscript_running` event we fired, it'll use that. If they want to disable the logbook functionality for some reason, they can pass `context=Context()`. * The logbook attributes actions to entity_ids. And entity ids can only have one "." between the domain and name. So I'm sending, essentially, `__name__`, with "." converted to "_". This means the entity_ids are a bit ugly (ex. `pyscript.file_myfile_myfunction`). This is set in `trigger.py` and can be changed to anything we want as long as it fits the rules for entity ids. I've tested events, service_calls, time triggers, and state.set with this code: ```python @state_trigger(["input_boolean.test_1"]) def test_state_trigger(**data): log.info("test_state_trigger") input_boolean.toggle(entity_id="input_boolean.test_2") state.set("binary_sensor.test", "on") @event_trigger("PYSCRIPT_TEST") def test_event_trigger(**data): log.info("test_event_trigger") input_boolean.toggle(entity_id="input_boolean.test_3") @state_trigger(["binary_sensor.test"]) def report_binary_sensor(**data): log.info(f"binary_sensor trigger with {data}") @time_trigger("startup") def test_time_trigger(**data): task.sleep(3) log.info(f"test_time_trigger {data}") input_boolean.toggle(entity_id="input_boolean.test_4") ``` It results in this logbook: ![logbook](https://user-images.githubusercontent.com/4126703/97559509-86680c80-19ab-11eb-88cf-f3852a51d2ab.png)

But I can’t find a way to disable them for the PV Excess script only.

Logbook or recorder exclusions in the configuration.yaml only work with entity IDs.

RienduPre · May 28, 2024, 10:33am

Help with my setup

I only get many of the same log items in my logboek

2024-05-28 12:22:16.250 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time got time trigger, running action (kwargs = {'trigger_type': 'time', 'trigger_time': datetime.datetime(2024, 5, 28, 12, 22, 16, 245653)})
2024-05-28 12:22:16.250 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time time_next = 2024-05-28 12:22:26.245653, now = 2024-05-28 12:22:16.250553
2024-05-28 12:22:16.251 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time waiting for 9.9951 secs
2024-05-28 12:22:16.266 DEBUG (MainThread) [custom_components.pyscript.eval] file.pv_excess_control.on_time: calling on_time(, {'trigger_type': 'time', 'trigger_time': datetime.datetime(2024, 5, 28, 12, 22, 16, 245653)})
2024-05-28 12:22:16.425 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time got time trigger, running action (kwargs = {'trigger_type': 'time', 'trigger_time': datetime.datetime(2024, 5, 28, 12, 22, 16, 423652)})
2024-05-28 12:22:16.426 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time time_next = 2024-05-28 12:22:26.423652, now = 2024-05-28 12:22:16.426245
2024-05-28 12:22:16.426 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time waiting for 9.99741 secs
2024-05-28 12:22:16.430 DEBUG (MainThread) [custom_components.pyscript.eval] file.pv_excess_control.on_time: calling on_time(, {'trigger_type': 'time', 'trigger_time': datetime.datetime(2024, 5, 28, 12, 22, 16, 423652)})
2024-05-28 12:22:17.104 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time got time trigger, running action (kwargs = {'trigger_type': 'time', 'trigger_time': datetime.datetime(2024, 5, 28, 12, 22, 17, 103568)})
2024-05-28 12:22:17.105 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time time_next = 2024-05-28 12:22:27.103568, now = 2024-05-28 12:22:17.104925
2024-05-28 12:22:17.105 DEBUG (MainThread) [custom_components.pyscript.trigger] trigger file.pv_excess_control.on_time waiting for 9.99864 secs

But nothing happens with my applicance?

Any help is more than welcome (I use the latest versions of all)

My automation yaml files is like this:

alias: Zwembad Warmtepomp PV excess optimizer
description: ""
use_blueprint:
  path: InventoCasa/pv_excess_control.yaml
  input:
    automation_id: "74075083"
    pv_power: sensor.actueel_zonnepanelen_opbrengst
    export_power: sensor.electricity_meter_energieproductie
    load_power: sensor.actueel_huis_gebruik
    home_battery_level: sensor.sessy_de7j_state_of_charge
    solar_production_forecast: sensor.solcast_pv_forecast_forecast_remaining_today
    actual_power: sensor.zwembad_total_power
    appliance_switch: input_boolean.zwembad_verwarming
    home_battery_capacity: 5

nukleuz80 · May 28, 2024, 12:46pm

I think your automation_id has to be the same with alias

EDIT: Check → PV / Solar Excess Optimizer: Auto-control appliances (wallbox, dish washer, heatpump, ...) based on excess solar power - #70 by InventoCasa

RienduPre · May 30, 2024, 2:22pm

Check !!!

That did the trick

Monster_D · May 31, 2024, 10:27am

wow … as the solcast integration is dead/deleted … what forecast method do you use for

solar_production_forecast: sensor.solcast_pv_forecast_forecast_remaining_today

and how happy are you with it?

Monster_D · May 31, 2024, 4:29pm

For now other users saved the work and keeping on with the solcast integration. Fingers crossed the api will not change to soon…

Reunion974 · June 2, 2024, 12:02pm

I use forecast.solar, it work fine.
I never used solcast as I’m out of its coverage area.

Mylua31 · June 2, 2024, 3:50pm

Hello,

I am testing this Blueprint, I made my frist automation but something is not working.

Calculated average excess power based on >> solar power - load power <<: 0 W

I use two sensors :

PW Power : sensor.envoy_consommation_electrique_actuelle, current state: 1.551 kW
Combined Import/Export Power : sensor.envoy_production_d_electricite_actuelle, current state : 0.512 kW

So the calculated excess power should not be null.

Can someone help me, please ?

techydude · June 3, 2024, 11:38am

Hi Juergen, me again
Could you please post the full entry for your sensor.new_charge_current_int is a template sensor?

Is this in templates.yaml? so:

sensor:
?

juergenjw · June 3, 2024, 11:46am

I created the sensor as template helper.

using the template from above.

cypresss · June 4, 2024, 10:49am

I have the exact same problem.

Was this ever solved for you over the last year?

Neroson · June 4, 2024, 2:53pm

Hi, first I would like to thank for this great Automation

any chance to implement 3-Phase to 1-Phase switching and vice versa?
Would be a great feature for a Wallbox.

Maik7 · June 7, 2024, 9:32pm

The issue is solved. Just update the script.

Reunion974 · June 8, 2024, 2:04pm

Hello @Maik7
I’m so happy, I can see that your 2 pull requests have been merged!

So there is no more issue with the dynamic priority?
We can use a template to define the priority in the automation and dynamicaly modify this priority, and then execute in the same script the PV automation to refresh with “service: automation.trigger” , right?
About the priority >1000:

You documented the priority adding:

If the priority is greater than 1000 this appliance will be switched on, even if the excess power is not sufficient for 100% of the needed power

Can you please precise the behaviour when prio > 1000 ?
Is the appliance ON while the solar panel produce 50% of the needed power? and then it is turned off? or is it different?
Also is it possible to modify the percentage??

Thank you so much