Tasmota LoraWan after Join, no communication

[EddyDsSmartHome]

Hello everyone,
first of all I want to apologize for my English, if it's hard to understand, it's the fault of DeepL.

I have been trying to install Tasmota 14.4.1 on an ESP32
LILYGO TTGO Lora 868Mhz OLED 0.96 to run.
I have also tried it on another ESP Lora board, but it didn't work either. The error pattern is identical.
As a Lora device or LoraWan device, I use an LDS02 door contact sensor from Dragino (I have several of them, none of them work with Tasmota).

My problem is as follows.
I am configuring Tasmota correctly as far as I can tell, as I can see the “Join” attempt in the console and also receive other LoraWan devices from time to time if they are transmitting on the correct frequency and have the correct “SpreadingFactor”.
After the device has connected to Tasmota (after add the device with the command LoraWanAppKey1 ec91633879e14b9a87bad7c4ba4a9aee), it is unfortunately over. When I open or close the door contact, it sends a message, but Tasmota does not receive it because the frequency with which the sensor sends the message and the “SpreadingFactor (SF)” do not match the value set in Tasmota (868.1 / SF 7).

I am also a bit confused about the message “Send (577032) ‘207BF45F2DB1091B88821D6714D101CD33’, Invert 1, Time 53” what does this mean, I have not found anything in the documentation.
I have various screenshots and logs available, I hope someone has an idea why this is happening.

I still have a Dragino Gateway and Chirpstack active here, the sensor is not connected to ChiprStack/Gateway, but I can use it to check whether the messages were sent by the sensor and on which frequency/SF.

The timestamp in Chipstack is unfortunately offset by 2 minutes and a few seconds, but you can see that the message in Chipstack changes from “Join” to “UnconfirmedDataUp” after the door contact sensor has communicated with Tasmota.
The sensor has the devEUI: “a84041709189509f” and the devAddr: “00c9e970”

If I send messages via a second ESP/Lora using the “LoraSend” command, they arrive without any problems. Only the LoraWan messages are not displayed because of the frequency/SF “hopping”.

If the sensor transmits on the correct frequency/SF, then I get the entry as in the Tasmota documentation
Example from Theo (as I don't have one available as I write this)
{“LwReceived”:{“LDS01”:{“Node”:1,“Device”:“0x4AD6”,“Name”:“LDS01”,“RSSI”:-49.0,“SNR”:9.5,“DevEUIh”:“A840410E”,“DevEUIl”:“71894AD6”,“FPort”:10,“Payload”:[11,196,1,0,0,2,0,0,19,0]}}}

I would be very grateful for any tips. I'm not a programmer, so please take this into account if you have any questions or tips 😊

Regards Eddy

.drvset000
{"drvset73":{"Crc":440244319,"Flags":1,"Frequency":868.1,"Bandwidth":125.0,"SpreadingFactor":7,"CodingRate4":5,"SyncWord":52,"OutputPower":10,"PreambleLength":8,"CurrentLimit":60.0,"ImplicitHeader":0,"CrcBytes":2},"drvset73_1":{"AppKey":"EC91633879E14B9A87BAD7C4BA4A9AEE","DevEUIh":2822783344,"DevEUIl":2441695391,"DevNonce":29828,"FCntUp":0,"FCntDown":0,"Flags":0,"NAME":"LDS02"}}

.settings
	�����������������������������

.settings.lkg
	�����������������������������

[arendst]

I happen to have the same hardware and were able to join the LDS01 with Tasmota but....

As Tasmota uses a fixed frequency most Lora devices will fail to connect during Join as they try different frequencies Tasmota does not support. So you'll have to tell the LDS01 first to stay on one frequency while trying to join.

To configure the LDS01 you'll have to serial connect to it and perform the following commands:

Password 123456
AT+CHS=868100000

Then try to join and aftwerwards perform:

AT+CADR=0
AT+CDATARATE=3

This will fix the join frequency to 868.1

[s-hadinger]

This looks like json.load(data) failed and returned nil. Can you print the value of data just before this error?

[EddyDsSmartHome]

12:06:44.932 MQT: Subscribe to cmnd/DVES_C9E970_fb/#
12:06:44.935 MQT: tele/tasmota_C9E970/INFO1 = {"Info1":{"Module":"ESP32-DevKit","Version":"14.4.1.3(b167955-tasmota32)","FallbackTopic":"cmnd/DVES_C9E970_fb/","GroupTopic":"cmnd/tasmotas/"}}
12:06:44.950 MQT: tele/tasmota_C9E970/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"tasmota-C9E970-2416","IPAddress":"192.168.1.241","IP6Global":"","IP6Local":"fe80::9215:6ff:fec9:e970%st1"}}
12:06:44.963 MQT: tele/tasmota_C9E970/INFO3 = {"Info3":{"RestartReason":"Software reset CPU","BootCount":148}}
12:06:44.979 MQT: stat/tasmota_C9E970/RESULT = {"POWER":"ON"}
12:06:44.984 MQT: stat/tasmota_C9E970/POWER = ON
12:06:47.061 HTP: Berry Console
12:06:47.641 WIF: IPv6 Global fd30:3667:9f84:c8ba:9215:6ff:fec9:e970
12:06:47.953 HTP: Main Menu
12:06:48.049 QPC: Reset
12:06:48.967 MQT: tele/tasmota_C9E970/STATE = {"Time":"2025-01-30T12:06:48","Uptime":"0T00:00:08","UptimeSec":8,"Heap":151,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":4,"Objects":46},"POWER":"ON","Wifi":{"AP":1,"SSId":"Hust24","BSSId":"F4:92:BF:11:9B:49","Channel":6,"Mode":"HT40","RSSI":100,"Signal":-46,"LinkCount":1,"Downtime":"0T00:00:03"}}
12:06:49.960 APP: Boot Count 148
12:06:50.531 CFG: Saved, Count 389, Bytes 4096
12:07:47.026 HTP: Console
12:07:48.967 MQT: tele/tasmota_C9E970/STATE = {"Time":"2025-01-30T12:07:48","Uptime":"0T00:01:08","UptimeSec":68,"Heap":146,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":5,"Objects":79},"POWER":"ON","Wifi":{"AP":1,"SSId":"Hust24","BSSId":"F4:92:BF:11:9B:49","Channel":6,"Mode":"HT40","RSSI":100,"Signal":-45,"LinkCount":1,"Downtime":"0T00:00:03"}}
12:08:33.194 MQT: tele/tasmota_C9E970/SENSOR = {"Node":1,"Device":"0x5061","Name":"LDS02a","RSSI":-77.0,"SNR":12.2,"Events":101,"LastEvent":4,"DoorOpen":0,"Alarm":0,"Battery":3.096}
12:08:33.211 BRY: Exception> 'type_error' - value 'nil' does not support subscriptable
12:08:33.213 stack traceback:
12:08:33.214 	<unknown source>: in function `_anonymous_`
12:08:33.225 	<unknown source>: in function `try_rule`
12:08:33.226 	<unknown source>: in function `exec_rules`
12:08:33.227 	<unknown source>: in function `event`
12:08:33.295 SRC: MQTT
12:08:33.296 CMD: Grp 0, Cmd 'POWER', Idx 1, Len 3, Pld 0, Data 'OFF'
12:08:33.303 MQT: stat/tasmota_C9E970/RESULT = {"POWER":"OFF"}
12:08:33.305 MQT: stat/tasmota_C9E970/POWER = OFF
12:08:33.979 CFG: Lora saved to file
12:08:34.095 CFG: Saved, Count 390, Bytes 4096
12:08:36.258 MQT: tele/tasmota_C9E970/SENSOR = {"Node":1,"Device":"0x5061","Name":"LDS02a","RSSI":-79.0,"SNR":12.8,"Events":102,"LastEvent":4,"DoorOpen":1,"Alarm":0,"Battery":3.096}
12:08:36.275 BRY: Exception> 'type_error' - value 'nil' does not support subscriptable
12:08:36.276 stack traceback:
12:08:36.277 	<unknown source>: in function `_anonymous_`
12:08:36.288 	<unknown source>: in function `try_rule`
12:08:36.289 	<unknown source>: in function `exec_rules`
12:08:36.290 	<unknown source>: in function `event`
12:08:36.309 SRC: MQTT
12:08:36.310 CMD: Grp 0, Cmd 'POWER', Idx 1, Len 2, Pld 1, Data 'ON'
12:08:36.317 MQT: stat/tasmota_C9E970/RESULT = {"POWER":"ON"}
12:08:36.319 MQT: stat/tasmota_C9E970/POWER = ON
12:08:36.954 CFG: Lora saved to file
12:08:37.117 CFG: Saved, Count 391, Bytes 4096
12:08:39.322 MQT: tele/tasmota_C9E970/SENSOR = {"Node":1,"Device":"0x5061","Name":"LDS02a","RSSI":-76.0,"SNR":9.8,"Events":103,"LastEvent":0,"DoorOpen":1,"Alarm":0,"Battery":3.090}
12:08:39.340 BRY: Exception> 'type_error' - value 'nil' does not support subscriptable
12:08:39.341 stack traceback:
12:08:39.343 	<unknown source>: in function `_anonymous_`
12:08:39.354 	<unknown source>: in function `try_rule`
12:08:39.355 	<unknown source>: in function `exec_rules`
12:08:39.357 	<unknown source>: in function `event`
12:08:39.944 CFG: Lora saved to file

[sfromis]

Sorry, got things mixed up. What is passed to the callback for tasmota.add_rule is already parsed, instead of being a json string. Better this way:

tasmota.add_rule(['DoorOpen','Name=LDS02a'],
  def (values, trigger, data)
    var doorstatus = values[0] # matching the trigger
    var name = values[1]
    var alarm = data['Alarm'] # another field from the payload
    print(f'{name=} {doorstatus=} {alarm=}')
  end)

[EddyDsSmartHome]

now i is working.
THANK YOU,
I hope I can do the rest myself with the integration into the GUI.
But I think it would be better in the code, since the sensor is “officially” supported, and then it should also be visible in the web-gui.

tasmota.add_rule(['DoorOpen','Name=LDS02a'],
  def (values, trigger, data)
    var doorstatus = values[0] # matching the trigger
    var name = values[1]
    var alarm = data['Alarm'] # another field from the payload
    print(f'{name=} {doorstatus=} {alarm=}')
  end)

name=LDS02a doorstatus=0 alarm=0
name=LDS02a doorstatus=1 alarm=0
name=LDS02a doorstatus=0 alarm=0
name=LDS02a doorstatus=1 alarm=0
name=LDS02a doorstatus=0 alarm=0
name=LDS02a doorstatus=1 alarm=0

With comments:

# Add a rule that listens for the 'DoorOpen' event with the name 'LDS02a'
tasmota.add_rule(['DoorOpen','Name=LDS02a'], 

# Define the function that is executed when the rule is triggered
  def (values, trigger, data)  

# Extract the door status (e.g., open or closed) from the values
    var doorstatus = values[0]  

# Extract the device name (e.g., 'LDS02a') from the values
    var name = values[1]  

# Extract the alarm status from the received data
    var alarm = data['Alarm'] 

  # Print the device name, door status, and alarm status
    print(f'{name=} {doorstatus=} {alarm=}') 
  end)

[sfromis]

Door open does not really "count" as a normal Tasmota sensor, which is more when monitoring things like temperature, instead of something happening now, like door open or alarm.

Tasmota is not even trying to have all "potentially interesting" data on the deliberately rudimentary admin/test web UI, which is not really meant as a place you sit and watch in normal operation. Things like a plain door sensor or PIR is also not replicated. And you already have the console where you can easily see if the communication works.

One reason for the web UI being rather sparse is that Tasmota was developed with ESP8266, where there just is not room to have all "it would be nice" things. And the intended scenario is that you have a backend dashboard setup (or similar) where you can keep track of many devices on one page.

[EddyDsSmartHome]

Hello everyone,
I have assembled the various Berry scripts from my questions into a project and it works as desired.
There is certainly room for improvement, but for my part I am satisfied.
Here is the final code and a picture of how it looks:

I will update the code in the next few days with the battery status and timestamp.

Thx @sfromis @s-hadinger @arendst for your help!

import webserver

class DoorStatus : Driver
  var value

  def init()
    self.value = "Door status unknown"  # Initial state
    print(f"Door status ?: {self.value}")
  end

  def doorstatuschange(doorstatus)
    print(f"Current door status: {self.value}")
    if (doorstatus == 1)
      self.value = "open"
    else
      self.value = "closed"
    end
    print(f"Door status changed to: {self.value}")
  end

  def web_sensor()
    # print(f"Door status sent to web server: {self.value}")
    webserver.content_send(format("{s}Door is:{m}%s{e}", self.value))  # Sends the door status to the web GUI
  end
end

# Instantiate the sensor and remove the old instance
global.door_sensor_instance = DoorStatus()
tasmota.remove_driver(global.door_sensor_instance)

# Add the new driver instance
tasmota.add_driver(global.door_sensor_instance)

# Use a Tasmota rule to monitor door status changes
tasmota.add_rule(['DoorOpen','Name=LDS02a'],
  def (values, trigger, data)
    var doorstatus = values[0] # Matching the trigger
    var alarm = data['Alarm'] # Another field from the payload
    global.door_sensor_instance.doorstatuschange(doorstatus)  # Sets the door status
  end)

[sfromis]

One observation... This way you are not removing the old instance, as you are first overwriting the old value with the new instance.

# Instantiate the sensor and remove the old instance
global.door_sensor_instance = DoorStatus()
tasmota.remove_driver(global.door_sensor_instance)

As a more robust programming structure, I prefer to have it all in the driver class as a more "self-contained" unit, but I'm not saying that this is "super-important"....

[EddyDsSmartHome]

if I understand correctly, I just have to swap the two with each other, right?

# Instantiate the sensor and remove the old instance
tasmota.remove_driver(global.door_sensor_instance)
global.door_sensor_instance = DoorStatus()