Best posts made by fixjunk

FYI I was able to get the gateway to work properly on a 64 bit Raspberry pi 400 machine.

pi@sixfour:~ $ cat /proc/cpuinfo | grep Model && uname -a
Model		: Raspberry Pi 400 Rev 1.0
Linux sixfour 5.10.5-v8+ #1392 SMP PREEMPT Sat Jan 9 18:56:30 GMT 2021 aarch64 GNU/Linux

I'm not sure if it's required, but installing the bcm2835 v 1.68 (that includes an earlier patch for pi 4) may have helped along with removing the bcm2711 flags from the configure file.

pi@sixfour:~/MySensors $ ./configure  --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttymysgw --my-rf24-ce-pin=22 --my-rf24-cs-pin=24 --my-rf24-irq-pin=15 --my-serial-groupname=dialout --soc=BCM2711
Warning: --my-serial-pty is deprecated, please use --my-serial-port
[SECTION] Detecting SPI driver.
  [OK] SPI driver detected:BCM.
[SECTION] Gateway configuration.
  [OK] Type: serial.
  [OK] Transport: rf24.
  [OK] Signing: Disabled.
  [OK] Encryption: Disabled.
  [OK] CPPFLAGS:  -DMY_RADIO_RF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_GROUPNAME="dialout" -DMY_RX_MESSAGE_BUFFER_FEATURE -DMY_RF24_IRQ_PIN=15 -DMY_RF24_CS_PIN=24 -DMY_RF24_CE_PIN=22 -DMY_LINUX_SERIAL_PORT="/dev/ttymysgw" -DMY_LINUX_SERIAL_IS_PTY 
  [OK] CXXFLAGS:  -std=c++11
[SECTION] Detecting init system.
  [OK] Init system detected: systemd.
[SECTION] Saving configuration.
  [OK] Saved.
[SECTION] Cleaning previous builds.
  [OK] Finished.

granted I have not fully tested this since I do not yet have a radio connected, but I think it went ok.

Jan 28 15:08:50 INFO  Starting gateway...
Jan 28 15:08:50 INFO  Protocol version - 2.3.2
Jan 28 15:08:50 DEBUG Serial port /dev/ttymysgw (115200 baud) created
Jan 28 15:08:50 DEBUG MCO:BGN:INIT GW,CP=RNNGL-Q-,FQ=NA,REL=255,VER=2.3.2
Jan 28 15:08:50 DEBUG TSF:LRT:OK
Jan 28 15:08:50 DEBUG TSM:INIT
Jan 28 15:08:50 DEBUG TSF:WUR:MS=0
Jan 28 15:08:50 DEBUG !TSM:INIT:TSP FAIL
Jan 28 15:08:50 DEBUG TSM:FAIL:CNT=1
Jan 28 15:08:50 DEBUG TSM:FAIL:DIS
Jan 28 15:08:50 DEBUG TSF:TDI:TSL
Jan 28 15:09:00 DEBUG TSM:FAIL:RE-INIT
Jan 28 15:09:00 DEBUG TSM:INIT
Jan 28 15:09:00 DEBUG !TSM:INIT:TSP FAIL

I will plop a radio in this weekend and see if it still works.

Just a small addendum...

I tried swapping my Pi3B+ install into a Pi 400 with the BCM2711 and it did not work.

I needed both the BCM2835 v 1.68 and to remove the flags from the "configure" script BCM2711 section.

@fredswed Honestly, I've moved on to playing with HASS... but I can still share my thoughts.

So there is no practical reason you need to run the MySensors MQTT stuff as OpenHAB can handle all the MQTT messages already without MySensors AddOn--it's just not very convenient to decipher a bunch of five level deep numeric topics that aren't intuitive. I guess I thought I was trying to be clever by doing it all in MQTT style instead of using something else (like Serial).

So what I did when I was switching over to HASS was rebuild the gateway as a serial gateway and avoid the whole conflict. I don't technically need MQTT visibility of the sensors and HASS now autodiscovers the serial sensor gateway sensors just fine. I suspect OpenHAB would do the same.

It's pretty trivial to rebuild the mysgw using serial as long as you're able to make your own /dev/ttyMySensorsGateway accessible by the openhab system (it might require changing owners or groups or both). For whatever reason, mine was root/root and not dialout or accessible to the automation software username. I just changed everything to the tty group and it all worked fine.

The end result of using the serial gateway should be identical within OpenHAB--in theory it should auto discover your sensors and populate them in PaperUI. But I haven't tried or tested it.