I like to report a bug.
Google Home app has [Lighting] button that shows all lights. This screen shows incorrect light status if Google Home app was used to show status of lights once and left it open and then the light is turned on/off by manually or by other apps. Basically, the app caches the light status and does not get the latest status from the device when showing the [Lighting] list.
I have Kasa (TP-Link) lights.
Steps to reproduce:
1. Open Google Home app.
2. Press [Lighting] button to see all lights in the home
3. Manually turn on/off one of the light (rather than using Google Home app)
4. Press [Lighting] button to see all lights in the home.
5. Verify the light status shown in the Google Home app matches the actual light you just turned on/off manually
The only way to correct this is to manually kill Google Home app in iOS (iPhone). Then it shows the correct status.
It looks like Google Home app caches the status of the light once it pulls the status and caches the status thinking that the app itself is the only means to turn on/off all the lights (which is wrong assumption).
Thanks for posting and for being a step ahead of us.
I know how it feels when something isn’t working as it should, so let’s get this resolved. A few things: was this feature working before? If so, when did you notice the issue started? Were there any recent changes made before the issue started? Is the behavior ok on the light’s native app? Is it happening on one light only or on all of them? If you have different brand lights, is it happening to them too?
You can uninstall and reinstall the Google Home app, then observe if this will make a difference. Also to further isolate try to use another phone and observe if it’s still the same.
Let me know how it goes.
The issue happens even after reinstalling the app and even with the new Preview version.
The issue might be specific to Kasa smart switches as I only have switches from Kasa.
Kasa app doesn’t have the same issue and even Alexa doesn’t have the same issue.
And even Nest Hub doesn’t have the same issue so I am convinced that it is indeed a bug of Google Home app.
if I kill Google Home and restart it then it shows the correct status.