and3rsl / visonicalarm-for-hassio Goto Github PK

Hi,

I use server alarmas.trablisa.es and I don't need to specify username and password.
It only requires panel id and master user code.

If I leave blank the values, I get the following error:
Invalid config for [visonicalarm]: string value is None for dictionary value @ data['visonicalarm']['user_email']. Got None
string value is None for dictionary value @ data['visonicalarm']['user_password']. Got None. (See /config/configuration.yaml, line 544).

I'm doing something wrong ?

Hi everyone,
I begin with home assistant and i try an integration of my visonic alarm (powermaster 10 +ip modul)
I filled the file as described and Home assistant return the following message:
Thanks to help me.

Setup failed for visonicalarm: Integration failed to initialize.
7:59:53 – setup.py (ERROR)
Connection failed: 'NoneType' object is not subscriptable
7:59:49 – visonicalarm (ERROR)
{"error":10001,"error_message":"Bad Request Params","error_reason_code":"BadRequestParams","extras":[{"key":"user_code","value":"minLength:4"}]}
7:59:49 – /usr/local/lib/python3.8/site-packages/visonic/alarm.py (ERROR)
{"error":10001,"error_message":"Bad Request Params","error_reason_code":"BadRequestParams","extras":[{"key":"user_code","value":"minLength:4"}]}
7:59:49 – /usr/local/lib/python3.8/site-packages/visonic/alarm.py (ERROR)
400 Client Error: Bad Request for url: https://visonic.tycomonitor.com/rest_api/8.0/panel/login
7:59:49 – /usr/local/lib/python3.8/site-packages/visonic/alarm.py (ERROR)

Hi,

Checking configuration file not validating after I added the lines below (with my own parameters).
I'm getting this error message: Component error: visonicalarm - Integration 'visonicalarm' not found.
What I missing?

visonicalarm:
host: YOURALARMCOMPANY.tycomonitor.com
panel_id: 123456
user_code: 1234
app_id: 00000000-0000-0000-0000-000000000000
user_email: '[email protected]'
user_password: 'yourpassword'
partition: -1
no_pin_required: False

Regards,
Oren

Hi all,

I added this to configuration.yaml:
visonicalarm:
host: visonic.tycomonitor.com
panel_id: xxxxxx
user_code: xxxx
app_id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
user_email: [email protected]
user_password: password as used by visonic-go app
partition: -1
no_pin_required: False

and I got the error:
Logger: root
Source: /usr/local/lib/python3.9/site-packages/visonic/alarm.py:607
First occurred: 20:26:01 (1 occurrences)
Last logged: 20:26:01

{"error":10004,"error_message":"Wrong combination","error_reason_code":"WrongCombination","extras":[{"key":"email","value":"wrong_combination"},{"key":"password","value":"wrong_combination"}]}

What I'm doing wrong?
Please help..

Hi,
First of all, you did a great job with this integration.
I have Visonic Max Pro.
I can connect to server,and get arm/disarm status. also, can change control arm/disarm,
but, I don't get any sensor list at all, just alarm control panel.
There is upto 10 sensors : door,window,motion...
none of them is set on HA.
HA version : 0.117
Can you help?

Hey, great job with the component.
It works great for my PowerMaster 360R system.
As I understand there is only support for Contact sensors, would it be possible to add other sensors?
I have the MP-802 PG2 motion sensors with the capability of reporting temperatur and lux which I would love to add.

The integration worked fine, until at some point it stopped loading. Here are the logs:

Logger: custom_components.visonicalarm
Source: custom_components/visonicalarm/__init__.py:66 
Integration: visonicalarm (documentation) 
First occurred: 10:20:35 (1 occurrences) 
Last logged: 10:20:35

Connection failed: Rest API version 8.0 or 9.0 is not supported by server.

Hi,

The integration works well for a few months and today I got this error message
Logger: homeassistant.setup
Source: setup.py:311
First occurred: 19:17:09 (1 occurrences)
Last logged: 19:17:09

Setup failed for custom integration visonicalarm: Integration failed to initialize.

Thanks

Hi,

Sorry but after trying to find a solution by myself without success, you are my last chance to find out what is wrong.
I am using Home Assistant version 2023.3.6 and everything was working until the last update.
Now the alarm stays in the "armed_away" state even when it is disarmed.
Here is the state of the alarm:

When I see the history, it is disarmed!

What's wrong with it?

Nice integration. It works on a Powermaster 33 connected with 4G data (SIM). I would prefer very high "scan intervals" not to stress the connection of the device, so I modified it; but I am not able to update.entity so that the panel gets connected (I built a script trying the update-entity of visonic panel each 10 seconds for 5 minutes). Any suggestion of how to do it? Thank you

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:

python -m call_visonic_api_using_visonicalarm2
Rest API version 8.0 is supported.

--------------
 Device #1 
--------------
ID:             4995
Name:           
Zone:           None
Device Type:    CONTROL_PANEL
Subtype:        VISONIC_PANEL
Warnings:       None

