Aaron Bach

Does this prevent the need for a code in calls to the SimpliSafe `alarm_control_panel`?

CI is a codecov failure; not related to this PR.

It should be okay as-is; I've marked this for the next patch release and will await other folks in the core project to verify or correct any misunderstanding.

Thank you for your patience. Can you send me diagnostics info? That will tell us whether that data is coming through via the API.

Thanks for your patience. Your diagnostics do show that the data is coming through. `hourlyrainin` _is_ a supported sensor though: https://github.com/home-assistant/core/blob/d68ee8dceae7acd2fbdc2be0724847ac0827dcde/homeassistant/components/ambient_network/sensor.py#L130-L137 Can you show me a screenshot of what sensors...

@charliermarsh @zanieb Is there anything further the community could provide input on here? Noting that CM said this was relatively easy; this one feature is all that remains for us...

> @bachya, any possibility the lost code could be added back with release notes stating that it does not authenticate against Simplisafe servers, and the PIN is purely local? With...

> Are you saying you would be welcome a PR to push them changes back in? Or what else would be needed for a PR, I could take a look...

> Could we not keep `_attr_code_arm_required = False` which you just added, and then bring back your changes with that flag set? > > > > Trying to understand how...

PINs via the UI are outside the SimpliSafe integration's direct control, unfortunately. I'm not an expert in that system, but will leave this issue open—perhaps someone more versed in it...