Robert Cook

This is probably due to the HA history work, which, I get, but gee whiz guys. This issue is most likey solved with some recent updates to the repository. The...

It is now officially released as 2022.6.0. Should come through soon via HACS. This following is text from the release notes about a config file error. It would be better...

You can setup a long-term statistics sensor like this: ```yaml template: - sensor: - name: Today Total C1 Z1 state_class: total_increasing icon: mdi:sprinkler unit_of_measurement: s state: > {{ state_attr('binary_sensor.irrigation_unlimited_c1_z1', 'today_total')...

I had only fleeting acquaintance with LTS when setting up my solar. Did a deep dive on the link you sent and created that sensor yesterday. Let me know how...

Now documented. Closing issue.

Short answer, yes. Take a look at the irrigation_unlimited.coordinator entity, it is the component entity for the integration, basically the top of the tree. This entity has an attribute `configuration`...

Exposing the schedule or other data is really not a problem. If you want specific pieces of information then perhaps a RESTful API might be the way to go.

There exists an undocumented `show:` parameter `config: true` which will expose the schedules on each zone entity. Place it under `all_zones_config:` or under the `zones:` for individual zones. ```yaml irrigation_unlimited:...

We might be talking cross purposes here. I think I understand but need to clear up some terminology. A `schedule` is not a datetime object but rather a set of...

A 'schedule centric' view, interesting. Let me see what I cobble together. Overlapped schedules are managed correctly. For any given zone, if at least one schedule is active then it...