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

Send wifi signal strength to HomeAssistant automatic discovery #8244

Closed
jrhbcn opened this issue Apr 21, 2020 · 3 comments · Fixed by #8370
Closed

Send wifi signal strength to HomeAssistant automatic discovery #8244

jrhbcn opened this issue Apr 21, 2020 · 3 comments · Fixed by #8370
Assignees
Labels
enhancement Type - Enhancement that will be worked on

Comments

@jrhbcn
Copy link

jrhbcn commented Apr 21, 2020

Hi,

Tasmota both reports RSSI and Signal Strength for WiFi connection (following issues #7113 and PR #7145). However, only RSSI is added back to Home Assistant and Signal Strength is missing in automatic discovery. I am trying to unify the wifi reporting of all my IoT devices (it is a nightmare! but the majority seems to report dBm). Would it be possible to add this into Home Assistant discovery?

Thanks!

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

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

Describe the solution you'd like
It'd be good to have the same info in the status mqtt topic as attributes in Home Assistant.

Describe alternatives you've considered
Convert RSSI to signal strength directly in Home Assistant but the entity cannot be added automatically to the Tasmota Device and looks as if an standalone entity.

Additional context

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

@ascillato2 ascillato2 added the feature request (devs?) Action - awaiting response from developers label Apr 22, 2020
@effelle
Copy link
Contributor

effelle commented Apr 22, 2020

As you probably knows, we have already dBm signal in information page:

EffE-WiFi (76%, -62 dBm)

RSSI is already used in Home Assistant for metrics and to have dBm too a new sensor must be created, because a combined sensor with RSSI and dBm can't be used on history, meaning code repetition and then greater space used on program memory.
What I can do is to add the dBm value on the resume list of status sensor that will limit the space used, but will be not an information available for history.

@effelle effelle added the awaiting feedback Action - Waiting for response or more information label Apr 22, 2020
@jrhbcn
Copy link
Author

jrhbcn commented Apr 22, 2020

What I can do is to add the dBm value on the resume list of status sensor that will limit the space used, but will be not an information available for history.

I think that is almost perfect. Info will be accessible to HomeAssistant (to create automations, etc.) and even if not available directly for history it could be forwarded to influxdb/grafana if history is needed anyway.

Many thanks for looking into this and let me know if you need someone to test the solution.

Regards,

@effelle effelle self-assigned this Apr 22, 2020
@effelle
Copy link
Contributor

effelle commented Apr 22, 2020

Ok, I was about to change the resume list anyway.
I'll add dBm on next update.

@effelle effelle removed the awaiting feedback Action - Waiting for response or more information label Apr 22, 2020
@ascillato2 ascillato2 added enhancement Type - Enhancement that will be worked on and removed feature request (devs?) Action - awaiting response from developers labels Apr 26, 2020
@effelle effelle linked a pull request May 6, 2020 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Type - Enhancement that will be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants