I am trying to change a GE Z-Wave Plus dimmer from this custom DTH to the Z-Wave Generic DTH. However, I am getting a 403/don’t have authorization to access this page when I try to. Any suggestions as to why I can no longer change the DTH?
Use Incognito mode. It will work. Or clear your cache
Thank you! This was driving me nuts.
When is this issue going to be resolved?
Using the IDE in private mode is a PIA and users on this forum keep having to answer the same question over and over.
As far as I am aware, we have been unable to reproduce the 403 error internally.
What steps are taken when it occurs (if you know)?
Every person that this has happened to has been told to open up an incognito browser and this has worked for all them and they don’t receive the error.
It appears that there is something stuck in cache in the normal browser and that something has changed creating this issue for some people. I haven’t had it happen to me yet, but it has been reported out here in the community at least 20 different times.
Actually… with more testing I think I’ve narrowed it down.
If I have the webcore dashboard open, and looking at a webcore instance from the matching ST location, the error occurs.
If I log out of webCoRE or switch to a different instance (on a different location) then the error does not occur.
This is helpful, thank you!!!
I don’t recall having a WebCore dashboard open at the time. If this does happen in the future, I’ll check to see if I do. (I hope the issue is resolved before then, however!)
Thanks to all.
Thanks a bunch, Robin!
I can reproduce with the webCoRE dashboard up. No 403 error when the tab is closed.
Glad to help… you (we) can now tell people it’s not ST’s fault haha
Bit of history, in the early days of webCoRE, opening the dashboard caused the IDE to log out, a ST staff member tweaked something on your side to prevent that… can’t remember who but Adrian probably knows.
I’ve shared your video and took some screenshots and videos of my own.
I also notice that I can reproduce it when editing a location as well.
I think some people saw it impacting GitHub updates as well.
wth. me too…
It seems this was never resolved?