Delay on/off from HA #6
Comments
|
Last version of HA and of the integration |
|
I will need a little more detail. Are you controlling these switches with the room switch entity or with the individual switch entity in HA? Which device(s) are affected? (Please refer to the name of the switch or group in the configuration information that you posted a few months ago). Is the behavior the same when you attempt to turn off the switch, or does it only occur when turning it on? |
|
Hello, I am also seeing the same issue, a consistent ~30 second delay when turning on & off my lighting group from Home Assistant. I have 4 of the "GE Cync Direct Connect Soft White A19" bulbs (I believe they are these ones), and they are all set to be in a group in the Cync app. In Home Assistant, I am using a simple switch for the group entity to turn all 4 lights on/off at the same time.
There is a 30 second delay when turning both on and off. |
|
Is the basement group switch one of the entities created by the integration? You'll need to run the cync_data.py script and post your results. I really have no idea what could be causing this issue at this point. If you want to try to help solve this problem, consider running a packet capture on an Android device while you are using the Cync app to turn your light bulb group on and off and send me the result. You can use an app called PCAPDroid. Set the app to capture packets from the Cync app and save the result as a file, then send me that file. That's how I've been working out the tcp protocol to control these devices. |
Yes, it's the default entity that was created when setting up through the integration. If it helps, I'm running my Home Assistant through a Docker instance. I don't have any Android devices so I don't think I can packet capture to check how the calls are being made on a mobile device. Here is the |
|
Just released a big update. Pretty sure I have plugs and On/Off bulbs and switches functioning as intended. Delete your old installation and download the updated version and reinstall. Let me know if this works for you. |
|
I removed everything from HACS and redownloaded the repo and readded the integration, but still the same result. On/off requests still take roughly 30 seconds to fire. Adjusting the brightness when the lights are on is instant though. |
I believe the bulbs you have are an older generation and they seem to use a slightly different set of command packets than the ones I have, in particular when turning on and off. All of my bulbs, switches, and plugs now work as expected. I thought I had it worked out, but clearly still having some issues. If you're unable to do a packet capture, one option would be to allow me to do it remotely. If this isn't too invasive for you, you could open a dummy cync account and add one of the troublesome bulbs to that account. You would have to share the username and password with me, but that would allow me to run a packet capture on the bulb and see what's going on. If you're okay with trying this, let me know. If not, no worries. |
|
The problem is also present for me after all the update for all my switch.
Le dim. 25 sept. 2022, 6 h 14 p.m., nikshriv ***@***.***> a
écrit :
… I removed everything from HACS and redownloaded the repo and readded the
integration, but still the same result. On/off requests still take roughly
30 seconds to fire. Adjusting the brightness when the lights are on is
instant though.
I believe the bulbs you have are an older generation and they seem to use
a slightly different set of command packets than the ones I have, in
particular when turning on and off. All of my bulbs, switches, and plugs
now work as expected. I thought I had it worked out, but clearly still
having some issues.
If you're unable to do a packet capture, one option would be to allow me
to do it remotely. If this isn't too invasive for you, you could open a
dummy cync account and add one of the troublesome bulbs to that account.
You would have to share the username and password with me, but that would
allow me to run a packet capture on the bulb and see what's going on. If
you're okay with trying this, let me know. If not, no worries.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQCP3474QNSK5P2MWNLWADFFNANCNFSM6AAAAAAQG7TOVU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I've been working with a new set of bulbs this weekend, and it seems that the strength of the WiFi connection of these bulbs (and probably switches) is affecting their ability to respond to commands. Currently, I send commands directly to switches and bulbs if they are WiFi enabled. I suspect that if the WiFi connection is poor, the devices fail to respond to commands and hence the behavior you are seeing. I'm going to implement steps to check for a response to commands, and if no response within a second, try another WiFi connected device. |
|
I ran a traffic capture using the Cync app on iOS + Fiddler on Windows. I was able to see the JSON for the device information, similar to how the cync_data.py script generates. However, turning the lights on/off and adjusting the brightness with the app did not generate any requests for me in Fiddler. |
|
I think I have finally figured out this bug. Should be working now. Please try downloading again. There was a problem with the on/off command that I didn't see until yesterday. Another issue that remains is Wi-Fi connectivity of the devices. I will be updating soon to check connectivity of Wi-Fi devices before sending commands. I think that was another issue for some users that was causing commands not to go through. |
|
Nice job! It's working perfectly for me now! No more delay.
Le ven. 30 sept. 2022, 10 h 45 a.m., nikshriv ***@***.***> a
écrit :
… I think I have finally figured out this bug. Should be working now. Please
try downloading again. There was a problem with the on/off command that I
didn't see until yesterday.
Another issue that remains is Wi-Fi connectivity of the devices. I will be
updating soon to check connectivity of Wi-Fi devices before sending
commands. I think that was another issue for some users that was causing
commands not to go through.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQADTJ26PXHK57GLCILWA34HHANCNFSM6AAAAAAQG7TOVU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@nikshriv I removed the existing repo & integration, and redownloaded and set up the new configuration. Unfortunately, requests now are not working at all. I have some errors in the Home Assistant Logs: |
|
It looks like your connection to the Cync server was lost. Not sure why, but sometimes the server closes the connection. The integration will automatically reconnect after 15 seconds if that occurs. As for you bulbs not responding, that is probably due to your connection being lost. Alternatively, in testing, I have found that most of these Cync bulbs are very flaky when it comes to Wi-Fi. Even though they report being connected, they often don't respond to any commands, even with the Cync app. I have a new update that I'll release in the next day or two that periodically checks for connected devices and only sends commands to them. It also will wait and check if the command resulted in action and will then repeat the command if necessary. Hopefully that will fix your issues. |
Just updated again. The new update checks to make sure that your Wifi devices are actually connected to the Cync server and respond to commands. If not, commands are routed to other devices that are connected. Response to commands is also checked and if no response, the commands are repeated. Hopefully this will make the integration more reliable. Let me know if this works for you. |
|
@nikshriv I just got the latest version and everything is working perfectly for me now. Turning on/off light requests take effect immediately. Thank you so much for fixing this! |
|
That's awesome! It has taken a lot of tries because these Cync devices are very quirky! Glad it's finally working for you |
|
I'm using directly the switch because the room are not working for me. I
have a group in a room and it do not work. It's happen for all the
switch/dimmer for the on/off.
Marc-André Ouellette
***@***.***
Le mer. 7 sept. 2022, 8 h 56 p.m., nikshriv ***@***.***> a
écrit :
… I will need a little more detail. Are you controlling these switches with
the room controlling switch or directly with the individual switch? Which
device(s) are affected? (Please refer to your configuration information
that you posted a few months ago). Is the behavior the same when you
attempt to turn off the switch, or does it only occur when turning it on?
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQDYDWP3H6B27TZG4DLV5E2SJANCNFSM6AAAAAAQG7TOVU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
The only problem I had was when I changed my Cync password. I had to reinstall your integration to get back to the user name/password option. Other than that, works with two bulbs and a switch. |
When on/off a switch from ha, there is a delay of 30 seconds. Dimmer work instantenly. When on/off from cync app or Google Home, it shows directly the action on ha.
The text was updated successfully, but these errors were encountered: