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

[Enhancement]: Using MQTT secure (MQTTS) where possible #1061

Open
3 tasks done
KlausStoertebeker opened this issue Oct 11, 2024 · 7 comments
Open
3 tasks done

[Enhancement]: Using MQTT secure (MQTTS) where possible #1061

KlausStoertebeker opened this issue Oct 11, 2024 · 7 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@KlausStoertebeker
Copy link

I'm sure that

  • This issue is still present in the current beta version of this adapter
  • There is no other (open) issue with the same topic (use the search!)
  • This issue is not described in the adapter documentation / FAQ (read the docs!)

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

@KlausStoertebeker KlausStoertebeker added the bug Something isn't working label Oct 11, 2024
Copy link

Thanks for reporting a new issue @KlausStoertebeker!

  1. Please make sure your topic is not covered in the documentation
  2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue
  3. Search for the issue topic in other/closed issues to avoid duplicates!

Otherwise this issue will be closed.

@mcm1957 mcm1957 added enhancement New feature or request and removed bug Something isn't working labels Oct 11, 2024
@KlausStoertebeker
Copy link
Author

  1. Issue is NOT covered in the documentation
  2. There are NO log files because this is an enhancement request
  3. I haven't found my issue in other/closed issues

@klein0r
Copy link
Contributor

klein0r commented Oct 18, 2024

Related to #645

@KlausStoertebeker
Copy link
Author

Thanks for information,
but I don't understand if it is still in progress or not because it seems to be still open but nothing happened during the last two years...

@mcm1957 mcm1957 added the duplicate This issue or pull request already exists label Oct 18, 2024
@klein0r
Copy link
Contributor

klein0r commented Oct 22, 2024

@KlausStoertebeker That's not true. I've tested some alternative libraries and created a new branch:

5a5416a

But I haven't had time to finish the feature (since it requires a lot of changes).

@KlausStoertebeker
Copy link
Author

I didn't want to offend you - sorry for that.
You're doing good work - thank you for that.
Is there a way to support your work, also in other issues (I have seen thatbyou're also involved in some "Shelly Wall Display" issues...)

@klein0r
Copy link
Contributor

klein0r commented Oct 22, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants