Can't create simplisafe PIN

Third party integrations
1

***I moved this over from Configuration

I’m trying to use the simplisafe integration to create a toggle that enables and dissables a “guest pin” on my SimpliSafe system.

I actually had this running previously, and it worked fine. However, I don’t use it often, so I don’t know if it stopped working with an upgrade, when I migrated to a new HA server, or following some undisclosed API change from SimpliSafe.

The automation below, is the exact automation that worked previously. (I redacted my PIN and system_id for privacy of course)

alias: Simplisafe Enable Guest PIN
description: ''
trigger:
  - entity_id: input_boolean.guest_pin
    from: 'off'
    platform: state
    to: 'on'
condition: []
action:
  - data:
      label: GuestPIN
      pin: ####
      system_id: ######
    service: simplisafe.set_pin
mode: single

When I run it, I get the following error:

Logger: homeassistant.components.simplisafe
Source: components/simplisafe/__init__.py:285
Integration: SimpliSafe (documentation, issues)
First occurred: 11:16:51 PM (1 occurrences)
Last logged: 11:16:51 PM

Error during service call: There was an error while requesting /ss3/subscriptions/######/settings/normal: 409, message='Conflict', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/######/settings/normal?forceUpdate=true')

Any thoughts?

This is the latest Simplisafe hardware, current firmware, HomeAssistant OS on a VM with everything as up-to-date as it gets.

The SimpliSafe docs are at https://www.home-assistant.io/integrations/simplisafe/ and they seem to say this is correct. I just don’t see what I’m missing.

2

Just a bump since I moved this to a different area.

3

As an additional point of information, this appears to affect other system setting changes as well. I have a switch set up to toggle the entry sensor chime, and it returns the same 409/Conflict error message.

4

Try updating to 2021.3.x and see if it helps; improvements were made to handle flaky 409 responses.

5

Well, I get new and different errors in the log now, although the end result is the same.

Logger: simplipy
Source: /usr/local/lib/python3.8/site-packages/simplipy/api.py:336
First occurred: 12:54:14 PM (1 occurrences)
Last logged: 12:54:14 PM

Error while requesting /ss3/subscriptions/REDACTEDSYSTEMID/settings/pins: 400, message='Bad Request', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/REDACTEDSYSTEMID/settings/pins') (attempt 1 of 3)

Logger: homeassistant.components.simplisafe
Source: components/simplisafe/__init__.py:285
Integration: SimpliSafe (documentation, issues)
First occurred: 12:54:26 PM (1 occurrences)
Last logged: 12:54:26 PM

Error during service call: Requesting /ss3/subscriptions/REDACTEDSYSTEMID/settings/pins failed after 4 tries

The new and improved retry system is great, but that doesn’t appear to be the problem here.

6

Since the last update to home assistant a few days ago, I’m back to getting more detailed error messages, but they’re just the same message they were in the beginning, retried a few times.

Anybody else have any ideas?

7

Well, still not working. Thought I’d bump. As of the latest HA version, I now get the following error:

Logger: simplipy
Source: /usr/local/lib/python3.8/site-packages/simplipy/api.py:336
First occurred: March 13, 2021, 8:40:47 PM (48 occurrences)
Last logged: 10:24:58 PM

Error while requesting /ss3/subscriptions/111111/sensors: 409, message='Conflict', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/111111/sensors?forceUpdate=true') (attempt 1 of 3)
Error while requesting /users/222222/subscriptions: 502, message='Bad Gateway', url=URL('https://api.simplisafe.com/v1/users/222222/subscriptions?activeOnly=true') (attempt 1 of 3)
Error while requesting /ss3/subscriptions/111111/settings/normal: 409, message='Conflict', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/111111/settings/normal?forceUpdate=true') (attempt 1 of 3)
Error while requesting /ss3/subscriptions/111111/settings/normal: 409, message='Conflict', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/111111/settings/normal?forceUpdate=true') (attempt 2 of 3)
Error while requesting /ss3/subscriptions/111111/settings/normal: 409, message='Conflict', url=URL('https://api.simplisafe.com/v1/ss3/subscriptions/111111/settings/normal?forceUpdate=true') (attempt 3 of 3)

It’s pretty much the same I’ve been getting all along, except that it now inlcudes references to a user, and there is a 502 error in there for good measure. And of course, there are more retries built in.

8

Are you experiencing this only when setting pins? Do other actions (arming/disarming) seem to work fine?

9

I’m able to arm and disarm consistently. I also get sensor state updates as fast as expected.

I first noticed the problem with PINs, but it appears to happen any time I try to change any kind of settings. PINs, chime volume, etc.

10

Monthly bump. This is still unresolved, and I’m still stymied.

Short of reverse engineering the whole thing and writing my own alternative integration, I don’t know what to do, and I’m afraid that would be utterly over my head.

The structure of the error messages has changed with recent updates because of the introduction of automatic retries, but I’m still getting 409 and 502 errors, which tells me that SimpliSafe moved or restructured something on their end, and this has been broken for everybody. Apparently, I’m the only person who actually uses the simplisafe integration to add PINs, remove PINs, or change settings.

**Correction- It looks like somewhere along the way I regained the ability to control settings. I still can’t add and remove PINS, but I can turn the entry chime on and off again.

11

Something is going on and I need more detail to figure out what. Please submit a bug in the library repo and let’s continue the conversation there: https://github.com/bachya/simplisafe-python/issues/new?assignees=&labels=&template=bug_report.md

12

You’ve probably already seen it, but I did go ahead and create a bug report. I tried to be as detailed as possible, although I don’t know that it contains any information that isn’t already in this thread.

13

Great report! As mentioned there, this has been fixed and flagged for HASS 2021.5.0.

1 Like
14

That’s absolutely fantastic. Thank you!