-
Notifications
You must be signed in to change notification settings - Fork 45
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
Not showing lights #15
Comments
I have the same issue.... |
I also have this problem, I suspect that it is because of entities with |
@PiotrMachowski Why do you think it is due to lights that have that status? |
I have had varying degrees of success by disabling and deleting unavailable entities. I've got switches, but no lights.... |
I can confirm that if you ensure that you don’t have any light entities with the status “unavailable”, you can use the light part in the watch app. But I will keep this issue open for the time being, for whom it doesn't work. |
That seems like its working as designed. Why would you want lights and things that are marked unavailable to show up? |
You're not getting it. Its not that the unavailable devices aren't showing up. That's not the issue. The issue is that NO devices are showing up because of the unavailable devices. In my case, I have deleted the unavailable devices in HA, but the lights are still not showing up. There may be other issues. |
I see. Thats strange, I could try to walk you through debugging but it requires building up a request to home assistant. The code to render the lists is very simple. It hits /api/states and that returns an array of json objects. I then check the entity_id on each object to see if it starts with "light." for example and put it on the page. So if the entities show up in that list and start with "light." then they show up on the lights page |
I have the same issue on Active 2. I have no light showing at all. The other options work. How can we resolve this? |
I have finally removed all lights with |
I have the same issue. Lists "Lights" and "Switches" do not open. When I click on their icon in the app nothing happens. Meanwhile "Scripts", "Covers", "Groups" and "Settings" work well. |
@am1ter I've never been able to reproduce this issue. I tried pulling out my z-stick so that all my lights are marked unavailable, but the app still works as expected. If someone can provide me with a way to reproduce id be happy to fix it |
@Jerrkawz you can try installing browser mod, its lights were breaking my app |
I had the same issue, everything aside from the "lights" menu worked - and disabling the "unavailable" lights in HA entity configuration fixed the problem. Is there any specific way I can find helpful information to assist you in reproducing the bug? |
I have now upgraded to a Galaxy Watch 3 and am now having trouble with all menus in the app. No menu even opens up (aside from the settings). I have removed all unavailable entities from HA - it didn't help. Is there any way I can troubleshoot this further? |
It seems my issue is with the authentication after all. I was using the external HA URL (nabu casa) with the "/lovelace/0" part at the end. I did not get any authentication errors. But when I try changing the token and it doesn't have any effect. The settings menu closes and I see a brief "loading" circle and it gives the impression the authentication succeeded. But none of the menus (lights, switches, scripts, covers, or groups) open. When I remove the "/lovelace/0" part of the HA URL, I get:
And in HA logs I see:
I have tried with 3 different long-lived tokens, same result every time. It's getting quite tedious to re-install the Home Assistant UI app on my watch, in order to get the hassgalaxy.app website link. Edit: My issue was resolved with the help of @michielscj in #13 |
Have the sampe problem for a while. No lights but other menu are working. |
For me this was the problem:
In the browser mod must disable the light and after restart the lights again working good. |
Hello folks! |
My galaxy watch active2 does not show the lights in the house.
If you need more information, please let me know.
The text was updated successfully, but these errors were encountered: