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

MySensors entities are not properly set when activating scenes/automations #79028

Closed
feanor-anglin opened this issue Sep 24, 2022 · 6 comments
Closed

Comments

@feanor-anglin
Copy link

The problem

There seem to be a problem in communication with multiple MySensors entities at the same time, that is while activating scenes or automations. I'm aware there was a similar issue here before, but I've managed to make some further research on this. Previously it was the MySensors signing feature which was blamed of causing the issue (see details).

But the thing is it happens also without signing and even without MySensors nodes connected to the gateway (so it is also not related to communication inside MySensors ecosystem). It seems the cause of the problem is probably the async mode of communication between HA and MySensors gateway resulting in flooding the gateway with messages which it is not able to cope with at the same time. The issue seems not to be present in Domoticz and OpenHab, which both use sendDelay parameter in communication with the gateway (more details in an issue on MySensors GitHub).

Current situation in which a user has to contrive while setting automations while scenes are almost unusable is quite annoying for MySensors users.

Is it possible for Home Assistant to adapt the same sendDelay parameter for communication with MySensors gateways?

What version of Home Assistant Core has the issue?

any

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

MySensors

Link to integration documentation on our website

https://www.home-assistant.io/integrations/mysensors/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@homeassistant
Copy link
Contributor

mysensors documentation
mysensors source
(message by IssueLinks)


Hey there @MartinHjelmare, @functionpointer, mind taking a look at this issue as it has been labeled with an integration (mysensors) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

@MartinHjelmare
Copy link
Member

If there should be a delay between messages from the controller to the gateway that recommendation or specification should come from the mysensors official documentation. As far as I know there's none yet. Have you found one?

@github-actions github-actions bot added the stale label Oct 24, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2022
@feanor-anglin
Copy link
Author

Actually, we reached an agreement on MySensors GitHub, that controller requirements list should be added with sendDelay described as a correct method of implementing communication between controller and MySensors Gateway.

@MartinHjelmare
Copy link
Member

There's still only a placeholder page for controller requirements, without content.

@feanor-anglin
Copy link
Author

Everything takes time, an important thing though is this quote by mfalkvidd, who is a member of MySensors team:

Yes, the acknowledgement method could be better, if MySensors supported acknowledgement. Adding support for acknowledgement has been discussed extensively, but I don't think such support will be added in the near term so the sendDelay solution is the realistic way to go.

@feanor-anglin
Copy link
Author

@github-actions github-actions bot locked and limited conversation to collaborators Dec 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants