@tekka

Fortunately a helpful guy gave me your bootloader 1.3 beta, which fixes the problem with nonworking bootloader commands. It seems I was not the first one asking you...

For all others trying the bootloader commands in bootloader 1.1 : this does not work at all, and you are only wasting your time.

I would really appreciate if the code for bl 1.3 was on github also. I do not mind if its beta only...

Below the working debug output for a reassign nodeid 8 --> nodeid 88

16.01.2016 23:06:46	RX	8;255;3;0;9;0108A000B9F7FFFEDA7221F0001E950F09
16.01.2016 23:06:48	RX	0;0;3;0;9;read: 8-8-0 s=255,c=4,t=0,pt=6,l=10,sg=0:1E00010048047AA801
16.01.2016 23:06:48	INFO	BL version=259
16.01.2016 23:06:48	INFO	Executing bootloader command section
16.01.2016 23:06:48	TX	8;255;4;0;1;0200580000007ADA
16.01.2016 23:06:48	RX	8;255;4;0;0;1E00010048047AA80103
16.01.2016 23:06:48	RX	0;0;3;0;9;send: 0-0-8-8 s=255,c=4,t=1,pt=6,l=8,sg=0,st=ok:02005800000
16.01.2016 23:06:48	RX	0;0;3;0;9;read: 88-88-255 s=255,c=3,t=7,pt=1,l=1,sg=0:0

@tekka
Can you verify it works for you? Do you see any response packets with the bl commands in your log?

@tekka
No repeater, clear eeprom via MYSController gui does not work. Clear eeprom via sketch works, node gets new id after reboot.
My assumption is that MYSController does not respond to the FW_CONFIG_REQU after reboot.

Has anyone tested successfully reassigning the node-id with MYSBootloader 1.1 and MYSController 1.2.282 ? Would give me some new motivation to hear it's possible and has been done before. At the very moment I m at a dead end.
If it is not working for you, I would also appreciate your feedback.

@tekka : I tested the ID reassign by hardcoding the functionality in the serial gw sketch. Reboot node 6, wait for FW_CONFIG_REQUEST, answer with FW_CONFIG_RESPONSE.

Works as expected & described in the MYSBootloader code. Please give me some hint why MYSController does not send the FW_CONFIG_RESPONSE packet with the bootloader commands after the reboot.

I trigger the reassign via the node´s context menu in the gui, MYSBootloader Commands --> reassign ID. Anything wrong with that ?

Maybe someone else has an idea what is happening/not happening ? @tekka could you find something in the log file?

Thanks a lot...

and also a ss for another reassign attempt node 6--> 12.
FIRMWARE_CONFIG_REQUEST is not answered from myscontroller. therefore no reassign of node id.

MySensors_20160110-115615_stebra.log

hi tekka,

here is the log. Contains:

[2016-01-10 12:02:26.390 Info] INFO *** Logging START *** // stebra : succesful reboot of node 6 via myscontroller

[2016-01-10 12:02:59.000 Info] INFO *** Logging START *** // stebra : succesful FW update of node 6 via myscontroller

[2016-01-10 12:05:35.109 Info] INFO *** Logging START *** // stebra : ID reassign attempt of node 6 to node 12 via myscontroller
[2016-01-10 12:05:48.328 Info] INFO Send FW info to node 6: type=1E, version=1, blocks=0x0448, CRC=0xA87A // here the behaviour is unexpected for me

[2016-01-10 12:06:37.437 Info] INFO *** Logging START *** // stebra: Clear eeprom attempt on node 6
[2016-01-10 12:06:44.812 Info] INFO Send FW info to node 6: type=1E, version=1, blocks=0x0448, CRC=0xA87A // here the behaviour is unexpected for me

thank you for having a look..

Hi @tekka,

tried now some evenings to change node-id / clear the eeprom. No luck. FW update works always. After reading the bootloader code I expected myscontroller to send a invalid fwrequestresponse packet with special crc for the bootloader commands. Never showed up in the log.
Myscontroller .282 on Win xp and msbootloader 1.1 on nano. 47uF on nrf. No transmission errors.

Any ideas where to look next ? Maybe .278 will do the trick ?

Thanks for your efforts ,
stebra