--------------
 Device #2 
--------------
ID:             8055
Name:           Stue
Zone:           INTERIOR
Device Type:    ZONE
Subtype:        FLAT_PIR_SMART
Warnings:       None

--------------
 Device #3 
--------------
ID:             8056
Name:           Entre
Zone:           INTERIOR
Device Type:    ZONE
Subtype:        FLAT_PIR_SMART
Warnings:       None

--------------
 Device #4 
--------------
ID:             8057
Name:           Gæsteværelse
Zone:           INTERIOR
Device Type:    ZONE
Subtype:        FLAT_PIR_SMART
Warnings:       None

--------------
 Device #5 
--------------
ID:             8058
Name:           Kontor
Zone:           INTERIOR
Device Type:    ZONE
Subtype:        FLAT_PIR_SMART
Warnings:       None

--------------
 Device #6 
--------------
ID:             8059
Name:           Hobbyrum
Zone:           INTERIOR
Device Type:    ZONE
Subtype:        FLAT_PIR_SMART
Warnings:       None

--------------
 Device #7 
--------------
ID:             8060
Name:           Bagdør til carport
Zone:           DELAY_1
Device Type:    ZONE
Subtype:        CONTACT
Warnings:       None
State:          closed

--------------
 Device #8 
--------------
ID:             8061
Name:           Bagdør til have
Zone:           DELAY_1
Device Type:    ZONE
Subtype:        CONTACT
Warnings:       None
State:          closed

--------------
 Device #9 
--------------
ID:             8062
Name:           Hobbyrum
Zone:           FIRE
Device Type:    ZONE
Subtype:        SMOKE_HEAT
Warnings:       None

--------------
 Device #10 
--------------
ID:             8063
Name:           Entre
Zone:           FIRE
Device Type:    ZONE
Subtype:        SMOKE_HEAT
Warnings:       None

--------------
 Device #11 
--------------
ID:             8072
Name:           
Zone:           None
Device Type:    WIRELESS_COMMANDER
Subtype:        LCD_PRG_KEYPAD
Warnings:       None

--------------
 Device #12 
--------------
ID:             8083
Name:           
Zone:           OUTPUT
Device Type:    PGM
Subtype:        PGM_ON_PANEL
Warnings:       None

--------------
 Device #13 
--------------
ID:             8210
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

--------------
 Device #14 
--------------
ID:             8211
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

--------------
 Device #15 
--------------
ID:             8212
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

--------------
 Device #16 
--------------
ID:             8213
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

--------------
 Device #17 
--------------
ID:             8214
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

--------------
 Device #18 
--------------
ID:             8215
Name:           
Zone:           None
Device Type:    PROXY_TAG
Subtype:        GENERIC_PROXY_TAG
Warnings:       None

In Home Assistant, I only have two entities other than the alarm_control_panel.visonic_alarm, namely the two contacts: sensor.visonic_alarm_8060 and sensor.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.

As title.

Upgraded to latest version to support API version 10. But still getting error about version 8 and 9 not being supported by server.

It's as though the pip3 upgrade is not happening.

As root on port 22222 I even did a

pip3 install visonicalarm2==3.1.3

It seemed to download 3.1.3 and install but still got same error on HA restart.

Krs

Mark

Hi, after updating the package to API 9, I started having the following errors in the log:

400 Client Error: Bad Request for url: https://visonic.tycomonitor.com/rest_api/9.0/set_state

{"error":400,"error_message":"Panel is not connected","error_reason_code":"PanelNotConnected","extras":[]}

Hello - great job on this integration.

Quick question, more than an "issue", but all my contacts are showing up as mdi:door-open/closed, which is ok, but most of my sensors are windows, and the icon is anoying me - is there a way to allow me to specify icon's per entity? I can override them (per entity) in LoveLace, but it is a complete override doesnt honour the open closed state. for example - i can override the icon to use mdi:window-open, but it always shows this icon, even when closed.

Happy new year!
Cheers
PC -

Copy paste from log:

Log Details (ERROR)
Thu Dec 12 2019 15:02:11 GMT+0100 (Central European Standard Time)
Error while setting up platform visonicalarm
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/visonicalarm/alarm_control_panel.py", line 39, in setup_platform
visonic_alarm = VisonicAlarm(hass)
TypeError: Can't instantiate abstract class VisonicAlarm with abstract methods supported_features

Log Details (ERROR)
Thu Dec 12 2019 15:02:25 GMT+0100 (Central European Standard Time)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 376, in _async_add_entity
suggested_object_id or entity.name or DEVICE_DEFAULT_NAME
File "/config/custom_components/visonicalarm/sensor.py", line 60, in name
return 'Visonic Alarm Contact ' + self._id
TypeError: can only concatenate str (not "NoneType") to str

Reboot make the component work again.
Last error message before the component stops updating is:
"Update of alarm_control_panel.visonic_alarm is taking over 10 seconds
29 januari 2020 10:45 main.py (WARNING)"

