Posts made by Avamander

I'm also interested about this: https://github.com/mysensors/MySensors/issues/1424

@ncollins

There's this nice HAT for the Raspberry Pi you might find interesting : https://gitlab.com/electronutlabs-public/indrium-pi-hat

On another topic, I would honestly like to see MySensors using OpenThread or BLE Mesh transport...

I have a few of these dongles myself and they're really rather nice. I am too wondering, is there a nice way to use them as a MySensors gateway? Compiling MySensors currently fails for the nRF52840 boards.

I tried flashing MySensors onto my nRF52840 Adafruit Feather board but it fails, I opened an issue on GH about it https://github.com/mysensors/MySensors/issues/1424, maybe someone here has any ideas how to get it running on those boards?

@TRS-80 said in Finally, progress! (evidence based radio testing method):

Perhaps one of you professional angry pixie wranglers out there can verify that there is in fact something to the "two capacitors of different values in parallel" theory?

Two capacitors in parallel lowers the ISR of the capacitance attached to the circuit, meaning it "reacts faster" to the changes in voltage and acts as a better filter. As BearWithBeard said, you can achieve a similar effect by combining electrolytic and ceramic capacitors. If you have a lot of LF and HF noise, that might give you a better result.

@NeverDie I personally took a bottle of nail polish and coated every sensor I had. I had a hunch that moisture seeping might affect the capacitive sensors so I took precautions. They've lasted a year now with no sign of deteriorating.

@Bmlsx Check the configuration defines and/or just post the sketch.

@Bmlsx You're better off taking 2.x.x humidity sensors example. Alternatively, you should check if all the configuration options you're currently using are valid and used.

I have a ton of different sensors , just to satisfy my own curiosity:

• 2x MQ-2
• MQ-3
• MQ-4
• MQ-5
• MQ-6
• MQ-7
• MQ-8
• MQ-9
• MQ-135
• GP2Y1010AU0F
• A few DHT11s, DHT22s and a few other temp/moisture sensors I can't recall atm
• A few BMP280's
• MS-1100
• RadiationD-v1.1
• Three dust sensors I can't recall the model of right now, bought them so long ago
• Probably something else I've forgotten right now

@cYnd I know, but the lack of proper solder flow (on at least two pins) and a cold joint should not happen even if soldered from the other side. I'd fix it just to be sure it doesn't cause any erratic issues.

@alowhum How's the SDS011, have you had the chance to compare it to other dust sensors?

I was wondering, what types of air quality sensors do people use here, has anyone maybe even calibrated or tested their sensors (e.g. compare performance across different types measuring the same thing)? Any favourites? I'm just curious about what people have and how they use them, maybe I'd like to get one as well

I personally have a lot of different sensors, bunch of different MQ-series sensors, four different dust sensors and a few CO2 sensors even.

@Kikakee
I couldn't find one, so I designed my own.

(My model is not suitable for anyone else because I made it fit very snugly around my board)

Wanting a smaller, neater solution than that, I bought a nRF52840 USB stick, hoping I could use that because it's very nice, but unfortunately there are some compatibility issues I have to yet resolve.

@alex28

plug them together with jumper wires and - nothing works' scenario

No not really, because the jumper wires are exactly the thing a pre-made sensor PCB would avoid.

Where you don't need to worry about fake components, etc.

That depends where the person sources the components to populate the PCB, it's up to the individual to decide if they want to take the risk. What would be a better alternative here?

@alex28:

Requiring them to solder SMD components kinda goes against the whole point of it.

Depends on the component though. Most sensors sold by Adafruit, AliExpress and so on, come on boards that have breadboard-compatible pin-headers. Plugging in those isn't hard compared to placing all those things on a perfboard and wiring all that stuff up.

Pretty sure Arduino wrote about their hassles getting an Arduino board with a radio out onto the market, even when using a module it was a hassle.

I'm wondering though, wouldn't it be possible to sell a PCB that allows just plugging in every component?

Ah, I think cussing is warranted here, I copied the radio configuration from my old sketch to the new ones, the node had:

#define RF24_DATARATE RF24_2MBPS

The GW has:

#define MY_RF24_DATARATE RF24_2MBPS

Lesson learned: Never copy configuration from an existing older sketch, you never know what has been deprecated without a warning. MY_RADIO_NRF24 threw a warning and I fixed that, had no idea about RF24_DATARATE and I didn't notice it.

@tekka

Just to be clear, the Arduino Mega node (megaNode) can talk to the Arduino Nano gateway (nanoGW), but no Arduino Nano node (nanoNode) can talk to the Arduino Nano gateway.

I'll post the sketches and logs.

Looking at the images, the wires might not be properly connected, a few wires look like they're just plugged in. In that case even the slightest movement could cause issues.

@Yveaux said in Arduino Nanos don't work as nodes:

The MySensors stack doesn't know if it is running on a nano, uno or pro mini, so why are you so certain this is a bug in the stack?
What I do know is that a lot of low quality nanos are available from Chinese sources, with bad ground planes or crappy power regulators.

Because I'm really rather certain it isn't the hardware. You can read what I've replaced, swapped and tried. The radios have been decoupled, the power has been decoupled. The setup works in all possible ways when using RF24.

What nano boards do you use? Could you try a different atmega328 based arduino?

Yeah, I said I tried an Uno and it exhibited pretty much the same symptoms when acting as a regular node.

I just discovered that on the Arduino Uno RF24_250KBPS works, but RF24_2MBPS doesn't. On the Nanos, neither work.

I used RF24 and tested the boards for a while, I've determined that 2MBPS on that specific channel works great, I've sent at least 100 000 packets and lost only two. Auto-ack and dynamic payloads also work.

I am 99.99% certain this is a bug in MySensors. @mfalkvidd maybe you have some ideas where to look next?

I'm going to finish my Arduino Uno node and if that too doesn't work getting MyController to work must take some goat sacrifice because I can't do it.

I've determined that it doesn't matter which:

• Radio
• Radio's power supply/source
• Nano
• Bootloader
• Arduino IDE (tried 1.8.2 and latest nightly)
• 2.x.x MySensors
• Example, or custom sketch
• Channel, data rate, power level or node ID
• Repeater or not
• WAIT_READY_MS or not
• Predefined master or not
• SPI bus speed, 0.5*default SPI speed didn't help

I just can't make a Nano act as a regular node.

Maybe a MySensors dev has an idea what I could try.

In your first sketch the baud rate was 2mbps. How is your existing network configured?

That's exactly the same across all my sketches.

If you take an example sketch and an example gateway sketch, does it work then. So don't change channels and so on

Yeah, I did that and wrote about it above, took RepeaterNode and just defined CE/CSN on GW and the node.

Just in case I also took clean RepeaterNode example and just defined the CE/CSN pins and channel, it's still unable to work.

I also tried the same example without any repeater functionality enabled, it's still unable to register. It's basically a blank sketch.

Changing Node ID didn't also work.

I also ran the full "test" suite of RF24 and all examples work great, so I am very certain communication is likely to be very good.

It's just that something makes MySensors not like it.

@electrik :

Could you try version 2.2 of mysensors? I remember summer changes in 2.4 regarding nrf modules

I went to the oldest available version and it doesn't work.

I don't really get it, if I swap the radios between the Mega node and the Nano node, it stops working, swapping CE/CSN also makes it stop working - any alterations make it fail loud and clear.

It does initialize the radio and claim everything is okay. I can be quite certain it's not the radios, it's not the boards themselves, it's not the wiring.

There's something very specific to the Nanos themselves that 2.x.x is unable to use the nRF24L01+.

I will assemble an Arduino Uno board and see if the issue is specific to the AtMega328P.

@electrik It's highly unlikely. I have more than one type of module and more than one module of each type, none of them work. I also swapped the modules between working GW and Mega node and it still works, I swap the module between working GW and the node, it doesn't work.

@niclas

Well, the documentation says I don't have to have it connected.

@electrik

I suggest to start with one of the examples.

The gateway and node both are examples with the minimal required changes.

The RF channel is the same everywhere I guess?

Yes.

What does the output on the gateway say?

Nothing, totally silent. When I plug in the Mega node, then it starts outputting all the sensor and other data.

Anyways, the weird thing here is that I remember this working a few years or so ago on the same boards and stuff, it just doesn't work now and I have 0 clue why. I'm thinking about downgrading MySensors to 1.something

@niclas

I meant, have you erased the EEPROM of the gateway?

Yes, that too.

And also, how is the interrupt pin connected?

The radio's IRQ pin is not connected. (The IRQ pin is only required to be connected if the MY_RX_MESSAGE_BUFFER_FEATURE is defined in the sketch.)

@niclas

It looks like you are setting a Static node Id? Is that ID "free" in the gateway?

Yes, there are no other nodes (other than the one with a different static node ID that works)

Have you tried powering of all the nodes you have running,

Yes.

wiping the EEPROM of the gateway, powering up the gateway and shortly after powering up the node?

Yes, I've wiped EEPROMs of all the nodes.

@alowhum

// Enable debug prints to serial monitor
#define MY_DEBUG
#define MY_DEBUG_VERBOSE_RF24
 
// Enable and select radio type attached
#define MY_RADIO_NRF24
#define MY_TRANSPORT_SANITY_CHECK
#define MY_RF24_CE_PIN     9
#define MY_RF24_CS_PIN     10
#define MY_RF24_CHANNEL    29
#define RF24_DATARATE      RF24_2MBPS
#define RF24_PA_LEVEL      RF24_PA_MIN
#define RF24_PA_LEVEL_GW   RF24_PA_MIN
#define MY_NODE_ID         1

16 MCO:BGN:INIT NODE,CP=RNNNA---,FQ=16,REL=255,VER=2.3.2
26 TSM:INIT
28 TSF:WUR:MS=0
29 RF24:INIT:PIN,CE=9,CS=10
31 RF24:SBY
32 RF24:WBR:REG=0,VAL=14
39 RF24:WBR:REG=3,VAL=3
41 RF24:WBR:REG=4,VAL=95
44 RF24:WBR:REG=5,VAL=29
47 RF24:WBR:REG=6,VAL=37
49 RF24:WBR:REG=29,VAL=4
51 RF24:RBR:REG=29,VAL=4
53 RF24:RBR:REG=6,VAL=37
55 RF24:RBR:REG=5,VAL=29
58 RF24:WBR:REG=2,VAL=2
60 RF24:WBR:REG=1,VAL=0
62 RF24:WBR:REG=28,VAL=3
64 RF24:FRX
65 RF24:FTX
66 RF24:WBR:REG=7,VAL=112
69 TSM:INIT:TSP OK
70 TSM:INIT:STATID=1
72 RF24:WBR:REG=2,VAL=3
74 RF24:WBR:REG=1,VAL=1
76 RF24:STL
78 RF24:WBR:REG=0,VAL=15
80 RF24:WBR:REG=10,VAL=1
82 TSF:SID:OK,ID=1
84 TSM:FPAR
86 RF24:SPL
87 RF24:WBR:REG=0,VAL=14
89 RF24:OWP:RCPT=255
91 RF24:WBR:REG=10,VAL=255
93 RF24:WBR:REG=16,VAL=255
96 RF24:TXM:TO=255,LEN=7
98 RF24:FTX
99 RF24:WBR:REG=4,VAL=80
103 RF24:WBR:REG=7,VAL=112
106 ?RF24:TXM:MAX_RT
108 RF24:FTX
109 RF24:WBR:REG=4,VAL=95
111 RF24:STL
113 RF24:WBR:REG=0,VAL=15
115 RF24:WBR:REG=10,VAL=1
117 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2125 !TSM:FPAR:NO REPLY
2127 TSM:FPAR
2128 RF24:SPL
2130 RF24:WBR:REG=0,VAL=14
2132 RF24:OWP:RCPT=255
2135 RF24:WBR:REG=10,VAL=255
2138 RF24:WBR:REG=16,VAL=255
2140 RF24:TXM:TO=255,LEN=7
2143 RF24:FTX
2144 RF24:WBR:REG=4,VAL=80
2149 RF24:WBR:REG=7,VAL=112
2151 ?RF24:TXM:MAX_RT
2153 RF24:FTX
2155 RF24:WBR:REG=4,VAL=95
2157 RF24:STL
2158 RF24:WBR:REG=0,VAL=15
2161 RF24:WBR:REG=10,VAL=1
2163 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4171 !TSM:FPAR:NO REPLY
4173 TSM:FPAR
4174 RF24:SPL
4175 RF24:WBR:REG=0,VAL=14
4178 RF24:OWP:RCPT=255
4180 RF24:WBR:REG=10,VAL=255
4184 RF24:WBR:REG=16,VAL=255
4186 RF24:TXM:TO=255,LEN=7
4189 RF24:FTX
4190 RF24:WBR:REG=4,VAL=80
4195 RF24:WBR:REG=7,VAL=112
4197 ?RF24:TXM:MAX_RT
4199 RF24:FTX
4201 RF24:WBR:REG=4,VAL=95
4203 RF24:STL
4204 RF24:WBR:REG=0,VAL=15
4207 RF24:WBR:REG=10,VAL=1
4209 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6217 !TSM:FPAR:NO REPLY

Still no reply.

@alowhum said in Arduino Nanos don't work as nodes:

Is there a reason you're swapping your CE and CS pins?

Because they're wired that way and it doesn't/shouldn't matter.

Also, your code never loads MySensors? It's commented out?

Um, line 22 #include <MySensors.h>

Your node code is very strange.

It was of the examples, barely modified.

@alowhum said in Arduino Nanos don't work as nodes:

How are you powering them?

USB, tried a wall-wart and two different PCs.

Are you sure there's nothing like encrpytion on the gateway?

Yes, it's the default gateway sketch, except configured to use the right channel, data rate and nRF24.

Have you tried replacing all the wires between the nano and the radio module?

Yeah, I have multiple boards, some years old and have worked with other nRF24 projects. Plus, any wiring changes actually break it for things such as RF24.

Have you tried enabling the advanced radio debug option? (I forget it's name).

I'll look into that.

Maybe you have some of those fake Atmel chips?

Three of them bought at different times, and the only issues are with MySensor? Seems unlikely.

My issue is rather simple, no matter what I do, Arduino Nano nodes are unable to act as nodes.

I have a working pair of an Arduino Nano based GW and an Arduino Mega 2560 based node.

I have:

• Switched the radios between the nodes, the same radios that work on the GW and the Mega work on each other.
• Tried PA+LNA and two different regular nRF24 boards (no, not the COB ones)
• Built three new boards to plug the radio and the Nano into -
• Tried 1uF, 10uF and 470uF decoupling all separately
• Tried both with and without MY_PARENT_NODE_ID and MY_PARENT_NODE_IS_STATIC
• Tried with and without MY_TRANSPORT_WAIT_READY_MS
• I wiped the EEPROM of all the devices
• Tried an external 3.3V regulator
• With both the old and new Nano bootloader
• Multiple Nano boards
• Downloaded newer Arduino IDE and newest MySensors
• Switched channel and tried different power levels

But the node still either outputs:

16 MCO:BGN:INIT REPEATER,CP=RNNRA---,FQ=16,REL=255,VER=2.3.2
27 TSM:INIT
28 TSF:WUR:MS=0
34 TSM:INIT:TSP OK
36 TSM:INIT:STATID=1
38 TSF:SID:OK,ID=1
40 TSM:FPAR
45 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
2052 !TSM:FPAR:NO REPLY
2054 TSM:FPAR
2058 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
4065 !TSM:FPAR:NO REPLY
4067 TSM:FPAR
4071 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
6078 !TSM:FPAR:NO REPLY
6080 TSM:FPAR
6084 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
8091 !TSM:FPAR:FAIL
8092 TSM:FAIL:CNT=1
8094 TSM:FAIL:DIS
8096 TSF:TDI:TSL
18098 TSM:FAIL:RE-INIT
18100 TSM:INIT
18106 TSM:INIT:TSP OK
18108 TSM:INIT:STATID=1
18111 TSF:SID:OK,ID=1
18113 TSM:FPAR
18117 ?TSF:MSG:SEND,1-1-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
20124 !TSM:FPAR:NO REPLY
20126 TSM:FPAR

or with MY_TRANSPORT_WAIT_READY_MS:

16 MCO:BGN:INIT REPEATER,CP=RNNRAS--,FQ=16,REL=255,VER=2.3.2
54 TSM:INIT
58 TSF:WUR:MS=1
64 TSM:INIT:TSP OK
66 TSM:INIT:STATID=1
68 TSF:SID:OK,ID=1
69 TSM:FPAR
70 TSM:FPAR:STATP=0
72 MCO:BGN:INIT OK,TSP=0
74 TSM:ID
1
Sensor: 17
76 !MCO:SND:NODE NOT REG
79 MCO:SLP:MS=500,SMS=0,I1=255,M1=255,I2=255,M2=255
84 !MCO:SLP:REP
86 TSM:ID:OK
87 TSM:UPL
123 !TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
2
Sensor: 34
586 !MCO:SND:NODE NOT REG
589 MCO:SLP:MS=500,SMS=0,I1=255,M1=255,I2=255,M2=255
594 !MCO:SLP:REP

Node code:

// Enable debug prints to serial monitor
#define MY_DEBUG

// Enable and select radio type attached
#define MY_RADIO_NRF24

#define MY_REPEATER_FEATURE
#define MY_TRANSPORT_SANITY_CHECK
#define MY_SIGNAL_REPORT_ENABLED
#define MY_RF24_CE_PIN     9
#define MY_RF24_CS_PIN     10
#define MY_RF24_CHANNEL   29
#define RF24_DATARATE      RF24_2MBPS
#define RF24_PA_LEVEL      RF24_PA_MIN
#define RF24_PA_LEVEL_GW   RF24_PA_MIN
#define MY_NODE_ID         1
#define MY_PARENT_NODE_ID  0
#define MY_PARENT_NODE_IS_STATIC

#define MY_TRANSPORT_WAIT_READY_MS 1

#include <MySensors.h>

uint32_t SLEEP_TIME = 500; // Sleep time between reads (in milliseconds)

MyMessage msg(0, V_LIGHT_LEVEL);

void presentation()
{
  pinMode(A7, INPUT);
  
  Serial.begin(115200);
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Basicsensor 1", "0.1");

  // Register all sensors to gateway (they will be created as child devices)
  delay(10);
  present(0, S_LIGHT_LEVEL, F("Light level sensor"), true);
}

uint16_t lightLevel = 0;
uint16_t lastLightLevel = 0;

void loop()
{
  lightLevel = analogRead(A7);

  if (lightLevel != lastLightLevel) {
    Serial.print("Sensor: ");
    Serial.println(lightLevel);
    send(msg.setSensor(0).setType(V_LIGHT_LEVEL).set(lightLevel));
    lastLightLevel = lightLevel;
  }

  sleep(SLEEP_TIME);
}

I now suspect there's a bug somewhere in MySensors introduced by some newer version affecting Arduino Nanos. Because I remember MySensors working on Nanos a while ago.

Maybe someone here has some ideas how to narrow the issue down?

Small update to the situation. With awesome work done by @jkandasa, the main developer of MyController the InfluxDB backend is now fast enough to almost keep up with the data inserted, that's a big improvement. This means the last issue I had with MyController just got resolved and it's suitable for my use-case. Yay!

@gizmocuz When you've got more than one sensor with the same reading type then it does make sense. The built-in ID variable helped to differentiate but I have 20 gas sensors and putting together that internal ID and node ID + sensor ID was too much work.

@kimot I used that workaround indeed and it started crashing :þ

@yveaux Can you explain a bit how your setup looks like? Are you controlling anything with it or just collecting data?

So far I've tried MyController, Home Assistant, Domoticz and OpenHAB and all of them have absolute deal breakers for me. Here's why I don't like any of them:

Home Assistant required so much hand holding (one must send "ppm" as the unit, doubling the load on the gateway just for numeric readings or you won't get a proper chart) and the UI, although pretty, absolutely died after a few days of sensor readings (or barely survived if you didn't misclick anything).

OpenHAB was just sluggish and started randomly dropping the serial gateway (claiming it was online) and ignoring sensor readings/presentations. Resets and restarts helped but that's unusable. Scripting was also something that lacked good manuals about anything above basics.

Domoticz started crashing after I enabled InfluxDB push (and didn't allow me to enter DB password without an ugly workaround), using the bare HTTP push required me to manually add every single sensor to be pushed - I have 50, added 15 and got fed up. Value pushing offers no way (nothing useful under the available keywords) to have node ID and sensor ID as the series name.

MyController couldn't handle pushing data to InfluxDB - crashed when doing so. But to be fair, one of it's developers responded to my issue and told they released a hotfix. So will try that out again, maybe I can track down what makes the hotfixed version crash. UPDATE: All the issues with MyController have been nicely resolved, it's now a clear winner in this category the very least. Also, thanks again to the developer who so kindly helped to squeeze the most out of my poor RPi :D.

So, could anyone kindly suggest me something that works with MySensors, can in theory ACK messages and can easily push data to influxdb and doesn't choke doing so?

I solved it by removing every item and thing of the same node and then re-adding them all.

@alexsh1 I'd do it but I'm waiting for my replacement multimeter to arrive, sorry.

@alexsh1 Just desolder the sensor itself from the board if you're that far already? I wouldn't be surprised if aliexpress sellers sell counterfeit chips that are s****ier, I'm already seeing that with nRF24L01+'s

@alexsh1 There's an I^2C address selection jumper on the board, maybe that draws current?

@alexsh1 I have the same board, there seems to be a regulator and a few other components on the board, if you remove those, how's the power consumption then?

@alexsh1

Did you try a different lib?

Haven't bothered, I'm just logging the raw values and then compensating with software.

Battery issues is one thing, SparkFun's VEML6075 library can't handle direct daylight even (compensated UV readings go negative).

It turns out that V_UNIT_PREFIX is not supported by OpenHAB's MySensors binding.

@freynder I'll comment that out, it was only needed for Home Assistant, I added it to get the right type of chart. But still, the crash itself happens after presentation?

So after switching from Home Assistant to MyController to OpenHAB it seems that OpenHAB doesn't like the way my sensors are reporting their values. I'm seeing this stacktrace in the log all the time (something is wrong with it's output, Konsole isn't letting me copy it properly, image of it: ) :

01:47:24.343 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Node 3 found in gateway
01:47:24.350 [DEBUG] [ors.internal.gateway.MySensorsGateway] - Child 4 found in node 3
01:47:24.357 [ERROR] [internal.event.MySensorsEventRegister] - Event broadcasting throw an exception
java.lang.NumberFormatException: null                                                                                          




24) ~[?:?]                                                                                                                     
?]                                                                                                                             
[?:?]                                                                                                                          



