Hi, can you set your logger settings as per the wiki here and create a log file for the first 5 minutes after restarting Home Assistant please.
Hey, I’ve added it to a new issue on GitHub for you.
Thanks
I’ve installed v0.12.0.0 and so far it seems to work very well.
The only issue I found was that I tested a flood alarm, which is normally silent, and the integration reported that siren was on (which was not the case).
But perhaps this is an issue with the alarm system itself which is reporting incorrectly.
I also wish there would be an easier way to display the friendly name of the zone which triggered the last event.
I solved it like this:
visonic_panel_last_event_zone_friendly_name:
value_template: >
{% set zone_name = state_attr('alarm_control_panel.visonic_alarm', 'lasteventname') %}
{% if "Zone " in zone_name %}
{% set zone_sensor = 'binary_sensor.visonic_{}'.format(zone.replace('Zone ','z')) | string %}
{{ state_attr(zone_sensor, 'friendly_name') }}
{% else %}
{{ none }}
{% endif %}
friendly_name: 'Last Event Zone Friendly Name'
If you want to create a log file then I’ll take a look
Thanks, here is the log:
siren.visonic_s01 reported as “active” when the event took place:
But of course I didn’t hear anything.
Hi Dave,
First of all, thanks for the good work. I have a powermax+, question after update version 0.12.0.1, i miss the panel for arm and disarm as it should be. what can i do to get it back?
@ thermostat
For your flood alarm, you’re correct, from your log file the panel creates a “Flood Alert” and then 2 seconds later it reports “Flood Alert Restore”. My integration just does what the panel tells it, and so a flood alert is reported. I do not get siren trigger data and that is why you need to set the siren reasons as part of the integration config. If you have “Flood” in this list then HA will show that the siren has triggered.
@Digiw
There seems to be a problem with PowerMax Pro/Plus Panels at the moment that I’m currently looking at, there are already issues created on Github for it (#194 and #199) I suggest sticking with 0.9.9.9 until it’s resolved.
I’ve released a HACS version with many updates, can you please try it 0.12.1.0 thanks
Powermax complete: Upgraded from 0.9.9.9 > 0.12.1.0
Lost the Alarm Panel (see below), looks like its because another entity as been added for the panel:-
alarm_control_panel.visonic_alarm (entity no longer provided by the integration)
alarm_control_panel.visonic_alarm_2 (New one)
And for each of the sensors now have the following:-
binary_sensor.visonic_z01 (active)
select.visonic_z01 (entity no longer provided by the integration)
I deleted the integration, re-added 0.9.9.9 > This returns to ‘alarm_control_panel.visonic_alarm’, but all the sensor are now unknown type.
I had to revert to Mondays backup of appdata to get back to previous state
Let me know if there is any specific testing you want me to do to generate any required logs, and I’ll try again. Thanks.
Let me know if there is any specific testing you want me to do to generate any required logs, and I’ll try again. Thanks.
Did you try:
- deleting the integration,
- deleting the visonic directory (it might be better to delete it from within HACS),
- restart HA,
- installing 0.12.1.0 from HACS,
- change your HA logger settings like this on the wiki
- and then restarting HA again?
- set up the integration
If it doesn’t work properly then please provide a debug log file (not the diagnostics) here and I’ll take a look. If you want to create a new issue on Github then go for it, put the log file in there as it’ll be easier (as it allows you to drag and drop log files and zip files straight in).
This process worked, thanks.
@thermostat
This looks really useful, can you explain how to use it?
I’ve looked at adding it via Helpers > Template
But I’m a bit lost. Thanks.
Hi All,
Just released 0.12.1.4 on HACS, any problems then report generic issues here and specific issues as a Github Issue. In either case an HA logfile is always useful to me.
I don’t see a ‘Panel Problem Count’ anymore. Has it been deprecated?
FYI, it’s still on the attributes list.
Ah good spot, I’d missed it in the wiki description, it’s now been deleted. I’ve also update that section on the wiki overall.
1 Like
Thanks.
FYI, there are also a couple of links in the Contents section that don’t resolve.
https://github.com/davesmeghead/visonic/wiki#the-different-connection-modes
https://github.com/davesmeghead/visonic/wiki#achieving-powerLink-mode
Hi all,
I’ve just released 0.12.3.0 on to Github and HACS. Please read the change log.
@pocket I’ve also fixed those 2 links on the wiki.
On the wiki I’ve also updated the ESPHOME files to my latest, in a zip file. I’m experimenting with a mechanism to dynamically be able to change the baud rate between 9600 and 38400 for PowerMaster panels. But why I hear you ask? 
Visonic have a range of PIRs that include a camera, this is for still images and not video. I can trigger the camera to send me an image but it only works when the baud rate is set to 38400, when it’s set to 9600 it’s too slow and the messages time out part way through sending the data. In the current release I create Image Entities in Home Assistant if I know it’s a camera PIR. If you have baud rate set to 38400 then give it ago, but remember that it’s very experimental at the moment. The updated ESPHOME release would allow me access to an Entity (Select) in Home Assistant to change the baud rate at any time I want. I also know the message data to send to the panel to get it to change its baud rate. The action in HA is visonic.alarm_sensor_image Thoughts anyone?
As usual, any general issues then post here so the community can help, if you have specific issues then create an issue on Github.
I’d like your opinions on a couple of things I’ve added to the discussions thread on Github
The first is about matter / thread / zigbee support
Matter / Thread support via ESPHOME
The seconds is about MQTT support
MQTT Support
If you are interested and have an opinion then please comment in these discussion threads
Hi!
I have gotten the integration working. I have powermaster 10. The only thing I haven’t gotten to work is getting an image when an alarm occurs. Is there anything special I have to do? Can anyone explain how I should proceed?
edit:
This is my automation:
alias: Bild vardagsrum
description: ""
triggers:
- type: motion
device_id: 1a4de69e751e4a1cf2c586424a650971
entity_id: 187977edcfef904b38995ad108a39be9
domain: binary_sensor
trigger: device
conditions: []
actions:
- action: image.snapshot
data:
filename: config/www/tmp/snapshot.jpg
target:
entity_id: image.visonic_z02
device_id: 1a4de69e751e4a1cf2c586424a650971
- action: notify.mobile_app_stefans_iphone
data:
title: Vardagsrum
message: Smile you´r on camera..
data:
attachment:
content-type: jpeg
url: https://mydomain.duckdns.org:8123/local/www/tmp/snapshot.jpg
mode: single
Hi and welcome,
I’ll get straight in to your post about getting camera images. You refer to my previous post about the baud rate and getting the camera images. Can you please confirm that you have a baud rate of 38400? Only this baud rate is fast enough to transfer the image data across before it times-out.
Also, your automation does not call the Action visonic.alarm_sensor_image to get the image (as it says in my post that you refer to), there is an Image HA Entity that should already be created if your visonic sensor reports that it’s a camera PIR e.g. image.visonic_z01.
So get it working with baud 38400 first, then make sure you have an Image Entity, then call the Action visonic.alarm_sensor_image on the Binary Sensor HA Entity (not the Image Entity) and the image(s) should work. I say images as it transfers about 10 images in sequence.