OS4 RSSI Graph Behavior

W4NMH

Anyone else notice that RSSI Graph is not showing the entire PTT like the OS3.
It does show briefly at the End of Transmission when the PTT is released. W4NMH

HA2NON

RSSI measurement and the graph works differently on the OS3 and OS4.

W4NMH

Why would it work differently?
For both, there is no control over speed or a pause for a meaningful capture.
The OS4 is particularly troublesome that it is not a continuous measurement, only a brief moment while de-keying PTT.

HA2NON

We've been able to reproduce the issue, thank you for reporting it. Fix will be available in the next beta firmware next week.

W4NMH

HA2NON F/W Ver V39 has made this even worse, RSSI Graph never changes off of -127 dBm.
-Previously it would plot on graph briefly when PTT is released.

Dashboard Status and Log show RSSI as expected.

HA2NON

Which modem mode and transceiver do you use?

W4NMH

HA2NON DMR to DMR; TYT MD-390, TYT MD-UV380, Anytone AT-D578UVIII PLUS.
-All work fine on my OpenSpot 3.
+OpenSpot4 showed RSSI @ End of Transmission until V39 was installed.

EdEdward

W4NMH
He doesn't have a D578UVIII PLUS.
I pointed out to him that Amazon sells them and has them in stock.

HA2NON

Please try using a different browser. If it does not work even with a different browser then please send us screenshots or a video which shows the issue.

W4NMH

HA2NON More info:

When OpenSpot4 is powered by Schedule, RSSI Bar Graph remains at -127 dBm.
Reboot via Dashboard Restores RSSI Bar Graph Function.

Correction, any First Boot by any method requires a reboot from the Dashboard for the RSSI Bar Graph to function.

Sincerely,

Rich Davis W4NMH EMT CETSr
https://W4NMH-Technical.net

W4NMH

Not Browser Dependent
Not Radio Dependent
Briefly worked at very End of Transmission in F/W V38
No change on Bar Graph in F/W V39
Status Screen, Logs Capture RSSI
BM Dashboard captures RSSI

OpenSpot3 RSSI Bar Graph works in ALL Cases

No Screenshot to Capture in F/W V39, remains bottomed out at -127 dBm

Tyrbiter

A suggestion, try a re-flash of the latest fw using the manual procedure.

W4NMH

V39 F/W Update resolved, however, a 'Fresh' Browser session is required after upgrade.
Confirmed on two OpenSpot4 units.
a. Before upgrading the faulty RSSI Bar Graph was present.
b. Post upgrade to V39 the situation was still present.
1. Restarting the browser session completed the resolution.

Tyrbiter

F5 in the browser to flush the cache ought to be enough.

W4NMH

Tyrbiter iOS iPAD does not have a “F5” key.
-Requires closing browser tab and starting a new browser connection.
-An OpenSpot4 reboot also establishes a new browser connection.
+HTTPS may solve this
+Does not occur with OpenSpot3; it’s the OpenSpot4 Web UI interface; i.e. often dropping API Keys.
-OpenSpot3 does not drop API Keys either.

W4NMH

More info:

When OpenSpot4 is powered by Schedule, RSSI Bar Graph remains at -127 dBm.
Reboot via Dashboard or a Manual Power on Restores RSSI Bar Graph Function.

Sincerely,

Rich Davis W4NMH EMT CETSr
https://W4NMH-Technical.net

W4NMH

Also when idle for a period of time, a reboot is required to restore the RSSI Bar Graph, otherwise remains @ -127 dBm

W4NMH

Tried multiple browsers with mixed results.
Brave, Chrome, Edge, Firefox, Safari

Consensus is that because the OpenSpot4 does not have HTTPS connectivity, all of the browsers balk.
i.e. Toggling Off all of the Security Features in Brave Enabled RSSI Bar Graph.
In Chrome, setting Site Settings to allow ADs, Pop-Ups, and Insecure Content worked with limitations.
Specifically Chrome Tab had to be Closed and a new session started to Re-Enabling RSSI Bar Graph.

A reboot of the OpenSpot4 also resets the Browser Connection with a new session, Re-Enabling RSSI Bar Graph.

Feature Request: HTTPS Dashboard to Browser connection.

HA2NON

Sorry, but we still can't reproduce the issue even with scheduled poweroff and poweron. Seems like a browser or device security setting issue.

W4NMH

Chrome iOS 16.3.1:

Refresh Tab x4, Close Tab, Close Chrome
Open Chrome, New Tab-> OpenSpot4
RSSI BarGraph works for awhile

HTTPS Socket would probably fix, or possibly keeping the Tab Active?