This is currently correct. I haven’t done anything with this for a little while due to other projects . The alarm doesnt really provide a state for devices like PIRs etc. I was going to look at how to make this make more sense but still on todo list.
Hello Mark
Thank you so much. I appreciate your quick response. I await the continuation of your developments to take into account the state of the sensors. Best app for this alarm.
See you soon
Best Regards
Hello Mark,
Your work is highly appreciated!
I just installed the repo and did the configuration to integrate my Panel.
I can see the devices and the status of the Panel, but cannot Arm or change any state of the panel for that matter.
Checking the Entity - it is marked as “Read Only”
Not sure why - I have PowerMaster 10
John
Can you provide a diagnostics and any log errors. Also a screenshot showing the entity (presume alarm panel entity) where it is showing read only. Thx
It could be as a result of this:
This entity ('alarm_control_panel.visonic_alarm') does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.
Can you provide the diagnostic download. I need that to look into this. You can post it to a github issue. Its redacted for any sensitive info.
You made my day! It works with DSC Neo alarms as well, The various arming/disarming functions works like a charm as well as the tags.
For some reason hardwired zones does not show up. By design?
I’m so sorry, but I’m not sure how to provide the “diagnostic download”.
I do know it’s possible for devices, but this integration provides entities only, no devices or integration block.
Is there a way to download this diagnostics from the entity?
On the 3 dots in settings → devices and services → visonic alarm as per below.
If that is not there then you are not using the right integration.
Edit: Actually, i dont think you are using the right integration as the name is Visonic Alarm System, not Visonic/betel/tyco as in your image. I would remove all this and follow these instructions to install this particular one. As said above in this thread, it works but is not fully released.
Yes indeed I had the wrong integration.
Thank you very much, the integration works great, I can arm and disarm nicely!
John
Hello Marc,
Have you found some time to add sensor status to your Visonic alarm app?
Many Thanks
Best Regards
Not yet i’m afraid. Much on the go atm with a big house refurb and significant updates to a couple of other integrations i write and support. I cant tell my wife she has no kitchen for xmas because i’ve been playing with the alarm integration! 
Maybe i’ll get some time in the new year. Don’t hold out for too much though as not sure how much status info you can get from the cloud api due to timing delays and only doing a periodic update call. I dont think there is any push capability from the cloud api.
Good morning,
I understand your priorities very well. Good luck with the work in your home. A lovely Christmas gift for your wife.
I hope to be able to see you again next year around the Visonic application.
Happy New Year and Merry Christmas.
Thank you for this integration! Works perfectly!
I just encountered 2 bugs:
1/ When the alarm is activated and you enter the house, the alarm status is unknown instead of being “disarming” or “pending”.
2/ The detectors are in unknown status.
And another great update is to see the battery status of sensors 
Happy New Year and Merry Christmas!
Hi all, I’m looking into trying to get msp1974’s integration working for our Visonic alarm and I’ve got HACS installed and the integration installed but I’ve not worked with RESTful. Can anyone guide me on how I need to do that?
I looked at the code and it seems to be set for a pool alarm system, so I just need a bit a pointer on which lines I need to change and which to leave well alone!!
Thanks in advance!
William
Will,
It should just work as long as you have a Powerlink module in your alarm and have setup an account with a monitoring service. What issue are you having?
Hi @msp1974,
I tried running your integration, but ran in to some issues. No contact sensors where detected. Did some troubleshooting and found that my sensors report as “CONTACT_V” -added contact_v to const.py and they appeared in HA, bypass seem to work -but state is just showing as “unknown”. Any input on what needs to be done to get open/closed state working?
sensor sample from diagnostics:
"717781": {
"device_number": 19,
"device_type": "ZONE",
"enrollment_id": "104-1084",
"id": 717781,
"name": "Office Window",
"partitions": [
1
],
"preenroll": false,
"removable": true,
"renamable": true,
"subtype": "CONTACT_V",
"traits": {
"bypass": {
"enabled": false
},
"rarely_used": {
"enabled": false
},
"rssi": {},
"soak": {
"enabled": false
}
},
"warnings": [
{
"in_memory": false,
"severity": "TROUBLE",
"type": "OPENED"
Let me have a look. Its been a while since i reviewed the code. Will come back to you,
1 Like
Sorry for taking a while. I think the issue is in the api (as well as the change you made in the integration).
I’ll make an update next week for you to download.
2 Likes
OK, if you update from the git repo again, it should work. I have also fixed a couple of other issues while I was there.
- Deprecation warning regarding awaiting config setup.
- New issue from 2024.8 onward, where default requires a pin to be entered and this integration does not.
Let me know how you get on.