kukulich / home-assistant-jablotron100

Home Assistant custom component for JABLOTRON 100+ alarm system
MIT License
67 stars 24 forks source link

Disarm not recognizing different users #9

Closed tomasbedrich closed 3 years ago

tomasbedrich commented 3 years ago

I do have 3 users in my Jablotron central unit:

When I install the integration using Service user passcode, then only that user's passcode is working to Disarm sections.

When I use passcode of either Admin or Non-admin user for disarming, everything seems good in HA (section green), but the Section is not really disarmed.

I know it worked previously, but I haven't used it for a while. Yesterday I did an update from Docker based HA installation to Home Assistant OS, therefore I wanted to test all the integrations and found this.

There is unfortunately nothing relevant in my logs.

kukulich commented 3 years ago

You should not use "service" user passcode to install the integration. Use the "admin" user.

However I can confirm that the "user" (non-admin) code cannot disarm section that is armed by "admin" user but I'm not sure if it can be solved...

tomasbedrich commented 3 years ago

Thanks for a suggestion regarding installation. I tried installation using Admin user passcode too, but the result is similar: in that case both Admin and Non-admin users were able to arm a section, but only Admin was able disarm it.

In a nutshell: I understand the limitation that Non-admin cannot disarm sections armed by Admin. What is surprising to me is that Non-admin cannot disarm the section he arms previously (in none of the installation methods mentioned above).

kukulich commented 3 years ago

@tomasbedrich Are you able to sniff packets with WireShark?

tomasbedrich commented 3 years ago

I do have some experience reverse-engineering network protocols, but not USB ones. What communication you interested in?

kukulich commented 3 years ago

@tomasbedrich It would be easier if you can connect to Discord https://github.com/kukulich/home-assistant-jablotron100/ :)

kukulich commented 3 years ago

It should be fixed in release 2.4.0 or 3.0.0.

It works in my testing version now :)