Closed alexiszecharies closed 6 years ago
'Same result' means you have this error:
This version of the ESP8266 library is not supported
?
Look in .piolibdeps/ESP8266MQTTMesh_ID1747/src/ESP8266MQTTMesh.cpp
(from wherever your platformio.ini is, and make sure it contains:
#ifndef pgm_read_with_offset //Requires Arduino core 2.4.0
#error "This version of the ESP8266 library is not supported"
#endif
If it doesn't have that, you don't have the right library. If it does have that you still don't have a compatible espressif8266 library.
I did a clean platformio install with features/stage and it does compile for me now. I had issues with the
platform = https://github.com/platformio/platform-espressif8266.git#feature/stage
line, and ended up needing this instead:
platform = espressif8266@4f59cef
I don't know why. platformio seems to make it difficult to point at the libraries I want to use
'Same result' means you have this error: yes.
I could make it compile!!!!!!!!!! I really do not understand the difference between .piolibdeps and .platformio/lib/ where aparently the code was being updated. Will look into this later. I will start with the tests with my code again. Thank you very much!!!!!!!!
I am having this problem with my code
.pioenvs/nossl/lib/libESP8266MQTTMesh_ID1747.a(ESP8266MQTTMesh.o): In function strlcat': ESP8266MQTTMesh.cpp:(.text.strlcat+0x8): multiple definition of
strlcat'
/home/alexis/.platformio/packages/framework-arduinoespressif8266@src-31d658a59f41540201fc3726a1394910/tools/sdk/libc/xtensa-lx106-elf/lib/libc.a(lib_a-strlcat.
o):/Users/igrokhotkov/e/newlib-xtensa/xtensa-lx106-elf/newlib/libc/string/../../../.././newlib/libc/string/strlcat.c:49: first defined here
collect2: error: ld returned 1 exit status
Gonna check it out later. Thank you for your help!
That specific issue should now be fixed. I have an alternate implementation of strlcat in the mesh code. It would collide with the libc variant. I've renamed mine to prevent that error. But please open new issues for things unrelated to the connectivity issue this thread has been about.
Ok, note taken. Today I had little time to do some testing, but after flashing the 3 ESPs and putting my software I could see that the are no disconnections as before and they got a different number for their subdomain in no time. It looks really promising.
I'm closing this issue for now. If you see problems with nodes not properly communicating with the broker, please reopen or file a new ticket.
Continuing this issue https://github.com/PhracturedBlue/ESP8266MQTTMesh/issues/18
Description of problem:
Despite succeeding to delay the broker IP set, when I tried to set the callback as i used to before this fix and testing it in the ESP I am getting this error:
Exception (9): epc1=0x4020dfb5 epc2=0x00000000 epc3=0x00000000 excvaddr=0xfe090016 depc=0x00000000
ctx: sys sp: 3ffffaa0 end: 3fffffb0 offset: 01a0
ets Jan 8 2013,rst cause:1, boot mode:(1,7)
ethets Jan 8 2013,rst cause:4, boot mode:(1,7)
wdt reset
I am referencing the callback at the top as all variables void callback(const char topic, const char msg);
And then implementing it below:
void callback(const char topic, const char msg) { // topic is the command and msg the payload Serial.println(topic); Serial.println(msg); }
This used to work before the fix in the issue. How should I declare the callback to make it global if it is not?