a:122) ~[?:?]                                                                                                                  
]                                                                                                                              
:?]                                                                                                                            



a:79) [211:org.openhab.binding.mysensors:2.3.0.201803141156]                                                                   
nection.java:358) [211:org.openhab.binding.mysensors:2.3.0.201803141156]                                                       





01:47:24.462 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;9;2225831 TSF:MSG:READ,3-3-0,s=4,c=1,t=37,pt=3,l=2,sg=0:0
01:47:24.469 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;9;2225838 TSF:MSG:ACK REQ
01:47:24.475 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 0;255;3;0;9;2225842 TSF:MSG:SEND,0-0-3-3,s=4,c=1,t=37,pt=3,l=2,sg=0,ft=0,st=OK:0
01:47:24.483 [DEBUG] [orsAbstractConnection$MySensorsReader] - Message from gateway received: 3;4;1;0;37;0                                                   

Sensor 3 sending code:

void presentation() {
  // Send the sketch version information to the gateway and Controller
  sendSketchInfo("Gassensor", "0.0");
  Serial.begin(115200);

  // Register all sensors to gateway (they will be created as child devices)
  for (uint8_t sensor_id = 0; sensor_id < 11; sensor_id++) {
    pinMode(sensor_pins[sensor_id], INPUT);
    present(sensor_id, V_UNIT_PREFIX);  // Custom unit message.
  }
}


