Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Answer to connect request when already connected (else report as disconnected) #41

Closed
wants to merge 1 commit into from

Conversation

albaintor
Copy link
Contributor

When the integration is already connected and the remote sends a connect request, the integration will not respond back and will be reported as disconnected. This modification will always report a connect event.
It should be applied to other integrations also that could have the same issue

@zehnm
Copy link
Contributor

zehnm commented Jun 19, 2024

This looks like the same fix I've recently applied: 2152b46
Could you please verify this? Then this PR wouldn't be required anymore.

The connect / disconnect messages will require a general cleanup and more importantly correctly implemented in the web-configurator. Unfortunately this got mixed up, it was intended to connect & disconnect related devices, but then also got used to determine the state of the integration itself...

@albaintor
Copy link
Contributor Author

Hi Markus @zehnm,

indeed this is fixed by your patch.
However as you said there is a mixup with integration state / device state. I will publish some thoughts on discord about integration state / device state and battery consumption. I close this PR

@albaintor albaintor closed this Jun 19, 2024
@albaintor albaintor deleted the reconnect branch June 19, 2024 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants