Posts made by jkandasa

@Greg-Bowers

MyController version 2.0.0.Final

There is no version in MyController 2.0.0.Final I think it should be 1.6.x or 2.0.0-devel?

@Greg-Bowers can you elaborate the issue you are facing with MyController? also please provide the MyController version details

@hek I see that MySensors logo is missing in the forum

Thanks @JeeLet @skywatch upgrade leads some issue, I believe I fixed it. I hope MyController forum looks ok now.

we can go back to the original topic

Thanks @hek !

Hello, MySensors forum search feature is not working? I tried with Incognito window too, but nothing changed.

CC @hek @mfalkvidd

@JeeLet can you share your MySensors sketch?

@alphaHotel https://forum.mysensors.org/topic/3453/mysbootloader-1-3-pre-release-myscontroller-1-0-0beta/186

@JeeLet the value, you have to set.
V_STATUS is not available in MyController, since it is not reported yet.
adding in setup sends the data only once. If you would like to retain the old status from MyController in your node, remove the send(msg.set(value==HIGH ? 1 : 0)); from your setup and create V_STATUS manually in MyController

• add new field in Resources >> Fields >> Add,
  

@JeeLet can you add send(msg.set(value==HIGH ? 1 : 0)); // Relay in your setup(){} function?

• message.getType - returns the type of the message. you can see different types in https://www.mysensors.org/download/serial_api_20 under set, req
• message.getBool - returns the boolean value of your payload. MySensors sends and receives all the payload in string format. in the arduino sketch with this different type of get functions you can get exact payload without additional steps. more details on https://www.mysensors.org/apidocs/classMyMessage.html

@qobouky You are correct, the Binary type sensors should be visible here.
I just revisited your sketch and I found a conflict on the allocated sensors id

#define CHILD_ID_HUM 0
#define CHILD_ID_TEMP 1
#define CHILD_ID_CO2 2

#define NUMBER_OF_RELAYS 3 // Total number of attached relays
void presentation()  {
present(CHILD_ID_HUM, S_HUM);
present(CHILD_ID_TEMP, S_TEMP);
present(CHILD_ID_CO2, S_AIR_QUALITY);

 for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) {
    // Register all sensors to gw (they will be created as child devices)
    present(sensor, S_BINARY);
  }
}

your relay sensor id should start from 3 or above.
I do not see the use of pin=RELAY_PIN.
You can present the status of your relay's, that can create V_STATUS on MyController

example:

#define RELAY_SENSOR 3 // Relay sensor starts at 3

void presentation()  {
....
MyMessage relayMsg(RELAY_SENSOR, V_STATUS);
for (int sensor=RELAY_SENSOR; sensor < (RELAY_SENSOR + NUMBER_OF_RELAYS); sensor++) {
    // Register all sensors to gw (they will be created as child devices)
    present(sensor, S_BINARY);
    relayMsg.sensor = sensor;
    send(relayMsg.set(loadState(sensor))); // current status of the relay
  }
}

NOTE: You have to update your relay code on setup and in receive too

@RagoTube looks like we need a gateway in a sensor network and with the help of gateway node-node communication can happen. The beauty of MySensors gateway is, you can use your gateway as a node.
I just updated my example shown here. Now the display node is a gateway node.

@RagoTube
Note: I didn't test this code. I believe it should work.

Sender node

#define MY_DEBUG
#define MY_RADIO_RF24
#define MY_NODE_ID 21

#define DISPLAY_NODE_ID 0

#define TEMPERATURE_SENSOR_ID 0

#include "MySensors.h"

// triggering interval
static const uint32_t trigger_ms = 10000; // 10 seconds

uint32_t lastTrigger = 0;
MyMessage msgGeneral(TEMPERATURE_SENSOR_ID, V_TEMP);

void setup() {
}

void presentation() {
  sendSketchInfo("Temperature node 1", "1.0");
  present(TEMPERATURE_SENSOR_ID, S_TEMP, "Temperature");
}

void loop() {
  if (millis() - lastTrigger > trigger_ms) {
    lastTrigger = millis();
    // set destination address
    msgGeneral.setDestination(DISPLAY_NODE_ID);
    
    // get temperature from your temperature sensor
    float lastTemperature = 0.0; // update from your sensor

    // send message to display node
    send(msgGeneral.set(lastTemperature));
  }
}

Display node (Gateway node)

#define MY_DEBUG
#define MY_RADIO_RF24
#define MY_GATEWAY_SERIAL

#define TEMPERATURE_SENSOR_ID 0
#define TEMPERATURE_NODE_ID 21

#include "MySensors.h"

float lastTemperature = 0.0;

void presentation() {
  sendSketchInfo("Display node / Gateway", "1.0");
}

void setup() {
}

void loop() {
}

void updateDisplay() {
  // update your display with "lastTemperature"
}

void receive(const MyMessage &message) {
  if (message.sender == TEMPERATURE_NODE_ID) { // message from temperature node
    if (message.sensor == TEMPERATURE_SENSOR_ID && message.type == V_TEMP) { // message from temperature sensor
      lastTemperature = message.getFloat();
      updateDisplay(); // update display
    }
  }
}

@RagoTube examples are there in,

• https://github.com/mysensors/MySensors/tree/development/examples
• https://github.com/mysensors/MySensorsArduinoExamples

The following sketch can help you to get your setup,
https://github.com/mysensors/MySensors/blob/development/examples/Node2Node/Node2Node.ino

@qobouky to get V_STATUS, you can do it two ways

1. (added automatically in MyController) Send the current status of the relays on your presentation block in your MySensors sketch
2. (add manually in MyController) - you can see S_BINARY sensors in MyController on this node. You can add a V_STATUS variable on each S_BINARY sensor in MyController

You will get a control option for your relays.

@qobouky seems you have problem with MyController and serial port communication. I do not see the node 0 too (gateway node).
can you check the MyController log file, is there any error? Also check the baud rate and port number of your serial device.

@qobouky your attachments are not available. can you please add it again?
do not you get your node by running discover on MyController?

@Yveaux said in serial, Ethernet to MQTT:

Of course, but MySensors MQTT gateway runs just as fine when connected over cabled ethernet, as when connected over wifi

I do not know that
Now on this tool, I do not see much benefit from ethernet to MQTT
Still, it is good from serial to MQTT.

@Yveaux Some people keep wants to use serial or ethernet for security reason. They do not want to use WiFi.
But still, they can enjoy the benefits of MQTT

• experiment different controllers via MQTT
• can have the serial gateways on the different places and connected to a controller (everything connected via MQTT)

Hi,

I have developed a new MQTT bridge to convert from serial, ethernet to mqtt.
Supports for MySensors.
You can have more than one serial ports and/or ethernet connections.
If you are interested in, https://github.com/mycontroller-org/2mqtt
Thanks!

@fixjunk this configuration will be supplied to your gateway from a controller.

Source: https://www.mysensors.org/download/serial_api_20
When your MySesnors node boots up, sends a I_CONFIG request to your controller, your controller has to respond to this request [response can be either (M)etric or (I)mperal ]

AFAIK, This metric change will not affect your sensor measurement units. You have to convert yourself in your sketch.
@mfalkvidd can confirm this.

The container image will be super easy to distribute.
It contains all its dependencies in it. "no more not working in my environment philosophy".
it is super lightweight compared to VM.

I would like to point that MyController.org has a docker image.
Version 1.x is managed by a community member: (available for x86_64 Linux arch): https://hub.docker.com/r/cdrocker/mycontroller

Version 2.0 is in the development phase and natively supports the container.
Supports for Linux x86_64, arm6, arm7, and arm64

# version 2.0
# run with default configuration
docker run  -d --name mycontroller \
    -p 8080:8080 \
    quay.io/mycontroller-org/all-in-one:master

Note: V2.0 is in the development stage, which means not ready for production. If you need metrics support install external influxdb(2.x).

@Puneit-Thukral Thanks for your suggestions

In future will it be possible port this to mobile apps for iOS and Android?

Mobile app is a long pending work for MyContorller. Yes, in future we have to develop.

One integration I would request is for HomeKit.

Sure, I add it in the note. Thanks!

Hello,
MyController 2.0 is in the development stage. I hope we can do a pre-release soon.
I do not want to limit MyController usage not only to the sensors world. can be used for another use case too.

Example:

• monitor stock market and act based on that
• monitor GitHub issues, JIRA issues act based on that
• Monitor an application on a computer
• We have many use cases...

The names should be generic and can be adaptable for all use cases.
So we need a better common name for the sensor and variable.

Current approach (In Version 1.x): Gateway >> Node >> Sensor >> Variable

Sensor:

• The sensor will be renamed as element
• I need better naming here if this is not looking good

Variable:

• We cannot use the name variable, it is more confusing.
• The Variable will be renamed as field (inputs are welcome)

Please respond back with your suggestions

between, Current work of MyController 2.0 deployed at https://demo-v2.mycontroller.org (Username:admin Password: admin)

@Alexandr-Kazakov Try with this start.sh file
https://github.com/mycontroller-org/mycontroller-v1-legacy/blob/0f473bafb729baf5551829daa5f838eec9df4384/dist/src/main/package/bin/start.sh

@chrispy @mfalkvidd sorry for the inconvenience. I didn't notice it. I have enabled search option for guests.

@Velo17 List of providers supported by MyController is https://github.com/mycontroller-org/mycontroller/tree/1.4.0.Final/modules/core/src/main/java/org/mycontroller/standalone/provider

You can extend your own or you can follow one of pre-defined. let me know if you need further assistant.

@andmaster Thank you for your patience!
Do you see any error in mycontroller/logs/mycontroller.log?
Can you trigger mycontroller/bin/start.sh manually?

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

@jgrieco You may try log raw data from the gateway.
https://github.com/mycontroller-org/mycontroller/issues/473

This changes available in SNAPSHOT version

@skywatch @mfalkvidd Thank you for your comments.

I am using Moteino R4 and RFM69 connected to hardware SPI pins. I tried the same pin with softSPI, but I could not get success.

Now I have altered the ADE7763 Arduino library to update SPI settings on every call. And added code to update the only flag on ADE7763 interrupt(like we have in RFM69_new library). Seems all look somewhat ok.

I think for RFM69 we use a default clock speed. for ADE7763: SPI_CLOCK_DIV4

Are you using pull up resistors on the CS lines to each device - that might be worth a try too....

Yes, I have

After some days, internet connection disconnected(identified via SIM800L LED blink status), but still, ESP says all ok. I lost communication from controller too.

193617834 RFM69:SAC:SEND ACK,TO=11,RSSI=-57
193617847 RFM69:CSMA:RSSI=-107
193617866 TSF:MSG:READ,12-11-0,s=255,c=3,t=0,pt=1,l=1,sg=0:48
193617882 GWT:TPS:TOPIC=out_rfm69/12/255/3/0/0,MSG SENT
193629390 RFM69:SAC:SEND ACK,TO=1,RSSI=-82
193629403 RFM69:CSMA:RSSI=-107
193629421 TSF:MSG:READ,1-1-0,s=1,c=1,t=25,pt=1,l=1,sg=0:64
193629437 GWT:TPS:TOPIC=out_rfm69/1/1/1/0/25,MSG SENT
193629735 RFM69:SAC:SEND ACK,TO=1,RSSI=-49
193629747 RFM69:CSMA:RSSI=-106
193629766 TSF:MSG:READ,1-1-0,s=1,c=1,t=35,pt=7,l=5,sg=0:70.60
193629782 GWT:TPS:TOPIC=out_rfm69/1/1/1/0/35,MSG SENT
193650334 RFM69:SAC:SEND ACK,TO=11,RSSI=-98
193650347 RFM69:CSMA:RSSI=-103
193650366 TSF:MSG:READ,11-11-0,s=1,c=1,t=0,pt=7,l=5,sg=0:30.75
193650382 GWT:TPS:TOPIC=out_rfm69/11/1/1/0/0,MSG SENT
193659264 RFM69:SAC:SEND ACK,TO=1,RSSI=-102
193659277 RFM69:CSMA:RSSI=-106
193659296 TSF:MSG:READ,1-1-0,s=1,c=1,t=25,pt=1,l=1,sg=0:64
193659311 GWT:TPS:TOPIC=out_rfm69/1/1/1/0/25,MSG SENT
193659609 RFM69:SAC:SEND ACK,TO=1,RSSI=-92
193659621 RFM69:CSMA:RSSI=-108
193659640 TSF:MSG:READ,1-1-0,s=1,c=1,t=35,pt=7,l=5,sg=0:70.60
193659656 GWT:TPS:TOPIC=out_rfm69/1/1/1/0/35,MSG SENT
193673497 RFM69:SAC:SEND ACK,TO=11,RSSI=-93
193673510 RFM69:CSMA:RSSI=-103
193673529 TSF:MSG:READ,12-11-0,s=1,c=1,t=38,pt=7,l=5,sg=0:12.89
193673546 GWT:TPS:TOPIC=out_rfm69/12/1/1/0/38,MSG SENT
193674042 RFM69:SAC:SEND ACK,TO=11,RSSI=-99
193674054 RFM69:CSMA:RSSI=-103
193674073 TSF:MSG:READ,12-11-0,s=1,c=1,t=0,pt=7,l=5,sg=0:27.00
193674090 GWT:TPS:TOPIC=out_rfm69/12/1/1/0/0,MSG SENT
193674585 RFM69:SAC:SEND ACK,TO=11,RSSI=-99
193674598 RFM69:CSMA:RSSI=-105
193674617 TSF:MSG:READ,12-11-0,s=1,c=1,t=25,pt=1,l=1,sg=0:247
193674633 GWT:TPS:TOPIC=out_rfm69/12/1/1/0/25,MSG SENT
193675129 RFM69:SAC:SEND ACK,TO=11,RSSI=-105
193675142 RFM69:CSMA:RSSI=-108
193675160 TSF:MSG:READ,12-11-0,s=3,c=1,t=38,pt=7,l=5,sg=0:13.65
193675177 GWT:TPS:TOPIC=out_rfm69/12/3/1/0/38,MSG SENT
193675675 RFM69:SAC:SEND ACK,TO=11,RSSI=-99
193675688 RFM69:CSMA:RSSI=-102
193675707 TSF:MSG:READ,12-11-0,s=3,c=1,t=39,pt=7,l=5,sg=0:0.97
193675723 GWT:TPS:TOPIC=out_rfm69/12/3/1/0/39,MSG SENT
193676219 RFM69:SAC:SEND ACK,TO=11,RSSI=-103
193676232 RFM69:CSMA:RSSI=-106
193676251 TSF:MSG:READ,12-11-0,s=0,c=1,t=38,pt=7,l=5,sg=0:4.979
193676268 GWT:TPS:TOPIC=out_rfm69/12/0/1/0/38,MSG SENT
193676755 RFM69:SAC:SEND ACK,TO=11,RSSI=-97

I did a hard reboot of ESP8266, all back to normal.

@thucar Great work! Thank you!
I am using MY_GATEWAY_TINYGSM from a month ago. I face Gateway hangs after a week and it needs a hard reboot(Power OFF and ON). Are you facing any issue similar to this?

My Hardware details:

• ESP8266 (ESP-12E)
• RFM69HW
• SIM800L

To power up GSM modem I am using 1500mA 18650 battery with charger board.

Can you share your hardware details?

My Hardware: Moteino R4, ATMEGA328P + RFM69HW

I have an issue when communicating with an additional SPI device. I have ADE7763 energy monitor SPI chip which operates on low clock speed.

When I read data from ADE7763, I reconfigure SPI settings as follows,

ADE7763 CS pin connected to D9.

void loop() {
  updateVoltageCurrentData();
  .....
  .....
}

void updateVoltageCurrentData() {
  SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE1));
  uint8_t status = ADE_sampleRMS(&vrms, &irms); // reads VRMS and IRMS from ADE7763
  SPI.endTransaction();
}

This settings working ok, but after some time, this particular node lost from RF network. Looks like RFM69 SPI settings corrupted.

Any recommended way to communicate with additional SPI device?

@prakhar-birla I do buy in Aliexpress, you can see some of the links in https://www.mysensors.org/build/connect_radio

@prakhar-birla Yes, I am using in my house. I see a good range between concrete walls.
I was using NRF24L01+ Chinese version and was facing range issue. I used to have Gateway for each floor.
But now only single gateway with RFM69HW.

I have replaced RFM69HW with NRF24L01+ couple of weeks ago. I am just experimenting with coverage with RFM69HW. So far I do not face any issue.

@prakhar-birla Hi I too from India. Recently I have pushed a PR to use India standard for RFM69. You may have a look at https://github.com/mysensors/MySensors/issues/1184

@Koresh Great work! I too facing this issue. At this moment I am handing with wait(200) in my application code.

@mfalkvidd @Yveaux Do we have any plan to implement this changes into MySensors mainline?

I have connected my gateway in GSM/GPRS(2G), It is slow internet, taking some time to transfer the data to the controller.
Big network(internet) latency.

I see some losses, Do we have any option to enable a queue in Gateway node? So node messages will be in the queue and send all the messages to the controller.

@rozpruwacz can you share your implementation details?

Just sharing my experience with MY_RFM69_MODEM_CONFIGURATION

IMPORTANT: We should not use brockets() when defining MY_RFM69_MODEM_CONFIGURATION,

Wrong way: #define MY_RFM69_MODEM_CONFIGURATION (RFM69_FSK_BR55_5_FD50)

Right way: #define MY_RFM69_MODEM_CONFIGURATION RFM69_FSK_BR55_5_FD50

Why? Check this, actually configuration values are defined as an array.

@mfalkvidd

with enough work, anything is possible

That's true Thank you!

@rejoe2

Additionally, you may have a look at this WIP: https://forum.mysensors.org/topic/6911/halo-esp32-multi-transport-gw-bridge-for-mysensors

Thank you Let me have a look.

Hello, I have two hardware networks in my home.

1. RFM69
2. NRF24L01+

Currently, I have two gateways. I would like to keep one gateway.
Is it possible to bridge NRF24L01 and RFM69 in a node or in gateway?

Kindly update MyController.org changes. Updated in this doc

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

@soloam AFAIK, MySBootloader will ask repeatedly if some messages lost from the controller. Enabling ack will lead high latency on a firmware update. I may include an option in the future version of MyController as, disable ack for firmware updates.

@soloam Which version of MyController are you using?
In MyController side, if you are using version 1.2.0 and above, try to disable acknowledgment feature on the gateway page and try again.

For user application and FOTA, radio libraries are different? @tekka Am I right?

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

@sushukka Yes, it's possible to define a port in NGINX.

@gohan

Preliminary test: if ACK enabled on gateway, OTA transfer is terribly slow.

What type of gateway are you using? MQTT? Whatever type. When we enable ack it will double the data rate. If we feel ack not required only for OTA, I can add some option to control ACK on OTA.

I am getting also quite some WRONG FWB on the node (they are 2 meters apart)

Could you please elaborate this issue?

I noticed that when SmartSleep option is enabled in node configuration the OTA process starts pretty much all the time
sending OTA all the time? on all the walkup?

I am still encountering problems when assigning the FW to node: in the beginning it works but after a few tests it stops working and I had to delete node from mycontroller and after that I was able to start OTA again.

I will check this. Can you please explain your set-up?

Thank you for all the tests!

In the gateway details page you can see time taken to process messages,

@sushukka We can define IP based authentication on nginx.
Have a look at these blogs,
https://www.nginx.com/resources/admin-guide/restricting-access-auth-basic/
https://www.booleanworld.com/set-basic-http-authentication-nginx/

MyController supports for sleep nodes and for now, we have to set it manually.
We would like to set it automatically based on node data.

Is there any uniqueness parameter sent by a node to identify it is a sleeping node?

https://github.com/mycontroller-org/mycontroller/issues/435

@gohan Yes, please report your experience on this version

Need volunteers to test 1.2.0-SNAPSHOT version. This version has major changes on the provider side.
Now it supports ack.

Report your issues here

CAUTION: This version might have major bugs, do not use it in your production environment.
Do backup your existing version and move to this version.

Steps to do backup/restore

Changes: https://github.com/mycontroller-org/mycontroller/commit/67b4f148ea36cd37d917d7560ffaed35871d2b6a

Remove following directory, if you do the dirty upgrade:

# rm mycontroller/conf/persistent_stores/mc/* -rf

To enable ack, edit gateway and,

To see gateway Statistics go to gateway details:

@gohan This node looks like sleeping node? Is it. I guess it won't walk up to update the entire firmware.

And I do not see any response for this request 2130 TSF:MSG:SEND,16-16-0-0,s=255,c=4,t=0,pt=6,l=10,sg=0,ft=0,st=OK:020005006004A3EB0300. Is there any firmware assigned for this node in MyController?

@gohan Enable node debug log and trigger firmware update. Post node debug log.

A few weeks before, I see an issue with the DualOptiboot firmware update. For some reason, if firmware update failed in between, and when we trigger firmware update once again, node says It is up to date.

@gohan What the issue are you facing? AFAIK, RFM69 supports only for DualOptiboot

@sushukka You can use NGINX as a reverse proxy on your Raspberry PI and you can enable authentication in NGINX for your controller URL. Do google as nginx reverse proxy with authentication to know more about the setup.

@neverdie If I go with the default RFM95_BW125CR45SF128 settings I see the failure rarely. I ran the setup minimal time only. So do not know about stability.

When I go with RFM95_BW31_25CR48SF512 or RFM95_BW125CR48SF4096, I see failure, when I request a payload from the gateway, because of gateway busy asking data from the controller, meantime node thinks message not received by the gateway and send a message once again, same time gateway sends ack to the node. Air/RF collision happens here, both side message not delivered.

@hek @mfalkvidd RFM95 radio part connection details are missing.

@ricorico94 here is the hardware connection details, that I followed.

Gateway Sketch:

  ESP8266         RFM95
-----------      ---------
(GPIO15) CS    <--> NSS
(GPIO13) MOSI  <--> MOSI
(GPIO12) MISO  <--> MISO
(GPIO14) CLK   <--> SCK
(GPIO 5) IRQ   <--> DIO0
         GND   <--> GND
         3.3V  <--> +3.3V

Add this line on ESP8266 sketch,
#define   MY_RFM95_IRQ_PIN 5
#define   MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
#define   MY_RFM95_CS_PIN 15

Node Sketch:

  PRO-MINI       RFM95
-----------     -------
(10) SS    <--> NSS
(11) MOSI  <--> MOSI
(12) MISO  <--> MISO
(13) CLK   <--> SCK
(2)  IRQ   <--> DIO0
     GND   <--> GND
     3.3V  <--> +3.3V

@zachflem Can you see a node 0? Select your gateway and run Discover

@gohan What type of gateway are you using? MQTT? Serial? What is the Tx message processing delay(Milliseconds) in MyController gateway configuration?

Is Controller and Gateway on the same network?

@gohan Sure, Please report back your results.

@manutremo said in OTA flash types for MySensors:

@Nca78 Thanks for the hint. I actually purchased from this seller who is chaper:

@manutremo I am getting trouble with W25Q32B. Can you help me to get success? I am struggling to get jedec id for this chip.

UPDATE: I included the following lines on the sketch it works,

//Enable OTA feature
#define MY_OTA_FIRMWARE_FEATURE
#define MY_OTA_FLASH_JDECID 0x00

@gohan, Yes, MyController works with Serial, Ethernet, and MQTT as well.

@mfalkvidd You are right! Seems these lines did the magic. Now I see 90% of success. But still, see few failures in starting when sending presentation message. I guess presentation message takes a long time than the normal message. As it is a bigger message. Let me find out the root cause.

Thank you for your support!

Configuration used at this stage,

#define MY_RADIO_RFM95
#define MY_TRANSPORT_STATE_TIMEOUT_MS  (3*1000ul)
#define RFM95_RETRY_TIMEOUT_MS  (3000ul) 
#define MY_RFM95_FREQUENCY  (RFM95_868MHZ)
#define MY_RFM95_MODEM_CONFIGRUATION  RFM95_BW125CR48SF4096

@mfalkvidd Thank you! I tried with #define MY_TRANSPORT_STATE_TIMEOUT_MS (20*1000ul) and #define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR48SF4096, Now it is working 50% pass and 50% failed. I do not know how to make it 100% perfect.

Node log messages:

 
 __  __       ____
|  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
|_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
        |___/                      2.2.0-rc.2

17 MCO:BGN:INIT REPEATER,CP=RLNRA---,VER=2.2.0-rc.2
26 TSM:INIT
28 TSF:WUR:MS=0
29 RFM95:INIT
30 RFM95:INIT:PIN,CS=10,IQP=2,IQN=0
44 RFM95:PTX:LEVEL=13
46 TSM:INIT:TSP OK
48 TSF:SID:OK,ID=1
50 TSM:FPAR
51 RFM95:SWR:SEND,TO=255,SEQ=0,RETRY=0
1565 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
3462 RFM95:SAC:SEND ACK,TO=0,SEQ=2,RSSI=-30,SNR=9
3527 TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
3532 TSF:MSG:FPAR OK,ID=0,D=1
6810 RFM95:SAC:SEND ACK,TO=0,SEQ=2,RSSI=-30,SNR=10
6876 TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
21572 TSM:FPAR:OK
21573 TSM:ID
21575 TSM:ID:OK
21576 TSM:UPL
21577 RFM95:SWR:SEND,TO=0,SEQ=3,RETRY=0
23592 !RFM95:SWR:NACK
23631 RFM95:SWR:SEND,TO=0,SEQ=4,RETRY=1
24195 !RFM95:SWR:NACK
24201 RFM95:SWR:SEND,TO=0,SEQ=4,RETRY=2
24764 !RFM95:SWR:NACK
24830 RFM95:SWR:SEND,TO=0,SEQ=4,RETRY=3
25394 !RFM95:SWR:NACK
25432 RFM95:SWR:SEND,TO=0,SEQ=4,RETRY=4
25995 !RFM95:SWR:NACK
26001 RFM95:SWR:SEND,TO=0,SEQ=4,RETRY=5
28014 !RFM95:SWR:NACK
28112 RFM95:PTX:LEVEL=14
28114 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
29158 RFM95:SAC:SEND ACK,TO=0,SEQ=4,RSSI=-31,SNR=10
29223 TSF:MSG:READ,0-0-1,s=255,c=3,t=25,pt=1,l=1,sg=0:1
29229 TSF:MSG:PONG RECV,HP=1
29232 TSM:UPL:OK
29233 TSM:READY:ID=1,PAR=0,DIS=1
29236 RFM95:SWR:SEND,TO=0,SEQ=5,RETRY=0
32423 !RFM95:SWR:NACK
32457 RFM95:SWR:SEND,TO=0,SEQ=6,RETRY=1
33021 !RFM95:SWR:NACK
33024 RFM95:SWR:SEND,TO=0,SEQ=6,RETRY=2
33587 !RFM95:SWR:NACK
33625 RFM95:SWR:SEND,TO=0,SEQ=6,RETRY=3
35639 !RFM95:SWR:NACK
35705 RFM95:SWR:SEND,TO=0,SEQ=6,RETRY=4
36269 !RFM95:SWR:NACK
36303 RFM95:SWR:SEND,TO=0,SEQ=6,RETRY=5
36867 !RFM95:SWR:NACK
36873 RFM95:PTX:LEVEL=15
36875 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
38870 RFM95:SAC:SEND ACK,TO=0,SEQ=6,RSSI=-30,SNR=9
38935 TSF:MSG:READ,0-0-1,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
38940 RFM95:SWR:SEND,TO=0,SEQ=7,RETRY=0
42658 !RFM95:SWR:NACK
42696 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
45234 !RFM95:SWR:NACK
45272 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
45835 !RFM95:SWR:NACK
45841 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
46404 !RFM95:SWR:NACK
46470 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
49007 !RFM95:SWR:NACK
49105 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
49669 !RFM95:SWR:NACK
49671 RFM95:PTX:LEVEL=16
49673 !TSF:MSG:SEND,1-1-0-0,s=255,c=0,t=18,pt=0,l=10,sg=0,ft=1,st=NACK:2.2.0-rc.2
49680 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
50244 !RFM95:SWR:NACK
50310 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
52323 !RFM95:SWR:NACK
52425 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
52989 !RFM95:SWR:NACK
52992 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
53555 !RFM95:SWR:NACK
53593 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
54156 !RFM95:SWR:NACK
54158 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
54721 !RFM95:SWR:NACK
54791 RFM95:PTX:LEVEL=17
54793 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=2,st=NACK:0
56799 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
57362 !RFM95:SWR:NACK
57368 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
60168 !RFM95:SWR:NACK
60174 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
62974 !RFM95:SWR:NACK
62977 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
63540 !RFM95:SWR:NACK
63606 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
64171 !RFM95:SWR:NACK
64209 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
67009 !RFM95:SWR:NACK
67079 RFM95:PTX:LEVEL=18
67081 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=11,pt=0,l=14,sg=0,ft=3,st=NACK:Signal Monitor
67089 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
67652 !RFM95:SWR:NACK
67718 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
68281 !RFM95:SWR:NACK
68352 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
70627 !RFM95:SWR:NACK
70729 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
71293 !RFM95:SWR:NACK
71296 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
71859 !RFM95:SWR:NACK
71897 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
74172 !RFM95:SWR:NACK
74238 RFM95:PTX:LEVEL=19
74241 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=12,pt=0,l=3,sg=0,ft=4,st=NACK:1.0
74247 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
74811 !RFM95:SWR:NACK
74881 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
75444 !RFM95:SWR:NACK
75510 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
77524 !RFM95:SWR:NACK
77623 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
78186 !RFM95:SWR:NACK
78288 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
78852 !RFM95:SWR:NACK
78854 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
80868 !RFM95:SWR:NACK
80966 RFM95:PTX:LEVEL=20
80968 !TSF:MSG:SEND,1-1-0-0,s=1,c=0,t=3,pt=0,l=0,sg=0,ft=5,st=NACK:
80974 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
81539 !RFM95:SWR:NACK
81545 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
82108 !RFM95:SWR:NACK
82174 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
84188 !RFM95:SWR:NACK
84286 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
84849 !RFM95:SWR:NACK
84951 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
85514 !RFM95:SWR:NACK
85520 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
86083 !RFM95:SWR:NACK
86153 !TSF:MSG:SEND,1-1-0-0,s=1,c=2,t=2,pt=0,l=0,sg=0,ft=6,st=NACK:
86159 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
86723 !RFM95:SWR:NACK
86793 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
89068 !RFM95:SWR:NACK
89166 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
89730 !RFM95:SWR:NACK
89736 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
90299 !RFM95:SWR:NACK
90369 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
92644 !RFM95:SWR:NACK
92742 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
95019 !RFM95:SWR:NACK
95057 !TSF:MSG:SEND,1-1-0-0,s=7,c=0,t=33,pt=0,l=6,sg=0,ft=7,st=NACK:Tx-dBm
95064 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
95628 !RFM95:SWR:NACK
95630 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
96193 !RFM95:SWR:NACK
96263 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
98538 !RFM95:SWR:NACK
98640 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
99204 !RFM95:SWR:NACK
99206 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
99769 !RFM95:SWR:NACK
99840 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
102115 !RFM95:SWR:NACK
102217 !TSF:MSG:SEND,1-1-0-0,s=8,c=0,t=33,pt=0,l=6,sg=0,ft=8,st=NACK:Rx-dBm
102223 MCO:REG:REQ
102225 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
102790 !RFM95:SWR:NACK
102792 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
103356 !RFM95:SWR:NACK
103422 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
105437 !RFM95:SWR:NACK
105535 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
106100 !RFM95:SWR:NACK
106102 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
106667 !RFM95:SWR:NACK
106705 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
107270 !RFM95:SWR:NACK
107272 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=9,st=NACK:2
109278 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=0
109842 !RFM95:SWR:NACK
109848 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=1
111863 !RFM95:SWR:NACK
111865 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=2
112430 !RFM95:SWR:NACK
112464 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=3
113029 !RFM95:SWR:NACK
113031 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=4
113595 !RFM95:SWR:NACK
113665 RFM95:SWR:SEND,TO=0,SEQ=8,RETRY=5
115679 !RFM95:SWR:NACK
115777 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=26,pt=1,l=1,sg=0,ft=10,st=NACK:2
115783 !TSM:READY:UPL FAIL,SNP
115786 TSM:FPAR
115788 RFM95:SWR:SEND,TO=255,SEQ=8,RETRY=0
115853 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=11,st=OK:
117783 !TSF:SND:TNR
117999 RFM95:SAC:SEND ACK,TO=0,SEQ=25,RSSI=-35,SNR=10
118065 TSF:MSG:READ,0-0-1,s=255,c=3,t=27,pt=1,l=1,sg=0:1
118070 MCO:PIM:NODE REG=1
121344 RFM95:SAC:SEND ACK,TO=0,SEQ=25,RSSI=-37,SNR=9
121409 TSF:MSG:READ,0-0-1,s=255,c=3,t=27,pt=1,l=1,sg=0:1
121414 MCO:PIM:NODE REG=1
138073 !TSM:FPAR:NO REPLY
138075 TSM:FPAR
138077 RFM95:SWR:SEND,TO=255,SEQ=10,RETRY=0
139591 TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
141298 RFM95:SAC:SEND ACK,TO=0,SEQ=26,RSSI=-39,SNR=10
141364 TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
141369 TSF:MSG:FPAR OK,ID=0,D=1
144643 RFM95:SAC:SEND ACK,TO=0,SEQ=26,RSSI=-39,SNR=12
144709 TSF:MSG:READ,0-0-1,s=255,c=3,t=8,pt=1,l=1,sg=0:0
159598 TSM:FPAR:OK
159599 TSM:ID
159601 TSM:ID:OK
159602 TSM:UPL
159604 RFM95:SWR:SEND,TO=0,SEQ=13,RETRY=0
161619 !RFM95:SWR:NACK
161690 RFM95:SWR:SEND,TO=0,SEQ=14,RETRY=1
162255 !RFM95:SWR:NACK
162321 RFM95:SWR:SEND,TO=0,SEQ=14,RETRY=2
162885 !RFM95:SWR:NACK
162951 RFM95:SWR:SEND,TO=0,SEQ=14,RETRY=3
163515 !RFM95:SWR:NACK
163585 RFM95:SWR:SEND,TO=0,SEQ=14,RETRY=4
164149 !RFM95:SWR:NACK
164215 RFM95:SWR:SEND,TO=0,SEQ=14,RETRY=5
166230 !RFM95:SWR:NACK
166328 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
167288 RFM95:SAC:SEND ACK,TO=0,SEQ=28,RSSI=-35,SNR=9
167354 TSF:MSG:READ,0-0-1,s=255,c=3,t=25,pt=1,l=1,sg=0:1
167359 TSF:MSG:PONG RECV,HP=1
167362 TSM:UPL:OK
167364 TSM:READY:ID=1,PAR=0,DIS=1
167367 MCO:BGN:STP
167369 MCO:BGN:INIT OK,TSP=1
182369 RFM95:SWR:SEND,TO=0,SEQ=15,RETRY=0
184383 !RFM95:SWR:NACK
184449 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=1
185013 !RFM95:SWR:NACK
185079 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=2
185644 !RFM95:SWR:NACK
185678 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=3
187693 !RFM95:SWR:NACK
187727 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=4
188292 !RFM95:SWR:NACK
188294 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=5
188858 !RFM95:SWR:NACK
188928 !TSF:MSG:SEND,1-1-0-0,s=7,c=1,t=37,pt=2,l=2,sg=0,ft=0,st=NACK:-256
189934 RFM95:SWR:SEND,TO=0,SEQ=16,RETRY=0
191949 !RFM95:SWR:NACK
192015 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=1
192579 !RFM95:SWR:NACK
192649 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=2
193213 !RFM95:SWR:NACK
193280 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=3
195294 !RFM95:SWR:NACK
195392 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=4
195957 !RFM95:SWR:NACK
195959 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=5
196524 !RFM95:SWR:NACK
196558 !TSF:MSG:SEND,1-1-0-0,s=8,c=1,t=37,pt=2,l=2,sg=0,ft=1,st=NACK:-35
197564 RFM95:SWR:SEND,TO=0,SEQ=17,RETRY=0
199578 !RFM95:SWR:NACK
199616 RFM95:SWR:SEND,TO=0,SEQ=18,RETRY=1
200181 !RFM95:SWR:NACK
200183 RFM95:SWR:SEND,TO=0,SEQ=18,RETRY=2
200748 !RFM95:SWR:NACK
200782 RFM95:SWR:SEND,TO=0,SEQ=18,RETRY=3

Gateway Log messages:

75051 TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
75056 TSF:MSG:BC
75058 TSF:MSG:FPAR REQ,ID=1
75060 TSF:PNG:SEND,TO=0
75062 TSF:CKU:OK
75064 TSF:MSG:GWL OK
75379 RFM95:SWR:SEND,TO=1,SEQ=1,RETRY=0
77393 !RFM95:SWR:NACK
77462 RFM95:SWR:SEND,TO=1,SEQ=2,RETRY=1
78026 !RFM95:SWR:NACK
78095 RFM95:SWR:SEND,TO=1,SEQ=2,RETRY=2
78659 !RFM95:SWR:NACK
78728 RFM95:SWR:SEND,TO=1,SEQ=2,RETRY=3
80742 !RFM95:SWR:NACK
80839 RFM95:SWR:SEND,TO=1,SEQ=2,RETRY=4
81403 !RFM95:SWR:NACK
81408 RFM95:SWR:SEND,TO=1,SEQ=2,RETRY=5
81972 !RFM95:SWR:NACK
82037 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
96582 RFM95:SAC:SEND ACK,TO=1,SEQ=4,RSSI=-29,SNR=9
96648 TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
96653 TSF:MSG:PINGED,ID=1,HP=1
96660 RFM95:SWR:SEND,TO=1,SEQ=3,RETRY=0
99847 !RFM95:SWR:NACK
99848 RFM95:SWR:SEND,TO=1,SEQ=4,RETRY=1
100413 !RFM95:SWR:NACK
100478 RFM95:SWR:SEND,TO=1,SEQ=4,RETRY=2
101042 !RFM95:SWR:NACK
101079 RFM95:SWR:SEND,TO=1,SEQ=4,RETRY=3
103093 !RFM95:SWR:NACK
103158 RFM95:SWR:SEND,TO=1,SEQ=4,RETRY=4
103722 !RFM95:SWR:NACK
103759 RFM95:SWR:SEND,TO=1,SEQ=4,RETRY=5
104323 !RFM95:SWR:NACK
104328 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
105414 RFM95:SAC:SEND ACK,TO=1,SEQ=6,RSSI=-28,SNR=9
105479 TSF:MSG:READ,1-1-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
105485 RFM95:SWR:SEND,TO=1,SEQ=5,RETRY=0
108679 !RFM95:SWR:NACK
108680 RFM95:SWR:SEND,TO=1,SEQ=6,RETRY=1
110695 !RFM95:SWR:NACK
110792 RFM95:SWR:SEND,TO=1,SEQ=6,RETRY=2
112806 !RFM95:SWR:NACK
112839 RFM95:SWR:SEND,TO=1,SEQ=6,RETRY=3
113403 !RFM95:SWR:NACK
113408 RFM95:SWR:SEND,TO=1,SEQ=6,RETRY=4
113972 !RFM95:SWR:NACK
114037 RFM95:SWR:SEND,TO=1,SEQ=6,RETRY=5
114601 !RFM95:SWR:NACK
114638 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
118228 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-27,SNR=10
118293 TSF:MSG:READ,1-1-0,s=255,c=0,t=18,pt=0,l=10,sg=0:2.2.0-rc.2
118299 Sending message on topic: out_rfm95/1/255/0/0/18
122002 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-27,SNR=11
122067 TSF:MSG:READ,1-1-0,s=255,c=0,t=18,pt=0,l=10,sg=0:2.2.0-rc.2
122073 Sending message on topic: out_rfm95/1/255/0/0/18
125318 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-28,SNR=10
125384 TSF:MSG:READ,1-1-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
125389 Sending message on topic: out_rfm95/1/255/3/0/6
125884 Message arrived on topic: in_rfm95/1/255/3/0/6
125889 RFM95:SWR:SEND,TO=1,SEQ=9,RETRY=0
128845 !RFM95:SWR:NACK
128910 RFM95:SWR:SEND,TO=1,SEQ=10,RETRY=1
131187 !RFM95:SWR:NACK
131288 RFM95:SWR:SEND,TO=1,SEQ=10,RETRY=2
131852 !RFM95:SWR:NACK
131853 RFM95:SWR:SEND,TO=1,SEQ=10,RETRY=3
132418 !RFM95:SWR:NACK
132487 RFM95:SWR:SEND,TO=1,SEQ=10,RETRY=4
133051 !RFM95:SWR:NACK
133120 RFM95:SWR:SEND,TO=1,SEQ=10,RETRY=5
133684 !RFM95:SWR:NACK
133749 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=6,pt=0,l=6,sg=0,ft=0,st=NACK:Metric
135970 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-26,SNR=11
136036 TSF:MSG:READ,1-1-0,s=255,c=3,t=11,pt=0,l=14,sg=0:Signal Monitor
136042 Sending message on topic: out_rfm95/1/255/3/0/11
140007 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-26,SNR=12
140072 TSF:MSG:READ,1-1-0,s=255,c=3,t=11,pt=0,l=14,sg=0:Signal Monitor
140078 Sending message on topic: out_rfm95/1/255/3/0/11
143625 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-25,SNR=11
143690 TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
143696 Sending message on topic: out_rfm95/1/255/3/0/12
147170 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-25,SNR=11
147236 TSF:MSG:READ,1-1-0,s=255,c=3,t=12,pt=0,l=3,sg=0:1.0
147241 Sending message on topic: out_rfm95/1/255/3/0/12
150523 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-26,SNR=9
150588 TSF:MSG:READ,1-1-0,s=1,c=0,t=3,pt=0,l=0,sg=0:
150593 Sending message on topic: out_rfm95/1/1/0/0/3
153867 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-26,SNR=9
153932 TSF:MSG:READ,1-1-0,s=1,c=0,t=3,pt=0,l=0,sg=0:
153937 Sending message on topic: out_rfm95/1/1/0/0/3
157188 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-25,SNR=10
157254 TSF:MSG:READ,1-1-0,s=1,c=2,t=2,pt=0,l=0,sg=0:
157258 Sending message on topic: out_rfm95/1/1/2/0/2
157627 Message arrived on topic: in_rfm95/1/1/1/0/2
157632 RFM95:SWR:SEND,TO=1,SEQ=17,RETRY=0
160453 !RFM95:SWR:NACK
160518 RFM95:SWR:SEND,TO=1,SEQ=18,RETRY=1
161082 !RFM95:SWR:NACK
161151 RFM95:SWR:SEND,TO=1,SEQ=18,RETRY=2
161715 !RFM95:SWR:NACK
161752 RFM95:SWR:SEND,TO=1,SEQ=18,RETRY=3
162316 !RFM95:SWR:NACK
162317 RFM95:SWR:SEND,TO=1,SEQ=18,RETRY=4
164333 !RFM95:SWR:NACK
164430 RFM95:SWR:SEND,TO=1,SEQ=18,RETRY=5
164994 !RFM95:SWR:NACK
164999 !TSF:MSG:SEND,0-0-1-1,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
168020 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-25,SNR=9
168085 TSF:MSG:READ,1-1-0,s=7,c=0,t=33,pt=0,l=6,sg=0:Tx-dBm
168090 Sending message on topic: out_rfm95/1/7/0/0/33
171541 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-25,SNR=10
171606 TSF:MSG:READ,1-1-0,s=8,c=0,t=33,pt=0,l=6,sg=0:Rx-dBm
171612 Sending message on topic: out_rfm95/1/8/0/0/33
175118 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-30,SNR=11
175184 TSF:MSG:READ,1-1-0,s=8,c=0,t=33,pt=0,l=6,sg=0:Rx-dBm
175189 Sending message on topic: out_rfm95/1/8/0/0/33
178439 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-34,SNR=9
178505 TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
178515 RFM95:SWR:SEND,TO=1,SEQ=22,RETRY=0
181704 !RFM95:SWR:NACK
181773 RFM95:SWR:SEND,TO=1,SEQ=23,RETRY=1
183787 !RFM95:SWR:NACK
183888 RFM95:SWR:SEND,TO=1,SEQ=23,RETRY=2
184452 !RFM95:SWR:NACK
184453 RFM95:SWR:SEND,TO=1,SEQ=23,RETRY=3
185018 !RFM95:SWR:NACK
185087 RFM95:SWR:SEND,TO=1,SEQ=23,RETRY=4
187101 !RFM95:SWR:NACK
187198 RFM95:SWR:SEND,TO=1,SEQ=23,RETRY=5
187762 !RFM95:SWR:NACK
187863 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=NACK:1
188683 RFM95:SAC:SEND ACK,TO=1,SEQ=8,RSSI=-29,SNR=9
188749 TSF:MSG:READ,1-1-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
188759 RFM95:SWR:SEND,TO=1,SEQ=24,RETRY=0
191948 !RFM95:SWR:NACK
192013 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=1
192577 !RFM95:SWR:NACK
192646 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=2
193210 !RFM95:SWR:NACK
193279 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=3
195293 !RFM95:SWR:NACK
195390 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=4
195954 !RFM95:SWR:NACK
196055 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=5
196619 !RFM95:SWR:NACK
196624 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=NACK:1
213099 TSF:MSG:READ,1-1-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
213104 TSF:MSG:BC
213106 TSF:MSG:FPAR REQ,ID=1
213108 TSF:PNG:SEND,TO=0
213111 TSF:CKU:OK
213112 TSF:MSG:GWL OK
213236 RFM95:SWR:SEND,TO=1,SEQ=25,RETRY=0
215251 !RFM95:SWR:NACK
215320 RFM95:SWR:SEND,TO=1,SEQ=26,RETRY=1
215884 !RFM95:SWR:NACK
215949 RFM95:SWR:SEND,TO=1,SEQ=26,RETRY=2
216513 !RFM95:SWR:NACK
216582 RFM95:SWR:SEND,TO=1,SEQ=26,RETRY=3
218597 !RFM95:SWR:NACK
218694 RFM95:SWR:SEND,TO=1,SEQ=26,RETRY=4
219258 !RFM95:SWR:NACK
219263 RFM95:SWR:SEND,TO=1,SEQ=26,RETRY=5
219827 !RFM95:SWR:NACK
219864 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=NACK:0
234631 RFM95:SAC:SEND ACK,TO=1,SEQ=14,RSSI=-28,SNR=10
234696 TSF:MSG:READ,1-1-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
234701 TSF:MSG:PINGED,ID=1,HP=1
234709 RFM95:SWR:SEND,TO=1,SEQ=27,RETRY=0
237896 !RFM95:SWR:NACK
237965 RFM95:SWR:SEND,TO=1,SEQ=28,RETRY=1
238529 !RFM95:SWR:NACK
238598 RFM95:SWR:SEND,TO=1,SEQ=28,RETRY=2
239162 !RFM95:SWR:NACK
239231 RFM95:SWR:SEND,TO=1,SEQ=28,RETRY=3
241245 !RFM95:SWR:NACK
241342 RFM95:SWR:SEND,TO=1,SEQ=28,RETRY=4
241906 !RFM95:SWR:NACK
242007 RFM95:SWR:SEND,TO=1,SEQ=28,RETRY=5
242571 !RFM95:SWR:NACK
242576 !TSF:MSG:SEND,0-0-1-1,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
257398 RFM95:SAC:SEND ACK,TO=1,SEQ=16,RSSI=-29,SNR=10
257464 TSF:MSG:READ,1-1-0,s=7,c=1,t=37,pt=2,l=2,sg=0:-256
257469 Sending message on topic: out_rfm95/1/7/1/0/37
260708 RFM95:SAC:SEND ACK,TO=1,SEQ=16,RSSI=-31,SNR=11
260774 TSF:MSG:READ,1-1-0,s=7,c=1,t=37,pt=2,l=2,sg=0:-256
260779 Sending message on topic: out_rfm95/1/7/1/0/37
264965 RFM95:SAC:SEND ACK,TO=1,SEQ=17,RSSI=-33,SNR=10
265031 TSF:MSG:READ,1-1-0,s=8,c=1,t=37,pt=2,l=2,sg=0:-35
265036 Sending message on topic: out_rfm95/1/8/1/0/37

@neverdie I do not have any specific project at this moment. Just checking the performance and range of LoRa (RFM95) with MySensors library.

Gateway(ESP8266 + RFM95):

// Application details
#define APPLICATION_NAME    "Gateway RFM95"
#define APPLICATION_VERSION "1.0.0.Beta"

// Enable debug prints to serial monitor
#define MY_DEBUG

// Use a bit lower baudrate for serial prints on ESP8266 than default in MyConfig.h
#define MY_BAUD_RATE 115200

// Enable and select radio type attached
#define   MY_RADIO_RFM95

#define   MY_DEBUG_VERBOSE_RFM95
//#define   MY_DEBUG_VERBOSE_RFM95_REGISTERS
//#define MY_RFM95_ATC_TARGET_RSSI (-70)  // target RSSI -70dBm
//#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_868MHZ)
//#define   MY_RFM95_MODEM_CONFIGRUATION (RFM95_BW500CR45SF128)
#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128

#define   MY_RFM95_IRQ_PIN 5
#define   MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
#define   MY_RFM95_CS_PIN 15

#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP8266

// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "out_rfm95"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "in_rfm95"

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "mys_rfm95_1"

// Enable these if your MQTT broker requires usenrame/password
#define MY_MQTT_USER "mqtt"
#define MY_MQTT_PASSWORD "mqtt"

// Set WIFI SSID and password
#define MY_ESP8266_SSID "jee"
#define MY_ESP8266_PASSWORD "password12345678"

// MQTT broker ip address.
#define MY_CONTROLLER_IP_ADDRESS 192.168.1.209

// The MQTT broker port to to open
#define MY_PORT 1883

#include <ESP8266WiFi.h>
#include <MySensors.h>
#include <SimpleTimer.h>
#include <ArduinoOTA.h>


SimpleTimer timer; // Create a Timer object called "timer"! 

#define OTA_PASSWORD "mycontrollerrfm95"

#define SEN_INTERNAL 10
  

void setup() {
  ArduinoOTA.onStart([]() {
    Serial.println("ArduinoOTA start");
  });
  ArduinoOTA.onEnd([]() {
    Serial.println("\nArduinoOTA end");
  });
  ArduinoOTA.onProgress([](unsigned int progress, unsigned int total) {
    Serial.printf("OTA Progress: %u%%\r", (progress / (total / 100)));
  });
  ArduinoOTA.onError([](ota_error_t error) {
    Serial.printf("Error[%u]: ", error);
    if (error == OTA_AUTH_ERROR) {
      Serial.println("Auth Failed");
    } else if (error == OTA_BEGIN_ERROR) {
      Serial.println("Begin Failed");
    } else if (error == OTA_CONNECT_ERROR) {
      Serial.println("Connect Failed");
    } else if (error == OTA_RECEIVE_ERROR) {
      Serial.println("Receive Failed");
    } else if (error == OTA_END_ERROR) {
      Serial.println("End Failed");
    }
  });
  ArduinoOTA.setPassword((const char *)OTA_PASSWORD);
  ArduinoOTA.begin();
  
  timer.setInterval(1000L * 60 * 15, sendInternals); //  Here you set interval and which function to call
}

void presentation() {
	sendSketchInfo(APPLICATION_NAME, APPLICATION_VERSION);
  present(SEN_INTERNAL, S_CUSTOM, "Internal:rssi");
  request(SEN_INTERNAL, V_VAR1);
  sendInternals();
}

void receive(const MyMessage &message) {
  //Do not process messages from other nodes
  if(message.sender != GATEWAY_ADDRESS){
    return;
  }
}


void sendInternals(){
  MyMessage _internal(SEN_INTERNAL, V_VAR5);
  char _msg[26];
  //rssiQuality
  snprintf_P(_msg, 25, "p:rssiAsQty=%d", getRSSIasQuality(WiFi.RSSI()));
  send(_internal.set(_msg));

  //ip
  snprintf_P(_msg, 25, "p:ip=%s", WiFi.localIP().toString().c_str());
  send(_internal.set(_msg));
  
  //Free Heap
  snprintf_P(_msg, 25, "p:heap-f=%d", ESP.getFreeHeap());
  send(_internal.set(_msg));
  
  //HostName
  snprintf_P(_msg, 25, "p:host=%s", WiFi.hostname().c_str());
  send(_internal.set(_msg));

  //rssi
  snprintf_P(_msg, 25, "rssi:%d dBm", WiFi.RSSI());
  send(_internal.set(_msg));

  //RFM95-rssi
  snprintf_P(_msg, 25, "RFM95-rssi:%d dBm", transportGetReceivingRSSI());
  send(_internal.set(_msg));

  _internal.setType(V_VAR1);
  send(_internal.set(getRSSIasQuality(WiFi.RSSI())));
}

int getRSSIasQuality(int RSSI) {
  int quality = 0;
  if (RSSI <= -100) {
    quality = 0;
  } else if (RSSI >= -50) {
    quality = 100;
  } else {
    quality = 2 * (RSSI + 100);
  }
  return quality;
}

void loop() {
  ArduinoOTA.handle();
  timer.run(); // SimpleTimer is working
}

Node source code(Promini + RFM95):

#define SKETCH_NAME "Signal Monitor"                // Change to a fancy name you like
#define SKETCH_VERSION "1.0"                    // Your version


// Enable and select radio type attached
#define   MY_RADIO_RFM95

#define   MY_DEBUG_VERBOSE_RFM95
//#define   MY_DEBUG_VERBOSE_RFM95_REGISTERS
//#define MY_RFM95_ATC_TARGET_RSSI (-70)  // target RSSI -70dBm
#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_868MHZ)
#define MY_RFM95_MODEM_CONFIGRUATION RFM95_BW125CR45SF128


// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE

#define MY_DEBUG

//This Node ID
#define NODE_ID (int8_t) AUTO

#include <MySensors.h>
#include <SimpleTimer.h>
SimpleTimer timer; // Create a Timer object called "timer"! 

int Send_rssi, Rec_rssi;                     // RSSI RFM95 chip
#define CHILD_ID_RSSI_HIGH  7                // RSSI received signal level
#define CHILD_ID_RSSI_LOW   8                // RSSI background noise level
MyMessage msgRSSI1(CHILD_ID_RSSI_HIGH, V_LEVEL);
MyMessage msgRSSI2(CHILD_ID_RSSI_LOW, V_LEVEL);

//Sensor
#define SEN_DUMMY    (uint8_t) 1

//Pin number
#define PIN_TEST    (uint8_t) A1


MyMessage msg(SEN_DUMMY, V_STATUS);

void setup() {
    pinMode(PIN_TEST, OUTPUT);
    timer.setInterval(1000L * 5, sendInternals); //  Here you set interval and which function to call
}

void sendInternals(){
  Send_rssi = transportGetSendingRSSI();  // read RSSI in RFM95. Measure reception signal from gw
  send(msgRSSI1.set(Send_rssi));          // send RSSI level
  wait(1000);                             // wait to get idle

  Rec_rssi = transportGetReceivingRSSI(); // read RSSI in RFM95. Wait and measure background noise
  send(msgRSSI2.set(Rec_rssi));           // send RSSI level
  wait(1000);                             // wait for next send
}


void presentation() {
  // Send the Sketch Version Information to the Gateway
  sendSketchInfo(SKETCH_NAME, SKETCH_VERSION);
  
  present(SEN_DUMMY, S_BINARY);
  request(SEN_DUMMY, V_STATUS);

  present(CHILD_ID_RSSI_HIGH, S_SOUND, "Tx-dBm");
  present(CHILD_ID_RSSI_LOW, S_SOUND, "Rx-dBm");
 
}


void loop() {
    timer.run(); // SimpleTimer is working
}

void receive(const MyMessage &message) {
    if (message.sensor == SEN_DUMMY && message.type == V_STATUS) {
        Serial.print("*** SWITCH: ");Serial.println(message.getInt());
        digitalWrite(PIN_TEST, message.getBool() ? HIGH : LOW);
    }
}

When I change the following settings modem configuration(MY_RFM95_MODEM_CONFIGRUATION), works nice,

RFM95_BW125CR45SF128
RFM95_BW500CR45SF128

Doesn't work with the following modem configurations,

RFM95_BW31_25CR48SF512
RFM95_BW125CR48SF4096

@scalz Thank you! I tried with 3.3 volts (with pro mini). no luck

I am trying to build LoRa setup as follows,

• ESP8266 + RFM95 (MQTT gateway). Works perfectly
• Arduino Uno(Atmega328P) + RFM95. Doesn't work.

My Configurations (arduino UNO),

// Enable and select radio type attached
#define   MY_RADIO_RFM95

#define   MY_DEBUG_VERBOSE_RFM95
#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_868MHZ)
#define   MY_RFM95_MODEM_CONFIGRUATION (RFM95_BW125CR48SF4096)

// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE

#define MY_DEBUG

My ESP8266 Configurations,

// Enable and select radio type attached
#define   MY_RADIO_RFM95

#define   MY_DEBUG_VERBOSE_RFM95
#define   MY_RFM95_MAX_POWER_LEVEL_DBM (20)   // max. TX power 10dBm = 10mW
#define   MY_RFM95_FREQUENCY (RFM95_868MHZ)
#define   MY_RFM95_MODEM_CONFIGRUATION (RFM95_BW125CR48SF4096)

#define   MY_RFM95_IRQ_PIN 5
#define   MY_RFM95_IRQ_NUM MY_RFM95_IRQ_PIN
#define   MY_RFM95_CS_PIN 15

#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP8266

Debug message atmega328p,

17 MCO:BGN:INIT REPEATER,CP=RLNRA---,VER=2.2.0-rc.2
26 TSM:INIT
28 TSF:WUR:MS=0
29 RFM95:INIT
30 RFM95:INIT:PIN,CS=10,IQP=2,IQN=0
44 RFM95:PTX:LEVEL=13
46 TSM:INIT:TSP OK
48 TSM:FPAR
49 RFM95:SWR:SEND,TO=255,SEQ=0,RETRY=0
2053 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4060 !TSM:FPAR:NO REPLY
4062 TSM:FPAR
4063 RFM95:SWR:SEND,TO=255,SEQ=0,RETRY=0
6068 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8075 !TSM:FPAR:NO REPLY
8077 TSM:FPAR
8078 RFM95:SWR:SEND,TO=255,SEQ=0,RETRY=0
10083 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:

Log message from gateway,

327 MCO:BGN:INIT GW,CP=RLNGE---,VER=2.2.0-rc.2
331 TSF:LRT:OK
333 TSM:INIT
334 TSF:WUR:MS=0
335 RFM95:INIT
337 RFM95:INIT:PIN,CS=15,IQP=5,IQN=5
350 RFM95:PTX:LEVEL=13
352 TSM:INIT:TSP OK
354 TSM:INIT:GW MODE
356 TSM:READY:ID=0,PAR=0,DIS=0
359 MCO:REG:NOT NEEDED
scandone
f 0, 861 .1361 .1861 .2361 .scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 8
cnt 

connected with jee, channel 6
dhcp client start...
2861 .3361 .3861 .4361 .4861 .5361 .5861 .6361 .6861 .7361 .7861 .8361 .8861 .9361 .9861 .10361 .ip:192.168.1.113,mask:255.255.255.0,gw:192.168.1.1
10861 .10861 IP: 192.168.1.113
10863 MCO:BGN:STP
10867 MCO:BGN:INIT OK,TSP=1
10869 IP: 192.168.1.113
10871 Attempting MQTT connection...
pm open,type:2 0
26601 IP: 192.168.1.113
26603 Attempting MQTT connection...
27633 MQTT connected
27635 Sending message on topic: out_rfm95/0/255/0/0/18
28247 Sending message on topic: out_rfm95/0/255/3/0/11

I have SIM800L+ATMEGA328P setup. With this setup, I can use MQTT with TintGSM library.

I have some remote areas, where I want to implement MySensors setup and Gateway needs internet. I believe when we change PubSubClient code as follows gateway will work with GSM/GPRS module.

TinyGsm modem(SerialAT);
TinyGsmClient client(modem);
PubSubClient mqtt(client);

Source: https://github.com/vshymanskyy/TinyGSM/blob/master/examples/MqttClient/MqttClient.ino#L54~L56

Have anyone experience with this setup? Any hits?

@juanmrodrigues I followed this example from MySensorsSampleController.

In MyController locations where you can find implementations,

• Convert HEX file as blocks and store it in DB
• Process FirmwareConfigRequest
• Process FirmwareRequest

Hope this will help you to implement your own code.

@juanmrodrigues Thank you for your support! Are you looking code level implementation?

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

Build download location

RELEASE NOTES AND USER DOCUMENT NEEDS TO BE UPDATED. STAY TUNED!

@moskovskiy82 If you use MyController, Yes, you should assign the firmware for the node and send reboot.

@talhatec

However, when a sensor calls back to the controller, both HomeAssistant and myController send out replies, and due to this, i think the messages clash, and the controllers endup sending it multiple times.

I do not know your preference about, which controller wants to response for your sensors request. Suppose you want MyController only on listen mode, you have to change MQTT Topic publish to some dummy topic on MyController gateway settings.

@talhatec Are you seeing this error often?

@talhatec Thank you for your patience
Finally the first version of serial2mqtt adapter available and released for public. Kindly report issues if you find any on issues page

@keldandorin https://forum.mysensors.org/topic/2262/server-restart

@talhatec Still I am working on this feature. I will update you once it gets ready.

@mpp can you post your gateway sketch and MyController gateway configuration page(select gateway, click edit and post that page)

@mpp use different MQTT client id on your gateway sketch and MyController gateway configuration page. In the recent version, 3 random chars will be appended on MyController to avoid this kind of issue. If you want to try recent SNAPSHOT version have a look on >> http://forum.mycontroller.org/topic/58/download-snapshot-build

@mpp What is the version of MyController are you using? Are you using inbuilt MQTT broker?

Check the topic to-subscribe and to-publish.

@Mister_ik As you have the router, why don't you try with DHCP and lock an IP on Router for this gateway?
Other solution you may go with MQTT gateway.

@maolintao thethingsnetwork.org may be a good solution for you. Around you, if someone has gateway you can use it.

Gateways around the world: https://www.thethingsnetwork.org/map

@mpp Yes, MyController.org supports MY_NODE_ID AUTO in any gateway (Serial, Ethernet or MQTT)

On Status >> Resources logs page can you check, Does MyController receives ID request from your node?

@slt1

Firstly MYSController only works on Ethernet and Serial.

I understand this. But the only test with MQTT. If you are not fine with the change of gateway. go back to current setup.

Secondly, in MyController.org I lose all my sensor data as it will create new nodes for each of the sensors it picks up on a new gateway.

No, You can use edit gateway option. Edit existing ethernet gateway and update to MQTT configuration. This will retain your setup as is.

@slt1 For now I do not have Ethernet gateway to reproduce your issue.

Yes, I request you to update your ESP8266 ethernet to MQTT. it is simple. Just modify your ESP8266 firmware as shown here. https://github.com/mysensors/MySensors/blob/development/examples/GatewayESP8266MQTTClient/GatewayESP8266MQTTClient.ino

@slt1 Thank you! Do you have the serial or MQTT gateway? If yes, Can you try once with the serial or MQTT gateway and report the status?

@slt1 I couldn't download the file you have attached. Can you please send it to jkandasa at gmail dot com?

@slt1 said in MyController OTA problems:

I also have mosquitto, node and node-red setup on the CHIP.

I guess this makes MyController too slow. When you are not using inbuilt MQTT broker. you can make it disable. Can you send me the MyController.log file to know more about Ethernet failure?

@slt1 said in MyController OTA problems:

There seems to be no way to remove Firmware from a Node once its assigned. If I continue to experience issues with MyController.org's OTA then I would like to remove the firmware assigned to the node and rather use MySController's firmware update for now. Is it possible to add an option to select "No Firmware"

Kindly open an issue for this. https://github.com/mycontroller-org/mycontroller/issues

@slt1 Hi Sorry for the inconvenience. Could you please report your version of MyController? C.H.I.P configuration.

What type of gateway is using with MYSController?

@slt1 Thanks for the report. I tested on two different nodes. Controller: MyController.org. Gateway MQTT(ESP8266), Radio: NRF24L01+

• 8 MHz internal crystal on the noisy environment: for 47K hex file takes 6 minutes and 42 seconds
• 16 MHz external crystal on clean environment: for 26K hex file takes 36 seconds

Bootloaders I use: https://forum.mysensors.org/uploads/files/1475275020003-mysbootloader_v13pre2.zip

Initial days I face coverage problem with NRF24L01+. I changed my antenna as per this specification, from this point I see notable improvement on coverage.

@slt1 Thanks for the detailed information. If you have enough time would you mind to give a try to https://forum.mysensors.org/topic/4991/mysbootloader-1-3pre2-testing ?

Bootloader link: https://forum.mysensors.org/uploads/files/1475275020003-mysbootloader_v13pre2.zip

@slt1 I hope you are also facing this kind of issue: https://github.com/mysensors/MySensorsBootloaderRF24/issues/12

@slt1 If you are using wait() to repeat some function. I recommend using http://playground.arduino.cc/Code/SimpleTimer, to avoid complete blocking when executing wait().