elden1337 / hass-peaq Goto Github PK

Depends on all locales having kwh-price

Calc if customer would gain from allowing an increase bc of low el-prices (hourly)

Fix by remving hardcoded parts of charger-aggregation

Since peaq cannot read car's chargelevel.

Set up call, params are

Desired kwh:
Departuretime:

Peaq should then tweak accordingly. As smart as possible. Ie perhaps break peak-energy, perhaps charge more at more expensive hours.

This must all be session-based and return to normal state after next disconnect

if i connect at 4pm and want x kwh to be charged before 7am next morning, let peaq (within the range of the current peaq-level) determine how many hours it needs to utilize and chose the cheapest among those hours.

This is a tricky one, since it cannot know beforehand how much the rest of the house consumes during those hours.

Change the generic chargerstates-object to include a pause/stop-flag. This is needed for Easee to work properly.
Also, after that, alter the charger.py to pause/resume when mid-charging instead of just stopping/starting.

I get different errors with different sensors, see log below.
My asumption is that eithere the naming, or attributes on them do not match up.
Or simply that i have miss judge what sensors that should be provided.

At setup it accepts my input and configuration steps. But then gives error that it cant be set up.
Full log below with modified entity due to adress (for the Tibber Pulse)
First i thought it was about that i have local production so some sensors goes negative, however tested during over consuption with same error.

Let me know what data i can collect and what assistans i can give/help out with

2022-04-19 10:16:08 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.total_power_total_mqtt for peaqev
File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry
File "/config/custom_components/peaqev/peaqservice/hub.py", line 105, in init
File "/config/custom_components/peaqev/peaqservice/hub.py", line 133, in init_hub_values
File "/config/custom_components/peaqev/peaqservice/util/hubmember.py", line 30, in value
2022-04-19 10:20:02 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.power_XXXadressXXX for peaqev
File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry
File "/config/custom_components/peaqev/peaqservice/hub.py", line 80, in init
File "/config/custom_components/peaqev/config_flow.py", line 77, in async_step_user
File "/config/custom_components/peaqev/config_flow.py", line 56, in validate_input_user
File "/config/custom_components/peaqev/config_flow.py", line 38, in _check_power_sensor
2022-04-19 10:31:51 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry sensor.power_XXXadressXXX for peaqev
File "/config/custom_components/peaqev/init.py", line 32, in async_setup_entry
File "/config/custom_components/peaqev/peaqservice/hub.py", line 80, in init

The price calc for hours only takes today into account.
I think we should do now and 24hr forward (if Nordpool had released tomorrow's prices) so that one can see when charging will start next time if stopped.

Originally posted by @elden1337 in https://github.com/elden1337/hass-peaq/discussions/38#discussioncomment-2648785

If using priceawareness. Combine peak tariffe price and elec price

All hours under this price are removed from non- or caution-hours

I feel really stupid but i cant get it to work, my guess is that i give the wrong Chargepoint ID
Tried all kind of stuff related to device and entitys

Checked out the code to see what it could be related to and tested. Sadly no luck

Easee charger, device is called 42 but i tried with different entitys aswell without luck
I asume that the power sensor should the the full entity name and mesure in W since power. Have a few but so far no luck

https://www.lindeenergi.se/elnat/elnatspriser/effekttariffer.4.1491a0b016e44ba6ccfe91b4.html

closed the last ticket, after clean install, and trying to figure out what could be wrong with my setup.

Guessing it got somthing with how to with the additional of the Nordpool, since this started to hapen when the priceaware beta got released.

Not really sure how to debugg or find the logs when it comes to custom integration setup throu gui. Let me know if its just my installation and what i can do.

v0.5.3
core-2022.4.7
supervisor-2022.04.0
Home Assistant OS 7.6

Move core functionality to separate package to be able to use peaqev in other places than HA.

• Prediction
• Threshold
• Controllers

https://www.distriktsenergi.no/artikler/2021/6/11/effekttariffer-vedtatt-endelig/

bool-setting

Adheres to the nordpool fluctuation.

if priceaware, create dynamic caution hours.

this will allow peaq to charge up to a certain threshold dynamically and not just based on the set peak.
with this feature, there will be a possibility to charge "a little" when prices are high but not high enough to cause a non-hour

Any example on how to set this up in conifguration since I am getting this error in lastest beta in v0.4.2-rev2

different ones. some have every weekend and every night
some have whole months

https://malungselnat.se/elnat/nattariffer/

Info: https://www.openevse.com/
API documentation: https://openevse.stoplight.io/docs/openevse-wifi-v4/

Updatecurrent must be audited. It seems to be updating only on init charging and when charger is paused.

Help wanted. Someone with easee needs to qa it since im having a hard time finalizing without the possibility to debug.

it should be possible to set an amp limiter in setup, based on your house total allowance.
peaq should then adhere to this and not up the amps on the charging, even if tolerance for peakhour would allow it.
this feature should also be able to disable the charger during high load.

The sensors break on HA updates because of various refactorings on the core side.

We need to restructure how peak is storing data in order to work without breakage when new releases of HA are made.

Sensor types that need to be altered are:

Integrationsensors
Utility meters
Sql sensors

Aura has 2x22kw chargers built in. Current chargeamps only supports (most def) Halo with one outlet.

https://skovdeenergi.se/effekttaxa-elnat/

If priceaware, check current peak, and try to calc the max kwh-price for today based on peak vs avg consumption vs el-prices vs caution and nonhours.

https://www.home-assistant.io/integrations/keba/

https://github.com/lbbrhzn/ocpp

Note from @jonasbkarlsson: make sure to alter on/off/pause/resume to not be bound to service calls.

Make template for people wanting to add locale or chargertypes with what's needed.

• Better logging on hubmembers and hubdata
• Ignore typeerror on init, but delay service starts until all is init

https://www.bjerke-energi.se/elnat/tariffer/effekttariff-fr-o-m-2022-02-01/

Could you add Belgium in the future?

Peak will be calculated for a period of 15 minutes.

The average of 12 month peaks will be the chargeable peak.

Done not triggered correctly by chargecontroller
Done not disabling charging
Done not disabled when starting new chqring session.

• fix chargecontroller as session bound and reinitialized

https://sheab.se/vinterpris-pa-effekttaxan-1-november/