Skip to content
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

Closed
felker opened this issue Sep 16, 2023 · 3 comments
Closed

Wrong version date shown in Phoscon #7239

felker opened this issue Sep 16, 2023 · 3 comments

Comments

@felker
Copy link

felker commented Sep 16, 2023

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

image

Environment

  • Host system: (Raspberry Pi / PC / NAS) Raspberry Pi 3B running bullseye
  • Running method: Raspbian
  • Firmware version: 26720700
  • deCONZ version:2.22.02
  • Device: ConBee II
  • Do you use an USB extension cable: yes
  • Is there any other USB or serial devices connected to the host system? If so: Which? No

deCONZ Logs

Additional context

@felker
Copy link
Author

felker commented Sep 16, 2023

I just noticed that coincidentally 2.23.01 was released today. I manually updated the package, and now no date appears after the version number--- so maybe this was a known problem in earlier versions?

image

@Mimiix
Copy link
Collaborator

Mimiix commented Sep 16, 2023

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.

@Mimiix Mimiix closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2023
@felker
Copy link
Author

felker commented Sep 16, 2023

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:
https://deconz.dresden-elektronik.de/deconz-firmware/deCONZ_ConBeeII_0x26720700.bin.GCF

And according to https://www.phoscon.de/en/support#phoscon-app-version

The Phoscon App version is given by the date behind the deCONZ version number in the Phoscon App settings.

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 README.md, especially the section:

Well, this list is a small guide on what to ask where ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants