💬 Sensebender Gateway

[Fabien]

@tbowmo : with wich RFM69 driver ?

[tbowmo]

@Fabien legacy, unless you would reflash all your nodes with the new driver as well. (they are not compatible)

[Fabien]

@tbowmo : Just flash my SBGW today with arduino 1.8.5, last boards.txt and dev branch of mysensors.
We will see if it's more stable. All my Node still in 2.1.1

[stefaanv]

Which driver to use on Ubuntu 16.04 ?

[stefaanv]

Hi, I'm trying to activate a sensebender gateway in OH2 on Ubuntu 16.04, however I'm having trouble setting up the serial port. Is there a how-to somewhere ? I suspect the serial port name is /dev/ttyACM0, but I'm not sure. How can I test ?
MySensors bundle is reported to be active, but there's no messages coming in. I set the log level for mysensors to DEBUG, but nothing on the log.

[stefaanv]

Here is my configuration file (mysensors.things)
Bridge mysensors:bridge-ser:gateway [ serialPort="/dev/ttyACM0", sendDelay=200 ]
{
humidity keuken_vochtigheid [ nodeId="3", childId="2", smartSleep=true ]
temperature keuken_temperatuur [ nodeId="3", childId="1", smartSleep=true ]
}

I suppose ttyACM0 because of
stefaan@home:~$ dmesg |grep -i tty
[ 0.000000] console [tty0] enabled
[ 22.328631] 8086228A:00: ttyS4 at MMIO 0x81420000 (irq = 39, base_baud = 2764800) is a 16550A
[ 22.329059] 8086228A:01: ttyS5 at MMIO 0x8141e000 (irq = 40, base_baud = 2764800) is a 16550A
[ 23.106128] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
[362074.592743] cdc_acm 1-3:1.0: ttyACM0: USB ACM device

There seems to be a premissions problem om the port :
stefaan@home:~$ cat /dev/ttyACM0
cat: /dev/ttyACM0: Permission denied

doing 'sudo usermod -a -G dialout openhab' doesn't help

Anyone any ideas ?

[stefaanv]

ttyUSB0 is a (different) RFXcom device

[zboblamont]

@stefaanv I can only suggest scanning the ports. When I connected the Gateway to the Pi3 it came up with /dev/ttyS0 instead of the listed options, although I ultimately ended up changing to a Pro-Mini as the radio did not work, and connected direct to the GPIO the serial port it worked with.

[tbowmo]

it should pop up as ttyACM0 or ttyACM1 (if you have another usb device that enumerates first and gets ttyACM0)

I added the following to /etc/udev/rules.d/10-local.rules file:

ACTION=="add", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="6949", SYMLINK+="ttyNRF24"

What that does is to create a symlink from the real device to ttyNRF24, so regardless of what I add to my rPI, i always know that ttyNRF24 is for my gateway.

(and then I use /dev/ttyNRF24 for the serial port in my controller)

[stefaanv]

@tbowmo Definately ttyACM0
However, the setserial command returns information that doesn't look good : port0 and IRQ0. Does the board need a driver under Linux ?

stefaan@home:~$ sudo setserial /dev/ttyACM0
/dev/ttyACM0, UART: unknown, Port: 0x0000, IRQ: 0, Flags: low_latency```

[tbowmo]

@stefaanv

No, it doesn't need a driver..

I get the same for mine, if I use setserial:

thomas at jarvis in ~ 
>sudo setserial /dev/ttyNRF24 
/dev/ttyNRF24, UART: unknown, Port: 0x0000, IRQ: 0, Flags: low_latency
thomas at jarvis in ~ 
>ll /dev/ttyNRF24 
lrwxrwxrwx 1 root root 7 nov 11 13:39 /dev/ttyNRF24 -> ttyACM1

Btw. the permission problem.. You are logged in using your normal user (stefaan) and then you set permissions for openhab user? (see below). Have you tried setting the permissions for your user, and then cat /dev/ttyACM0?

@stefaanv said in 💬 Sensebender Gateway:

There seems to be a premissions problem om the port :
stefaan@home:~$ cat /dev/ttyACM0
cat: /dev/ttyACM0: Permission denied

doing 'sudo usermod -a -G dialout openhab' doesn't help

Anyone any ideas ?

[stefaanv]

@tbowmo OK, is working now after restarting the bundle in OH.
Must have been the permission problem after all.
Thanks for your help !!

[rzylius]

When I try to compile SensebenderGW sketch with signing features, I receive a bunch of errors. What am I missing?

Arduino: 1.8.5 (Windows Store 1.8.10.0) (Windows 10), Board: "Sensebender Gateway"

In file included from C:\Users\rzylius\AppData\Local\Temp\arduino_modified_sketch_737033\SensebenderGatewaySerial.ino:88:0:

C:\Users\rzylius\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:6:16: error: redefinition of 'uint8_t device_pin'

static uint8_t device_pin;

            ^

In file included from C:\Users\rzylius\Documents\Arduino\libraries\MySensors/MySensors.h:131:0,

             from C:\Users\rzylius\AppData\Local\Temp\arduino_modified_sketch_737033\SensebenderGatewaySerial.ino:86:

C:\Users\rzylius\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:6:16: error: 'uint8_t device_pin' previously declared here

static uint8_t device_pin;

            ^

In file included from C:\Users\rzylius\AppData\Local\Temp\arduino_modified_sketch_737033\SensebenderGatewaySerial.ino:88:0:

C:\Users\rzylius\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp: In function 'void swi_set_signal_pin(uint8_t)':

C:\Users\rzylius\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:24:13: error: redefinition of 'void swi_set_signal_pin(uint8_t)'

static void swi_set_signal_pin(uint8_t is_high)

         ^

In file included from C:\Users\rzylius\Documents\Arduino\libraries\MySensors/MySensors.h:131:0,

             from C:\Users\rzylius\AppData\Local\Temp\arduino_modified_sketch_737033\SensebenderGatewaySerial.ino:86:

C:\Users\rzylius\Documents\Arduino\libraries\MySensors/drivers/ATSHA204/ATSHA204.cpp:24:13: error: 'void swi_set_signal_pin(uint8_t)' previously defined here

static void swi_set_signal_pin(uint8_t is_high)

         ^

and the same type of errors reoccurs multiple times.

[Anticimex]

@rzylius I think you have an #include in the sketch for the atsha driver. Try to remove that #include from the sketch.

[rzylius]

@Anticimex yes, when I delete #include atsha driver line, it compiles well. thanks.

[Fabien]

@tbowmo After 2 month on the dev version, no more problem with the gateway. Perhaps it's time to made a new stable release ?

[tbowmo]

@Fabien

It's on the todo list.. :)

[8667]

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.

[tbowmo]

@8667

Is it over the air encryption / signing that you are aiming after? Then that is possible with the gateway, it has the ATSHA204 onboard for signing capabilities. And it also works with the W5100 module attached. The Gateway have 256Kb of flash onboard, so it has "enough" room for both network stack, and signing.

[rzylius]

Are there performance limitations to be considered for mysensors and SensebenderGW specifically. Will the gateway handle the load of signed communications if rules will be firing messages to different sensors like 1-2-5-10 per second?