forum.pistar.uk

The error was in the dashboard version 20200526.

Dashboards get updated automatically whenever there is a new version by a nightly script or when a user runs sudo pistar-update.

The dashboard version 20200526 broke hotspots, and only if users went in and fiddled around with that dropdown on that ...

Do you see now why I was as you put it "splitting hairs" on the conclusion that it was the 4.1.2 upgrade that killed it?

honestly no. as reproduced, running the upgrade process from 4.1.1 to 4.1.2 broke hotspots...

regardless i'm glad to have in some way helped here. hopefully save a few people ...

Hey fantastic. I'm the other guy (op). Work corralled me for the day yesterday. One of my hotspots I rebuilt on a new card so I can get you whatever you might want from the non-working config or try tests to revive it. The other one came back to life when I inadvertently selected NONE for the oled3 ...

I understand what steps you performed, but you haven't provided any actual evidence that something in the upgrading process actually broke your systems.

this is an odd splitting of hairs. i agree, sudo pistar-upgrade didnt break the hotspot. but something in the process absolutely did. i think ...

Does your hotspot even have a display screen?

yes. not sure if you mean to be aggressive or if that's accidental. thanks, never understood the difference between nextion and OLED. definitely oled. try googling that one to see why i had no idea how to sort it out...

I wouldn't conclude that the ...

What screen do you have? If you have a Nextion it should be set to Nextion. If you have an OLED it should be set to OLED.
sorry to be dense, but i dont know what a nextion vs oled is. they have always been set to oled in recent memory and i went through old configs by hand and they were set as ...

after the upgrade they were both set to type OLED3. i went through an old config zip and they were set to type "OLED". the PCB they come on says nextion but i cant recall (been a long time since initial config) if the original selection was nextion or OLED. i have some older configs if that's ...

first let me state, i'm a dummy. pi-star has been so reliable that i stopped having good habits. like testing an update for good functionality before updating a second unit. i didn't do that. now i have 2 non functional units. i have actively troubleshot with the one and left the other one alone ...

thanks for the step, here's the result:

thanks, i appreciate the concept of the bad characters. what i am wondering is how to simply revive the page? i was able to use nano to edit the ircDDBgateway file to squash dstar's DPRS which turned on by default (not something i wanted)... so the root issue has been solved. i just don't understand ...