Hardware

@AffordableTech, regarding PIR sensors, I've got an advice to add 3rd battery since this sensor is very sensible to VCC level and under 3v isn't predictable. So I've connected batteries as suggested here: [image: 1490118549165-upload-52d98145-abd5-4638-aec4-e113815f2474.png] I also thought about step-up convertor to power PIR with exactly 3.3v, but I was said this kind of power line is quite noisy which again will cause false positives so Ive rejected this option. With this setup (3AA) my node became reliable and works that way about 1 week. As for light sensor, after some thoughts I came into decision to use BH1750FVI sensor which is also I2C one with low consumption if configure it with one time measurement mode (by default it's continuous mode). My use case is to trigger light by motion only if light level is 0. Now I just send light level alongside with motion event, thus no need of waking up by light interrupt anymore.

Ah! I never thought of that. Nice to see it's solved! And I think you're right, this kind of info should be made available for easy access.

I don't think redundancy is supported

On other sites, they sell a 3.3V version and a 5V version. The 5V version has level translators and an on-board 3.3V LDO regulator. I can't tell which is which from the Ali description.

@irenla You have probably already figured this out but try this. return temp; float tempF = (temp * 9.0) / 5.0 + 32.0; you get the idea now.

@Nathan-Matos you'll probably be interested in the discussion in https://forum.mysensors.org/topic/6519/stm32/ I have ordered two stm32 but not received them yet.

@hek - Awesome!

@gohan My understanding of the ESP8266 is that much like the ethernet solution, each node would have to be configured as a gateway as it is still running on an IP protocol like the ethernet node. I ran into this when I got some Sonoffs and was trying to connect them to my Vera Plus. I ended up using them with the ESPEasy firmware and a different plugin on my Vera.

Try #define MY_TRANSPORT_WAIT_READY_MS 1

I love this one: https://www.openhardware.io/view/268/RFM69HW-interstitial-board-for-Pro-Mini-Temp-Humidity-sensor

I use these and they plug straight into my Gert Saunders boards with no wires ;-) https://oshpark.com/shared_projects/TKNcHTRl Only for rfm69hw or rfm69w not the compact version. They work a treat

If you need a signal both if the window was closed and opened you can buy this sensor: https://www.aliexpress.com/item/Free-shipping-Wireless-window-and-door-magnetic-sensor-open-detector-1527-chips/32334214010.html It is based on a 1527 Chip. Open the rear cover and connect these pins with a solder point: [image: 1490295556726-433mhz-reed-sensor-small.jpeg]

Hello together, there is no "right" or "wrong" answer to this questions imo. Both concepts have their two sides. Personally, I prefer to go the multisensor way (and also use RS485, which limits the numbers of sensors to 32 per gateway with standard interface boards). In addition to that I also like the idea to let the arduinos decide (some) things locally or make them configurable to some extend. So things may not become completely out of controll in case there is (temporary) no controller. Advantages: Less parts, especially power adopters/batteries, less "optic irritation" better use of arduino potential (use of more than 40% of the memory, not sleeping all the time) Less RF, means also lower risk of RF conflicts (or best: no RF at all => RS485) in case of e.g. failure or power off, I will most likely notice this earlier because of the bigger "footprint" Disadvantages: its (sometimes) hard work to get things working (but also fun and satisfaction :satisfied: ) higher risk of messing things up because of bad code (I am just a beginner in programming. This is more related to distributed logic as mentioned above; just combining some simple examples isn't rocket science...) in case of e.g. failure or power off, a multisensor has the bigger "footprint" So it's up to you which way to go (or to which extent, to be more precise).

Welcome to the MySensors community @Andrew-McInnes use #define MY_RF24_CS_PIN 5 in your sketch before including MySensors.h Details: https://github.com/mysensors/MySensors/blob/8bb3cfb2e14214ae19e8531c989d1e81c9660614/MyConfig.h#L508

@mfalkvidd right, I was thinking of updating RFM69 wiring diagrams on https://www.mysensors.org/view/171#rfm69-&-esp8266 , but for how the radio module go I was interested in the rfm96 range / reliability to see how it goes. Anyway I will look for futures updates on the forum.

I suggested those modules because you can quickly swap the radio module, but that may work too. Pls post back your results

@napo7 thanks for response. Actually I want to avoid such solution. The main reason is the reliability. Just want to have wired connection between switch and the actuator. I tried the solution with resistor ladder like this: (5V) | (R=2kOhm) | (ADC PIN) --- (SW1) --- (R=1kOhm) ----- -- (SW2) --- (R=1.5kOhm) -- --- (SW3) --- (R=3kOhm) ----- --- (GND) So pressing different switches (SW1 to SW3) should result in different resistance seen between ADC PIN and GND. And to be able to detect multiple switches pressed at the same moment the resistor values must differ. Unfortunetly this makes very little differences between some combinations, and i'm afraid that on 5 meter long wire the noise will cause misdetections. Does anybody used such solution ?