Eduard van Valkenburg

ok, so I added the line above to the tests and there it works so there is something else going on, you have the keys used for encrypting the same...

No that is not completely the case, it can also be raised by the parse_content function later on [(here)](https://github.com/eavanvalkenburg/pysiaalarm/blob/f79fa061a955dda35221a4cd85916392c566b580/src/pysiaalarm/event.py#L373). So I noticed there is a small gap when the account...

which version did you try?

Well, I think changing that would break other alarms. Most alarms use a key inputted as string with just hex characters, so I will have to test to see. What...

I am! In my alarm they ask you to set the key as a hex, so you type in a key with just 0-9A-F, but I'll have a look!

@bropat could you share an example of the key you use, especially the format?

Hey that is fantastic since I can't test that myself, please turn on logging for both the component and package (pysiaalarm) and report back to me here! Take note that...

you need: ``` logger: default: error logs: homeassistant.components.sia: debug pysiaalarm: debug ```

any update on this? the current HA integration uses the latest version of the package which has additional ADM-CID codes so should work for a lot of cases, please let...

That you cannot set the alarm through HA is by design, because the SIA protocol doesn't allow that!