Core: Homematic door/window binary sensor get NA state on conection lost with Homematic IP cloud

[Dysman]

Home Assistant release with the issue:
Since introduction of window and door contact support starts on HomematicIP Cloud support.
Around version 0.88

Last working Home Assistant release (if known):
never

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io 0.92.1
Hass.io supervisor 162
RPI 3 B+

Component/platform:
https://www.home-assistant.io/components/homematicip_cloud/

Description of problem:
The window and door contact binary sensor go to NA state if the HomematicIP cloud lost connection to the server. Like at daly reconect of the router. All other HomematicIP entries can deal with this but not the binary sensor of the magnetic window or door contact.

A full hassio restart bring the sensors back to live

_HomeAssistant Log_

ERROR (MainThread) [homematicip.aio.connection] No Pong received from server.
ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] Error connecting to HomematicIP with HAP <MY_SGTIN>.Retrying in 1 seconds
ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] HMIP access point has lost connection with the cloud
ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] HMIP access point has lost connection with the cloud

Additional information:
Use HomematicIP Cloud integration configured from UI

Sensor types:
HmIP-SWDM
HmIP-SWDM-B2

[SukramJ]

Please check the state of the device in the Homematic IP App.
NA means that the device has (currently) no connection to the Homematic IP Accesspoint.
In this case you should talk to the support at eQ3.

If your other devices are available in HA, then this is not a HA bug.

[Dysman]

The official Homematic IP App works fine. All sensores there connected with good signal quality.
Into the App log i can see the Accesspoint disconect as well and the following reconect as well.
The support mentiond that this is standard behaviour. What makes sense that the assecc point reastablish a connection after internet connection lost.

All other Hmip devices dosen't have issues only the binary sensor of the window and door contact. Looks for me like a state sync issue.

[SukramJ]

Sounds strange. If a hmip sensor in HA is not available then the API reports that the device is unreach(able). The icon in the hmip app should also show a strikedthru signal icon.

I don't own HmIP-SWDM, but i have lots of HmIP-SWDO(-I), and never had issues.
Have you tried to remove these devices from Access Point and add them again?

Your log message only shows, that the AP is not available (due to route reconnect).

Please add this to configuration.yaml to have more verbose log messages:

logger:
  default: info
  logs:
    homeassistant.components.homematicip_cloud: debug
    homematicip: debug

[SukramJ]

I forgot to mention that the same HA implementation is used for for HmIP-SWDM and HmIP-SWDO(-I)

[Dysman]

A snipped from the log with the issue.

2019-05-02 04:06:34 DEBUG (MainThread) [homematicip.aio.connection] Sending out ping request. 
2019-05-02 04:06:37 ERROR (MainThread) [homematicip.aio.connection] No Pong received from server. 
2019-05-02 04:06:37 DEBUG (MainThread) [homematicip.aio.connection] Closing connection 
2019-05-02 04:06:37 INFO (MainThread) [homematicip.aio.connection] Reading task is cancelled. 
2019-05-02 04:07:07 ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] Error connecting to HomematicIP with HAP <SGTIN>. Retrying in 1 seconds 
2019-05-02 04:07:09 DEBUG (MainThread) [homematicip.aio.connection] Sending out ping request. 
2019-05-02 04:07:09 DEBUG (MainThread) [homematicip.aio.connection] Pong received. 
2019-05-02 04:07:28 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.cloud 
2019-05-02 04:07:28 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 357, in _async_add_entity raise HomeAssistantError(msg) homeassistant.exceptions.HomeAssistantError: Entity id already exists: binary_sensor.remote_ui. Platform cloud does not generate unique IDs 
2019-05-02 04:08:09 DEBUG (MainThread) [homematicip.aio.connection] Sending out ping request. 
2019-05-02 04:08:09 DEBUG (MainThread) [homematicip.aio.connection] Pong received. 
2019-05-02 04:08:33 ERROR (MainThread) [snitun.multiplexer.core] Ping fails, no response from peer 
2019-05-02 04:08:33 DEBUG (MainThread) [homematicip.aio.connection] incoming hmip message 
2019-05-02 04:08:33 DEBUG (MainThread) [homematicip.home] SECURITY_JOURNAL_CHANGED 
2019-05-02 04:08:33 DEBUG (MainThread) [homematicip.aio.connection] incoming hmip message 
2019-05-02 04:08:33 DEBUG (MainThread) [homematicip.home] HOME_CHANGED 
2019-05-02 04:08:33 ERROR (MainThread) [homeassistant.components.homematicip_cloud.hap] HMIP access point has lost connection with the cloud 
2019-05-02 04:08:33 DEBUG (MainThread) [homeassistant.components.homematicip_cloud.device] Event HmIP Heizkörperthermostat Battery (HmIP-eTRV-B1)
<than all devices listed like the entry above> 
2019-05-02 04:09:09 DEBUG (MainThread) [homematicip.aio.connection] Sending out ping request. 
2019-05-02 04:09:09 DEBUG (MainThread) [homematicip.aio.connection] Pong received. 
2019-05-02 04:09:09 DEBUG (MainThread) [homematicip.aio.connection] incoming hmip message 

The python error look like a indicator for remote_ui

[SukramJ]

Have you tried to remove these devices from Access Point and add them again?

[Dysman]

Have done this two times with full factory reset.

[SukramJ]

How many of these devices do you have?
Do all devices of the type have this problem?
What is the rssi for these devices?

@mxworm do you have any ideas?

[Dysman]

All five sensores have the same behaviour.

[SukramJ]

What is the rssi for these devices?
You can get from HA. Click on the sensor. It' an attribute: rssi device

[Dysman]

This sensors dosen't have one. Only following atributes are avaiable:

model_type: HmIP-SWDM     OR     HmIP-SWDM-B2
friendly_name: <device name>
device_class: door

[SukramJ]

You should have somethink like this, if you click on the sensor:

[Dysman]

[SukramJ]

Strange.

[SukramJ]

Are you able to execute whats described in the first post from this: https://github.com/coreGreenberet/homematicip-rest-api/issues/150

This output gives detailed (but anonymized) Infos from the unterlying rest api, that is used by HA.
The output contains your anonymized cloud config.

Would be very helpful.

[Dysman]

The config of the affected sensors.

[SukramJ]

Thanks.
As far i could see from your config, these sensors are fully supported by HA.

[t0bse]

same here, i never had this problem before. seems like it's a problem since the last few versions.
every time my internet disconnects for 1-2 minutes, the sensor is lost.
i also can see the state in the homematic ip app and if i restart HA, the sensor is working again until the next disconnect.
used sensor: model_type: HmIP-SWDM-B2

[SukramJ]

It might be very helpful if you could identify the last working version.

[t0bse]

It might be very helpful if you could identify the last working version.

sorry i can't, i think it was 2-3 versions ago (running 0.92.2 now)
but since my posting, it is working again. have to check if my internet wasn't disconnecting since then.

[Dysman]

For me it's already there (running 0.93.1 now). I already ask Homematic to check the disconnects. They resond that everything works fine from there perspective.

[monotonus]

Here the same, running 0.94.1.

Currently annoying, because my ISP seems to have some problems on his side, because I have several router reconnects in the morning hours. The only thing to get my 3 HmIP-SWDM-B2 window contacts online in HA is to restart it, because reload of single components is not possible (yet?).

Opening the window or pressing the button doesn't help.

In the app everything is working fine directly. So just HA has to poll the state from the cloud again or from time to time?

[SukramJ]

Hi @Dysman,
please test with 0.97.x again.
I fixed a small issue in the upstream lib, but i don't know if it is related to you issue.
BR

[t0bse]

in the last week i had this problem everyday, restarted hassio every morning to get it running again.
since the update to 0.97.0 its running fine yet. lets see what happens in the upcoming days :) thanks @sukramj!

[Dysman]

@SukramJ This night it dosen't happend, i will give you feedback how it looks like the next days.

[monotonus]

@SukramJ I just restartet my fritzbox manually and everything came back after the accesspoint has connected again to the cloud. Thank you very much for the fix.

[Dysman]

@SukramJ Now it works for me like a charm. The auto restard workaound is already removed. ;-)
For me this issue is solved.