Tasmota: implement option to present WiFi RSSI in dbm instead of percent

Created on 5 Dec 2019  路  17Comments  路  Source: arendst/Tasmota

Have you looked for this feature in other issues and in the wiki?

Yes,

Is your feature request related to a problem? Please describe.

Having the RSSI in percent instead of dbm is user friendly, but not very precise.

Describe the solution you'd like

A SetOption to choose between the current percent presentation and dbm.

(Please, remember to close the issue when the problem has been addressed)

I would implement this myself and send a PR, just wanting to know if this has a chance of being accepted before I invest the time.

enhancement fixed

Most helpful comment

It can stay as % as default... but allow users to change it with a SetOption if they desire? This way most users retain the current output but those that want dBm can change the setting?

All 17 comments

I think it should stay as % for the sake of simplicity to users.

It can stay as % as default... but allow users to change it with a SetOption if they desire? This way most users retain the current output but those that want dBm can change the setting?

Instead of adding a SetOption to select one over another, IMO it's better to have RSSI always displayed and use a SetOption to optionally add dBm value as well. RSSI (while simplified) is a very useful on-glance quick diagnose wifi metric. Forcing external tools to poll the device for something so trivial is - IMO again - a bit overkill.

Instead of adding a SetOption to select one over another, IMO it's better to have RSSI always displayed and use a SetOption to optionally add dBm value as well.

My plan was to also switch the value of the RSSI in the MQTT topic when the SetOption is in use. Displaying both on the WebUI is fine, but adding another node to the MQTT json is IMHO overkill.

Anyhow, after looking a bit more at the RSSI code I've decided that the changes are going to be quite simple. So, I'm going to just build it over the weekend, send a PR and then we can discuss based on an actual implementation.

But in any scenario, RSSI won't be reported as -dBm?

@jziolkowski It is in dBm if the conversion is NOT done as Adrian showed.
I deleted the conversion and i get "RSSI dBm":-51
You just have to change the text here: https://github.com/arendst/Tasmota/blob/development/tasmota/i18n.h#L127

RSSI dBm does not make sense, because RSSI by design is a unitless value. You have either RSSI, or dBm. Using "RSSI dBm" is like saying "percent Celsius"

Whatever you want :-) Just edit the text in that line
"Wifi dBm":-51

The point is not how that node is named. What I'm saying is: keep RSSI 0-100. If user wants to display dBm value, don't present it as RSSI, because it is not.

It is named correctly if you change the line. There is NO RSSI anymore (in mqtt)
EDIT: I dont looked at Webfrontend. It needs a change too. So it is a bit more to change
10:01:17 MQT: tele/sonoff-53CBF8/STATE = {"Time":"2019-12-06T10:01:17","Uptime":"0T00:00:12","UptimeSec":12,"Vcc":3.041,"Heap":29,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"Jason_Home_WLAN","BSSId":"00:A0:57:2A:BD:19","Channel":13,"Wifi dBm":-54,"LinkCount":1,"Downtime":"0T00:00:06"}}

dBm is enough, as it's a sub-dictionary of Wifi anyway :) However I still prefer having RSSI in place and dBm as an additional node, enabled with setoption

This thread is indeed entertaining...

RSSI and dBm, best of both worlds. +1

Yup, now we can add all the rounding errors and find the missing wifi waves...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

smadds picture smadds  路  3Comments

Ndrinta picture Ndrinta  路  3Comments

ximonline picture ximonline  路  3Comments

esp32x picture esp32x  路  3Comments

Joeyhza picture Joeyhza  路  3Comments