-
Notifications
You must be signed in to change notification settings - Fork 27
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
Changing light status works, but slowly starts to respond less till i restart the app #37
Comments
Regarding issue 1), this may be a session timeout indeed. Perhaps, the current iBox2 uses a shorter session timeout than the older makes. Session keep-alive would certainly solve the issue. One thing you can try: I'll make that configurable with the next release and possibly change the default. Regarding issue 2) I am not sure. At a first glance your code only seems to handle either rgbww or cct or fullColor depending on the response of the '/gateways/:addr/:type/:group' post request. Does a group switch trigger multiple post requests? Did you trace the post responses? |
Hi Marcus, I've just set that at 30 seconds (30000) as advised. However, i'm a bit skeptical if this will work.
As you can see, right after a reconnect (the 27 bytes buffer) the commands still don't work at all. We'll see if the 30 second reconnect solves it, i will report back about that one. Regarding the group switch. As far as i can tell it's only doing one post per command. |
To get back on the 30 second part. It works! The fact that it works doesn't mean that it's the right fix in this case ;) |
Sounds great. Note, there is no connection as the protocol is based on UDP. "Session start" and "Session keep-alive" are just datagrams sent to the bridge. I doubt the bridge can handle keep-alive datagrams in sleep mode. Most likely there is no sleep mode at all. Unfortunately, I don't have a USB power meter to check that. |
Can you please do me a favor and check the same with 150 secs (150000)? |
Sure, done. |
150 seconds is a no-go. I'm back to 30 seconds as that seems to work really well. |
Thanks for the update! I'll change the default value to 30000 then and I'll look into implementing keep-alive soon which is fairly easy to do. |
Hi,
I think i need to clarify this a little.
I'm making a MiLight hub proxy so that it can be used with Samsung SmartThings.
The code i have right now:
note: heavily work in progress! I'm just hacking it together at the moment to get things working.
That is the whole app at the moment. It's going to be on github in this repository sometime soon: https://github.com/markg85/MiLightNodeProxy
It allows me to set the light status and brightness, so far so good. And, the most awesome part, it really works on smartthings (which i import in Google Home to control the bulbs, that really works)!
I have 2 issues though.
And right after it reconnects, the lights work again:
Perhaps the keep-alive packet would fix this?
So:
CW/WW, group 1: on - goes on
RGBW, group 1: on - stays off
I'm not adding any delays here so that might be a potential fix, do you know something else that might be causing this?
Bert regards,
Mark
The text was updated successfully, but these errors were encountered: