@Johhnywalter i don't think so, it's a transceiver only..and the very few IOs may be used for the serial comm (from datasheet for tx,rx).
imho a rf spi module has faster communication (so, more sw freedom for the rf stack) and "easier" to use, as it doesn't need to have a free serial or deal with softserial.
I know I don't give news about this project.
So, maybe I should show you few pics, just in case.. ,)
First, I prefer to say, we can't share code for the moment..not very release-able.
We are using completely custom code for this project. GW code is quite big, mysensors is an experimental version (sort of "v3"). Plus for all the features, sometimes it can need some tweaks in esp32 libs etc. for the moment, sw is still tied to this project&hw.
That said we have lot of neat stuff working, hw choices changed a bit too.
Here we go:
Concept is autonomous simple network without need of a advanced controller, or when linkto/controller is down, that you can control and debug from your phone or computer. With step by step configuration, inclusion etc for easy getting started.
Pics of the app ?? Teasing ON!
The app is realtime and very reactive. Responsive and mobile friendly. This is a single page app. written with Vue, no jquery. lightweight Bulma CSS
I started to make some widgets.. there are also multiple filters for dashboard.
It will also be possible to get infos about network, rssi, stats etc
Lot of settings, I let you imagine them.. there are a few dedicated steps by steps too, handy for starters (like my family, friends..).
It's also possible to see all logs, downloading them, updating app files etc.
Teasing OFF, I prefer to keep some other nice features to show you later 
don't ask for a release date plz, we're busy on lot of projects, but we'll try to do our best! stay tuned 
@henrik-nielsen said in SmartSleep wake up message always get NACK:
if "everyone" uses cheap chinese radios, should this fix be part of the official code base?
simple! add issue or pull request to mysensors github. that's the easiest way when there's issue to fix 
because the team can't follow all forum topics and make todolist, in this way this is not handy.
@TSD
glad to hear i helped you.
you have to work with doxygen and sources
I also have a setup with SNIPS here, and a few different mics (this respeaker model included). I started something for using snips with my mysensors gw..
The snips server is installed on my rpi3 controller for the moment (will maybe use a separate machine or VM, don't know yet), and have two satellites (rpi2 and rpi0).
Yes respeaker hat uses SPI0 for leds, so it may overlap with mysensors default setup. I don't know if it's possible to change mysensors with another spi as I'm not using rpi as gw
(I prefer to have a separate gw so if my controller or something else fails, mysensors still works and I can access it by the phone app or computer, it's more independant&modular).
This rpi hat uses: i2c (2 pins), i2s (4), spi pins (2), user button on IO17, and 12&13 are simply gpio on JST connector. That's 11 pins as they say
On the two spi pins, there are serie resistor that you could remove if you want to use spi0. it will disable leds and you should be fine.
For getting started they recommend this pi Hat, but this not the best mic&dsp hat. Mic&audio processing is very important for voice recognition quality, range etc. There are others, more expensive hat, with better recognition, sensibility.
Still snips is very nice to use, offline and natively handles my language (fr) so that's very sexy. But of course other languages can work by using google cloud speech api.
I've a ghome mini i bought for tests with mysensors too, I like both, it's different use as ghome knows more things. But for long term and privacy I prefer snips of course!
For snips, requirement for server is rpi3 minimum and for the decentralized satellites, a rpi0 is ok.
@berkseo
as OP asked for a end user solution, I can't give a better answer than what I already said.
I didn't say you changed lib nor it doesn't work (in all cases, with signing etc?).
and as you noticed, it works in 2.x. Maybe things will be different for 3.x in future, in case transport layer etc is revamped..
But most important is to use what fit your needs. and of course then to be able to maintain it in long term. less easy for endusers with less programming skills.
Anyway thx for sharing.
@Heizelmann
if node2node not in range, it should try to find a parent I think. but then i've not tested.
@alowhum
I would say this technique is efficient depending on the usecase.
For example, for basic ambiant sensors not needing any security why not. On other side, for main doors which could benefit security, I prefer to use hearbeat with less interval time, so it's possible to know if the sensor is offline. else controller wouldn't know this if the sensor only update when door state change.
@TSD
I've not digged and not time to replicate your setup, but I have a suspicion with wait()
Does it help by using delay() instead of wait().
you won't use wait() if you make your own sleep() I think, and maybe you'll also need to make your custom wait() if needed.
Because wait() purpose is :
When you sleep radio with low level function like you do, then a few vars may be not updated in mysensors machine (like transportActive I think)
So mysensors machine does not know you disabled/slept the radio (whereas when using mysensors and sleep in regular way it knows it of course).
Then when you call wait(), mysensors machine will try to check link (as the state variable has not been updated), link check fails and then it reinit radio. no sleep!
Not checked on my side, but it could be that
@TSD
it's more clear now, because with the stripped version it could have been lot of other things
you'll need to make your own sleep function. because for the moment, powerdown mode only is available in MySensors. and as you may know it's not good for your timer2 (you need powersave mode).
@tsd
afaik mysensors is not using timer2.
could you show us you logs plz? gw logs as well.
also, what is your hardware for the gw and node?
I've no time to test on my side, but what happens, for test, when you enable mysensors and blink your led from your isr (not from the loop)