davef wrote: ↑
Thu Dec 24, 2020 4:45 am
For the examples given:
- missing : after if statement<br/>
Thanks for picking that up - I'll fix docs in next commit.
lines 13 and 17 seemed to work better with (peer, str, True)
I'll look into that. On the ESP32 it is *supposed* to work with just 'msg' as argument, (not on ESP8266 - due to need to compress the code size) but I may have broken something here - I'll investigate.
seemed to work better with a value in init() Also, need to work out how to get the msgs
It *should* not be necessary to provide an argument to init(), but on the ESP8266 you can provide the read buffer size as an argument - as there is NO config() call on the 8266 (because the code size requirements are too tight) (see my docs). 100 bytes seems small for the buffer size.
An example of how to grab the messages using a ESP8266 would be appreciated.
As inidcated in the docs, the only method for receiving messages on the ESP8266 is irecv(). I recommend leaving the default buffer size: ie. **e.init()** and then **e.irecv()** should work fine.
(I am away from my esp32s for a few days, so can't absolutely verify everything definitively - but all this was working for my tests a few days ago).
If using the esp8266 check my docs to confirm which calls are available on the 8266.