Feature Request: Add entities for "next_event", "duration" and "start_time"

[303acid]

Hi Simone,

first of all, thank you for this great integration!

I am using SimpleScheduler for a battery-powered irrigation system based on ESP32. To save power, the ESP32 uses Deep Sleep and needs to know exactly when the next event will happen to calculate its wake-up time.

Currently, I have to manually parse the simplescheduler.json file via a command-line sensor in Home Assistant, which is quite complex.

It would be amazing if the integration could provide the following as native entities or attributes:

next_event_time (The very next scheduled ON or OFF -time)

next_event_duration (The duration of that specific event)

current_status (A simpler way to see the next transition)

This would make the integration much more powerful for everyone using low-power hardware (ESPs, E-Paper displays, etc.).

Keep up the great work!
Best regards,
Mike, not a progammer only hobbyist ;-)

[arthurdent75]

I think you can already achieve what you need.
Just to be sure, can you please write here the configuration/time list of one of your schedulers?

[303acid]

{"id": "cc061681313d40e0990827f462e9d9e8", "name": "Slot1", "enabled": "1", "entity_id": ["switch.testclient_ventil", "switch.nussbaum_ventil"], "recurring": {"on_start": "00:00", "on_end": "23:59", "on_interval": "10", "off_start": "00:02", "off_end": "23:59", "off_interval": "10"}, "on_tod": "00:00 00:10 00:20 00:30 00:40 00:50 01:00 01:10 01:20 01:30 01:40 ...aso ", "on_dow": "1234567", "off_tod": "00:02 00:12 00:22 00:32 00:42 00:52 01:02 01:12 01:22 01:32 01:42 ...aso ", "off_dow": "1234567", "dontretry": 0, "template": ""}

this list (extreme test case):
Start 00:00 Interval 10
Stop 00:02 Interval 10 

results in 'switch on for 2 minutes, every 10minutes'

The associated JSON is very long. Currently, I parse and calculate this to create a command-line sensor - Python script. This generates a sensor with:

State: next_event_time (HH:MM)

Attributes: duration: 2, t1: "15:50" (start), t2: "15:52" (stop)

I’ve integrated this sensor into my ESPHome project, and it works, but the usability is poor. If I had this data available natively, I wouldn't need the complex Python script to create the sensor.