@anticimex I was no talking about the hardware specs, but about the limitations you have with each choice of hardware as mysensor gateway

@anticimex said in Best hardware for gateway with encryption and signing:

SenseBender gateway

There should be a table with all the features of each gateway so people can choose easily.

I am looking for Gateway that will get me the results to MQTT but will support encryption + signing. That mean it should be easy to add new signatures (recompile/reflash) the module

I suppose if I use Sensebender with LAN module it will be a pain to do that

Is this doable if I use Orange zero as USB host for the Sensbender and let it act as serial gateway, then convert serial to mqtt with software on the Linux side? Also is it possible to reflash it easily this way? I do not want to rewire the hardware each time a add new node.

Well, I avoided the MEGA board as it requires USB connection with PC to recompile when whitelisting new nodes. I have RPi3 close to it, if I can recompile the MEGA from the PI without physical intervention (changing cables/ removing LAN module) then I might try that way...but anyone with such setup?

I really like the MySensors concept and was experimenting with it for some time using Arduino UNOs as Gateway and nodes. Then I wanted signing and encryption and UNO was too lite for it. Then I went or Orange Zero as it will provide me option to use SSH for including new signatures and easy recompile. I also prefer MQTT.

Now I am stuck. I can not make signing nor encryption to work on the Orange. Is it really supported? I found an old post that for Raspberry it is not available yet.

Does Sensebender will do it? Will MQTT work with Ethernet shield?

Had anyone succeeded using signing+encryption on OrangePi MQTT gateway? I managed to make Arduino gateway and it worked but I can not replicate the same thing with Pi. What file should be edited to enter the keys? and the whitelist?

NOTE for Armbian and Orange Pi Zero.

Set static IP address or the device will lose connection on next DHCP request. I use only the LAN and was having problems for few days.

Before using wireless technology in my automation system I was building MQTT Arduino nodes with Ethernet.

I like MySensors as a platform and want to unify the code I have on my nodes so I am considering reflashing those (3 at the moment) Arduinos and use MySensors.

What I have in mind is having more Arduino gateways without antennas that will have own mqtt topic and have sensors attached directly in them. I do not know how much work it will be to remove the code for chechking the NRF module at startup.

The other option is to have code of a node but I will need to add mqtt client code so it might be a lot of work to go that route.

Has anyone considered something like this? Standalone node/gateway with local sensors only with own Ethernet module for MQTT communication?

This should be in the wiki

root@pi0:~/MySensors# ./configure --help
configure script for MySensors gateway.
Options:

Help:
    -h, --help                  print this message

SPI driver options:
    --spi-driver=[BCM|SPIDEV]
    --spi-spidev-device=<DEVICE>
                                Device path. [/dev/spidev0.0]

Building options:
    --soc=[BCM2835|BCM2836|BCM2837|AM33XX|A10|A13|A20|H3]
                                SoC type to be used. [configure autodetected]
    --cpu-flags=<CPUFLAGS>      CPU defining/optimizing flags to be used. [configure autodetected]
    --extra-cflags=<CFLAGS>     Extra C flags passed to C compilation. []
    --extra-cxxflags=<CXXFLAGS> Extra C++ flags passed to C++ compilation. []
    --extra-ldflags=<LDFLAGS>   Extra C flags passed to linking. []
    --c_compiler=<CC>           C compiler. [arm-linux-gnueabihf-gcc][gcc]
    --cxx_compiler=<CXX>        C++ compiler. [arm-linux-gnueabihf-g++][g++]
    --build-dir=<DIR>           Compiler directory to store object files. [build]
    --bin-dir=<DIR>             Compiler directory to store binary files. [bin]
    --arduino-lib-dir=<DIR>     Arduino library directory.
    --no-clean                  Don't clean previous build artifacts.

Installation options:
    --prefix=<PREFIX>           Installation prefix path. [/usr/local]
    --gateway-dir=<DIR>         Gateway files installation directory. [PREFIX/bin]

MySensors options:
    --my-debug=[enable|disable] Enables or disables MySensors core debugging. [enable]
    --my-config-file=<FILE>     Config file path. [/etc/mysensors.dat]
    --my-gateway=[none|ethernet|serial|mqtt]
                                Set the protocol used to communicate with the controller.
                                [ethernet]
    --my-node-id=<ID>           Disable gateway feature and run as a node with the specified id.
    --my-controller-url-address=<URL>
                                Controller or MQTT broker url.
    --my-controller-ip-address=<IP>
                                Controller or MQTT broker ip.
    --my-port=<PORT>            The port to keep open on gateway mode.
                                If gateway is set to mqtt, it sets the broker port.
    --my-serial-port=<PORT>     Serial port. [/dev/ttyACM0]
    --my-serial-baudrate=<BAUD> Serial baud rate. [115200]
    --my-serial-is-pty          Set the serial port to be a pseudo terminal. Use this if you want
                                to connect to a controller running on the same device.
    --my-serial-pty=<NAME>      Symlink name for the PTY device. [/dev/ttyMySensorsGateway]
    --my-serial-groupname=<GROUP>
                                Grant access to the specified system group for the serial device.
    --my-mqtt-client-id=<ID>    MQTT client id.
    --my-mqtt-user=<UID>        MQTT user id.
    --my-mqtt-password=<PASS>   MQTT password.
    --my-mqtt-publish-topic-prefix=<PREFIX>
                                MQTT publish topic prefix.
    --my-mqtt-subscribe-topic-prefix=<PREFIX>
                                MQTT subscribe topic prefix.
    --my-transport=[none|nrf24|rs485|rfm95|rfm69]
                                Set the transport to be used to communicate with other nodes.
                                [nrf24]
    --my-rf24-channel=<0-125>   RF channel for the sensor net. [76]
    --my-rf24-pa-level=[RF24_PA_MAX|RF24_PA_LOW]
                                RF24 PA level. [RF24_PA_MAX]
    --my-rf24-ce-pin=<PIN>      Pin number to use for rf24 Chip-Enable.
    --my-rf24-cs-pin=<PIN>      Pin number to use for rf24 Chip-Select.
    --my-rf24-irq-pin=<PIN>     Pin number connected to nRF24L01 IRQ pin.
    --my-rf24-encryption-enabled
                                Enables RF24 encryption.
                                All nodes and gateway must have this enabled, and all must be
                                personalized with the same AES key
    --my-rx-message-buffer-size=<SIZE>
                                Buffer size for incoming messages when using rf24 interrupts. [20]
    --my-rfm69-frequency=[315|433|868|915]
                                RFM69 Module Frequency. [868]
    --my-is-rfm69hw             Enable high-powered rfm69hw.
    --my-rfm69-irq-pin=<PIN>    Pin number connected to RFM69 IRQ pin.
    --my-rfm69-cs-pin=<PIN>     Pin number to use for RFM69 Chip-Select.
    --my-rs485-serial-port=<PORT>
                                RS485 serial port. You must provide a port.
    --my-rs485-baudrate=<BAUD>  RS485 baudrate. [9600]
    --my-rs485-de-pin=<PIN>     Pin number connected to RS485 driver enable pin.
    --my-rs485-max-msg-length=<LENGTH>
                                The maximum message length used for RS485. [40]
    --my-leds-err-pin=<PIN>     Error LED pin.
    --my-leds-rx-pin=<PIN>      Receive LED pin.
    --my-leds-tx-pin=<PIN>      Transmit LED pin.
    --my-leds-blinking-inverse  Inverse the blinking feature.
    --my-signing=[none|software|password]
                                Message signing. [none]
    --my-signing-debug          Enable signing related debug.
    --my-signing-request-signatures
                                Enable signature request from nodes that in turn requested
                                gateway signature.
    --my-signing-weak_security  Enable this to permit downgrade of security preferences and
                                relaxed gateway signing requirements.
    --my-signing-password=<PASSWORD>
                                If you are using password as the signature type, set your password here.

root@pi0:~/MySensors# sudo ./bin/mysgw -h
mysgw: Config file /etc/mysensors.dat does not exist, creating new config file.
Usage: mysgw [options]

Options:
  -h, --help                 Display a short summary of all program options.
  -d, --debug                Enable debug.
  -b, --background           Run as a background process.
  --gen-soft-hmac-key        Generate and print a soft hmac key.
  --gen-soft-serial-key      Generate and print a soft serial key.
  --gen-aes-key              Generate and print an aes encryption key.
  --print-soft-hmac-key      Print the soft hmac key from the config file.
  --print-soft-serial-key    Print the soft serial key from the config file.
  --print-aes-key            Print the aes encryption key from the config file.
  --set-soft-hmac-key        Write a soft hmac key to the config file.
  --set-soft-serial-key      Write a soft serial key to the config file.
  --set-aes-key              Write an aes encryption key to the config file.

@Anticimex said in Building a Orange Pi Gateway:

@8667 no, it won't. As it is for the moment, whitelisting works no different compared to Arduino based devices. You will have to recompile your GW if you add new nodes as you will need to add their serials to the whitelist in the GW.

So how personalization works on the orange and how to pass the list of serials?