-
Notifications
You must be signed in to change notification settings - Fork 68
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
[Enhancement]: Using MQTT secure (MQTTS) where possible #1061
Comments
Thanks for reporting a new issue @KlausStoertebeker!
Otherwise this issue will be closed. |
|
Related to #645 |
Thanks for information, |
@KlausStoertebeker That's not true. I've tested some alternative libraries and created a new branch: But I haven't had time to finish the feature (since it requires a lot of changes). |
I didn't want to offend you - sorry for that. |
@KlausStoertebeker Thank you - I'm developing the Shelly adapter since three years now: See changelog: https://github.com/iobroker-community-adapters/ioBroker.shelly/blob/master/CHANGELOG_OLD.md Feel free to book the ioBroker Master Kurs to support my work. |
I'm sure that
Shelly device
General issue
Shelly firmware version
General issue
Protocol
MQTT
The problem
I'd like to use a SSL connection to increase the security in my home automation network. So it would be nice if the Gen2 (maybe Gen3)-Shelly-devices could be operated/controlled via an SSL/TSL connection.
iobroker.current.log (in debug mode!)
No response
Version of nodejs
18.20.4
Version of ioBroker js-controller
6.0.11
Version of adapter
8.3.0
The text was updated successfully, but these errors were encountered: