OTA updates on Arduino Nano

[tekka]

@mvader said:

mine does this as well.
It seems like (to me anyways)
that when i had everything on 1.4 it worked well.
but once i moved all my stuff over to the 1.5 lib, this stuff didn't play nice anymore.
hoping that once @tekka releases the new app, it will solve some of those issues.

Didn't you mention in one of your posts that some nodes were having different lib versions?

[mvader]

@tekka said:

@mvader said:

mine does this as well.
It seems like (to me anyways)
that when i had everything on 1.4 it worked well.
but once i moved all my stuff over to the 1.5 lib, this stuff didn't play nice anymore.
hoping that once @tekka releases the new app, it will solve some of those issues.

Didn't you mention in one of your posts that some nodes were having different lib versions?

I have everything on 1.5 stable now.
but i do notice that i have to constantly disconnect / connect in MYSController
I know that the controller and nodes still work, because lights (in my house) turn on and off. but no data is displayed in the controller screen.. i have to D/C
same with firmware update. they go so far and then stop.. i have to D/C
i have a nano with MYSBootloader acting as a 433 bridge and repeater, it does that (above screen shot) all the time. I'm using the 1.1 v of the bootloader.
it felt like things worked much better on 1.4 lib with the MYSController.

[tekka]

@mvader are you using serial or tcp/ip to connect the gw? can you post the myscontroller log (ideally with debug on) when those things happen?

[rvweert]

Hi Tekka,

Please see here my log:
MySensors_20151109-085110.log

Also yes, all my nodes are running the same version from git.

Cheers,

Rene

[Oitzu]

@rvweert: i see no bootloader involved. Could you try to add an wdt_reset(); at the beginning of the setup() routine?

[rvweert]

Hi Oitzu,

Just tried that, same result...

[rvweert]

No more news on this?;-)

[Oitzu]

@rvweert out of ideas by simply looking at the logs.
Maybe @tekka knows anything.
Did you try to enable debug on the node and look at the nodes output?

[tekka]

@rvweert I'll look into that in a little bit.

[tekka]

@rvweert there is potentially an id conflict: was the node previously used as gateway? Anyhow, try clearing the eeprom with the ClearEepromConfig sketch and upload the log again.

[rvweert]

Hey Tekka,

Tried clearing both eeproms, still same problem. Actually tried two completely new nano's and same problem again...

[tekka]

@rvweert Looking at the logs, there is no bootloader involved (@Oitzu already confirmed this).
This looks like a bad nRF chip and/or power issues (try with different a cap) since the msgs sent from the GW never reach the node.

[tekka]

@rvweert MY_OTA_FIRMWARE_FEATURE enabled in MyConfig.h? This seems to be the cause of the restarting nodes. Try disabling this option unless you are using the sensebender board...

[rvweert]

@tekka I checked but MY_OTA_FIRMWARE_FEATURE wasn't enabled. Also I tried Mysensors 1.4.1 and 1.5.2 but same result. Can't get it to work;-(