Hi C-Soft,
do you have any idea how we can accomplish this?
Work with virtual inputs in DLOADX?
Hi C-Soft,
do you have any idea how we can accomplish this?
Work with virtual inputs in DLOADX?
Can you give a part of code for SATEL?
I did integration and my garage (open/close) works from SATEL APP and as well from HA.
You need to remember to setup CODE (Service code) in SATEL declaration. Otherwise you will not be authorized to do anything with your output.
Moreover in SATEL you need to setup output as a switch depend on the motor of you Garage (it might be NO or other).
Hello. Thanks a lot for your reply. I have the service code setup. And Iām sure that itās working, because I can arm and disarm the alarm system via home assistant using the GUI on the HA overview page.
I think that the issue has to do with my setup of outputs and/or switchable outputs. Iāve not been able to clearly understand what has to be configured to make this work. In the app, when opening the garage doors, they are labeled as 17 and 18. And I can see in the outputs of DLOADX, there are mono switches also labeled as 17 and 18 (with zones 60 and 62 in the triggering column). My assumption is that I need to configure 17 and 18 as switchable outputs in HA which is what Iāve done.
The switches show up in HA. But when you toggle them, they donāt open or close either garage door. Iāve not done anything in DLOADX beyond what the original installer configured other than to turn off encryption as required for HA integration to work.
Iāve included some of my code and a screenshot from DLOADX below of my setup if that helps. I would love to get this working if you have some time to help me debug. Once done, Iām happy to post my working example for anyone else whoād like to accomplish this. Thanks a lot!
Brian
switchable_outputs:
17:
name: 'Left Garage Door Toggle'
18:
name: 'Right Garage Door Toggle'
Hi,
According to SATEL component āoutputā is only to see what is current status on output.
If you will make:
output:
17:
name: ''Left Garage Door'
18:
name: ''Right Garage Door'
you will be able to monitor.
To be able to Open/Close gate you have to use as you described above. But it can be some error in you program due it is to litter space. Try like below:
switchable_outputs:
17:
name: 'Left Garage Door Toggle'
18:
name: 'Right Garage Door Toggle'
and please make āoutputā as well so you will be able to check what is status of your current output.
In additional you have setup in SATEL triggering zone 60 & 62. This has to be something to do with your input on Satel. Iām able to open and close gate form SATEL and HA but my triggering is empty.
I can only assume that zone 60 or 62 is a switch in your garage. This can reason that you are not able to do. In my opinion you should make dummy HA button and for output make a sum of outputs so you will be able to start from button and HA.
Below you can see my configuration for out output that can feet your needs.
Can you make screen of input and output 60 & 62? This will give a better view.
Hello. I am attaching below a screenshot of the zones 60 and 62. This is the only place that I can find them defined in DLOADX. I do not see them defined as outputs or anywhere else.
Another interesting noteā¦ I went into the Keyfob configuration menu (Users ==> Keyfobs ABAX) and the buttons for the garage doors are programmed for zone 60 and 62. So, Iām a bit confused as to the purpose of the outputs 17 & 18 defined in DLOADX. The switches for the garage doors in the Outputs menu of the Integra app (iOS) are labeled 17 & 18 as well. Perhaps way the garage doors are opened via the Integra app is different/independent from the way it is programmed into the keyfobs. I had assumed that they used the same mechanisms.
The garage door openers pre-existed my Satel system. And I asked the installer to integrate them into they security system so that we could open/close the garage doors using the keyfob or using the Integra app via the security system. Maybe there is no way to get this to work from Home Assistant. But I had assumed that if the app can do it, then HA can too.
Thanks for your input and advice.
Brian
So try to make it as i described above and make a logic sum of outputs.
On last outputs in your SATEL make a copy of 16 and 17 as you have today.
On other last outputs makes HA_Door_L & R with mono switch , trigger none.
On outputs 17 make a logic sum (position 47) and output HA_Door_L with Left Garage Door.
This should help.
Than you will be able to open/close door from your system and HA.
Thanks for the advice. Iām a bit of a newbie (particularly in DLOADX). Iām not entirely sure that I understand your instructions. But I will try to follow this on the weekend when I have more time. Thanks again for your help. I will let you know how it goes.
Brian
Folks, hereās how I have it done:
I have garage door that is opened/closed by one button: click, it goes up. Another - it stops. Another - it goes down.
I use Satel fob and switch in HA open/close my garage door. I also have alarm contact switch that monitors if my doors are open or closed.
Hereās setup of output to open garage door in DloadX:
Hereās my setup in HA:
host: 192.xxx
port: 7094
code: !secret alarm_code
partitions:
01:
name: 'Dom'
arm_home_mode: 2
zones:
41:
name: 'Garaż brama'
type: 'garage_door'
switchable_outputs:
8:
name: 'Brama garaż'
The brama_garaz
switch will however only turn on for one second (see DloadX definition) and then come back to off.
So, to have switch in HA that truly displays if my garage door is on or off, I use template switch and contact sensor from Satel (āGaraż bramaā):
- platform: template
switches:
brama_garazowa:
friendly_name: "Brama garażowa"
value_template: "{{ is_state('binary_sensor.garaz_brama', 'on') }}"
turn_on:
service: switch.turn_on
data:
entity_id: switch.brama_garaz
turn_off:
service: switch.turn_on
data:
entity_id: switch.brama_garaz
icon_template: >-
{% if is_state('binary_sensor.garaz_brama', 'on') %}
mdi:garage-open
{% else %}
mdi:garage
{% endif %}
As a result I have switch that after turning on goes back to off after one second, and then back to on when the gate is fully open and contact sensor triggers. Itās not ideal, but good enough for me.
Hope it helps!
@c-soft one question ā¦ is it possible somehow to call macros defined in satel integra ?
currently Iām not arming all zones every time but selectively (depending on the situation: are we at home and willing to feel safe or eā¦g all persons outside house etc.)
It can also be achieve if I would have e.g. a service to ark specific zone only ā¦ they I can create some automaton or scenes around it
Well, I had no idea there are macros there Havenāt tested it out, but I would guess there isnāt any way of doing that, unless you can trigger them by setting some output.
But the use case youāre describing seems like something that arming modes are for - have you checked it out? And arming modes are supported (arm away, arm home etc.)
Hello, so i got a Integra Alarm pannel and iām having issues connecting to ist the connection is flaky
iām currently running ETHM-1 Plus module with firmware version > 2.07 does anybody have issues ?
ETHM-1 is using a static IP does anyone have an idea ?
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] Iteration...
2020-06-17 21:46:41 INFO (MainThread) [satel_integra.satel_integra] Not connected, re-connecting...
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] Connecting...
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] sucess connecting...
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] -- Sending data --
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] \xfe\xfe\x7f\x01\xdc\x99\x80\x00\x04\x00\x00\x00\x00\x00\x00\x6d\x59\xfe\x0d
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] -- ------------- --
2020-06-17 21:46:41 DEBUG (MainThread) [satel_integra.satel_integra] Sending 19 bytes...
2020-06-17 21:46:41 WARNING (MainThread) [satel_integra.satel_integra] Got exception: 16 bytes read on a total of None expected bytes. Most likely the other side has disconnected!
2020-06-17 21:46:41 WARNING (MainThread) [satel_integra.satel_integra] Start monitoring - no data!
2020-06-17 21:46:41 WARNING (MainThread) [satel_integra.satel_integra] Start monitoring failed, sleeping for 10s...
2020-06-17 21:46:45 DEBUG (MainThread) [satel_integra.satel_integra] -- Sending data --
2020-06-17 21:46:45 DEBUG (MainThread) [satel_integra.satel_integra] \xfe\xfe\xee\x01\x01\x63\x08\xfe\x0d
2020-06-17 21:46:45 DEBUG (MainThread) [satel_integra.satel_integra] -- ------------- --
2020-06-17 21:46:45 DEBUG (MainThread) [satel_integra.satel_integra] Sending 9 bytes...
2020-06-17 21:46:45 WARNING (MainThread) [satel_integra.satel_integra] Ignoring data because we're disconnected!
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] Iteration...
2020-06-17 21:46:56 INFO (MainThread) [satel_integra.satel_integra] Not connected, re-connecting...
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] Connecting...
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] sucess connecting...
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] -- Sending data --
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] \xfe\xfe\x7f\x01\xdc\x99\x80\x00\x04\x00\x00\x00\x00\x00\x00\x6d\x59\xfe\x0d
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] -- ------------- --
2020-06-17 21:46:56 DEBUG (MainThread) [satel_integra.satel_integra] Sending 19 bytes...
2020-06-17 21:46:56 WARNING (MainThread) [satel_integra.satel_integra] Got exception: 16 bytes read on a total of None expected bytes. Most likely the other side has disconnected!
2020-06-17 21:46:56 WARNING (MainThread) [satel_integra.satel_integra] Start monitoring - no data!
2020-06-17 21:46:56 WARNING (MainThread) [satel_integra.satel_integra] Start monitoring failed, sleeping for 10s...
2020-06-17 21:47:05 DEBUG (MainThread) [satel_integra.satel_integra] -- Sending data --
2020-06-17 21:47:05 DEBUG (MainThread) [satel_integra.satel_integra] \xfe\xfe\xee\x01\x01\x63\x08\xfe\x0d
2020-06-17 21:47:05 DEBUG (MainThread) [satel_integra.satel_integra] -- ------------- --
2020-06-17 21:47:05 DEBUG (MainThread) [satel_integra.satel_integra] Sending 9 bytes...
2020-06-17 21:47:05 WARNING (MainThread) [satel_integra.satel_integra] Ignoring data because we're disconnected!
2020-06-17 21:47:11 DEBUG (MainThread) [satel_integra.satel_integra] Iteration...
2020-06-17 21:47:11 INFO (MainThread) [satel_integra.satel_integra] Not connected, re-connecting...
2020-06-17 21:47:11 DEBUG (MainThread) [satel_integra.satel_integra] Connecting...
2020-06-17 21:47:11 WARNING (MainThread) [satel_integra.satel_integra] Exception during connecting: [Errno 111] Connect call failed ('x.x.x.x', 7090).
2020-06-17 21:47:11 WARNING (MainThread) [satel_integra.satel_integra] Not connected, sleeping for 10s...
2020-06-17 21:47:25 WARNING (MainThread) [homeassistant.components.cloud.google_config] Error reporting state - 5: Requested entity was not found.
2020-06-17 21:47:25 DEBUG (MainThread) [satel_integra.satel_integra] -- Sending data --
2020-06-17 21:47:25 DEBUG (MainThread) [satel_integra.satel_integra] \xfe\xfe\xee\x01\x01\x63\x08\xfe\x0d
2020-06-17 21:47:25 DEBUG (MainThread) [satel_integra.satel_integra] -- ------------- --
2020-06-17 21:47:25 DEBUG (MainThread) [satel_integra.satel_integra] Sending 9 bytes...
2020-06-17 21:47:25 WARNING (MainThread) [satel_integra.satel_integra] Ignoring data because we're disconnected!
2020-06-17 21:47:26 INFO (MainThread) [satel_integra.satel_integra] Not connected, re-connecting...
2020-06-17 21:47:26 DEBUG (MainThread) [satel_integra.satel_integra] Connecting...
2020-06-17 21:47:26 WARNING (MainThread) [satel_integra.satel_integra] Exception during connecting: [Errno 111] Connect call failed ('x.x.x.x', 7090).
2020-06-17 21:47:26 WARNING (MainThread) [satel_integra.satel_integra] Not connected, sleeping for 10s...
2020-06-17 21:47:41 INFO (MainThread) [satel_integra.satel_integra] Not connected, re-connecting...
2020-06-17 21:47:41 DEBUG (MainThread) [satel_integra.satel_integra] Connecting...
2020-06-17 21:47:41 WARNING (MainThread) [satel_integra.satel_integra] Exception during connecting: [Errno 111] Connect call failed ('x.x.x.x', 7090).
2020-06-17 21:47:41 WARNING (MainThread) [satel_integra.satel_integra] Not connected, sleeping for 10s...
Fixed, I used the wrong Port
sorry for late answer ā¦ indeed in the alarm panel I see 3 modes (arm: away,home,night) what in general would cover my basic needs, but - to be honest - I do not know how to use it and which exactly zones in satel integra are being armed when I use any of those modes ? is there any option in integra to define that e.g. āarm nightā arming zones 1-4 but not 5-7 ?
tried to find something in satem manual but no luck could you please guide me ?
when I made few tests ā¦ modes away and home arming only zone1 ā¦ mode night does nothing
This knowledge is beyond the HA component, itās about configuration of your SATEL Integra. Judging by your nick I assume you speak Polish. If so, hereās quite good & short read on the subject: https://www.montersi.pl/wsparcie/porada/tryby-czuwania-centrali-integra/
Then once you know what you want to achieve, itās about proper config in DloadX.
I have my Satel Integra32 finally installed ā¦ I am testing with ABAX2 (firmware 6.02) and an APMD250, but the detection in Home Assistant seem to be almost instant when I enable āalways onā option in the PIR (I know the batter life will be less ;-)).
Are there any good guides / resources in English?
That DloadX seems very difficult for me to figure out and iāve procrastinated enough already
Sorry, I donāt know. Google translate would be your last resource, itās doing not a bad job these days. Or better yet - https://www.deepl.com/ , these guys are even better sometimesā¦
@breevesdc
Did you solve this problem? I have the same situation as you, arm / disarm works I can read all statuses, but I canāt control any output.
Unfortunately, noā¦ I was never able to solve this. I think it has something to do with my installation which required the installer to integrate our existing garage doors into the new alarm system. Iām thinking that they applied a workaround solution to achieve this which makes my integration with Home Assistant not work.
I solved: the documentation is incorrect:
code string (optional)
The INTEGRA ID (found in DLOADX under āCommunication configurationā or in polish āKomunikacja Konfiguracjiā section), itās needed for making use of the switchable_outputs.
Correctly as follows:
code string (optional)
Access code of any user, or create a separate user for Home Assistan integration.