Core: ETHM-1 satel integra - not connected and error

[roblad]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (0.57.3):

Python release (Python 3.6.3 ):

Component/platform:
satel_integra.py
RPI2 Raspbian jesse

Description of problem:

Expected:
Error - componet not work

e: card.
2017-11-16 20:23:09 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
    yield from self.start_monitoring()
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 166, in start_monitoring
    raise Exception("Monitoring not accepted.")
Exception: Monitoring not accepted.

Problem-relevant configuration.yaml entries and steps to reproduce:

satel_integra:
 host: 192.168.100.180
 port: 7094
 partition: 1
 arm_home_mode: 2

 zones:
   01:
     name: 'Wejscie dom 1'
     type: 'motion'
   02:
     name: 'Garaz'
     type: 'motion'
   03:
     name: 'Salon'
     type: 'motion'

1. 
   
   
   2.
   
3.

Traceback (if applicable):

Additional info:

[c-soft]

The exception you have is due to unexpected response from Satel Integra alarm.

Are you sure you have turned off encryption?

If you did and it is a real bug, I don't think it's related to the HomeAssistant version, more likely some issue with my Satel communication library. I would be grateful for debug log from your session to the point where you get this error.

Thank you!

[roblad]

Hi,
Ver. Centrali 1.15 INTEGRA64
ETHM-1 1.07

encryptionis switched off

and 3.6.3 python installed

error:

2017-11-20 07:22:42 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
    yield from self.start_monitoring()
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 166, in start_monitoring
    raise Exception("Monitoring not accepted.")
Exception: Monitoring not accepted.

PS.

haw to switch debug option

I set

logger:
  default: error
  logs:
    homeassistant.components.satel_integra: debug
    homeassistant.components.binary_sensor.satel_integra: debug

but not many information is given

2017-11-20 08:40:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homeassistant_stop[L]>
2017-11-20 08:40:04 INFO (MainThread) [homeassistant.core] Bus:Handling <Event homeassistant_close[L]>
tail: /home/homeassistant/.homeassistant/home-assistant.log: file truncated
2017-11-20 12:18:36 DEBUG (MainThread) [homeassistant.components.satel_integra] Arm home config: OrderedDict([('host', '192.168.100.180'), ('port', 7094), ('partition', 1), ('arm_home_mode', 2), ('zones', OrderedDict([(1, OrderedDict([('name', 'Wejscie dom 1'), ('type', 'motion')])), (2, OrderedDict([('name', 'Garaz'), ('type', 'motion')])), (3, OrderedDict([('name', 'Salon'), ('type', 'motion')]))]))]), mode: 2 

2017-11-20 12:23:33 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
    yield from self.start_monitoring()
  File "/srv/homeassistant/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 166, in start_monitoring
    raise Exception("Monitoring not accepted.")
Exception: Monitoring not accepted.

In www:

I have

Alarm Panel
2 minutes ago
unknown

Rgs,
RL

[c-soft]

This is with DEBUG enabled for satel_integra?
Your ETHM module is ETHM-1 not ETHM-1 plus, correct?
Can you put latest firmware (v1.13) on it?

I suspect it is indeed real bug with the communication library, but I'm not seeing enough to understand the reason.
Can you please answer above questions, and we'll figure out next steps.
Thanks!

[roblad]

Yes ETHM-1

Haw to upgrade ETHM-1 to v1.13 ? do you have manual for that ?
last one is 1.07
https://www.satel.pl/pl/product/348/ETHM-FLASH,Program-do-aktualizacji-oprogramowania-modulu-ETHM-1

DEBUG enabled for satel_integra - haw to do it ?

[roblad]

Hi,

Any improvement is going ?

[roblad]

Hi,

I think that Author does not care for this plugin, I do not have any answere - the plugin is not usable.

[c-soft]

Hi Roblad,

I really don't appreciate your judgmental tone: in case you haven't noticed this is open source and I haven't charged a dime for my effort.
So while I do care, I have other responsibilities such as day job, my close ones, and million other things in my life that I have to prioritise.
Slamming me here won't help, in fact it discourages me from engaging & helping you.
If you think this is usable - please be my guest and fork/copy/clone/do whatever else and fix it.
Open source community will help you!

Regards!

[roblad]

Hi,

There is misunderstanding.

I did not want to offend you, I had a intention to get only the responce/information from you - you answered quickly :-), and from both sides we are both from Poland and we should support and not fight each other. The point is that unnecessarily puts in the error of Hassio users that it works with ETHM-1 since it only works ETHM-1 plus. It would be useful to make a correction or information whether it will be corrected or not or give a people that only ETHM-1 PLUS is supported. From what I see, you do not want to correct it and this is also an information.

You do not have to react so much :-)

Rgs,
RL

[c-soft]

Well, I've actually put some effort in it and I do care, hence my reaction.

But I get it and it's fine - peace :)

Now, to your questions:

• updating firmware on ETHM-1 should be described on SATEL's website, but there's disclaimer: I have never done it myself (installer made it for me) and if you haven't done it before - it might be difficult and/or dangerous. You may break things.
• Other than that, to make some progress I need to give you some piece of software to run, then based on output I would be able to debug. I can't commit to anything unfortunately as my dev time is very limited these days so it may well be weeks before you get any progress.

Having said that I want to fix this issue so I will be updating this page.

[roblad]

Hi,

PEACE !!! :-)

If you have something for testing on my environment with ETHM-1, do not hesitate to send it to me, I will do test and send you response with debug. I am afraid that upgrade of firmware is not possible to that version you mentioned. I can wait even weeks, but could we make some plan for solve that issue together ? If you give me direct contact to you, it will be easier to cooperate with me and test something. If you are from Warsaw that will be great and even we can meet together and make a discussing :-)

Thanks,
RL

[c-soft]

Sounds good - I will ping you once I have some debug code for you.

[roblad]

Hi,

Any progress ?

[roblad]

Hi,

I do not see any update on that and no any private information I have not received - it make sens to keep that plugin in hassio ?

[gregwis]

Description for satel_integra component was corrected by me on on 2 Dec 2017.
The component supports only ETHM-1 Plus module with firmware version > 2.00. I was able to confirm that component doesn't work with firmware version 2.00 and it works fine with version 2.04.
ETHM-1 (without "Plus") and ETHM-1 Plus with firmware version 2.00 don't support communication mode used in satel_integra component (something like publish-subcribe) and these versions require polling.

Latest available version of firmware for ETHM-1 is 1.07 and according to EHTM-1 communication protocol specification publish-subscribe method is only possible from version 2.00 (but in fact it doesn't work on 2.00).

[c-soft]

I'm still alive and reading this thread. Not responding for simple lack of time.
From what I understand the component works for some, but it doesn't for earlier versions (got a pretty good idea why now).
Thanks for updating the description.
I can only say that I will eventually come back to work on this. Some day. I don't want to make any promisses behind that, as I have been wrong before.

[roblad]

Hi,

Thanks for response, but if it will not be corrected for ETHM-1 it should be clearly said that only ETHM-1 Plus 2.04 and above is supported. In that case I have to resign from hassio and move to DOMOTICZ where both of them works and it is also writhen in Python :-) shame :-(

Rgs,
RL

[djxela]

Hi,
I have ETHM-1 Plus 2.04. Satel component is configured in HA like this:

satel_integra:
  host: 192.168.1.xx
  port: xxxx
  partition: 1
  arm_home_mode: 1

  zones:
    01:
      name: 'All'
      type: 'motion'

Integration - checked, "Kodowanie" - unchecked
I can't connect with Satel and in HA logs I've got this:

```Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/home/djxela/.homeassistant/deps/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
yield from self.start_monitoring()
File "/home/djxela/.homeassistant/deps/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 163, in start_monitoring
resp = yield from self._read_data()
File "/home/djxela/.homeassistant/deps/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 261, in _read_data
data = yield from self._reader.readuntil(b'xFEx0D')
File "/usr/lib/python3.5/asyncio/streams.py", line 571, in readuntil
raise IncompleteReadError(chunk, None)
asyncio.streams.IncompleteReadError: 0 bytes read on a total of None expected bytes

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/home/djxela/.homeassistant/deps/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 279, in keep_alive
yield from self._send_data(data)
File "/home/djxela/.homeassistant/deps/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 207, in _send_data
yield from self._writer.drain()
File "/usr/lib/python3.5/asyncio/streams.py", line 333, in drain
yield from self._protocol._drain_helper()
File "/usr/lib/python3.5/asyncio/streams.py", line 204, in _drain_helper
raise ConnectionResetError('Connection lost')
ConnectionResetError: Connection lost
```
Any suggestions what is wrong?

[roblad]

Hi,

It means that HASIO not supports ETHM-1 and satel integra alarm systems with ETHM-1

[djxela]

This component doesn't work. I have ETHM-1 PLUS my friend have ETHM-1 and HA doesn't connect with Satel (see errors in my previous post). This isn't Satel or ETHM problem, because Domoticz can connect with these Satel devices.
I had one sucesfull connection. Then I rebooted HA and after this it stoped connecting with Satel.

[djxela]

Also when you use Domoticz you have to provide code for integration. This HA component doesn't need to enter Satel code. It's ok?

[roblad]

In my opinion, the announcement about Satel ETHM-1 or ETHM-1 plus was issued to fast, nobady has properly tested all ETHMs-1 to clearly specify the supporting. Also on Domoticz I do not have any problems I type in option 4 digits code to admin rights and all functions work in ETHM-1, the same is on OPENHAB1/2 no any problem with the connection and operations, but the integration code is needed.
In my opinion HASIO module for ETHM-1 should be removed from repository of HASIO - it does not work properly and in my opinion HASIO does not support Satel ETHM-1.

[c-soft]

@djxela thanks for trying out the extension. Indeed it's a really early phase, so it does have bugs and I'm pretty sure you've just discovered another one: error you got is caused when a connection is reset while it reads the data.

The reason why it doesn't need code is because it communicates with ETHM without encryption.

Interestingly, it works fine for me, so I wonder what's different with your configuration.
I plan on updating the extension but for the past 4 months I'm involved in personal project that takes 100% of my time. That will change in 1-2 months, so expect updates then.

[c-soft]

... except from @roblad since I'm really tired of his "bad extension, kick it out!" mantra :-)

[djxela]

@c-soft my configuration is pretty simple:
HA:
`satel_integra:

host: 192.168.1.xx
port: xxxx
partition: 1
arm_home_mode: 1

zones:
01:
name: 'All'
type: 'motion'
'
Satel:
IP address
Kodowanie - unchecked

I can connect to ETHM using DLOADX and GUARDX. Integra and Ethm software was updated.
My friend has this same errors. He tested conneciton with Domoticz and it worked.
I hope that new release will be faster than you say ;))

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[c-soft]

Most likely this is still valid, as no work has been done to fix it. It's still on my radar though, I'm not giving up on fixing it.

[pepeEL]

I also has the same problem. After add component to Home Assistant i have in log error:

2018-08-20 20:09:37 DEBUG (MainThread) [homeassistant.components.satel_integra] Arm home config: OrderedDict([('host', '192.168.xxx.xxx'), ('port', 7094), ('partition', 1), ('arm_home_mode', 1), ('zones', OrderedDict([(1, OrderedDict([('name', 'Wejście do domu'), ('type', 'motion')])), (2, OrderedDict([('name', 'Kontaktron'), ('type', 'opening')]))]))]), mode: 1 
2018-08-20 20:09:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
    yield from self.start_monitoring()
  File "/srv/homeassistant/lib/python3.5/site-packages/satel_integra/satel_integra.py", line 166, in start_monitoring
    raise Exception("Monitoring not accepted.")
Exception: Monitoring not accepted.

Version FW of my Satel Integra 128 is 1.18
Version ETHM-1 FW 1.07
Version Home Assistant 0.76.1

Please help us...

[mbnn]

Same problem for me, the alarm panel disarm/arm stuff does not work and i cant get it to connect (works fine when using Domoticz, but that also asks for a password). My Integra 64 has ETHM-1 with 2.03 and encryption is off. @c-soft im willing to donate money to get this to work if that helps or pay for the project to be finished for Integra :)

https://community.home-assistant.io/t/satel-integra/8254/51

[c-soft]

I'm doing some work currently to improve the component.

Work items on my plate:

• status readout during HA start (currently it's in the dark until next state change) - I know what's wrong.
• support for ETHM-1 - no idea why id doesn't work
• enable monitoring for outputs (currently only inputs are supported)
• enable output manipulation

For fixing issues with ETHM-1 I would need your support: if you have issues, please provide me with full dump of communication.
You will get it by putting something along these lines as your logging config in configuration.yaml in Homeassistant:

    logger:
      default: warning
      logs:
        homeassistant.components.satel_integra: debug
        satel_integra.satel_integra: debug

Thank you!

[pepeEL]

Where debug is write in HA ? I add this to configuration and i want send you debug from my enviroment.

[c-soft]

In home-assistant.log . You may also see it in the GUI in Hassio. You can attach the log or fragment of it here, as an attachment.

[pepeEL]

Ok i send you on facebook

[gregwis]

* support for ETHM-1 - no idea why id doesn't work

ETHM-1 requires different kind of communication: it is required to actively poll ETHM-1 for changes with command 0x7F

[c-soft]

Correct, this is the culprit. That means that currrent version of async communication simply won't work with older modules. This needs more work than couple of fixes.

[pepeEL]

But is any chance to fix it in next time?

[c-soft]

I'm currently cooking next release that will add outputs visibility and should improve arm/disarm status reporting. Previous ETHM-1 still won't be supported. I will clean up the issues so it's easier to track after it lands.

[pepeEL]

Summary
Never ETHM1 not support this function and never in future not working with HA ? You dont plan fix it ?

[djxela]

I have ETHM1 PLUS and I have problems too

[pepeEL]

We know that on ETHM1 Plus is no problem. Only ETHM1 has a problem.

[djxela]

As I mentioned on march 2018, ETHM1 plus have problems too:

2018-12-09 17:11:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/djxela/.homeassistant/deps/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 322, in monitor_status
    yield from self.start_monitoring()
  File "/home/djxela/.homeassistant/deps/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 163, in start_monitoring
    resp = yield from self._read_data()
  File "/home/djxela/.homeassistant/deps/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 261, in _read_data
    data = yield from self._reader.readuntil(b'\xFE\x0D')
  File "/usr/local/lib/python3.6/asyncio/streams.py", line 572, in readuntil
    raise IncompleteReadError(chunk, None)
asyncio.streams.IncompleteReadError: 0 bytes read on a total of None expected bytes`
`2018-12-09 17:11:23 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/djxela/.homeassistant/deps/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 279, in keep_alive
    yield from self._send_data(data)
  File "/home/djxela/.homeassistant/deps/lib/python3.6/site-packages/satel_integra/satel_integra.py", line 207, in _send_data
    yield from self._writer.drain()
  File "/usr/local/lib/python3.6/asyncio/streams.py", line 333, in drain
    yield from self._protocol._drain_helper()
  File "/usr/local/lib/python3.6/asyncio/streams.py", line 204, in _drain_helper
    raise ConnectionResetError('Connection lost')
ConnectionResetError: Connection lost

[mbnn]

Maybe a stupid question but how is it possible this works fine with ETHM-1 and Domoticz, Homey or Openhab but it wont work with HA? Just wondering. If there is anything I can do or donate to help you add support let me know.

[c-soft]

Well, the question isn't stupid, but answer is extremely simple: because I'm the only one maintaining and fixing this component, and my time is very limited. Realistically money or donations are not the solution here, rather someone with time & coding skill on their hands who can help push this thing forward.

Simple as that.

I'm not keeping this component to myself, will support anyone who can do anything about it.

[pepeEL]

:( no found solution ?

[c-soft]

Folks, this bug has become collection of all sorts of griefs and grievances with satel_integra component.
Originally raised bug is caused by lack of support for versions of the ETHM firmware older than 2.00.

This is still not fixed and I will put out updates regarding progress -if any - here.

Before posting your comments here, please make sure that your version is indeed older than 2.00.

*If you have version 2.00 or newer - please raise the new issue * describing your problem and stating clearly ETHM module firmware version (as well as your alarm system). Otherwise your issue will get unnoticed.

But before you do, wait for 2 more weeks, my PR just got accepted, so at least initial alarm status will be updated during start :)

Here is how you know which version you have (this is DLOADX starting screenshot):

[pepeEL]

I have ETHM-1 and please fix problem with this module.... please...

[ghost]

ETHM-1 Plus, latest firmware 2.05, integration/encryption: off

Plugin does not work at all, please remove it from repository. It only causes confusion.
Works with Openhab and Domoticz.

[c-soft]

@SirPietruch your asking for removal of the component because it doesn't work for you makes as much sense as me asking you to remove your account because you can't google and thus contribute nothing.

If you could, you'd know that it's currently working for several people and further fix development is in progress. But hey, haters gonna hate :P

[ghost]

You are too offensive. This component is unstable, and the number of reports of problems associated with it is very large, even difficult to review all of them. It hasn't been fixed for months, even in its basic scope. I don't think that it works well for anyone because it's not compatible with the current version of HA. Until it is fixed, I think it should be withdrawn or marked as unstable.

[c-soft]

I'm not offensive, I'm just pointing out that your argument to remove the component because it doesn't work for you - makes no sense.
First of all, it works for group of people (including myself) - so there's that.
Secondly, there's ongoing effort to improve it - even PR in process of acceptance. You could even help by downloading test version of component and beta-testing in custom_components.

You would know all that ,should you have spent minimum effort on looking around for other issues or googling a bit.

Instead you have found first bug report, which - as per my comment above - is unrelated to your firmware, and you have dumped your sorrows. No log, no config, just "Doesn't work for me, drop it".

I am not being paid for whatever I do with this component and I do have plenty of other things in my life to spend time on, so I don't appreciate people being disrespectful this way.

[ghost]

You waste your time mainly on discussions. I checked yesterday the last version that you published in one of the threads at the request of a colleague who unsuccessfully tries to start communication for several weeks. Log with HA shows errors, it is even impossible to establish a connection. HA does not even initiate the network connection correctly. So, what else are you expect? That is pointless.

[c-soft]

I see no bug report from you except here, so not sure what you’ve tried. But yeah, seems like discussing with you is indeed pointless.

[ghost]

After all, you have had the same unresolved reports for months, with the same bugs. Will the next ones improve your mood? I don't think so.

[MartinHjelmare]

Please keep this issue on topic. This is a bug report. It's not a place to throw dirt at each other.

If we can't keep it on topic I'll lock this thread.

[MartinHjelmare]

That is a different stack trace than in the original post here. Please open a new separate issue for this.

[c-soft]

This has already been raised - incompatibility with Python 3.7. It's addressed with the latest PR, approved yesterday.

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.