Topics created by Matt

@Matt Yes, the landscape there is incredible. Unfortunately, I mostly have to work when I'm there Where are you from?

Some humidity sensors are known to lose accuracy with age. For instance, the Si7021 is known to have this problem. If that matters to you, then the best choice is to pick sensors that have datasheets and which have specs as to their expected longevity or accuracy over time. Then buy from mouser/digikey to be certain you're getting the real thing rather than factory rejects or counterfeits. For extra insurance, I avoid electrolytic capacitors entirely whenever possible. I buy only 7XR rated ceramic capacitors that are overspec'd. The difference in price is small compared to a failure down the road.

@mfalkvidd Thanks heaps, enjoy your trip

Support for atmega168 has been added in the development version of MySensors and will be available in the next stable release. More info in https://forum.mysensors.org/topic/5727/compile-error-for-pro-mini-5-5v-168/

@Matt Not sure if you do this. But in my experience, you need to add small delays (wait(15)) in your sketch after communication. Especially when creating large multi sensor nodes. The radio isn't always fast enough to digest all of the communication. Not sure if this is your problem, but it solved my problems.

Hallo! Ich habe gerade meinen Aduino Nano mit einem GY-BME/P-280 verbunden über SPI verbunden. Im Sketch habe ich nur die PINS geändert und zwar auf: #define BMP_SCK 13 #define BMP_MISO 12 #define BMP_MOSI 11 #define BMP_CS 10 Ich bekomme aber bei der Ausgabe am seriellen Monitor nur "Hyroglyphen" zB 5��,�lh����}����'�O8��m�h,� Mit einem anderen Sketch funktioniert der Sensor einwandfrei. Auch mit einem anderen Nano dasselbe Ergebnis. Hat jemand eine Idee was das Problem sein könnte? Zusatzfrage da ich in C++ nicht so firm bin: Könnte es sein, dass MY_DEBUG oder MY_RADIO_NRF24 das problem verursacht. Was machen diese Definitionen eigentlich? Grüße

Did you verify that the message is received by the node? I'm not familiar with FHEM, please note, that the first outlet uses child ID 4. What's the debug output of the node?

OK so rather than wait for shipping from China I went to my local Jaycar and got one of these LDRs. If the link gets broken its a cadmium sulphine LDR with a rise time of 50ms and decay of 40ms. Works like a charm. Because its flat I can tape it directly to the LED in my power meter, covering the whole thing with black tape to ensure no ambient light problems. Two pinholes in the tape and the LDR leads go right through no probs. I have some thin wires going to the LM393 unit (so minimal weight on the LDR/Tape itself) and I guess the comparator in there is good enough to pick up the change in resistance on the LED pulses. So if you wind up with one of these units I recommend swapping the photodiode with a high spec LDR and soldering some leads from the module to the LDR to facilitate accurate fixing to the meters LED. I used two bits off an old length of ribbon cable (IDE HDD type stuff).

<SOLVED> OK so my presumption/suspicion was right, does need to be sending an active signal for the node to transmit any data. Seems to be working well now, just have to find a spot in my long house where the gateway will reliably talk to the polytunnel AND the meter reader. And for any others struggling with this, especially getting the sensor LM393 to work, I found it needs to be pointed directly at the LED in my meter, not side on. To achieve this I drilled a small hole in the top of a jam jar lid and epoxied the board to it, then taped the lid to the meter. Seems to be working a treat now. YAY! Thanks MS team, you have a great product. Next step is temp sensors for the kids bedrooms and a relay on their heaters (winter is coming to the deep south of NZ) Cheers, Matt

@brianmichalk Do tell us more. Sounds interesting.