FalconChristmas / fpp

Falcon Player
http://FalconChristmas.com
Other
567 stars 197 forks source link

Renaming Device causes UI Issue on multisync until fppd restarted #1983

Open agent462 opened 1 month ago

agent462 commented 1 month ago

(Steps at end)

Please answer the following:

FPP Version and Hardware: FPP 8.1 running on Pi or BBB

Describe the bug and Steps to reproduce:

  1. Rename host of a controller/reboot
  2. Go to multisync page on separate controller
  3. Now you have have a controller that is no longer seen by FPP (old hostname) but does show up as a different hostname
  4. Enable Auto refresh Multisync Screen
  5. Wifi symbols will start to repeat themselves in controllers not seen

Expected behavior: No duplicate UI icons

Additional context: I've only tested this after renaming some hosts from their temproray host names but I have tested in a Pi or BBB based FPP on 8.1.

Additional Attachments Picture attached

Screenshot 2024-10-01 at 10 51 20 PM
patdelaney commented 1 month ago

And restart fppd and then refresh the page. That will likely clear the error

On Tue, Oct 1, 2024 at 10:53 PM Bryan Brandau @.***> wrote:

(Steps at end) Please answer the following:

FPP Version and Hardware: FPP 8.1 running on Pi or BBB

Describe the bug and Steps to reproduce:

  1. Rename host of a controller/reboot
  2. Go to multisync page on separate controller
  3. Now you have have a controller that is no longer seen by FPP (old hostname) but does show up as a different hostname
  4. Enable Auto refresh Multisync Screen
  5. Wifi symbols will start to repeat themselves in controllers not seen

Expected behavior: No duplicate UI icons

Additional context: I've only tested this after renaming some hosts from their temproray host names but I have tested in a Pi or BBB based FPP on 8.1.

Additional Attachments Picture attached Screenshot.2024-10-01.at.10.51.20.PM.png (view on web) https://github.com/user-attachments/assets/72622561-ed41-4d06-a99f-31cd74cae893

— Reply to this email directly, view it on GitHub https://github.com/FalconChristmas/fpp/issues/1983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB6FEA4CLV7PTJD5XE3YV2LZZNU3LAVCNFSM6AAAAABPG3GVIGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DANRSGE2DQMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

agent462 commented 1 month ago

Restarting fpp does fix the error but just reporting the bug.

On Wed, Oct 2, 2024, 4:31 PM patdelaney @.***> wrote:

And restart fppd and then refresh the page. That will likely clear the error

On Tue, Oct 1, 2024 at 10:53 PM Bryan Brandau @.***> wrote:

(Steps at end) Please answer the following:

FPP Version and Hardware: FPP 8.1 running on Pi or BBB

Describe the bug and Steps to reproduce:

  1. Rename host of a controller/reboot
  2. Go to multisync page on separate controller
  3. Now you have have a controller that is no longer seen by FPP (old hostname) but does show up as a different hostname
  4. Enable Auto refresh Multisync Screen
  5. Wifi symbols will start to repeat themselves in controllers not seen

Expected behavior: No duplicate UI icons

Additional context: I've only tested this after renaming some hosts from their temproray host names but I have tested in a Pi or BBB based FPP on 8.1.

Additional Attachments Picture attached Screenshot.2024-10-01.at.10.51.20.PM.png (view on web) < https://github.com/user-attachments/assets/72622561-ed41-4d06-a99f-31cd74cae893>

— Reply to this email directly, view it on GitHub https://github.com/FalconChristmas/fpp/issues/1983, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB6FEA4CLV7PTJD5XE3YV2LZZNU3LAVCNFSM6AAAAABPG3GVIGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DANRSGE2DQMQ>

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/FalconChristmas/fpp/issues/1983#issuecomment-2389730218, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB3E2ZQ2VSCPAF7STGZDJTZZRQ3PAVCNFSM6AAAAABPG3GVIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBZG4ZTAMRRHA . You are receiving this because you authored the thread.Message ID: @.***>