@jkandasa The weirdest thing.

I added that function with a call at every loop and it makes a new unexistent sensor at the node:

SENSOR_BC HVAC flow (?)

And still won't send the parent EUI.

Don't worry! Is not that important. All works fine. It is my small peeve trying to know my topology.

Thanks!

Works great! Thanks

@guille One thing that took me a while to learn, when in the future you want to upgrade the firmware, there is no need to create a new version. Just edit the same firmware, upload the new .hex, and it will detect that it is new.

@guille Solved! It worked with 2 seconds.

Thanks a lot.

@aliasjim

1. You can add versions, like "1.0", and type "whatever node type you like".

2. Then add firmware. Upload your .hex

3. On the specific node, go to EDIT and assign this firmware.

4. Reboot. By hand or by command.

If you use MQTT you can watch as the new fw is uploading.

@aliasjim That's great!

Just for the record, I compiled all the bootloaders here:

https://github.com/guillebot/MYSensors-Bootloaders

all the channels, for 1, 8 and 16MHz.

@skywatch You can use every channel!

Take a look:

https://github.com/guillebot/MYSensors-Bootloaders

I would be great some form of scanning or automation, but for the moment this will do.

@aliasjim That's great!

Just for the record, I compiled all the bootloaders here:

https://github.com/guillebot/MYSensors-Bootloaders

all the channels, for 1, 8 and 16MHz.

@jkandasa The weirdest thing.

I added that function with a call at every loop and it makes a new unexistent sensor at the node:

SENSOR_BC HVAC flow (?)

And still won't send the parent EUI.

Don't worry! Is not that important. All works fine. It is my small peeve trying to know my topology.

Thanks!

@aliasjim Is it the correct bootloader? I mean check the clock frecuency 8/16MHz, internal vs external resonator/xtal. Also check the fuses, are you using avrdudess to burn the bootloader? I had way better results with it than with arduino ide.

@jkandasa said in Missing Parent EUI:

@guille 2 seconds may eat your sleeping node battery, keep in mind

Indeed. It sucked 2% in less than 4 hours

@jkandasa It "disconnected" again.

Can you make the Parent EUI more permanent in mycontroller.org?

@guille Solved! It worked with 2 seconds.

Thanks a lot.

Bumped it to 2 seconds.

Still no luck.

Should I try bigger values? 5 secs?

@guille One thing that took me a while to learn, when in the future you want to upgrade the firmware, there is no need to create a new version. Just edit the same firmware, upload the new .hex, and it will detect that it is new.

@aliasjim

1. You can add versions, like "1.0", and type "whatever node type you like".

2. Then add firmware. Upload your .hex

3. On the specific node, go to EDIT and assign this firmware.

4. Reboot. By hand or by command.

If you use MQTT you can watch as the new fw is uploading.