Visonic Powermax and Powermaster Component

OK, fixed that one, can you please try 0.0.8.4. It’s tricky to debug something that I don’t really have. I used to have X10 and have a couple of devices set up in the alarm but no X10 hardware to test with.

Forgot to say, thank’s for doing this testing with me :smiley:

1 Like

I also don’t use X10 anymore.

I uploaded 0.0.8.4 and got no error in the logs. Sensor do work. But switch.visonic_alarm_panel isn’t available. And alarm_control_panel.visonic_alarm doesn’t show the number buttons in his more_info panel.

Ah yes, check out my post from a few days ago

As for this I’m not sure why, I’ll look in to it and let you know

OK, I think I’ve recovered it, can you please give it a try. I’ve uploaded 0.0.8.5 and thanks for your patience

1 Like

*** Breaking change ***
I have converted the Component to the new HA Component file structure and it is now release 0.1.0.

The content of what goes in your custom_components directory has completely changed. If you have used this Component before, please delete the following files before you copy across version 0.1.0

    custom_components/visonic.py
    custom_components/pyvisonic.py
    custom_components/test.py
    custom_components/switch/visonic.py
    custom_components/binary_sensor/visonic.py
    custom_components/alarm_control_panel/visonic.py
    custom_components/alarm_control_panel/__init__.py

Everything should work as before, there are no internal or config changes, so please let me know here if you get any problems.

Just updated, deleting the old files and loading the new. I get the following error message;

- Invalid config for [visonic]: [debug] is an invalid option for [visonic]. Check: visonic->visonic->debug. (See /config/configuration.yaml, line 1019). Please check the docs at https://home-assistant.io/components/visonic/

the definition in configuration.yaml is
visonic:
device:
type: usb
# device declaration is not persistent, may be swapped with USB0
path: ‘/dev/ttyUSB1’
motion_off: 120
language: ‘EN’
debug: ‘no’
force_standard: ‘no’
sync_time: ‘yes’
allow_remote_arm: ‘yes’
allow_remote_disarm: ‘yes’
# override_code: ‘’
override_code: !secret alarm_override_code
arm_without_usercode: ‘no’

Ok ignore that last post, removed the debug option and bob’s your uncle.

Thank you Dave. Version 0.0.8.5 did the trick. And later the update to 0.1.0 worked also. Super!

My comments (for 0.1.0):

  • The version number inside the component is still 0.0.9.0. No problem for me.
  • Shouldn’t the parameters (previously visible in the switch more_info popup) be visible in the alarm_control_panel more_info popup now? If not, no problem, because I can see them in the /dev-state page.
  • The number buttons are visible in my Lovelace alarm-panel card. They are not visible in the alarm_control_panel more_info popup. No problem for me, because I use the Lovelace card of course, but I think in previous versions they were visible in the more_info popup also. (The arm/disarm buttons are still visible in the more_info popup).

Hi and thanks for the update, it’s much appreciated

Oops, I’ve fixed it and sneaked the upload to Github without changing the main version number. It seems a bit weird to change the version number, just to fix the version number!

Ah yes, this is not something I can fix. The new way is Lovelace and that is what I’ve programmed it for as that is what I use too. I don’t think I can check which frontend is being used as I could put conditional statements in my code, so Lovelace it is! The technical answer, just in case anyone is wondering, is that code_format returns “number” and not “Number”

This is another effect of using Lovelace I think. I noticed that too with mine. You could make your own Lovelace card and display whatever Entity attributes you would like to.

1 Like

And if you look closer… i only linked to the original code which was initially developed for ST, but it now also have support for MQTT which in turn will work with home assistant. Feel free to check it out.

I realise that this was not the right thread and i kind of hijacked it, apologies for that.

Hi,

I’m also strugling with the Powermax Pro and the PowerLink…
in standard-mode I can arm/disarm the alarm and all sensors are working fine. When using ‘force-standard: no’ HA sometimes sees the sensors, but mostly not. When I see the sensors, they work, but arm/disarm does not work.

Ik tried the powerlink enrollment procedure several times with no result…

The logging:

2019-03-04 17:06:23 WARNING (MainThread) [homeassistant.loader] You are using a custom component for visonic which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key MotionOffDelay to value 120
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key PluginLanguage to value NL
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key ForceStandard to value False
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key AutoSyncTime to value True
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key EnableRemoteArm to value True
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key EnableRemoteDisArm to value True
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic.pyvisonic] Setting key ResetCounter to value 0
2019-03-04 17:06:31 INFO (SyncWorker_5) [custom_components.visonic] Visonic Connection Device Type is OrderedDict([('type', 'ethernet'), ('host', '192.168.2.80'), ('port', 20108)])
2019-03-04 17:06:32 INFO (MainThread) [custom_components.visonic.pyvisonic] [Connection] Connected to local Protocol handler and Transport Layer
2019-03-04 17:06:32 INFO (MainThread) [custom_components.visonic.pyvisonic] [Startup] Trying to initialise panel
2019-03-04 17:06:32 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Exit
2019-03-04 17:06:32 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Exit)    raw data 0d 0f f0 0a 
2019-03-04 17:06:33 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Stop
2019-03-04 17:06:33 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Stop)    raw data 0d 0b f4 0a 
2019-03-04 17:06:34 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Initializing PowerMax/Master PowerLink Connection
2019-03-04 17:06:34 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Initializing PowerMax/Master PowerLink Connection)    raw data 0d ab 0a 00 01 00 00 00 00 00 00 00 43 06 0a 
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [Startup]   count is 1
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [Start_Download] Starting download mode
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Start Download Mode
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Start Download Mode)    raw data 0d 24 00 00 56 50 00 00 00 00 00 00 35 0a 
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtype08] Access Denied  len 0 data 
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:51 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:52 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:52 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:52 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:52 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:52 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 03 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 04 00 61 01 05 00 04 00 00 43 
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic] Visonic got new sensors/switches defaultdict(<class 'list'>, {'switch': [<custom_components.visonic.pyvisonic.X10Device object at 0x6d419830>, <custom_components.visonic.pyvisonic.X10Device object at 0x700b9a90>, <custom_components.visonic.pyvisonic.X10Device object at 0x700b9a70>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f43e2d0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f43edd0>, <custom_components.visonic.pyvisonic.X10Device object at 0x72aca630>, <custom_components.visonic.pyvisonic.X10Device object at 0x72aca1d0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6fd0ad30>, <custom_components.visonic.pyvisonic.X10Device object at 0x72aa9570>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f43a050>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f43a3b0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f435af0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f4353d0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f435610>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f432fd0>, <custom_components.visonic.pyvisonic.X10Device object at 0x6f432f50>]})
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic] Visonic update event 1
2019-03-04 17:06:53 INFO (SyncWorker_11) [custom_components.visonic.alarm_control_panel] alarm control panel received update event
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch PGM    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_0) [custom_components.visonic.binary_sensor] In setup_platform the sensor config file
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 0
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X01    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 1
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X02    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 2
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X03    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 3
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X04    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 4
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X05    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 5
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X06    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 6
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X07    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 7
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X08    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 8
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X09    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 9
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X10    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X11    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 11
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X12    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 12
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X13    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 05 00 00 00 03 00 00 12 34 43 
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 13
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X14    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 14
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] X10 Switch X15    type is <class 'custom_components.visonic.pyvisonic.X10Device'>
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.switch] In setup_platform in switch for X10
2019-03-04 17:06:53 INFO (SyncWorker_16) [custom_components.visonic.pyvisonic] Installing update handler for device 15
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 06 0f 00 00 00 00 00 00 00 43 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Requesting Zone Names
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Requesting Zone Names)    raw data 0d a3 00 00 00 00 00 00 00 00 00 00 43 19 0a 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic] Visonic got new sensors/switches defaultdict(<class 'list'>, {'sensor': [<custom_components.visonic.pyvisonic.SensorDevice object at 0x6f41a390>, <custom_components.visonic.pyvisonic.SensorDevice object at 0x6f43e390>, <custom_components.visonic.pyvisonic.SensorDevice object at 0x6d35ae30>, <custom_components.visonic.pyvisonic.SensorDevice object at 0x6d35aeb0>]})
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] =============================================== Display Status ===============================================
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 0  Sensor id=1  dname=Z01  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 1  Sensor id=2  dname=Z02  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 2  Sensor id=3  dname=Z03  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 3  Sensor id=4  dname=Z04  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]    Model Unknown                PowerMaster No                     LastEvent None                   Ready   Yes          
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic]    Mode  Download               Status      Uitgeschakeld          Armed     No                     Trouble None              AlarmStatus None        
2019-03-04 17:06:54 INFO (MainThread) [custom_components.visonic.pyvisonic] ==============================================================================================================
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.binary_sensor] In setup_platform the sensor config file
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.binary_sensor] In setup_platform in binary sensor
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.pyvisonic] Installing update handler for device 1
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.binary_sensor] In setup_platform in binary sensor
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.pyvisonic] Installing update handler for device 2
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.binary_sensor] In setup_platform in binary sensor
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.pyvisonic] Installing update handler for device 3
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.binary_sensor] In setup_platform in binary sensor
2019-03-04 17:06:54 INFO (SyncWorker_12) [custom_components.visonic.pyvisonic] Installing update handler for device 4
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 06 0f 00 00 00 00 00 00 00 43 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] =============================================== Display Status ===============================================
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 0  Sensor id=1  dname=Z01  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 1  Sensor id=2  dname=Z02  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 2  Sensor id=3  dname=Z03  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]      key 3  Sensor id=4  dname=Z04  stype=None zname=None ztypeName=None ztamper=0  ztrip=0  bypass=0  lowbatt=0  status=0  tamper=0  enrolled=1  triggered=0 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]    Model Unknown                PowerMaster No                     LastEvent None                   Ready   Yes          
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic]    Mode  Download               Status      Uitgeschakeld          Armed     No                     Trouble None              AlarmStatus None        
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] ==============================================================================================================
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 07 00 00 00 00 00 10 00 00 43 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 08 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:57 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 09 00 00 00 00 00 00 00 00 43 
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA7] Panel Status Change 01 00 00 60 00 00 00 00 00 00 43 
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA7]         System message Installateur programmeert / Systeem  alarmStatus None   troubleStatus None
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA7]           self.pmSirenActive=None   siren=False   eventType=0x60   self.pmSilentPanic=False   tamper=False
2019-03-04 17:06:58 WARNING (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA7]         Panel has been reset. Don't do anything and the comms will fail and then we'll reconnect
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic] Visonic update event 4
2019-03-04 17:06:58 INFO (MainThread) [custom_components.visonic] Visonic update event 2
2019-03-04 17:06:58 INFO (SyncWorker_5) [custom_components.visonic.alarm_control_panel] alarm control panel received update event
2019-03-04 17:06:58 INFO (SyncWorker_5) [custom_components.visonic.alarm_control_panel] alarm control panel received update event
2019-03-04 17:08:11 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:08:11 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 04 00 21 02 05 00 00 00 00 43 
2019-03-04 17:08:11 INFO (MainThread) [custom_components.visonic] Visonic update event 1
2019-03-04 17:08:11 INFO (SyncWorker_12) [custom_components.visonic.alarm_control_panel] alarm control panel received update event
2019-03-04 17:08:29 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:08:29 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 04 00 21 03 05 00 00 00 00 43 
2019-03-04 17:08:29 INFO (MainThread) [custom_components.visonic] Visonic update event 1
2019-03-04 17:08:29 INFO (SyncWorker_9) [custom_components.visonic.alarm_control_panel] alarm control panel received update event
2019-03-04 17:08:39 WARNING (MainThread) [custom_components.visonic.pyvisonic] ********************** Download Timer has Expired, Download has taken too long *********************
2019-03-04 17:08:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Exit
2019-03-04 17:08:39 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Exit)    raw data 0d 0f f0 0a 
2019-03-04 17:08:40 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Stop
2019-03-04 17:08:40 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Stop)    raw data 0d 0b f4 0a 
2019-03-04 17:08:41 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Initializing PowerMax/Master PowerLink Connection
2019-03-04 17:08:41 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Initializing PowerMax/Master PowerLink Connection)    raw data 0d ab 0a 00 01 00 00 00 00 00 00 00 43 06 0a 
2019-03-04 17:08:42 INFO (MainThread) [custom_components.visonic.pyvisonic] [QueueMessage] Getting Status
2019-03-04 17:12:01 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:12:01 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 02 00 00 00 00 00 00 00 00 43 
2019-03-04 17:12:05 INFO (MainThread) [custom_components.visonic.pyvisonic] [pmSendPdu] Sending Command (Ack)    raw data 0d 02 fd 0a 
2019-03-04 17:12:05 INFO (MainThread) [custom_components.visonic.pyvisonic] [handle_msgtypeA5] Parsing A5 packet 00 04 00 21 02 05 00 00 00 00 43 
2019-03-04 17:12:05 INFO (MainThread) [custom_components.visonic] Visonic update event 1
2019-03-04 17:12:05 INFO (SyncWorker_0) [custom_components.visonic.alarm_control_panel] alarm control panel received update event

Please help !

p.s. I bought the Powermax Pro in 2010

Hi and welcome onboard

It looks like you started HA whilst the panel was in the “Installer” state and then you exited installer state and the panel did a reset (what it is supposed to do). I can’t really use the info that you included in your post.

Can you try it again when the panel is in it’s normal state, set the logger to debug (see earlier post in this thread on how to do it if you don’t know), restart HA, leave it for 15 minutes and attach your log file by changing the extension from log to yaml and attaching it to your post. You can upload yaml files but not log files.

Thanks again and best of luck

Thanx for your quick response!

As you can tell I’m a rookie on HA…

I did as you told me and attached the logfile. I hope this helps…

B.t.w. is there any way I can see whether the panel is doing a ‘reset’?

home-assistant.yaml (13.3 KB)

Well we all have to start somewhere… :smile:

I admit that the log file you’ve uploaded confuses me and I need the debug logs, I need mode detailed information. Can you put this in your configuration.yaml

logger:
    default: error
        logs:
            custom_components.visonic: debug
            custom_components.visonic.alarm_control_panel: debug
            custom_components.visonic.binary_sensor: debug
            custom_components.visonic.switch: debug
            custom_components.visonic.pyvisonic: debug
            custom_components.visonic.__init__: debug

If there is already a “logger:” entry then comment it out and put this in, you can un-comment your original later. Please upload the log file again in the same way that you have this time.

