2.1.1

What's Changed

• issue #76 - device without offpeak_time should not starts at midnight by @jmcollin78 in #77
• Issue #72 - remove battery conditions for offpeak starts

Full Changelog: 2.1.0...2.1.1

2.1.0

What's Changed

• [not working as expected] Issue #66 add reload service by @jmcollin78 in #71
• Issue #70 add min on time per day min by @jmcollin78 in #74

To use this the #70 feature, you should:

1. read carefully the README to learn how it works,
2. change the integration configuration (parameters / integration / solar optimizer / configure) and update the reset time (when the total activation duration is resetted ; ie the begining of the day). It has been set to "05:00" by default,
3. update your configuration.yaml (or solar_optimizer.yaml if you have externalized it) and add some configuration for device that should be activated at a minimum duration: offpeak_time and `min_on_time_per_day_min. See readme for their meaning.

You have example in the readme:

solar_optimizer:
....
  devices:
    ....
    - name: "Water boiler"
      # 2 hours per day maximum
      max_on_time_per_day_min: 120
      # 1h per day minimum ...
      min_on_time_per_day_min: 60
      # ... starting at 22:30
      offpeak_time: "22:30"

This will start you Water boiler at 22:30 if it has not been activated for at least 60 min per day even if the solar production has been too weak. It will be activated until the max_on_time_per_day_min is reach or the reset time (cf. point 2). If max_on_time_per_day_min is not set, it will be activated during all the off-peak hours.

Don't hesitate to make some remarks in the comment of the associated discussion

Full Changelog: 2.0.0...2.1.0

Fix Not usable cannot be forced in offpeak

2.1.0.beta4

Not usable cannot be forced in offpeak

Fix when offpeak_time is > raz_time

In case we want to start between midnight and the raz_time (005h00), the rules was wrong.

Fix 2.1.0.beta2

Report of 2.1.0.beta1 are:

1. starting at off-peak declared in the device seems to work fine,
2. the reset time at 05:00 don't work. My devices, have been reset at 00:00 which was the value before this enhancement. I will have a look why.

All are fixed. I add also should_be_forced_offpeak and raz_time as attributes of the on_time counter so that we be able to watch it.

Beta release for testing #70

Content

This preview release contains a preview of the #70 feature.

Don't install it if you are not invited to do so.

To use this feature, you should:

1. read carefully the README to learn how it works,
2. change the integration configuration (parameters / integration / solar optimizer / configure) and update the reset time (when the total activation duration is resetted ; ie the begining of the day). It has been set to "05:00",
3. update your configuration.yaml (or solar_optimizer.yaml if you have externalized it) and add some configuration for device that should be activated at a minimum duration: offpeak_time and `min_on_time_per_day_min. See readme for their meaning.

You have example in the readme:

solar_optimizer:
....
  devices:
    ....
    - name: "Water boiler"
      # 2 hours per day maximum
      max_on_time_per_day_min: 120
      # 1h per day minimum ...
      min_on_time_per_day_min: 60
      # ... starting at 22:30
      offpeak_time: "22:30"

This will start you Water boiler at least 60 min per day even if the solar production has been too weak.

Don't hesitate to make some remarks in the comment of the issue #70 .

2.0.0

What's Changed

• Issue 47 Maximum On-Time per Device per Day #47
• Issue 60 create virtual for managed device by @jmcollin78 in #61
• Add formatted on_time value by @jmcollin78 in #62
• Add device_name attribute and remove warnings by @jmcollin78 in #63
• Add unit test and release by @jmcollin78 in #64

Full Changelog: 1.7.1...2.0.0

---

To use it you should add a max_on_time_per_day_min: in your solar_optimizer.yaml file. Example:

solar_optimizer:
algorithm:
...

• name: "Equipement name"
  entity_id: "input_boolean.fake_device_g"
  power_max: 1200
  check_usable_template: "{{ True }}"
  duration_min: 1.5
  action_mode: "service_call"
  activation_service: "input_boolean/turn_on"
  deactivation_service: "input_boolean/turn_off"
  battery_soc_threshold: 40
  max_on_time_per_day_min: 30 <------------------ add this
  ...
  You will also notice than there is now one device per devices in solar_optimizer.yaml in which you will find some entities:
  

2.0.0.beta3

What's Changed

• Add device_name attribute and remove warnings by @jmcollin78 in #63

Full Changelog: 2.0.0.beta2...2.0.0.beta3

2.0.0.beta2

What's Changed

• Add formatted on_time value by @jmcollin78 in #62

Full Changelog: 1.7.1...2.0.0.beta2

2.0.0.beta1

What's Changed

• Issue 60 create virtual for managed device by @jmcollin78 in #61
• Issue 47 Maximum On-Time per Device per Day #47

Full Changelog: 1.7.1...2.0.0.beta1

Note: this is beta release and it should contains bug. It is relesed to have more test don by early users.

To use it you should add a max_on_time_per_day_min: in your solar_optimizer.yaml file. Example:

solar_optimizer:
algorithm:
...
- name: "Equipement name"
entity_id: "input_boolean.fake_device_g"
power_max: 1200
check_usable_template: "{{ True }}"
duration_min: 1.5
action_mode: "service_call"
activation_service: "input_boolean/turn_on"
deactivation_service: "input_boolean/turn_off"
battery_soc_threshold: 40
max_on_time_per_day_min: 30 <------------------ add this
...
You will also notice than there is now one device per devices in solar_optimizer.yaml in which you will find some entities: