I have added a translation for the Netherlands but this only includes the text in the original integration so is very dodgy and only about 20% complete. If anyone wants to edit it to complete it or just improve it further then post in the Github Issue Translation for Netherlands · Issue #157 · davesmeghead/visonic (github.com)
Entities are now linked to their Device so for example the Image and Select Entities are linked to the Binary Sensor Device.
@davesmeghead hi, i have a question. I reinstall integration and now i have a little config problem in a automation.
Before, my panel name is alarm_control_panel.visonic_alarm. Now it’s alarm_control_panel.visonic_alarm_2.
My automation doesn’t work :
alias: Notification - Alarme Sonne
description: Notification sur Oneplus8t Alarm Sonne Home Assistant & Telegram
trigger:
- platform: event
event_type: visonic_alarm_panel_state_update
event_data:
condition: 3
condition: []
action:
- data:
message: "☠️ ☠️ L'alarme de la maison sonne !! "
title: "Alarme Maison :"
data:
image: /local/Photos/IMG_20210415_175246.jpg
action: notify.mobile_app_iphone
what did i put in event type ? Is it always visonic_alarm_panel_state_update ?
Thanks
after a fresh installation from the intergration and updating it to version 0.9.8.3, Powerlink is working again with my Powermax+. And it is reconnecting to Powerlink after each restart from H.A.
I’ve created a HACS release 0.9.9.3 that includes all changes and updates to the integration. It’s on the master branch on Github and is the default release so you should be able to install it using HACS.
The dev and dev_B0 branches are on hold.
Any general issues please report them here.
Any specific issues please report them as issues on Github.
In either case please include a debug Home Assistant log file.
So condition 3 meant siren triggered, one of the reasons to change is that it’s easy to get this wrong. You need to look at the main state of the Alarm Entity being set to Triggered.
Using the latest HA 2024.10
triggers:
- trigger: state
entity_id: alarm_control_panel.visonic_alarm
to: triggered
I hope that everyone can see that this is much better than condition: 3 in an Event.
EDIT: Please see the next post by me as I’ve added a Siren Entity
EDIT 2: Try this using the latest HA 2024.10
Hi,
I’ve spent a couple of hours this morning adding a Siren Entity to the integration. I have created Github release 0.9.9.4 but not made it a HACS release so you will need to download the zip and manually install it.
EDIT: I didn’t make it a HACS release as it’s had very little testing, if you’re willing to test it and let me know it’s OK or not then I’ll make it a HACS release when I’m sure it’s robust enough
So what does it do:
It makes a slight change to the operation of Panic, Emergency and Flood. These no longer trigger the Alarm Control Panel Entity.
Only “Intruders” trigger the Alarm Control Panel Entity.
The Siren is triggered by all possible sources i.e. whatever is set in the configuration.
The Siren Entity is also a Switch and so it can be set from other HA automations etc.
The Mute service call seems to mute the actual siren but it doesn’t notify the integration so the Siren Entity is still “on”
I have copied the “Alarm” language translations from the Alarm Control Panel Entity to the Siren Entity
The alarm attribute of the Alarm Control Panel Entity and Siren Entity are the same, except when the Siren Entity is used in HA as a Switch which overrides the setting
The Siren Entity includes an attribute called trigger. When the alarm type is Intruder this attribute tells you the zone entity that triggered the siren.
So this automation works with this release, using the Siren Entity
alias: Alarm Siren Triggered Action
triggers:
- trigger: state
entity_id:
- siren.visonic_s01
to: "on"
from: "off"
actions:
- data:
title: >-
{% set fn = trigger.to_state.attributes.friendly_name|string %}
{{ fn }} Panel Siren is Sounding
message: >-
{% set fn = trigger.to_state.attributes.friendly_name|string %}
The {{ fn }} Panel Siren is Sounding
{% set etys = trigger.to_state.attributes.trigger|string %}
{% set alrm = trigger.to_state.attributes.alarm|string %}
{% if etys == "" %}
Alarm siren due to {{ alrm }}
{% else %}
{% set ety = 'binary_sensor.{}'.format(etys) | string %}
The Sensor that triggered the Siren is the {{ state_attr(ety, 'friendly_name') }}
{% endif %}
action: notify.persistent_notification
initial_state: true
EDIT: The trigger attribute is only set when the alarm attribute is intruder but you don’t need to check it, checking the length of the trigger attribute is the short cut way of doing it i.e. check trigger attribute length, if not “” then assume intruder alarm and it’s the sensor that triggered the siren
I’m sure that you’ll let me have any feedback, what do you think?
EDIT (again): After reading it through I thought I’d add this. When panic, emergency, fire are triggered in the actual alarm panel, it doesn’t change it’s state. If the panel is disarmed and panic it triggered, the panel remains disarmed but the siren is sounding. So that is why I created a new Siren Entity. The Alarm Control Panel Entity now only represents “intruder”, the Siren Entity represents all possible sources (including “intruder”).
I’ve been working on Partitions for a couple of months and finally got the time to do a bit of testing.
This only works with PowerMaster Series Panels
I have uploaded the code to the dev release on github here, you’ll need to manually download the zip file and delete/replace the existing visonic directory.
Hi @davesmeghead I noticed this log entry today while trying to arm/disarm, then the panel gets unavailable. Been working fine for years.
Latest version of the custom component 0.9.9.7 and also the latest version of HA 2024.10.4.
Power Master 30 in power link mode.
2024-10-29 22:38:14.075 ERROR (MainThread) [custom_components.visonic.pyvisonic] [_sequencer] Visonic Executor loop has caused an exception
2024-10-29 22:38:14.075 ERROR (MainThread) [custom_components.visonic.pyvisonic] ‘str’ object cannot be interpreted as an integer
@davesmeghead I see you also released version 0.9.9.9, and a quick test of it with Arm Home and then Disarm seems to be ok. No error in log and the panel status did not go into unavailable/unknown state
Hi all, Dave thanks a lot for this great integration!
I have a powermaster 10 panel and an USR-TCP232-T2 ethernet connection.
The 2 door switches report back immediately when i open the door.
Next to that i have 4 PIR motion detectors wich do not report back or very slow.
I’m using the dev_B0 integration.
I tested a lot with the PIR sensors and have seen a perculiar behaviour, it looks like a detection is only transmitted to HA once every 60 seconds.
Even if i trigger the PIR before the 60 seconds have passed it reports in HA excactly 60 seconds after the previous detection.
I have set the off delay time for motion sensors to 5 seconds wich shows in the attached image.
Another thing is that only the first detected sensor is transmitted to HA.
Hi,
The dev_B0 release is a few months old and was set up for a specific purpose. I’ve just deleted it from Github so not one else makes the mistake of using it. The master (HACS) release is the main release, the dev release contains the latest, and sometime a bit experimental, functionality.
Having said all that, a PowerMax panel outputs all sensor changes pretty quickly. A PowerMaster panel outputs a message that contains a list of messages that I need to ask for, to get the state of the sensors. Even then, for motion sensors the message I get when I ask for it just tells me the last date & time that the sensor PIR was triggered, so I need to know the date & time in the panel.
Hence, there’s a longer response time for PowerMaster PIR/Motion Sensors.
Can you try it with the Master or the Dev release, your choice, and let me know how it goes.
Hi,
I have just uploaded a new “dev” release to Github.
This is a significant update with both breaking changes and some limitations on capability whilst I’m experimenting.
As such this is a development (experimental) release.
First of all the limitations that I’ve introduced as I have not tested them:
Emulation Mode: I have disabled Minimal and Standard Mode.
Emulation Mode is ignored and tries for Powerlink anyway
(and gives an error in the log file to make sure you see it).
It does not set the time in the panel.
And now for the added and experimental functionalities
Powermaster: Changes to the startup sequence for PowerMaster panels, the EPROM is not downloaded, instead it uses B0 messages to get the needed information. This is experimental. If it fails to get the required B0 data then it downloads the EPROM as before.
When selecting to Arm/Bypass a sensor there is a 3 second timeout and then it reverts to the known value, this is in-case the panel does not respond.
I have added Arm Home Bypass and Arm Away Bypass as new commands (for the HA action). These bypass all “open” sensors first and then arm the panel.
Powermaster: Changes to the way the event log is processed.
Powermaster: I have added temperature and luminance Attributes to the Sensors in HA for supported sensors. This is experimental as I have no way to test these.
Powermaster: A few bug fixes to Partitions
As normal, let me know of any issues that you have, either general issues here or specific issues on Github.
One final thing, you’ll need to update to the latest HA to use it, at least 2024.11.1
I wanted to make a separate post to announce this compatibility as it’s an important milestone for this Integration.
“What does this do for me?” I hear you ask
It allows you to use this Integration with a PowerLink 3.1 Hardware Module within your Panel. It supports:
Not having an external connection (set up the visonic proxy and have direct interaction).
An external connection to a visonic server to also use the Visonic Go app. The proxy acts as a “router” between the panel, the external site and my Integration.
Once you get the “Visonic Proxy” set up and working as per Mark’s instructions, then you can use my integration. You will need to use my dev release to support this at the moment. Configure my integration using Ethernet to connect to port 5002 and it should allow you to control your panel from within Home Assistant via the proxy.
Mark also has a custom component “visonic_powerlink” that you can install in HA. Although this is not needed for my Integration please give it a go.
Thanks to Mark for all the work he’s put in to this and being so positive and patient with me.
Lastly, give me and Mark feedback, if you think it’s a proxy problem then to Mark or my integration then here!
