SmartHome Community

ArcherS

Thought it could be good for future users to give a short write up on how to set up Tasmota devices reporting sensors into OpenLuup with the new Tasmota bridge.

First setup the Tasmota device:
Browse to the Tasmota device IP and then select "Configuration"
Go into Configuration Other
Make sure "Mqtt enable" is set and give a Device Name
Then into Configuration MQTT
Give IP adress and port of OpenLuup Mqtt server
Give a Client name
Set user and password
Set topic name

If you want to change how often the Tasmota device pushes data over Mqtt you can do that in the Console for the Tasmota by using the "TelePeriod" command. By default TelePeriod is set to 300 seconds, e.g. "TelePeriod 60" sets it to once every minute. (Just typing "TelePeriod" shows the current value.)

Second set up OpenLuup:
Paste the following into Lua Startup:

luup.attr_set ("openLuup.MQTT.Port", 1883)
luup.attr_set ("openLuup.MQTT.Username", "luup")
luup.attr_set ("openLuup.MQTT.Password", "password")
luup.attr_set ("openLuup.MQTT.PublishVariableUpdates", true) -- Not requred for Tasmota, publish every variable update if wanted

Save and reload Luup engine, you should now get the Tasmota bridge in OpenLuup

You should also get the Tasmota device you setup above
On my OpenLuup it got placed in the room "Tasmota".

Next step is to set up devices for the sensor data you want to get from the Tasmota device. This data is pushed into variables for the Tasmota device (if you hover above a variable name you see the sensor, e.g. "BME280"):

Download the plugin "Virtual Sensor" if you do not have it.
Go into Virtual Sensors, tab "Virtual Sensors" and create the new virtual sensors you need for the data you want to display from the Tasmota device, you want one virtual sensor per value.

Next step is to set the data from the Tasmota variables to the corresponding virtual sensors.
Go into the Virtual Sensor plugin, into the tab "Virtual Sensors"
Select the Tasmota device in the first drop down and then the variable in the second:

Job done! Now repeat for all the variables you wish to add into OpenLuup.

ArcherS

@therealdb I built my outdoor sensor from what I had in the garage, very much DIY in other words.
I used an outdoor junction box, to this I hot glued a plastic dome from an old motion sensor for the light sensor. I also added a short piece of plastic pipe for the BME280 so that it is outside of the box to get better readings. To keep spiders etc out of the pipe I added an old stainless mesh dome to the end of it.
In the box is also a 240V/5V transformer.

The intention is to mount it on the north wall of the house outside of the sun. At the moment it is laying on the window sill.

Some more small tips on rules:
It is possible to create up to three rules for each sensor.
It is possible to have several "Do" stamements in each rule.
Rule<x> ON <trigger1> DO <command> ENDON ON <trigger2> DO <command> ENDON ...

It is very easy to find out the name of each sensor for using in the rules by looking at: http://IP_address/cm?cmnd=Status%2010

A rule is defined by pasting the rule from e.g. notepad to the Console window of the sensor.
After that the rule needs to be enabled by Rule1 1, Rule2 1 etc.
After enabling a rule check in the console that the rule is sending values.
A rule is deactivated by Rule1 0 etc.
To see the contents of a rule just type Rule1 etc.
To delete a rule type Rule1 " etc.

My recommendation is for people to look at the Tasmota rules documentation, it is very good.
.
//ArcherS

ArcherS

Thank's for a really quick reply! That indeed did the trick, I knew it was something easy I missed.
Now I just need to go through my Reactors and re-map my z-way devices. Not too much work.

//ArcherS

ArcherS

Checked with v20.7.14 and the "sl_CentralScene" variable is updated with the key pressed.

Thanks again for the update!

ArcherS

Some time ago I stumbled on some rather nice looking temperature and humidity sensors from Xiaomi and how to get them to communicate with a Tasmota ESP32 with BLE.

I ordered an ESP32 on Ebay and a three-pack of the sensors from Bangood. The sensors are quite cheap, you can find them for €4-5 in the usual sites.

The sensors are quite small, approx 4.5cm and run on a CR2032 battery. Time will tell how long the batteries will last. With the custom firmware you can change the reporting interval.

I have now been running this for little over two months and it works surprisingly well, bringing the temperature and humidity data into OpenLuup.

In short what you do is the following:

Download the beta Tasmota for ESP32, flashing is a bit different from the regular Tasmota but pretty straight forward
Enable bluetooth with setoption115 1
The Xiaomi sensors can used both with stock firmware and flashed with a custom firmware that removes the encryption from the transmit of data, I flashed them with a Win10 laptop and it was super easy. You can even roll back the original firmware if you want.

The Xiaomi sensors will then be included by the ESP32 Tasmota device and can be sent to OpenLuup with rules, brought in with Sitesensor or now via MQTT.

ArcherS

It seems as if it is possible to modify it with an external antenna.
Here is an article on how to modify the Razberry2 EU:
Modify Razberry2 (translated)

Is is in Swedish, hopefully the translated text is understandable.
In short you cut away the built-in antenna and solder on an antenna connector for the external antenna. You of course need an antenna for the frequency in your country, the article is for 868 MHz (EU).

//ArcherS

ArcherS

@matteburk if you have a Pi 3B+ then you are in luck since it will boot from USB without doing anything.
If it is a Pi 3B then you have to change a "USB boot bit", see e.g. this instruction.

I took the easy route and bought a new Pi 3B+ when I moved my Z-way server to SSD from SD. They are quite cheap anyway and I guess I can get use of the Pi 3B for something else later on.

As @toggledbits says the Pi's are a bit picky on SSD adapters. I had two old 2.5" cases laying around, one worked and the other did not. The SSD migration cable that came with a Samsung SSD that I used for another PC also works.

Edit: And if you buy a new Pi 4 they should now also have USB boot out of the box. Assuming the box has not been sitting on the shelf in the store for too long of course.

ArcherS

@akbooer thanks for the assistance and patience, now it works!

Edit: Added the humidity to the code:

local json = require "openLuup.json"

function MyMQTThandler (topic, message)
  local info = json.decode (message)
  local t = info.AM2301.Temperature
  local h = info.AM2301.Humidity
  luup.variable_set ("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature",  t, 216)
  luup.variable_set ("urn:micasaverde-com:serviceId:HumiditySensor1", "CurrentLevel",  h, 228)
end

luup.register_handler ("MyMQTThandler", "mqtt:tele/tasmota_test/SENSOR")

ArcherS

@buxton yes it opens up new possibilities. On the Tasmota bluetooth webpage some other devices are listed, e.g. a soil humidity meter.

So far it has been quite stable for more than two months.
The Tasmota ESP32 is still beta, I assume it will get better over time.

I will also make the ESP32 to report over Mqtt now that OpenLuup has support for it, hopefully that will make the setup even more stable.

ArcherS

@droy I use the excellent Telegram plugin by @therealdb in OpenLuup, it should work on the Vera also.

ArcherS

@crille said in Xiaomi Platform Integration:

@rafale77 I have them in my greenhouse connected to a Sonoff Dual R3 running Tasmota and pushing values via MQTT to openLuup and HomeKit.

Yes the MiFlora should be supported by Tasmota.
I use three small Xiaomi temperature and humidity sensors (LYWSD03MMC) over BLE to an ESP32 with Tasmota and it works very well, so I would assume that the MiFlora also should work.
Tasmota support for the ESP32 is beta, but so far it has been quite ok. There is a new update that I have not yet tried.

My Temp/humidity sensors are some 7-8 meters away from the ESP with some drywalls in between and it works.

ArcherS

@akbooer said in openLuup: Shelly Bridge plugin:

Yup, done that too. OK if you can get used to the 2 second delay (unless on USB power.)

I have now included the Button1 and it works ok, it added without problems in OpenLuup. No child devices, but I assume that is the way it should be.

I think I will keep it attached to USB power. I have power available where the button is located and this gives more or less instant actions. I also noticed that if it is not on USB in some cases it does not connect as it should when going out of sleep when you push the button.
I assume that wifi is not the best technology for battery powered devices.
So far I am using a direct action from the button to the 1PM that it should control.

ArcherS

@christian_fabre said in MQTT – setup and use:

I have removed several of the Shelly and Tasmota bridges. But after the Reload, they are created in NoRoom.

Yes, the bridges are created in "No room", but the child devices should be created in the two rooms "Shellies" and "Tasmota" respectively.

ArcherS

@christian_fabre that is good news, then it looks as the Shelly works as it should in respect of the Mqtt settings.

Just to rule out the obvious; the Shelly devices and Tasmota devices should show up in OpenLuup in the two rooms "Shellies" and "Tasmota" and not in "No room".

Maybe deleting the Shelly bridge and reloading as @akbooer suggests now that you have the announce message.

ArcherS

@christian_fabre my Plug (not the S version) looks like this in Mqtt Explorer:

For some reason there is no announce message from your plug when comparing with my plug.

ArcherS

@akbooer yepp, edited that typo.

ArcherS

@christian_fabre said in MQTT – setup and use:

I have the same problem with the Tasmota bridge

Regarding the Tasmota bridge it creates one device per Tasmota, i.e. no additional child devices as for the Shellies. These you instead need to create yourself by e.g. using the Virtual Sensor plugin.
In this post you can find more on how I have done that.

Did you try with Mqtt Explorer? It is a very good tool to see that the Mqtt devices, both Tasmota and Shellies are working as they should, and also to look at what they send.

ArcherS

@akbooer I routinely updated the two new Shellies and then I got v1.10.3, bad decision as it turnes out.
My two older Shellies are on v1.9.0 and worked directly when I enabled Mqtt.

Manual update is better, automatic is a pain, Win 10 is a good example on that. I assume I will get it on my Qnap when I update it.
I have also blocked the Shellies and Tasmotas in the the router

ArcherS

@christian_fabre I added my Shelly 1PM today to OpenLuup v21.4.29b.

At first it did not work, and I could not figure out why. Then I found a post on the Shelly forum that said that there in some cases (or for some devices) could be a problem with the latest Shelly firmware and Mqtt.

I had the latest v1.10.3 in my 1PM. After I downgraded the Shelly to v1.9.4 it worked.

Check what firmware you have in your plug and if you have the latest you can try to downgrade and see if it works.
Go to https://www.shelly-support.eu/index.php?shelly-firmware-archive/ and enter your IP address, select the right plug variant (there are a few to choose from) and firmware release. Then you copy the url that is generated into a browser.
If you have blocked the Shelly in your router from Internet access you probably have to open it temporary for the downgrade.

I also added my Shelly Button to OpenLuup and for some reason I could not downgrade it, but I managed to get it working anyway after a few attempts.
(A bit strange since the post I found on the forum was on problems with the Button and v1.10.3.)

Another tip is to use MqttExplorer if you do not already use it and see if the Shelly shows up there. If it does, then at least the Mqtt part of the Shelly most likely works.

ArcherS

@catmanv2 do you mean this dialogue?

Check what version of OpenLuup you are running, there was a problem with these tags in v21.4.25 that is fixed in v21.4.26.
See the posts in the end of this thread for more info.

Will this rule work for lighting?

Creating Rules with Conditional Logic

Error updating reactor on Vera

formatting of "set variable" in rules

Vera Thermostat trigger wrong Setpoint value

Xiaomi Platform Integration

Build 21123

Rethinking HVAC moving from Reactor (Vera) to MSR

MQTT – setup and use

Expressions and LuaXP Functions

Multi-System Reactor Developer Preview AVAILABLE

openLuup: Shelly Bridge plugin

How do you post images on this forum from a smart device?

Security exposure with internet connected homes

Using MSR as a Gaming Engine: LIGHTS OUT

Let's talk about MSR-provided Virtual Devices... NOT!

Rapidjson instead of cjson and dkjson

New Ezlo Web GUI now in "beta"

ArcherS

@ArcherS

Best posts made by ArcherS

Latest posts made by ArcherS