Program keeps crashing #261
Comments
|
hmm... that's really odd. Why are you getting and unauthorized user error ? Looks like your user has somehow been removed from the whitelist (cannot be done inside winhue since philips require to do it in their web gui) so someone mostlikely deleted your api key. This is either on purpose of trying to crash the app or someone really deleted your key. You can test your api key by going in a browser and typing "http://[your bridge ip]/api/[your api key]/lights" without the quotes and replacing the required sections. This will give you either an unauthorized error or list the bridge lights. If this is the case you can go inside %APPDATA%\WinHue and delete the WinHueBridges.set. This will force you to reconnect to the bridge. |
|
I'm sorry, I don't understand...
When I try to go to http:///api//lights - I get a page not found error.
Jeff
…On Fri, Oct 18, 2019 at 4:16 PM Hyrules ***@***.***> wrote:
hmm... that's really odd. Why are you getting and unauthorized user error
? Looks like your user has somehow been removed from the whitelist (cannot
be done inside winhue since philips require to do it in their web gui) so
someone mostlikely deleted your api key. This is either on purpose of
trying to crash the app or someone really deleted your key. You can test
your api key by going in a browser and typeing "http:///api//lights"
without the quotes and replacing the required sections. This will give you
either an unauthorized error or list the bridge lights.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#261?email_source=notifications&email_token=ADFNF2X37HRX5TTKF27HIQTQPI7UFA5CNFSM4JCMVIBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBWMQAQ#issuecomment-544000002>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFNF2TI6QGEYHLREXVO4NLQPI7UFANCNFSM4JCMVIBA>
.
|
|
http://[your bridge ip]/api/[your api key]/lights github just removed everything between "<>" you have to add the bridge ip after http:// and before /api and add the apikey after /api/ before lights. eg : http://192.168.3.23/api/89sdjk23jhfdjk45jkksl5ia35igj6992kdakb (this is an example and wont work) ok for your sake here is yours : http://192.168.1.24/api/V496AoY55e7PAvZoSzJ9usthLp4I6Wu4rlZdi1HG/lights |
|
I've tried the IP address of the bridge and //lights (e.g.
192.168.x.x//lights) and get a 404 error
…On Fri, Oct 18, 2019 at 4:22 PM Jeff Ghitelman ***@***.***> wrote:
I'm sorry, I don't understand...
When I try to go to http:///api//lights - I get a page not found error.
Jeff
On Fri, Oct 18, 2019 at 4:16 PM Hyrules ***@***.***> wrote:
> hmm... that's really odd. Why are you getting and unauthorized user error
> ? Looks like your user has somehow been removed from the whitelist (cannot
> be done inside winhue since philips require to do it in their web gui) so
> someone mostlikely deleted your api key. This is either on purpose of
> trying to crash the app or someone really deleted your key. You can test
> your api key by going in a browser and typeing "http:///api//lights"
> without the quotes and replacing the required sections. This will give you
> either an unauthorized error or list the bridge lights.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#261?email_source=notifications&email_token=ADFNF2X37HRX5TTKF27HIQTQPI7UFA5CNFSM4JCMVIBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBWMQAQ#issuecomment-544000002>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ADFNF2TI6QGEYHLREXVO4NLQPI7UFANCNFSM4JCMVIBA>
> .
>
|
|
no this wont work you really need the full url with the api key. Check my last message you should have it. |
|
This is what I got...
[{"error":{"type":1,"address":"/lights","description":"unauthorized user"}}]
…On Fri, Oct 18, 2019 at 4:27 PM Hyrules ***@***.***> wrote:
try this one :
http://192.168.1.24/api/V496AoY55e7PAvZoSzJ9usthLp4I6Wu4rlZdi1HG/lights
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#261?email_source=notifications&email_token=ADFNF2XK7MYINZM3UU27YADQPJA63A5CNFSM4JCMVIBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBWNQ6I#issuecomment-544004217>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFNF2VEJJV7SBR6V4YFS7LQPJA63ANCNFSM4JCMVIBA>
.
|
|
Yeah basically you api key have been revoked. Open window explorer and paste this %APPDATA%\WinHue in the address bar up top. You will see some WinHue files. Delete the WinHueBridges.set and do a new pairing. |
|
That did the trick !!!
Thank you so much and thanks for the work on the app, can't wait to get
cracking.
Jeff
…On Fri, Oct 18, 2019 at 4:33 PM Hyrules ***@***.***> wrote:
Yeah basically you api key have been revoked. Open window explorer and
paste this %APPDATA%\WinHue in the address bar up top. You will see some
WinHue files. Delete the WinHueBridges.set and do a new pairing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#261?email_source=notifications&email_token=ADFNF2RNQ7WGL7URNIHU5E3QPJBV5A5CNFSM4JCMVIBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBWOC2I#issuecomment-544006505>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFNF2WX3VQR2HWIP43IGYLQPJBV5ANCNFSM4JCMVIBA>
.
|
|
Great to see you go that working. Don't hesitate I will try to fix this issue on my side because this could happen but should not and it should definitely not crash the app. |
Hyrules
added
bug
WinHue3.log
Before submitting a request please make sure you are running the latest version of WinHue
available in the release section of this site. Support will not be done on older version.
Your setup
WinHue version : (eg. 3.0.2400.0)
Bridge api version : (1.16)
Light model : (if you have a problem with a particular light)
Expected behavior and actual behavior
Cannot perform any action
...
Actual behavior
Program crashes when any action attempted
...
Steps to reproduce the problem
In the case of a crash, please make sure to add a logfile containg the crash located in the %APPDATA%\WinHue3
to the issue you are opening.
The text was updated successfully, but these errors were encountered: