🐞 [Bug]: Node Name Updates Don't Reflect in App without Restarting

[Xaositek]

Firmware Version

2.5.18 (1355)

What did you do?

I changed the "Owner" name is a node and noticed even after multiple hours the application doesn't reflect the update in my node list.

Old Name:

New Name:

Expected Behavior

As NodeInfo updates are received by the radio, name updates are immediately reflected in the app

Current Behavior

As NodeInfo updates are received by the radio, name updates are only updated if you force close the app and restart it.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[thebentern]

@Xaositek what happens if you disconnect / reconnect BLE? I'm wondering if I need to send the owner info back up over the PhoneAPI

[Xaositek]

Confirmed a BLE disconnect / reconnect also works to fix it

[Xaositek]

Also noticed owner short name experiences the same issue

[madeofstown]

@Xaositek what happens if you disconnect / reconnect BLE? I'm wondering if I need to send the owner info back up over the PhoneAPI

With firmware v2.5.20 (and I'm sure earlier as well) nodes automatically reboot after a name change which would trigger a Bluetooth disconnect/reconnect. Did this change in a more recent firmware?

[madeofstown]

Also, there are known issues with v2.5.18 and the router_late role

[Xaositek]

@Xaositek what happens if you disconnect / reconnect BLE? I'm wondering if I need to send the owner info back up over the PhoneAPI

With firmware v2.5.20 (and I'm sure earlier as well) nodes automatically reboot after a name change which would trigger a Bluetooth disconnect/reconnect. Did this change in a more recent firmware?

This is not about the directly connected node, this is about nodes in the node list

[madeofstown]

@Xaositek what happens if you disconnect / reconnect BLE? I'm wondering if I need to send the owner info back up over the PhoneAPI

With firmware v2.5.20 (and I'm sure earlier as well) nodes automatically reboot after a name change which would trigger a Bluetooth disconnect/reconnect. Did this change in a more recent firmware?

This is not about the directly connected node, this is about nodes in the node list

A change of a nodes name should still trigger a reboot whether it is connected to your phone or remotely administered or administered by somebody else... When a node boots up it should send out it's node information. I guess I'm missing something here...

I just tested this with a remotely administered node and it did TX it's new node name. Remote node was v2.5.12. RX node is v2.5.20. Android app version 2.5.17. I can do more testing this evening.

I'm wondering if this bug report needs to go in the iOS-app repo.