Errors after updating to MQTTController build 25139

[3rdStng]

Hubitat C7 = 2.3.2.141 AND 2.3.3.123
MSR in a docker = latest-22264-93bf3814 and latest-22266-88868fc0

I'm curious if this is a bug or expected behavior. Unfortunately I don't know exactly when this began either. I have renamed a few devices over the course of the last few MSR builds, but never really brought it up before. Plus I don't rename devices too often. But I have a motion sensor right now that I renamed in Hubitat from "Office Motion" to "Living Room Motion" over 2 weeks week ago. Probably closer to 3 or 4 weeks now. I have restarted MSR several times since the rename, hard refreshed the browser, tried a different machine and different browser, and even an updated version of MSR. MSR is still showing the old name within the Entities section. I know I could rename it within MSR, but I would prefer to only have to rename devices in one location. I don't recall how long ago I started noticing this, which I know does not help at all.

[toggledbits]

@3rdstng "label" takes priority over "name":

[3rdStng]

@toggledbits said in How does MSR handle renamed entities?:

"label" takes priority over "name":

That makes sense, however the device label was updated within Hubitat. Should this update be pulled into MSR too?

EDIT: As a test, I renamed the Device Name and Label within Hubitat. Restarted my MSR docker and hard refreshed the page.

[toggledbits]

If you delete the entity (in MSR) and restart MSR, does it come up with the correct, updated name?

[3rdStng]

@toggledbits said in How does MSR handle renamed entities?:

If you delete the entity (in MSR) and restart MSR, does it come up with the correct, updated name?

Yes. I get the new device notice. Along with any existing rules that may now be broken. The hub device ID is still the same though. Should these remap or are they linked by the name and not the ID?

I renamed another contact sensor since I am looking into using it in a different spot I originally was thinking.

EDIT: I went to the rule and the entity was referenced properly. The Expression was self corrected when I clicked on the "Try this expression" button. I guess things weren't as broken as I originally thought, but I needed to touch each (rule & expression).

[toggledbits]

@3rdstng said in How does MSR handle renamed entities?:

I guess things weren't as broken as I originally thought, but I needed to touch each (rule & expression).

A second restart would also resolve it, without the need to touch each thing.

I think your result gives me my answer. Update coming this weekend.

[3rdStng]

@toggledbits said in How does MSR handle renamed entities?:

A second restart would also resolve it, without the need to touch each thing.

Thx. Yes it does. I deleted my other renamed object and restarted. The initial errors appeared, cleared them and restarted again. No errors returned.

@toggledbits said in How does MSR handle renamed entities?:

Update coming this weekend.

Awesome. Thank you.

[3rdStng]

@toggledbits said in How does MSR handle renamed entities?:

Update coming

Your fix worked. I renamed a virtual device, restarted MSR and just as I was about to hard refresh my Reactor page, the entity renamed itself within MSR. Thank you!

[toggledbits]

Great. If you didn't see the note, you can also just do a soft-restart on the HubitatController system entity. Search for the entity in the Entities list (recommend: clear all filters, then filter by capability sys_system and it should stand out). Run its sys_system.restart action. HubitatController will reinventory hub devices and see the name change. Unfortunately, HE doesn't send an event when a device name or label changes (other controllers do, so this soft restart or full restart isn't necessary with those).