-
Notifications
You must be signed in to change notification settings - Fork 33
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
User/Password for Tasmota #159
Comments
Hi, currently user and password is not supported for tasmota webAPI, but it shouldn´t be a problem to implement it. i´ll add it soon and let you know. |
I can create a PR, if that is of any help. Its really a quite trivial
modification...
Thanks for your efforts!
Best, Jörg
…On 06.03.24 08:09, reserve85 wrote:
Hi,
currently user and password is not supported for tasmota webAPI, but
it shouldn´t be a problem to implement it.
|http://<ip>/cm?user=<username>&password=<password>&cmnd=status%2010|
instead of
|http://<ip>/cm?cmnd=status%2010|
i´ll add it soon and let you know.
—
Reply to this email directly, view it on GitHub
<#159 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACM4Q2HZA6SCUJMOYW2QI53YW26I3AVCNFSM6AAAAABEIOLPMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGIZDANZUGE>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
That would be great if you have already implemented it. |
reserve85
added a commit
that referenced
this issue
Apr 19, 2024
## V1.91 ### script * support Home Assistant over HTTPS (#178) * Support login credentials for Tasmota (#159) ### config * add `[HOMEASSISTANT]`: `HA_HTTPS` * add `[INTERMEDIATE_HOMEASSISTANT]`: `HA_HTTPS_INTERMEDIATE` * add `[TASMOTA]`: `USER` and `PASS` * add `[TASMOTA_INTERMEDIATE]`: `USER_INTERMEDIATE` and `PASS_INTERMEDIATE`
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, my Tasmota (Hichi) power meter demands user/password when querying the API. I have augmented the config and the constructor accordingly. If that is a common issue this should maybe go into the main dev branch...
The text was updated successfully, but these errors were encountered: