Closed HomeACcessoryKid closed 6 years ago
I couldn't find in documentation that sending events to controller that caused event is prohibited. I am aware that it might be a nice to have feature, but I chose implementation simplicity over slightly less network usage. Do you see any obvious drawbacks of this approach?
It was as much an attempt to show that event was armed twice. Other than that, no problem.
BR, HacK
On 27 Dec 2017, at 10:19, Maxim Kulkin notifications@github.com wrote:
I couldn't find in documentation that sending events to controller that caused event is prohibited. I am aware that it might be a nice to have feature, but I chose implementation simplicity over slightly less network usage. Do you see any obvious drawbacks of this approach?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Should be fixed now
I observed something that might be a bug or an undesired feature (IMO). I would say that when a specific phone sets the value, it should not receive an event of this. Also, when setting up a new client context, I notice it happens twice in a row. Maybe that makes the event gets send to self?
In the log below, I added a 200ms repeating Task that reports heap and time...
report code: