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.

@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

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

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

Thanks again for the update!

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.

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

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

@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")

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

@rafale77 I tried this way of delaying at startup and it works fine. It does not cause delays when reloading luup which is a clear benefit.

About one month ago I got a new electrical meter in the house. The new meter is a "smart" meter equipped with a data port. It is more or less the same type of meter that is used in a number of European countries, e.g. The Netherlands, Belgium, Sweden etc.
Norway has selected a different version with a RJ45 port with another protocol.

The dataport is a serial "P1" port in the form of a RJ12 contact that sends quite a lot of data every 10 seconds:

The data will show both consumption and production if you e.g. have solar panels at home.

My initial though was to use the Tasmota P1 Smart Meter with Mqtt. I tried this and it works, but unfortunately I got some serial data errors every 5-10th message for some reason so I decided to try another solution.

I found a few other alternatives and tested one of them. The upside with this version is that it is adapted to the Swedish data fomat that differs from the Dutch a bit and that it delivers the data in Mqtt form:

The hardware is pretty simple. For the Tasmota variant and most of the other solutions you need a ESP8266, e.g. a Wemos mini and then a transistor and two resistors (image below). The version I use is even simpler since it does not need the transistor.
For a lot of the meters delivered (DSMR 5 versions if I am right) you can power the ESP from the 5V provided in the RJ12 port, very handy.

It is also possible to buy a readymade P1 meter, this one looks quite nice, although I have not tested it.

In order to get a good overview of the data from the meter I have started creating a dashboard in Grafana that gets data from Historian in OpenLuup. It is quite useful to be able to see the load over time per phase etc.

I also managed to grab the hourly prices in json format and display that in the dashboard via some lua code in a scene.

At the moment I have built no logic around this, but it opens up posibilities for sure. In Sweden the electrical tarrifs will change from daily rates to being higher when demand is higher, perhaps then this can be used.

All in all a fun DIY project that provides some useful data out of the electrical meter.

That did the trick!

Alpine and Docker, need to look at that also later on.

Thank's @CatmanV2 and @akbooer for your swift help!

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

Like @Crille I have an electrical meter with a P1 data port. I use a DIY ESP8266 reader that I described some time ago in this thread. Since writing my post I have changed the software on the ESP, the version I am using now publishes the meter data approx every 10s as a json.

A good wifi solution for the whole house if lacking a dataport is to use a Shelly 3EM. It is a three clamp meter that can measure all three incoming phases, assuming you have that. I have a few of these for measuring both single and multiple phase consumers, e.g. a two-phase water heater. It reports both energy, power, voltage and current per phase.
The only downside I can see is that the clamps are a bit big, so some space is required to get them in place around the incoming power lines.

@therealdb thank you for the update!

I have tried it and it does not quite work.
The Lua code is executed ok (with the added comma as below), and I get a message in Telegram.
The text is ok, however instead of getting an image I get "camsnapshot117439654.gif" (the number is different each time). The gif does not seem to contain anything.
The url I call generates a .jpg file, I do not know why arrives as an empty .gif.

Any ideas?

(Btw, there is a small typo in the luup.call_action, the comma is missing after the VideoUrl line. It should be:)

luup.call_action("urn:bochicchio-com:serviceId:VeraTelegram1", 
  "Send",
  {
     Text="This is a protected endpoint!",
     VideoUrl="https://media.giphy.com/media/3o84sIqsVAJNfWyjy8/giphy.gif",
     UrlParams="--digest -u daniel:secret" -- <== curl parameters!
  }, 515)

//ArcherS

I included a ZRC90 remote to Z-way. The inclusion was without problems, and in Z-way you can see what button is pressed.

In OpenLuup I get the same variables as Catman has listed above. I tested and the two variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" on the remote device are updated on key presses.

Depending on what you press "zway_61-0-91-DS" get the following values:
Btn 1 single press: 10
Btn 2 single press: 20
...
Btn 8 single press: 80

Btn 1 double press: 13
Btn 2 double press: 23
...
Btn 8 double press: 83

Btn 1 press&hold: 11
Btn 2 press&hold: 21
...
Btn 8 press&hold: 81

Each time a button is pressed zway_61-0-91-DS_LastUpdate is also updated with a new time.

So far so good, the above two parameters gives the possibility to capture the various key presses on the ZRC90.

What does not work is that I get the same problem as I did for the Zwave.me wall controller, i.e. that the two variable are not updated in Reactor on key presses.
@akbooer is this something that can be fixed?

I am running OL 20.7.4b and Z-way plugin 20.5.12.
(The key presses on the Zwave.me wall controller are still working.)

//ArcherS

@akbooer I am on 7.3.1 and what I have done is to add links on the top of the pages to navigate between them.
The link buttons work pretty well also on an iPad or even on the phone.

//ArcherS

@therealdb now it works!

For my Axis camera that seems to require Digest mode for curl authentication I use the following to send an image:

luup.call_action("urn:bochicchio-com:serviceId:VeraTelegram1", 
  "Send",
  {
     Text = "Motion in garage", 
     ImageUrl = "http://192.168.x.x/jpg/image.jpg",
     UrlParams = "--digest -u daniel:secret"
  }, 515)

Thanks for the addition to an already nice plugin!

//ArcherS

I updated to v20.7.12 and it works partially!

"LastSceneTime" is updated every time you press a key, so that one works.

"sl_CentralSceneUpdates" however stays "null" all the time.

On the ZRC90 that I still have on the Vera there is a variable called "sl_CentralScene" but no variable called "sl_CentralSceneUpdates". I do not know if this could be the reason.

As a side note the variables "zway_61-0-91-DS" and "zway_61-0-91-DS_LastUpdate" are now updated instantly in Reactor.
So a functional workaround could be to use the "zway_61-0-91-DS" and "LastSceneTime" variables for capturing keys pressed in e.g. Reactor. I did a quick test and it seems to work.

One solution that I can think of is to use MySensors. https://www.mysensors.org/
This is a DIY community platform for making sensors etc. It is supported by Vera and OpenLuup, @akbooer is using it if I am not wrong.

I found someone that had made a water pressure sensor that you perhaps could have a look at for inspiration: https://forum.mysensors.org/topic/8731/water-pressure-sensor/1?_=1590472756396&lang=en-US

In short with MySensors you set up a gateway and then the sensors you want. Each node is an Arduino or similar. I used an USB connected gateway with my Vera, but an Ethernet connected gateway is needed for OpenLuup.

I set it up a number of years ago on my VeraLite and it actually worked really well. I used it mainly for simple temperature sensors. I stopped using it because of that each time the Vera rebooted the gateway was lost, and I had to re-discover it on the Vera USB port. Quite a bit of hazzle since the Vera had a tendency to reboot quite a lot.

If I get some time I may have a go at restarting MySensors now that I am using OpenLuup since it would be a good way to add dirt-cheap sensors to the system.