ioBroker / ioBroker.sonoff

Control Sonoff-Tasmota devices via ioBroker
MIT License
37 stars 28 forks source link
iobroker mqtt smarthome sonoff tasmota

Logo

ioBroker Sonoff

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Comparison of ioBroker adapters using MQTT protocol

If you only have Tasmotas speaking MQTT protocol go for ioBroker.sonoff. For other scenarios, consider the different options:

Feature ioBroker.sonoff ioBroker.mqtt (in broker mode) ioBroker.mqtt (in client mode) ioBroker.mqtt-client
Has a built-in MQTT broker yes yes no no
Relays messages to other MQTT subscribers NO!!! yes not applicable not applicable
External MQTT broker unsupported unsupported required required
Tasmota MQTT messages to ioBroker Objects smart processing 1:1 processing of all messages 1:1 processing of subscribed messages 1:1 processing of subscribed messages
non-Tasmota MQTT messages to ioBroker Objects no processing 1:1 processing of all messages 1:1 processing of subscribed messages 1:1 processing of subscribed messages
publish ioBroker values as MQTT messages none configured subtrees configured subtrees individually configured values

Usage

This adapter communicates with Sonoff devices with Tasmota firmware or ESP devices via MQTT.

The following topics are expected:

Note: The list could be easily extended. Please send Pull Requests or debug data for unknown states to the developer (via issue).

Auto-creation of objects

In the web config, you can determine which MQTT telegrams create the new objects not in default data points:

Usually TELE_SENSOR should be sufficient for most users.

Warning! This option will mess up your sonoff object tree! You have to redo all the settings for storage... Store the object structure as JSON file, so you can recreate your old structure. Best is to stop the adapter, delete all objects under sonoff and start the adapter again.

Flags for LED controllers

The mode states will be created only if the device has one of the states:

States:

Changelog

3.2.1 (2024-10-07)

3.2.0 (2024-08-28)

3.1.2 (2024-08-17)

3.1.1 (2024-08-09)

3.1.0 (2024-05-25)

3.0.3 (2023-09-25)

2.5.7 (2023-07-07)

2.5.3 (2023-03-30)

2.5.1 (2022-04-23)

2.5.0 (2022-03-21)

2.4.7 (2021-11-14)

2.4.6 (2021-11-13)

2.4.5 (2021-07-21)

2.4.4 (2021-07-19)

2.4.3 (2021-07-18)

2.4.2 (2021-07-17)

2.4.1 (2021-07-17)

2.4.0 (2021-02-04)

2.3.3 (2019-11-27)

2.3.2 (2019-10-23)

2.2.3 (2019-01-10)

2.2.2 (2018-06-22)

2.2.1 (2018-06-20)

2.2.0 (2018-05-22)

2.1.3 (2018-05-08)

2.1.2 (2018-04-23)

2.1.1 (2018-04-13)

2.1.0 (2018-03-30)

2.0.2 (2018-03-19)

2.0.1 (2018-03-17)

1.0.3 (2018-03-03)

1.0.2 (2018-02-17)

1.0.1 (2018-02-05)

1.0.0 (2017-11-27)

0.3.3 (2017-11-03)

0.3.2 (2017-10-22)

0.3.1 (2017-10-12)

0.3.0 (2017-10-06)

0.2.0 (2017-10-05)

0.1.0 (2017-10-01)

License

The MIT License (MIT)

Copyright (c) 2017-2024, bluefox dogafox@gmail.com

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.