-
Notifications
You must be signed in to change notification settings - Fork 502
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
Wrong version date shown in Phoscon #7239
Comments
Hi This is not the correct place to report this . Additionally the date is referenced to the firmware. If you need any more information or still believe this is a bug: please use the forums. Closing. |
Apologies, even though the screenshot was showing a Phoscon screen, I thought such a bug report fell under the purview of deCONZ since it is tied to the deCONZ release metadata. Phoscon bug reports are via the forum too? (EDIT: nevermind, found the spot there). The firmware that I am running seems to have been released on 2021-08-19, not the above date: And according to https://www.phoscon.de/en/support#phoscon-app-version
Yet I cannot find a 2022-09-19 dated release of Phoscon in https://phoscon.de/en/changelog nor ID the version released with deCONZ 2.22.02 Anyway I will move to the forums, sorry for the noise, and thanks for your help! I was searching around for where to report probable bugs; is this repo only for reporting bugs in the plugin source code contained herein? I assume the deCONZ GUI source code is not public, so wasnt sure where to report probable bugs with that or the overall deCONZ packaging. I eventually stumbled on #5113--- it would be great to include a link to that guide in the Issue template or even the
|
Describe the bug
I access Phoscon from local IP.
The Phoscon > Settings > Gateway menu shows that I am running the latest release, 2.22.02. However, the release date written to the right of the version number is 2022-09-19, which seems to correspond to the 2.18.02 release. See below screenshot.
The deCONZ GUI "About" window correctly shows a 2023 copyright and the correct version (does not list the release date).
Steps to reproduce the behavior
Expected behavior
Screenshots
Environment
deCONZ Logs
Additional context
The text was updated successfully, but these errors were encountered: