@flyize Once you set the following, you should be presented with the various sensors, depending on your account:
#SurePetCare credentials set in configuration.yaml
username: !secret my_email_address
password: !secret surepetcare_password
Replace/define the username/password credentials in your own Home Assistant secrets.yaml file, as per guide here
In my case I am presented with various entities for 1x hub, 1x cat connect flap, 2x pets. I can execute the “set_lock_state” service with all 4x values that are available as options (unlocked, locked_all, locked_in, locked_out). There are currently no other service calls defined in script, as far as I’m aware of.
If you do not have your flap_id value already, you may have to enter some dummy flap_id value first, and execute the service call. The error message should then indicate other (possible) correct values to try next. I am presented with 4x values, two of which are the IDs for my pets, and 1x each for the connect flap and the hub. Try each value out and one of them will work.
@benleb , I believe there is some clash/mix between the official surepetcare repo (which has some known issues) and the updated one that some of us loaded via HACS. The result seems to indicate to me that values/fields are not correctly updated and/or presented into lovelace.
In my case I get the updated (correct) data in lovelace after I manually change the hass:icons to something else. Once I select “Update”, the correct pet_status/lock_Status/battery_state is displayed. The manual update of the hass:icon seems to trigger a refresh of the values, which in turn presents the correct data.
Hope the above observation of mine makes some sense to you. I feel that once the updated code is within the official HA/HASSIO repo, it will all sort itself out.
Have a lovely mothers-day