V2025.01.06

V2025.01.06
Fixed bug #114, #116 - Entities card yaml: Incorrect switch identifiers when updating the configuration

This Release V2025.01.xx

BREAKING CHANGE

• Depending on the complexity of the implementation some options may need to be transitioned to different entity types.
• Frequency selection options will need to be updated in the program configuration.
• The custom card will need to be edited.

This has been a significant redevelopment.
All helper objects are now created automatically. All you need to configure now are the switches/valves and sensors.

Naming of entities is determined using the translation files. These have gaps so please volunteer to update or provide a new file. Contact me if you can help, it is not a complex process.

The custom card has been updated for this release, the move to entities rather than attributes on the program switch have allowed for a richer experience leveraging the icon translation capabilities.

It is now easier to get support information with the integration of Diagnostics

Frequency can now be determined as an offset of Sunrise or Sunset.

Add the option to pause and resume a running program.

Allow multiple zones to run concurrently in a program. If this setting is selected the zone transition is not available.

Upgrading

• Once installed:
• The frequency options will default to a single value '1', reconfigure the program to add additional options.
• Watering time/volume will default to 1.
• ECO attributes will default to 1.
• The previous version supported input types for sensors, these have been limited to sensor, or binary_sensor types. Where the existing configuration does not comply the entry will be removed and a notification raised. Samples of translating input types to sensors can be found in the test helpers yaml file.
• the custom card will be upgraded, edit the card to select the zones to display. CTRL-Click to select multiple zones.

Experiencing issues with the custom card?

V2025.01.03 provides the yaml to recreate the custom card as an entities card. The custom card is just an entities card that has been automatically populated.

• The script is regenerated each time you modify the configuration and on restart.
• Copy the script to a manual card.
• More detail here
• You need to enable the feature in the advanced setting of the program.

Note:

• You can remove the helpers that have been created for Frequency, Start time ... These will be automatically created now.
• The name of entities is dependent on the translation files. Please reach out if you can help translate the files.
• Setting frequency and start time via a sensor is no longer possible

v2025.01.05

V2025.01.05
Fixed bug #110 - Adjustment factor >1 not working on Rainbird controllers
Updated German translation file

This Release V2025.01.xx

BREAKING CHANGE

• Depending on the complexity of the implementation some options may need to be transitioned to different entity types.
• Frequency selection options will need to be updated in the program configuration.
• The custom card will need to be edited.

This has been a significant redevelopment.
All helper objects are now created automatically. All you need to configure now are the switches/valves and sensors.

Naming of entities is determined using the translation files. These have gaps so please volunteer to update or provide a new file. Contact me if you can help, it is not a complex process.

The custom card has been updated for this release, the move to entities rather than attributes on the program switch have allowed for a richer experience leveraging the icon translation capabilities.

It is now easier to get support information with the integration of Diagnostics

Frequency can now be determined as an offset of Sunrise or Sunset.

Add the option to pause and resume a running program.

Allow multiple zones to run concurrently in a program. If this setting is selected the zone transition is not available.

Upgrading

• Once installed:
• The frequency options will default to a single value '1', reconfigure the program to add additional options.
• Watering time/volume will default to 1.
• ECO attributes will default to 1.
• The previous version supported input types for sensors, these have been limited to sensor, or binary_sensor types. Where the existing configuration does not comply the entry will be removed and a notification raised. Samples of translating input types to sensors can be found in the test helpers yaml file.
• the custom card will be upgraded, edit the card to select the zones to display. CTRL-Click to select multiple zones.

Experiencing issues with the custom card?

V2025.01.03 provides the yaml to recreate the custom card as an entities card. The custom card is just an entities card that has been automatically populated.

• The script is regenerated each time you modify the configuration and on restart.
• Copy the script to a manual card.
• More detail here
• You need to enable the feature in the advanced setting of the program.

Note:

• You can remove the helpers that have been created for Frequency, Start time ... These will be automatically created now.
• The name of entities is dependent on the translation files. Please reach out if you can help translate the files.
• Setting frequency and start time via a sensor is no longer possible

V2025.01.04

V2025.01.04 - add Spanish translation file

This Release V2025.01.xx

BREAKING CHANGE

• Depending on the complexity of the implementation some options may need to be transitioned to different entity types.
• Frequency selection options will need to be updated in the program configuration.
• The custom card will need to be edited.

This has been a significant redevelopment.
All helper objects are now created automatically. All you need to configure now are the switches/valves and sensors.

Naming of entities is determined using the translation files. These have gaps so please volunteer to update or provide a new file. Contact me if you can help, it is not a complex process.

The custom card has been updated for this release, the move to entities rather than attributes on the program switch have allowed for a richer experience leveraging the icon translation capabilities.

It is now easier to get support information with the integration of Diagnostics

Frequency can now be determined as an offset of Sunrise or Sunset.

Add the option to pause and resume a running program.

Allow multiple zones to run concurrently in a program. If this setting is selected the zone transition is not available.

Upgrading

• Once installed:
• The frequency options will default to a single value '1', reconfigure the program to add additional options.
• Watering time/volume will default to 1.
• ECO attributes will default to 1.
• The previous version supported input types for sensors, these have been limited to sensor, or binary_sensor types. Where the existing configuration does not comply the entry will be removed and a notification raised. Samples of translating input types to sensors can be found in the test helpers yaml file.
• the custom card will be upgraded, edit the card to select the zones to display. CTRL-Click to select multiple zones.

Experiencing issues with the custom card?

V2025.01.03 provides the yaml to recreate the custom card as an entities card. The custom card is just an entities card that has been automatically populated.

• The script is regenerated each time you modify the configuration and on restart.
• Copy the script to a manual card.
• More detail here
• You need to enable the feature in the advanced setting of the program.

Note:

• You can remove the helpers that have been created for Frequency, Start time ... These will be automatically created now.
• The name of entities is dependent on the translation files. Please reach out if you can help translate the files.
• Setting frequency and start time via a sensor is no longer possible

V2025.01.03

This Release V2025.01.xx

BREAKING CHANGE

• Depending on the complexity of the implementation some options may need to be transitioned to different entity types.
• Frequency selection options will need to be updated in the program configuration.
• The custom card will need to be edited.

This has been a significant redevelopment.
All helper objects are now created automatically. All you need to configure now are the switches/valves and sensors.

Naming of entities is determined using the translation files. These have gaps so please volunteer to update or provide a new file. Contact me if you can help, it is not a complex process.

The custom card has been updated for this release, the move to entities rather than attributes on the program switch have allowed for a richer experience leveraging the icon translation capabilities.

It is now easier to get support information with the integration of Diagnostics

Frequency can now be determined as an offset of Sunrise or Sunset.

Add the option to pause and resume a running program.

Allow multiple zones to run concurrently in a program. If this setting is selected the zone transition is not available.

Upgrading

• Once installed:
• The frequency options will default to a single value '1', reconfigure the program to add additional options.
• Watering time/volume will default to 1.
• ECO attributes will default to 1.
• The previous version supported input types for sensors, these have been limited to sensor, or binary_sensor types. Where the existing configuration does not comply the entry will be removed and a notification raised. Samples of translating input types to sensors can be found in the test helpers yaml file.
• the custom card will be upgraded, edit the card to select the zones to display. CTRL-Click to select multiple zones.

Experiencing issues with the custom card?

V2025.01.03 provides the yaml to recreate the custom card as an entities card. The custom card is just an entities card that has been automatically populated.

• The script is regenerated each time you modify the configuration and on restart.
• Copy the script to a manual card.
• More detail here
• You need to enable the feature in the advanced setting of the program.

Note:

• You can remove the helpers that have been created for Frequency, Start time ... These will be automatically created now.
• The name of entities is dependent on the translation files. Please reach out if you can help translate the files.
• Setting frequency and start time via a sensor is no longer possible

V2025.01.03b3

• fix missing program buttons

V2025.01.03b2

V2025.01.03b2

• Correct some differences in the entities card yaml export
• add config flow option to enable/disable the production of the yaml export
• correct an issue when removing a configuration, remove the entry from the domain correctly

V2025.01.03b1

To work around issue #103

• Add persistent notification providing the yaml to create the the equivalent of the custom card using a manual card
• Copy the script from the notification into a manual card replacing any text present in the card.
• When saved a entities card is created with the same interface as the custom card.
• The script will be regenerated each time the irrigation program is modified and on restart

V2025.01.02b60

More work on issue #103

V2025.01.02b23

Another attempt at fixing issue #103

V2025.01.02b20

Issue #103