{DEV} Multi-Sensor Node goes into boot loop
-
Thanks for looking into this with me. I had some more luck believe it or not after upgrading to 2.0.0 on my Gateway. Using the same sketch as I posted for my node, and updating my ESP8266 Gateway to the 2.0 sketch solved the reboot issue. Only problem now is the DallasTemperature sensor does not seem to be registering with the gateway.
Of curious notice, when I looked through the example sketches in the new MySensors 2.0 Library, i did not see an example sketch for the DallasTemperature sensors this time around.
@drock1985 I had similar problems with the failure messages. After an upgrade of my repeater it functions again. Development seems to have some issues with backward compatibility. Hard to reproduce the errors..
-
@drock1985 I had similar problems with the failure messages. After an upgrade of my repeater it functions again. Development seems to have some issues with backward compatibility. Hard to reproduce the errors..
-
@rollercontainer said:
TSP:CHKUPL:FAIL (hops=255) !TSM:UPL:FAILDid you end up finding what was the problem?
I have the same errors on new nodes compiled with the stable release. It was working fine on the dev branch before, and my old sensors still works, but not the new ones...Edit:
I had to revert to https://github.com/mysensors/MySensors/tree/244f79771acb60588c6b4fd6dd0fa4b5daf4cb64
June 26th commit break everything for me. Unfortunately a lot of changes were made this day... -
read above again:
Gateway 2.0.0beta with Node 2.0.0 = UPL:FAIL (which means UPLink)
Gateway 2.0.0 with Node 2.0.0 = FPAR:FAIL (which means FindPARent)my error is reported to github, maybe you should do this too with yours?
https://github.com/mysensors/MySensors/issues -
Oh, so just switching from beta to 2.0 master "fixed" UPL:FAIL by switching it to a FPAR:FAIL?
I thought you did some fixes and then ended up with another error, my bad. Github it is I guess... -
I am not a coder, just a user. So I am not able to fix errors here.
-
@rollercontainer said:
TSP:CHKUPL:FAIL (hops=255) !TSM:UPL:FAILDid you end up finding what was the problem?
I have the same errors on new nodes compiled with the stable release. It was working fine on the dev branch before, and my old sensors still works, but not the new ones...Edit:
I had to revert to https://github.com/mysensors/MySensors/tree/244f79771acb60588c6b4fd6dd0fa4b5daf4cb64
June 26th commit break everything for me. Unfortunately a lot of changes were made this day...@emc2 said:
@rollercontainer said:
TSP:CHKUPL:FAIL (hops=255) !TSM:UPL:FAILDid you end up finding what was the problem?
I have the same errors on new nodes compiled with the stable release. It was working fine on the dev branch before, and my old sensors still works, but not the new ones...Edit:
I had to revert to https://github.com/mysensors/MySensors/tree/244f79771acb60588c6b4fd6dd0fa4b5daf4cb64
June 26th commit break everything for me. Unfortunately a lot of changes were made this day...Thank you, had the same problem, replaced it with the files from the 26th and got it working.
-
@mitchell Glad it was useful.
Do you also have a Raspberry Pi Gateway with the radio module directly on the GPIO? It seems the problem come from here, issue can now be tracked on https://github.com/mysensors/Raspberry/issues/31Also if needed you can replace core/MyHwESP8266.h and core/MyMainESP8266.cpp with the release version so you can use an ESP8266 device too.
-
@mitchell Glad it was useful.
Do you also have a Raspberry Pi Gateway with the radio module directly on the GPIO? It seems the problem come from here, issue can now be tracked on https://github.com/mysensors/Raspberry/issues/31Also if needed you can replace core/MyHwESP8266.h and core/MyMainESP8266.cpp with the release version so you can use an ESP8266 device too.
