@hek said:

@ximinez

You can add a before()-method.

It's that easy? I'll give it a try when I get around to it, unless @alexsh1 feels like trying it first

Is there a "pre setup" available yet? The failed transmits are before sensor values are transmitted, so they aren't in the actual sketch but somewhere in the library. I'd like to try just sleeping the sensor 5-10 seconds before the initial data is transmitted and see if that makes a difference.

I just ignore the first fails. It works after that, and has done so for close to a month.

I'm seeing the same failed signings when the device powers up, but it doesn't fail after those.

@FotoFieber said:

@Anticimex said:

@FotoFieber with a SenseBender, there is no reason for soft signing. It should have a ATSHA204A chip. But nice that you have working setup

Yes, but encryption and ATSHA204A is to big for the SenseBender...

Old thread, but... In the dev branch, there's a RF24 refactor that is much smaller. With that, and removing test-mode, there's plenty of space on the sensebender:

#define MY_RADIO_NRF24
#define MY_SIGNING_ATSHA204
#define MY_SIGNING_REQUEST_SIGNATURES
#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = GATEWAY_ADDRESS,.serial = {0xBO,0xGU,0xSK,0xEY,0xZZ,0xFC,0xAD,0x04,0xD1}}}
#define MY_OTA_FIRMWARE_FEATURE
#define MY_RF24_ENABLE_ENCRYPTION

Sketch uses 23,196 bytes (75%) of program storage space. Maximum is 30,720 bytes.
Global variables use 1,386 bytes (67%) of dynamic memory, leaving 662 bytes for local variables. Maximum is 2,048 bytes.

Even with debug it's only at 91%.

My W5100 gateway ends up at 107% with AES though, but it fits (with 592 bytes to spare) if I use a static address instead of DHCP.
Serial Gateway ends up at only 65%.

Both soft and hard SPI work on my cheap W5100 clone shield (with SD).

@tekka said:

@ximinez Just tested your setup/settings using an Arduino UNO + W5100 shield and I can confirm, that SOFTSPI (A2=MISO, A1=MOSI, A0=SCK, D6=CSN, D5=CE) and HWSPI (D12=MISO, D11=MOSI, D13=SCK, D6=CSN, D5=CE + #define MY_W5100_SPI_EN 4) work with the refactored RF24 driver.

Please double check you are using the most recent MySensors 2.0.0-beta lib and GatewayW5100 sketch.

I just did (for the second time), and lo and behold it works. Absolutely no clue why, but I'm sorry I've wasted your time.

My gateway can finally have DHCP and signing at the same time

#define MY_DEBUG
#define MY_RADIO_NRF24
#define MY_DEBUG_VERBOSE_RF24
#define MY_GATEWAY_W5100
#define MY_SIGNING_SOFT
#define MY_SIGNING_REQUEST_SIGNATURES
#define MY_RF24_CE_PIN 5
#define MY_RF24_CS_PIN 6

Using an UNO with an ethernet shield, wired up like this: https://www.mysensors.org/build/ethernet_gateway
A2 MISO
A1 MOSI
A0 SCK
6 CSN
5 CE

Yes. When I say that I haven't changed the pins, I mean that I haven't changed the physical pins (or the CE/CSN numbers in my sketch) compared to when the same setup worked with the previous RF24 driver.

I love the difference in available space the new driver gives, but I'd love it even more if the radio continued to work

I updated to dev branch yesterday, and on my W5100 gateway the radio now fails to initialize:

0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0-beta)
0;255;3;0;9;write register, reg=0, value=6
0;255;3;0;9;write register, reg=3, value=3
0;255;3;0;9;write register, reg=4, value=95
0;255;3;0;9;write register, reg=5, value=76
0;255;3;0;9;write register, reg=6, value=35
0;255;3;0;9;read register, reg=6, value=255
0;255;3;0;9;read register, reg=6, value=255
0;255;3;0;9;Sanity check failed: RF_SETUP register=255 instead of 35, check wiring, replace module or non-P version
0;255;3;0;9;Radio init failed. Check wiring.

I've tried three different (confirmed working on my sensebender micro) radios, I've quadruple-checked my wiring, and I haven't changed the pins. So something is funky after the RF24 refactor.