void loop() {
  for (uint8_t sensor_id = 0; sensor_id < 10; sensor_id++) {
    uint16_t reading = analogRead(sensor_pins[sensor_id]);
    Serial.print(F("Sensor: "));
    Serial.print(sensor_id);
    Serial.print(F(", reading: "));
    Serial.println(reading);
    send(msgPrefix.setSensor(sensor_id).set("ppm"), true);
    send(msg.setSensor(sensor_id).set(reading), true);
    sleep(100);
  }

  send(msgPrefix.setSensor(10).set("ppm"), true);
  send(msg.setSensor(10).set(analogRead(DUST)), true);
  sleep(SLEEP_TIME);
}

@yveaux

grafana + influxdb combo can easily handle very large sets of sensor data.

Is there a way to get mycontroller to use influxdb + grafana? I only found a small tutorial for Home Assistant but I'd really rather use mycontroller, it's way more usable.

I've tried Home Assistant ant mycontroller.org and both of them are really slow. In the first case Home Assistant just totally kills my RPi3+ after it has collected about 300k readings collected by ten sensors (and I've not even asked to display the data). And in the second case it takes about eight seconds to just display me eight data points where there should be about 100k.

So are there any controllers available that can actually plot a subjectively large amount of points (so about 10-100k, should totally not be a problem)?

@gohan Fair enough. That pretty much answers my question too, that noone has needed this functionality enough for it to be built-in to MySensors.

@dbemowsk @gohan It already has capacitors smoothing the switch, it's an automated mux doing it after all, but badly timed switch (when say gas sensors get turned on exactly when an actuator needs to be triggered) can mess that up. Even if it doesn't reset it would be nice to have more redundancy in the system.

@dbemowsk I've built a single bus that supplies my entire sensor network and actuators and as I don't want to waste energy running a 500W PSU a 10W one usually is enough and is way more efficient, it switches automatically between them when more power is needed.

@gohan I could theoretically, but then I'd have to change the rPi gateway code to add a few features that I need and I'd rather not do that.

It resets itself and starts to reinitialize (that causes sensor reading/packet loss I mentioned which I really don't like). The RPi itself is powered from another power supply and the grounds are just connected.

I was wondering if it was possible to make a random node take over the gateway functionality?

I've noticed that in my current setup when I sometimes have to switch PSUs of my gateway node it doesn't always survive without rebooting (and I don't want to damage the power mux with a larger capacitor+inrush current either). So having one node buffer (or process) some messages and then maybe send them to the gateway for processing when it comes online would be really nice. Has anyone tried to have redundant gateways?

@Anticimex Hello, I found this thread now. I'll ask a few more questions, sorry. This all seems really-really great.

1. If someone wishes to use TMRh20's RF24Mesh instead of MySensors how would one sign the messages sent with that library? Is is even possible? What should be done to use that functionality?

2. Also, as I understand it is possible to emulate the ATSHA204A, on what hardware is is possible (on Uno's ATMega too?)?

3. Is it also possible to use whitelisting with RF24Mesh somehow?

Again, sorry for any dumb questions and my poor English.

@Anticimex I am not familiar with MySensors so sorry for the questions, who are the "we" you are speaking of having the features? Is this something MySensors now supports?

@Anticimex How far are you with authenticity verification?

Speed is one thing that can be tested, fakes are slower. Packet loss too. ACK with dynamic payloads too. Registers that exist only on fakes (the datasheet error one for example).

Would it be possible that someone would create a sketch that would detect fake modules and warn about discrepancies? I would hate to spend more money on fake modules.