matthias-bs / bresserweathersensorlw Goto Github PK

CMD_SET_OW_CFG num_ow_sensors[7:0]

<num_ow_sensors>: actual number of sensors

https://github.com/bengtmartensson/KeywordsTxtGenerator

Currently, the available sensor data decoders are defined at compile time. It could be useful to implement enabling/disabling of decoders at run time via downlink command.
Disabling of unused decoders improves run time/energy consumption.

See https://resources.lora-alliance.org/technical-specifications/ts013-1-0-0-payload-codec-api

[X] Check existing scripts for standard compliance
[X] Create metadata.json file
[X] Create examples
[ ] Create npm package

For some unknown reason the 1-Wire sensor code did not make it into the project yet...

Currently the LoRaWAN credentials are defined at compile time. This means, a separate binary image has to be created for each deployed device.
The credentials could be provided as a file stored in the Flash file system which could be read by the SW at startup.

See https://github.com/earlephilhower/arduino-littlefs-upload

HI,
I think this isn't the best way but I think I've made a mess.
I'll pass you the material here.

Davide
document.zip

Currently, the number of sensors is defined at compile time.

• If the number is too small, some sensors could be missed even if the receive timeout is sufficient, a decoder is available and reserved space for it in the uplink payload.
• If the number is larger than required, the SW will always wait until all sensors are received or a timeout occurs. This results in unnecessary run time/energy consumption.

See https://github.com/matthias-bs/BresserWeatherSensorLW?tab=readme-ov-file#customizing-the-application-layer for a first step.

To find your sensors (or other sensors within range) you currently have to run BresserWeatherSensorBasic or BresserWeatherSensorLW with debugging enabled and USB connection to serial console for analysis .

This feature will allow to get the same information via LoRaWAN.

CMD_SENSORS_SCAN <scan_time>

Resonse:

<id0>, <type0>, <ch0>[, <flags0>], <rssi0>
...
<idN>, <typeN>, <chN>[, <flagsN>], <rssiN>

To change the sensor configuration and the uplink payload, BresserWeatherSensorLWCfg.h has to be modified. Afterwards, scripts/uplink_formatter.js has to be modified.
A spreadsheet could be used to select the types and numbers of sensors and generate the required code sections.

• longSleep (1 bit)
  

  BresserWeatherSensorLW/BresserWeatherSensorLW.ino

  Line 755 in 54a13e1

  encoder.writeBitmap(0,

  
  Send as response to CMD_GET_LW_CONFIG

• Sensor valid flags (1 bit per sensor)
  

  BresserWeatherSensorLW/src/AppLayer.cpp

  Line 462 in 54a13e1

  encoder.writeBitmap(0,

  
  Encode in signals — all bytes 0xFF means 'invalid'
  Check if this works with all datatypes/value ranges

• Sensor battery status flags (1 bit per sensor)
  

  BresserWeatherSensorLW/src/AppLayer.cpp

  Line 462 in 54a13e1

  encoder.writeBitmap(0,

  
  Add new command CMD_GET_SENSORS_STAT
  Send as response to CMD_GET_SENSORS_STAT

@evon800c You kindly offered your help in testing - much appreciated!

It would be great if you could test if the current main branch works. Heltec WiFi LoRa 32 V3 is implemented, even if the README.md doesn't show it.

Currently, the BLE scan time is defined at compile time.

• If the scan time is too short, sensors will be missed.
• If the scan time is longer than needed, run time/energy consumption is higher than necessary

This can be implemented in the same way as ws_timeout.