Sorry there is a bug in the recent deCONZ version regarding using the Phoscon App in a browser on iOS. This has already been fixed and will be rolled out with the next version. Sorry for the inconvience.
We have changed the login page. When you call phoscon.de/pwa you will be redirected to phoscon.de/pwa/login2.html (before it was /login.html)
When you click at your Gateway you will be redirected to <your-ip>/login2.html
And there something went wrong and the browser will tell you “the page could not be found”.
You can add “pwa” like in <your-ip>/pwa/login2.html to open the correct page.
This will be fixed from us directly at the Phoscon App page. So no need to update deCONZ. The Update will be online this weekend or beginning next week.
And 2. is the iPhone / IPad bug when you call the Phoscon app in the browser on that devices.
This will also be fixed at the same time. You need to install the next deCONZ beta release.
If the Login does not accept the password go back to the start page and start a new gateway scan.
It seems missing data in the browsers session storage is the problem and it needs to be re-filled with a gateway search.
the new Phoscon App version is available tomorrow at phoscon.de/pwa that will fix the missing /pwa in the link when you click at a gateway. and the new deCONZ beta version will be released thursday. It also includes the bugfix for iOS users.
@ChrisHae will this fix also the HA+deconz plugin setup? I am experiencing the same problem in this setup, and from my (probably too premature) understanding it won’t.
Me to, and the gateway scan is really slow and redoing the scan does nothing for me. But if I exit deconz for node red or something like that and then back to deconz I get in to phoscon, but it’s empty. I can see a new blinds menu and some layout changes. But I can’t login.
I found out that not working login is based on a missing variable in brwosers session storage.
A gw scan did it for me. Perhaps you also have to clear the browser cache and delete the local storage.
When the Login page does not show any gateways and then the gw scan finds a gateway the login should defenitely work. There was no change in the app that affects the login procedure.
I’ve always been able to see the gateway on the first page but it never worked (login error). A new scan didn’t help (always the same gateway showing up, that does not work). I tried to clear all browser caches and storages with no help, even tried on an incognito window.
Is it maybe because the plugin starts phoscon from the (now) wrong login page?
It does not really matter if you use the old login.html or the newer login2.html to login. Both redirect to the index.html which is the main page of the app after loging in.
You could also try to login from phoscon.de/pwa it does not matter where deCONZ is running.
You can test if there is a app.gateways variable which is not empty in your local storage because that caused the problem in my test.
Yes I can see the app.gateways key, if I delete it gets recreated straightaway. Tried to add an app.gw like you have in your screenshot but it does not help.
To be honest I don’t know what the problem is, but I (and others) couldn’t get into phoscon anymore as it says wrong credential (different message but I don’t recall it exactly anymore). What I saw in the developer console you can see in my message above. I cannot replicate anymore because I reverted to the previous deconz HA plugin version as everyone was having this problem (see here the discussion on the plugin revert: Revert deCONZ to 2.22.2 due to a Phoscon bug by francescopeloi · Pull Request #3233 · home-assistant/addons · GitHub)