Not much to go on...

I am running 0.104.3

Hi,

I use the official app but without username and password. It only requires panel id and master user code. Is there anyway this amazing code can be configured to allow for a connection without username/password? I saw some one else also wrote something about a similar problem.

thanks
D

Hi,

I can't create a script that send me notification when the alarm is triggered.
I field the script like the photo.

Please help me.
Regards,
Oren

Hello, many thanks for this plugin and keeping it running. I have been wanting to get motion sensors working and have narrowed down the sensors not working due to them not 'pinging' the app with any status change.

I actually own a visonic server that runs powermanage this is what the 'Visonic-go' app connects to. In the server ui is a virtual keypad screen, once connected to the panel this shows what zone is violated etc wondering if there would be a way for this log to trigger a motion event. unfortunately I would not have the knowledge to put this in to action or code it!

Many thanks.

When I arm or disarm the alarm it takes more than 10 seconds to reflect that changed state in the alarm (e.g. that it's "arming"). Is it possible to get the update sooner to get action result quicker?

Dear Andrea,

I found some issue to connect the Visonic - Tyco changed their API some months ago, anyway If if got the oficial API are you able to work on it?

regards,

Hi
Thank you for developing this integration. I am using a PowerMaster-33 and the alarm panel component is arming/disarming well. All the motion sensors have been integrated as entities. The contact and vibration/shock/contact sensors have not been integrated and are missing from HA. I am new at this so perhaps missing something.
Thank you for your help.

the ready status is for arming away. If you have sensors set to internal that can be open in armed_home.

ideally the logic should really try calling the api anyway and then follow/poll the reference you get back to see if it worked or if that request failed

my alarm for who knows why (please say if you have clues) doesn’t seem to like updating the status of sensors very often, so I should be able to try arming away and let the monitoring station try and deal with it, rather than block it at this level

Hello,

Great plugin! Can see massive potential in me using this. However I am stuck...

I am setting this up and I have a fair few of shock contacts. they are identified as:SHOCK_CONTACT_AUX_ANTIMASK

I have added this into the sensor.py on my local machine which identifies and adds the sensors

    for device in hub.alarm.devices:
        if device.subtype == 'SHOCK_CONTACT_AUX_ANTIMASK' or device.subtype == 'CONTACT_AUX' or device.subtype == 'CONTACT' or device.subtype == 'MOTION_CAMERA' or device.subtype == 'MOTION' or device.subtype == 'CURTAIN':
          _LOGGER.debug("New device found [Type:" + str(device.subtype) + "] [ID:" + str(device.id) + "]")
          add_devices([VisonicAlarmContact(hub.alarm, device.id)], True)

however, they don't seem to return "open" or "closed", so they are showing as unknown and are currently useless. Anyone know what they return for open and closed state? I can code it myself if i know

Thanks in advance.

Has this release been tested with Tempest (SE) SOC?

Since 15 days the integration doesn't update the current actual state of the alarm anymore, or it does just for a limited time after restarting HA.

If I manually restart HA, the integration refresh the correct state.

This is the error I found in the log:

Logger: homeassistant.helpers.entity
Source: custom_components/visonicalarm/__init__.py:119
First occurred: 28 gennaio 2021, 22:58:55 (25808 occurrences)
Last logged: 9:13:37

Update for sensor.visonic_alarm_204150 fails
Update for sensor.visonic_alarm_204152 fails
Update for sensor.visonic_alarm_204151 fails
Update for sensor.visonic_alarm_204149 fails
Update for sensor.visonic_alarm_204153 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 278, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 474, in async_device_update
    raise exc
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/visonicalarm/sensor.py", line 92, in update
    hub.update()
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 259, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/visonicalarm/__init__.py", line 119, in update
    self.alarm.update_status()
  File "/usr/local/lib/python3.8/site-packages/visonic/alarm.py", line 350, in update_status
    partition = status['partitions'][0]
TypeError: 'NoneType' object is not subscriptable

congratulations for the work, I saw on hacs that bentel is also reported in the title.
which control panels are supported?
my control panel has a UUID in this format

abc12345
id:
1 2 3 4

Hi, I receive this 2 messages in the log:

2022-01-13 13:35:26 ERROR (SyncWorker_2) [custom_components.visonicalarm] Connection failed: Rest API version 8.0 is not supported by server.
2022-01-13 13:35:26 ERROR (MainThread) [homeassistant.setup] Setup failed for visonicalarm: Integration failed to initialize.

Any idea? Thank you!

Hello,

How I can integrate a Bentel alarm system? Because I don't have host, email or password.

I'm logging on the android app only with serial number and 4 digit password.

Thank you for your job!

Tried the CrienClash code but could not get it to work in Hassio, saw your new updated ones. Which files do I need and in wich directories should they be placed.
I get the following in Hassio;
2019-12-26 14:22:29 ERROR (MainThread) [homeassistant.components.hassio] Component error: visonicalarm - Integration 'visonicalarm' not found.