I have just made tries on my side.
http://phoscon.de/app > http://phoscon.de/pwa > http://phoscon.de/pwa/ > http://phoscon.de/pwa/login2.html?1694733854304 > http://phoscon.de/pwa/login2.html?1694733854304#OVERVIEW
(Yeah a 301 redirection just for the missing /)
But I think it can depend of cache.
It shows a single gateway with the correct local IP address, but when I click on it, it displays a page:
Ok so I haven’t finished the procedure, I have same issue. Even on other brower
Phoscon is broken in several ways recently. On my windows I had to change bookmarks
On my iPad it stopped working totally. And that is with local IP address links
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.
I was running into the original issue on Google Chrome on a laptop, not on iOS. Is it the same issue?
To clarify 2 things:
- We have changed the login page. When you call
phoscon.de/pwayou will be redirected tophoscon.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.htmlto 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.
I’ve migrated the 2 topics.
Manually adding pwa to <your-ip>/pwa/login2.html did redirect me to the correct login page for my gateway, but it did not accept my password.
Same issue here. I noticed that I have one switch that doesn’t work anymore. When I try to access the page : http://192.168.1.4/pwa/devices-switches.html it says
This is not the page you are looking for
The file /pwa/devices-switches.html couldn’t be found.
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.
It’s being discussed here: Bump deCONZ to v2.23.1 by francescopeloi · Pull Request #3226 · home-assistant/addons · GitHub
This is where the login entry point is defined in the plugin: https://github.com/home-assistant/addons/blob/master/deconz/rootfs/usr/share/www/ingress.html#L289
Note that only non-beta deconz releases are usually released as deconz HA plugin.
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?
Look here: https://github.com/home-assistant/addons/blob/master/deconz/rootfs/usr/share/www/ingress.html#L289
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.
Forget that, from index.html I can see that I am redirected to the right /pwa/login2.html. Then in the dev console I see:
jquery-min.js?946589:2 GET http://my-hostname-hidden:8123/api/hidden?_=1695822728138 404 (Not Found)
jquery-min.js?946589:2 POST http://my-hostname-hidden:8123/api/hassio_ingress/paACb-hidden/api/ 403 (Forbidden)
49c0ab42-288a-4cee-afaa-783bb867e1ba:235 found gw: my-hostname-hidden 8123
login2.js?946589:3 WebApp Send Message: GATEWAYS_DATA - [{"apiversion":"1.16.0","bridgeid":"hidden","datastoreversion":"93","devicename":"RaspBee","factorynew":false,"mac":"hidden","modelid":"deCONZ","name":"villalta","replacesbridgeid":null,"starterkitid":"","swversion":"2.23.1","id":"hidden","ip":"my-hostname-hidden","port":"8123","reachable":true,"lastseen":1695822733324,"apikey":"hidden"}]
scanner.js?946589:3 Parameter missing, gw
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.
Sorry for my misunderstanding. I was not really aware of that problem in HA. And I thought it had something to do with this thread.
I just had a talk with @manup And the HA login problem is already known and he thinks he can fix it with an update in deCONZ.
So if I understood him right, it is a problem with a missing port in the URL. The HA port is 40850, isn’t it?
So if youput it after the IP like <your_ip>:40850/pwa/login2.html the login should work?
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)
Why did we have changes like this in a stable release?