-
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
Some entities not updating correctly #19
Comments
Thanks for reporting this, I'll check out the branch and get a fix in |
I have the same issue, meanwhile thanks for the great app :-) |
Thanks for the report. I will try to implement a fix in the next few days. |
i have try to install this and it's not working |
i have can login on my garmin but i can't see the any of my lights etc.. i have created a group |
Hi Alan, First off: Kudos for an excellent app! I had no idea that I'd get this capability with my Garmin watch. Your app is clean, simple, and fast! Here's what I'm seeing and I think it is related to this issue: When I toggle a device (mine are connected through a Lutron Pro bridge using https://github.com/upsert/lutron-caseta-pro), the device toggles correctly, but the status doesn't change in the app unless I leave the app and come back in. It's really not a big deal, but I figure this might give some clues to what others might be seeing. Thanks again! |
@kbtang88 I think you are raising a different issue. You might consider opening a new one I had a little bit of an issue getting this to work initially. You need to make sure that your group name in HA matches that which you configure through Garmin Express. I set mine to group.garmin. Here's a snippet from my config.yaml: group:
|
Hi again Alan
I'm finding that some entities do not return data from homeassistant.toggle, instead only returning '[ ]'. However, the POST request is always successful and the entity does get toggled. In my household the problem entities are Fibaro Dimmers and Sonoff switches - everything else (Hue lights, TP link switches) works fine. The issue is that the entity does not then refresh correctly in State View after being toggled as there is no data passed to onServiceReceive.
I've made a new branch (https://github.com/aegjoyce/hassiq/tree/aegjoyce-refresh-after-request) on my repository with a rather ugly patch - this workaround refreshes all entities after an entity is toggled so that after a brief refresh time all entities appear correctly on State View.
I have tried using state.singleUpdate(entity) in place of state.requestUpdate() in this patch but it didn't work - I think it fired off the state request too quickly; state.requestUpdate, whilst slower to perform, works every time. A better fix would be a bit of code where if '[ ]' is received from the POST command, HassIQ waits for ~500ms and then fires off a GET to update the state of the entity.
The text was updated successfully, but these errors were encountered: