-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only panel and contact entities are added #32
Comments
I have the same issue. I can see the panel and can bypass the sensors however I am unable to gain their status. Im not a programmer but trying to hash my way through! |
@PeterSR Did you ever work it out? |
Sadly no. I didn't look much into and just came to the conclusion that maybe I should just get a new alarm system that is more smart home friendly. |
What did you go for? |
I actually didn't go with anything yet. Currently I am just using the Visonic-Go app and haven't hooked anything else alarm-related up to HA. Might look into it in some months. |
Try the latest version, V3.1, and see if that solves the problem. I extended some of the subtypes. |
Thanks for your work on this. I am not using any of the subtypes but the recent update just fixed my install. |
Thank you for the integration.
I have it up and running, and I am able to arm and disarm the alarm which is the most important thing.
In my house, I have a panel, a couple of indoor sensors and some contacts for the doors. Here's what I see if I use the script from https://github.com/And3rsL/VisonicAlarm2:
In Home Assistant, I only have two entities other than the
alarm_control_panel.visonic_alarm
, namely the two contacts:sensor.visonic_alarm_8060
andsensor.visonic_alarm_8061
.I had a brief look through the code and it seems that only certain types and subtypes get created. Do you know if it could be possible to add some of the other Visonic devices as Home Assistant devices? I might be able to do a PR, but would be nice if you already have some learnings.
The text was updated successfully, but these errors were encountered: