Skip to content
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

Invalid/unknown request: <Request PUT /api/c013fbe396b847f9a306/groups/ > --> {'stream': {'active': False}} #67

Closed
Mr-Groch opened this issue Jan 10, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@Mr-Groch
Copy link
Contributor

Describe the bug

I'm getting warning in logs when I'm disabling Ambilight+Hue on non-Android Philips TV

Steps to Reproduce

  1. Turn Ambilight+Hue on
  2. Turn Ambilight+Hue off
  3. Observer Warning in logs

Expected behavior

No warning on disabling Ambilight+Hue

Logs

2021-01-10 12:39:21,495 WARNING emulated_hue.api -- Invalid/unknown request: <Request PUT /api/c013fbe396b847f9a306/groups/ > --> {'stream': {'active': False}}

Hardware Info:

  • Architecture (Ex: x86, ARM): ARMv7
  • Addon version (Ex: stable or dev): stable
    • Value of "tag_commit_or_branch" if using dev:
  • OS (Ex: Windows 10, Ubuntu Buster): HassOS
  • Hardware (Ex: PC, Raspberry Pi 1/2/3/Zero): RPI 3

Additional context

@Mr-Groch Mr-Groch added the bug Something isn't working label Jan 10, 2021
@alexyao2015
Copy link
Member

That's peculiar. Do you see those exact same logs every time you turn it off? Strange that there's no group id there. What happens if you create another entertainment area then try it again?

@Mr-Groch
Copy link
Contributor Author

Firstly - I'm not using entertainment area, my non-Android Philips TV use standard API for ambilight+hue. This warning sometimes shows, sometimes not.. Today morning this warning was happening every time, but now when I toggle Ambilight+Hue on/off it dosn't appear.. Don't know why sometimes my TV is sending that request...

@alexyao2015
Copy link
Member

alexyao2015 commented Jan 11, 2021

Hmm I would assume this would be similar to #62 . Any request that has an unknown or no group id should be considered group 0. Lets group this issue with the group 0 bug there to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants