kesteraernoudt / dobiss

Custom Home Assistant Integration for the Dobiss NXT platform
MIT License
8 stars 1 forks source link

contact status not updated #109

Closed bosjp closed 1 year ago

bosjp commented 1 year ago

hello,

long time ago, hope you are doing well ?

I made an upgrade of DOBISS nxt (actually on [DOBISS NXT 3.20-1]) I am in the last version for Home Assistant

I have 2 modules of contacts and in the past everything worked perfectly but since few days/weeks it's not the case anymore (I can't confirm after which upgrade problem appears) for somes windows/doors open or close, the sensor work and the status is changed but it's not the case for some other windows/doors. in the application (webserever NXT), the status is changed correctly but not in HA. if I restart the integration when the status of a window/door is changed, the correct status appears in HA only after the restart. that means if I need the right status, I need to restart the integration to be sure.

Version of the custom_component

If you are unsure about the version check the const.py file. --> no reference about the version in const.py

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log


Add your logs here.
kesteraernoudt commented 1 year ago

Could you try with the dev branch? You probably need to reinstall the dobiss integration, and then select the dev branch instead of a release. I did make some updates to be better compatible with the latest dobiss NXT release, and I don't have issues anymore. So i'd like to understand if this fixes these for you as well...

bosjp commented 1 year ago

thanks for your answer..... I will do it asap I keep you posted

bosjp commented 1 year ago

I delete the integration and try to reinstall it, but where can i select de dev branch into the GUI of HA ?

kesteraernoudt commented 1 year ago

in HACS, you can select the release or development branch

kesteraernoudt commented 1 year ago

To be more specific, in HACS, when you open the dobiss integration, you click on the 3 dots top right, and select 'redownload'. There you can pick the version, and dev is one of them: image

bosjp commented 1 year ago

hello,

sorry i selected v1.5, now I redownload, select dev and restart HA.... keep you posted

problem seems still there ...

here info about dobiss version :

image
kesteraernoudt commented 1 year ago

ok, so we need to debug this indeed. Do you know which contacts don't work? Is it from one module, or is it a mix?

bosjp commented 1 year ago

yes for sure ....

first of all, the three contacts from the NXT server himself.... the rest seems working now ....but no NXT server contact

kesteraernoudt commented 1 year ago

if I understand correctly, the inputs on the NXT module itself don't work for you, but the external module work fine?

I only have inputs on an external module, so I can't really reproduce this... I'll have a look at adding more debug info - if you could help me get the logs for those, that would be great

bosjp commented 1 year ago

for sure i can help you to troubleshoot

yes you understand correctly... I assume you have a NXT ? if you connect 2 cables between M & I1 or M & I2 or M & I3, you can simulate external contact, when the shortcut with the two cables is done, the contact is close and open when no contact between M & I1 ...

as illustrate here below

image

otherwise I can debug to help you

bosjp commented 1 year ago

IMG_3986 Small

kesteraernoudt commented 1 year ago

I just pushed a new version which implements a fix for this issue - could you go ahead and test it? So install the latest dev version... If it works for you, I'll create a new release.

bosjp commented 1 year ago

hello,

it works ...... you are the best ! rootcause was a change into the API of Dobiss ?

thx a lot,

jean-pierre

kesteraernoudt commented 1 year ago

I do get a different message from the NXT server now indeed, but I asked for clarification if it's a bug or if it's also a valid message. I've implemented a workaround which now also accepts that message, and will see what they come back with...

kesteraernoudt commented 1 year ago

I've released v1.6 with the fix included - closing this issue