Hey there @dan-r, mind taking a look at this feedback as it has been labeled with an integration (ohme) you are listed as a code owner for? Thanks!

Whoops, I hit 'send' too soon. The code to make the action work (ref ### Issue 1) is:

action: ohme.list_charge_slots
data:
config_entry: 1234567890ABCDEFGHIJKLMNOP

(I mention this because the Developer Tools -> Actions tab does not usefully guide a user towards the correct answer)

For me the dev tools > actions tab gives me a dropdown that lets me select my account. The go to yaml button then shows the config entry ID.

I too am interested in some better docs around issue 2 above.

I simply cannot get my template sensor to return anything but an array with 1 item, which is a string of all the charging slots, which I can’t do much with.

- trigger:
    - platform: time_pattern
      minutes: /15
    - platform: homeassistant
      event: start
  action:
  - action: ohme.list_charge_slots
    data:
      config_entry: {config_entry_id}
    response_variable: charging_slots
  sensor:
  - name: Ohme charging slots
    unique_id: cheap_charge_slots
    icon: mdi:lightning-bolt
    state: "{{ charging_slots.slots | count() }}"
    attributes:
      events: "{{ charging_slots.slots }}"

Would love a simple example in the docs, where I can return the same array of slots as the action in a template sensor to use on my dashboard.

@dan-r , please accept my apologies...I was in YAML mode and therefore didn't see that dropdown/selector.

I might still suggest including this hint in the documentation, because none of the googling I did led me to using UI Mode to select the integration (identified in an easy to read format of my email address!) and then moving to YAML mode to find the ASCII string which one might need when pulling together an automation / script to actually conduct the action usefully.

I remain stuck with ### Issue 2, however and I remain unable to fetch the array and place it in the attributes of a useable sensor / helper / set of helpers.

But that said, I am sorry about ### Issue 1 - fully my bad!

Both,

In terms of the documentation, I think it'd be something needed on a wider scale than just this integration so if you find an area you think this would fit, it might be worth a separate issue.

On the topic of charge slots sensor, I've added it to the core version under home-assistant/core#139203 and it behaves in the same way as in the HACS version, so no need for any templating. If you want notifications on this, it should be as simple as setting up an automation when the value moves from unknown to anything. This will be in the March release which should begin beta testing very shortly.

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved.
If this issue is still relevant, please let us know by leaving a comment 👍
This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.