Satel integra

papakigr · January 31, 2019, 6:14am

Hi, great job with the component, works great!

i have an issue, i lost 3 binary sensors since i upgrade to 0,86, any idea?

pepeEL · January 31, 2019, 6:37am

Not working full great… because sometime status alarm show as UNKNOWN.

maresob · February 13, 2019, 12:22pm

Hi,
Any news about adding support for ETHM-1??

mbnn · February 19, 2019, 7:53am

Any updates pls?

89krzychu · March 8, 2019, 10:12am

hi i have a problem with satel_integra too. i don’t have any info from satel, and this was all working in past. somebody know when will the bug be fixed? or any solution?

c-soft · March 11, 2019, 7:41pm

OK, folks, thanks for waiting.
Some news for you:

New version is merged into the core, so with the next release it should work stable. It works fine for me, including arming & disarming.
If you want you can test out brand new version of this component, with additional features: partitions support (“strefy” in Polish) and setting outputs. Be warned: new config scheme is different from the old one, no compatibility - see below.

Here’s how to do it:

Download component from here: https://www.dropbox.com/s/t3449xjoiugnyu4/satel_integra.zip?dl=0
Unpack contents of the zip to your <config-dir>/custom_components so e.g. in my case *.py files are located here: \\HASSIO\config\custom_components\satel_integra
Make sure you are using recent version (at least 0.88, otherwise it won’t work properly!)
Configure your component. See example below. zones and outputs work as they do now - they show up as binary sensors. partitions are represented by separate alarm panels. switchable_outputs are represented as switches.
Give it a go, test it out, comment. I’m pretty sure there are some issues, but it works quite allright for me now. Cheers!

satel_integra:
  host: 192.168.2.230
  port: 7094
  code: !secret alarm_code  
  partitions:
    01:
      name: 'Dom'
      arm_home_mode: 2
    02:
      name: 'Kontaktrony'
    03:
      name: 'Garage'
      arm_home_mode: 1   
  outputs:
    6:
      name: 'Dawn sensor'
      type: 'light'
  zones:
    01:
      name: 'czujka wejście'
      type: 'motion'
    02:
      name: 'hol'
      type: 'motion'
    03:
      name: 'wc dół'
      type: 'motion'
    05:
      name: 'salon'
      type: 'motion'
  switchable_outputs:
    8:
      name: 'Brama garaż'
    9:
      name: 'Otwarcie bramy'
    10:
      name: 'Zamknięcie bramy'

majdzik84 · March 11, 2019, 8:38pm

At the moment when the DloadX program is determined by the input-based state, the switch does not work properly.

For example, pulse control (1s) with a garage door: The button opens the gate but it will not close it.

The solution for me was the template switch.

  - platform: template
    switches:
      brama_wjazdowa:
        friendly_name: "Brama Wjazdowa"
        value_template: "{{ is_state('binary_sensor.brama_wjazdowa', 'on') }}"
        turn_on:
          service: switch.turn_on
          data:
            entity_id: switch.brama_wjazdowa2
        turn_off:
          service: switch.turn_on
          data:
            entity_id: switch.brama_wjazdowa2
        icon_template: >-
          {% if is_state('binary_sensor.brama_wjazdowa', 'on') %}
            mdi:garage-open
          {% else %}
            mdi:garage
          {% endif %}

c-soft · March 12, 2019, 6:52am

For everybody else having this issue: this is by design.

Status of the switch changes when it’s notified from Satel module. In this configuration Satel does not send update about changed output, and thus switch stays in previous state.

One possible workaround would be to introduce optional “optimistic” approach just as they do in MQTT switch, but that only assumes that switch was changed, without confirmation too.

This template solution above sounds much better.

pepeEL · March 12, 2019, 7:08am

Can you explaine more this section ? It is polish STREFA ? Why on some is arm_home_mode: 2 but on some is arm_home_mode: 1 but on some nothing ? For what is arm_home_mode ?

And i have an error on new version 0.3.4

Invalid config for [satel_integra]: expected int for dictionary value @ data[‘satel_integra’][‘partition’]. Got OrderedDict([(1, OrderedDict([(‘name’, ‘Dom’), (‘arm_home_mode’, 1)]))]). (See /home/homeassistant/.homeassistant/configuration.yaml, line 158). Please check the docs at Satel Integra - Home Assistant

My config example:
satel_integra:
host: 192.168.13.10
port: 7094
code: 12345
partition:
01:
name: ‘Dom’
arm_home_mode: 1
zones:
01:
name: ‘Wejście 1’
type: ‘motion’
15:
name: ‘Wejście 15’
type: ‘opening’

What is wrong ?

c-soft · March 12, 2019, 9:43am

Please read original docs and my post carefully - there are all the answers. You got wrong config word, it’s partitions not partition.

pepeEL · March 12, 2019, 9:46am

But please explaine what is arm_home_mode: 1 or arm_home_mode: 2 or nothing(empty)?

c-soft · March 12, 2019, 10:37am

Quote from: Satel Integra - Home Assistant :

arm_home_mode
(integer)(Optional)The mode in which arm Satel Integra when ‘arm home’ is used. Possible options are 1 , 2 or 3 . For more information on what are the differences between them, please refer to Satel Integra manual.

Default value: 1

pepeEL · March 12, 2019, 10:42am

On new version 0.3.4… it not working…no found any device from alarm… Now configuration is ok but i not found any device…

Error during setup of component satel_integra
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py”, line 154, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module ‘custom_components.satel_integra’ has no attribute ‘setup’

c-soft · March 12, 2019, 2:49pm

Interesting - can you attach full log please? What platform is it? There were no important changes around that, so it’s surprising error. I wonder if anybody else sees that?

pepeEL · March 12, 2019, 3:31pm

2019-03-12 11:58:08 WARNING (MainThread) [homeassistant.loader] You are using a custom component for custom_updater 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-12 11:58:08 WARNING (MainThread) [homeassistant.loader] You are using a custom component for satel_integra 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-12 11:58:08 WARNING (MainThread) [homeassistant.components.http] Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks
2019-03-12 11:58:11 WARNING (MainThread) [homeassistant.loader] You are using a custom component for sensor.rpi_power 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-12 11:58:11 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 11:58:12 ERROR (MainThread) [homeassistant.setup] Error during setup of component satel_integra
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py”, line 154, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module ‘custom_components.satel_integra’ has no attribute ‘setup’
2019-03-12 11:58:12 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 11:58:27 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 11:58:28 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 11:59:25 ERROR (MainThread) [homeassistant.components.shell_command] Error running command: echo [hass password] | /home/homeassistant/.homeassistant/HA_backup_system.sh >> /home/homeassistant/.homeassistant/Logs_scripts/backup/backup-date +%Y%m%d-%H%M.log, return code: 1
NoneType: None
2019-03-12 11:59:49 WARNING (Thread-8) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 11:59:49 WARNING (Thread-8) [homeassistant.components.http] Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks
2019-03-12 12:05:56 WARNING (Thread-21) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/rpi_power.py to rpi_power/sensor.py. This will stop working soon.
2019-03-12 12:05:57 WARNING (Thread-21) [homeassistant.components.http] Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks

89krzychu · March 12, 2019, 3:38pm

for me it’s working fine now thx

c-soft · March 12, 2019, 3:58pm

I will check this error, separately, but It seems it’s unrelated to this component. Googling around for this error messages showed me 2-3 bug reports all boiling down to something funny in the config. Can you double check your config?

pepeEL · March 12, 2019, 5:20pm

This is my config:
satel_integra:
host: 192.168.13.10
port: 7094
code: 12345
partitions:
01:
name: ‘Dom’
arm_home_mode: 1
zones:
01:
name: ‘Wejście 1’
type: ‘motion’
15:
name: ‘Wejście 15’
type: ‘opening’

But it is my previous working config for old version component:
satel_integra:
host: 192.168.13.10
port: 7094
partition: 1
arm_home_mode: 1
zones:
01:
name: ‘Wejście 1’
type: ‘motion’
15:
name: ‘Wejście 15’
type: ‘opening’

pepeEL · March 13, 2019, 9:24am

Any help…?

c-soft · March 13, 2019, 10:24am

Honestly, this doesn’t seem like the issue with the component. Noone else is reporting anything similar, but you will find similar issues with different components on this forum.

I would suggest getting your config to the smallest working and then adding components one by one or something along these lines.

You got multiple custom components, with warning too - maybe some cross-corelation between them?
You may also just wait until code makes it into official HA release, that will most likely help too.