Telling you to use a previous “logger:” format from an earlier post in this forum was incorrect of me, I realise now that it is in the wrong format after HA changed the Component directory structure. I think that the following should produce the same results now that the component directory structure has been redone but just in case use the above.

logger:
    default: error
        logs:
            custom_components.visonic: debug

You can see it on the panel when it does it but only for a very short time. It does a soft reset on the panel when it exits the installer state. This clears any current failures with the panel such as comms failures etc.

I put the right entries in the configuration.yaml, restarted HA and uploaded the logfile…

Just to be clear, I restarted HA with the option force-standard to ‘no’ and no reset of the panel (I think that’s what you asked for).

In configuration.yaml:
visonic:
device:
type: ethernet
host: ‘192.168.2.80’
port: 20108
motion_off: 120
language: ‘NL’
force_standard: ‘no’
sync_time: ‘yes’
allow_remote_arm: ‘yes’
allow_remote_disarm: ‘yes’

home-assistant.yaml (16.0 KB)

You’re still not getting “debug” entries in your log file, can you check the “logger” entry again please. The only thing I can think of is that the change in the directory structure within HA is affecting how the logger works, this is not something I can do anything about.
The only way around it is to get debug data for everything by putting

  logger: 
         default: debug

This should do it!

If I do this I get a logfile of 9.5MB after 10 minutes… A file this big cannot be uploaded.
So I disables the z-wave devices, RFXtrx devices, Thermostate, etc. This creates some errors in the logging…

I uploaded the logfile after running for about 10 mins.
I hope this file gives you a clue… (fingers crossed)

home-assistant.yaml (2.9 MB)

Hi again, I apologise but it’s my fault although I don’t know what is wrong yet. I tried setting mine to debug the component and mine too only puts info in to the log file and not debug logs. I’ll do some more investigation and let you know how I get on. It seems to have only happened since I updated my HA to 0.88.

Apologies again for misleading you and getting you to do things that just don’t work, are you using HA version 0.88 i.e. the latest version?

1 Like

Please don’t apologize… I’m very thankful that you’re willing to help me!

I’m running Hassio, version 0.88.2

Awesome, i updated and all still working for me. Does this get the component any closer to being submitted as an offical one?

Thanks for your continued work on this.