@ncollins It is possible to use NRF51822 for gateways with serial. I am using it for many months now. We need USB to serial adapter.
Also, I do not use JLink or ST-Link for flashing the NRF51 chips. I use raspberry pi with OpenOCD.
OpenOCD setup can be overwhelming (it was for me) but I have been able to make it work and replicate for a while now. If someone needs inputs, I am happy to help. Ask here or reach out to me on discord @ Puneit#2433

For the very reason you stated - hardware bugs in NR51 chips leading to high power-consumption - they make compact repeater nodes / powered nodes with repeaters.

@jamzm From what I understood is that a Fing box is an interface device which adds to your router and it is something related to the WiFi network.

I am no expert - -still loads to learn but then I think there is some disconnect. While the Mysensors network does work on the 2.4GHz frequency range (through the NRF24 or NRF5 radios), the network is an ISM band network and not a WiFi standard. Therefore you need to add a gateway from the door sensor to your network.

Take a look at the Getting Started and Build pages.

The minimum you need is a arduino board of your choice with a radio of your choice for the sensor; an arduino/esp8266 of your choice and the same radio for the gateway and a controller of your choice as well.

Had I been starting and someone asked me to choose a bunch of stuff, I would get scared. So I will tell you what I use.. its just one of the implementations.

For the sensors I use arduino pro mini 3.3v with NRF24L01 and I am experimenting with NRF51822 (stay away from these)
For the gateway, I use an arduino uno with NRF24l01 with an ethernet shield running MQTT gateway
For the controller I use Home Assistant.

Now for the sensor itself - if you want to DIY the same, then I would do it this way (again different people would have different methods)

Use arduino pro-mini with NRF24l01 and a reed-switch. 3D print the case for it and use it.

I hope I was able to help in some manner.

Home assistant has a docker container which talks nicely with a mysensors serial gateway connected via USB on a Dell machine.

 homeassistant:
    container_name: hass
    image: homeassistant/home-assistant:stable
    volumes:
      - /home/server/homeassistant/:/config
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0:rwm
    healthcheck:
      test: ["CMD", "curl", "-f", "http://127.0.0.1:8123"]
      interval: 30s
      timeout: 10s
      retries: 6
    network_mode: host
    depends_on: 
      - mosquitto

the following line enables serial gateway into HA and then in the latest release 2021.3 one can add Mysensors from UI

devices:
      - /dev/ttyUSB0:/dev/ttyUSB0:rwm

@jkandasa I am yet to use to Serial2Mqtt in order to test this out without breaking my current setup.. I will do it and share my feedback. I would definitely want to run Mycontroller in parallel to HA.

You can upload Mysensors sketch to NRF5 modules and that way it can speak to mysensors network and then communicate to your controller through the gateway

Thank you so much!

@mfalkvidd
The diagnosis solved the issue. The Arduino pro mini 3.3V 8 MHz sold to me was actually a 5v 16 MHz. No more Failed reading temperature from DHT!. However, there are still a few st:fail during initialisation but later goes away.
Should I work towards eliminating these or would it be fine. The Openhab2 still is not reading from this node and shows NaN (even though the sensor is online).

Thanks for your continued help.

TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-1 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=1)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-1 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
!TSP:MSG:SEND 1-1-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=fail:2.0.0
!TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=1,st=fail:0
!TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=11,pt=0,l=22,sg=0,ft=2,st=fail:TemperatureAndHumidity
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=3,st=ok:1.1
TSP:MSG:SEND 1-1-0-0 s=0,c=0,t=7,pt=0,l=0,sg=0,ft=0,st=ok:
TSP:MSG:SEND 1-1-0-0 s=1,c=0,t=6,pt=0,l=0,sg=0,ft=0,st=ok:
Request registration...
TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-1 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registration=1
Init complete, id=1, parent=0, distance=1, registration=1
TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,ft=0,st=ok:24.6
T: 24.60
TSP:MSG:SEND 1-1-0-0 s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=ok:41.9
H: 41.90
TSP:MSG:SEND 1-1-0-0 s=0,c=1,t=1,pt=7,l=5,sg=0,ft=0,st=ok:42.0
H: 42.00

@ncollins Yes, it is very easy to (re)deploy a whole system using the docker compose files.
I have 4 splits --- one being my core containers , Homeassistant, Nodered, Mosquitto, etc and then one of them being "applications that I don't need but have".. I recently had to redeploy and my core stack was running in under 10 minutes..

It is a very powerful tool.

@tBS I think I am in the same boat as you. Well, I started with MySensors few years ago and then shifted most of my stuff to Esp8266 - Tasmota and ESPHome. I am rebooting this project personally for me.

Yet, I feel somehow MySensors is a better implementation in terms of its mesh capabilities and repeater function.
And it is easier to make MySensors battery operated. NRF24 or NRF5x are more efficient power wise as compared to ESP8266 or ESP32.
That said, I think what we lack in this project (and if I am unable to find, maybe someone can point it out) are YouTubers like Drzzs of Home Assistant.

I have a Telegram group of Home Automation users in India and off-late I have been pushing this project on my group. We are in the midst of a lockdown, hence we cannot source parts for now.
That said, I think while you could be late in the game - a lot of development has happened and bugs were ironed out.
I am extremely happy to help as much as I can. I am no expert - so most likely I won't have the answers. I believe two heads are better than one so we can work things out together.

Cheers!

Hello.
I dipped my toes into the world of home automation and discovered mysensors a couple of years ago. Then, I built (successfully) couple of relay actuators and stopped. Reason: I was in a rented apartment and couldn’t do anything permanent as such. Now, I have my own apartment and we have more or less settled in.
I would like to make our home a wee bit smarter- turn on/off lights , put a timer on a washing machine power source, humidity detection , gas leak detection , door sensors etc.
I have Arduinos pro mini and nrf24 radios with me from earlier.
My questions are the following

1. I used domoticz earlier but now more inclined towards openahb2. Is it advisable to make a switch ?
2. I read about zigbee and zwave. But I don’t have any existing hardware of these protocols but the only advantage I have so far read is that these protocols are “stable” or “safer”. I am in India and as far as I know there are no regulations as such when it comes to tinkering with home electricals (I still don’t want to burn down the house). In my scenario , will Mysensors be a stable solution?
3. I want some kind of redundancy in the setup - if my home network fails or is down, I should still be able to get things running. Hence, shall I also consider building a scene controller which can control the relays if a phone is unavailable or Alexa is down etc. basically it should be SO friendly or a guest friendly.
   I am planning to start tomorrow and looking for advice. Thanks.

I moved from keepass to Bitwarden self hosted. For a while I used both in parallel and now I have fully moved to Bitwarden self hosted. It integrates very well with everything- iOS, Safari on Mac and other browsers

@NeverDie creating VLANs and restricting access of the IOT devices to must have access is the method I follow.

@jkandasa I am yet to use to Serial2Mqtt in order to test this out without breaking my current setup.. I will do it and share my feedback. I would definitely want to run Mycontroller in parallel to HA.

@NeverDie MySensors via UI came in this release 2021.3. Prior to that it was through an entry (very simple one) in configuration.yaml.

If you have cameras, 3D printer (running Klipper) - all that can come into HA. And Homekit via HA works great as well.

@NeverDie VM install is one with the supervisor.. yes this is what I was referring to. VM is one of the supported methods, I guess

@NeverDie While I never used proxmox or VM, I did use the supervised install on Linux and then moved away from it. The advantage of supervised install is that you get the addon store but the disadvantage is that Supervisors starts to complain and moan as you install more containers on the host system.
It then stops you from upgrading to latest versions and prevents addons to be updated. At that stage I decided to move away from a supervised install.

@Ron @Anticimex The radio stops at 1.9V.. so I think its fair to do a BOD of 1.8V.

I used arduinoAsISP to burn bootloader and this is my platformio.ini

[env:program_via_ArduinoISP]
platform = atmelavr
framework = arduino
;  Serial bootloader protocol
upload_protocol = custom
; Serial upload port
upload_port = /dev/cu.*
; Get upload baud rate defined in the fuses_bootloader environment
upload_speed = 19200
board_build.f_cpu = 8000000L
board_hardware.oscillator = internal
board_hardware.uart = uart0
board_hardware.bod = 1.8v
board_hardware.eesave = yes
board_hardware.ckout = no
upload_flags =
    -C
    ; use "tool-avrdude-megaavr" for the atmelmegaavr platform
    /Users/puneit/Nextcloud/PlatformIO/bootloader/tool-avrdude/avrdude2.conf
    -p
    $BOARD_MCU
    -P
    $UPLOAD_PORT
    -b
    $UPLOAD_SPEED
    -c
    stk500
upload_command = avrdude $UPLOAD_FLAGS -U flash:w:$SOURCE:i

@ncollins Yes, it is very easy to (re)deploy a whole system using the docker compose files.
I have 4 splits --- one being my core containers , Homeassistant, Nodered, Mosquitto, etc and then one of them being "applications that I don't need but have".. I recently had to redeploy and my core stack was running in under 10 minutes..

It is a very powerful tool.

Hi great design... If I can suggest one improvement, it would be to burn a minicore bootloader and set BOD to 1.8V so that the batteries can last longer.

Home assistant has a docker container which talks nicely with a mysensors serial gateway connected via USB on a Dell machine.

 homeassistant:
    container_name: hass
    image: homeassistant/home-assistant:stable
    volumes:
      - /home/server/homeassistant/:/config
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0:rwm
    healthcheck:
      test: ["CMD", "curl", "-f", "http://127.0.0.1:8123"]
      interval: 30s
      timeout: 10s
      retries: 6
    network_mode: host
    depends_on: 
      - mosquitto

the following line enables serial gateway into HA and then in the latest release 2021.3 one can add Mysensors from UI

devices:
      - /dev/ttyUSB0:/dev/ttyUSB0:rwm