core
core copied to clipboard
MySensors entities are not properly set when activating scenes/automations
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
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)
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?
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.
There's still only a placeholder page for controller requirements, without content.
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.
@MartinHjelmare how about now? https://www.mysensors.org/controller/requirements