31
How do you replace devices? (lemmy.world)
submitted 4 months ago by to c/homeassistant@lemmy.world
13 comments fedilink hide all child comments
 

I recently had to replace an old Zigbee bulb that had stopped working properly. How do you handle this? Do you manually replace all instances of this device in all automations, scenes, etc.? Or is there a magic button I am not aware of that makes this easier? At least I could use Spook to let me know which places I need to look at, but especially for scenes it is a pain because you need to reconfigure the settings for the device manually.

you are viewing a single comment's thread
view the rest of the comments
[–] 36 points 4 months ago (8 children)

Copy the entity ID from the old device. Delete it. Add new device and change the entity ID of the new one to the old.

It would be great if they built a device replacement function that would intelligently swap all the entities from an old device to a new one.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 16 points 4 months ago (7 children)

    Missing basics like this are one of the things that drive me crazy about HA (as an 8-year user). Yes, the new Maintenance dashboard is nice, but they really need to focus more on creaky foundational problems.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] -3 points 4 months ago (4 children)

    Whatever you do don't tell them that. The "community project" with 5-6 full time paid developers will berate you for being ungrateful for your free software that thousands of users pay monthly to have developed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 4 months ago (3 children)

    I haven’t seen that attitude with HA, but for some other projects yes. It also may depend on what your attitude is when asking questions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 4 months ago (2 children)

    I 1000% get the fully volunteer projects being defensive. They catch a lot of shit for no pay.

    But once I asked why they reworked and removed functionality that was easier to use and understand than what they replaced it with and they took me to task about how the person who did it was a volunteer contributor. OKAY, I get that there's still lots of volunteer code submissions but shouldn't the full time employees being overseeing it to make sure changes are improvements in all aspects?

    I love the software and I have used it almost since the beginning, but if the community is paying for development and it's the actual livelyhood of the employees, I don't want to hear that I should be happy with what I get because it's "free."

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 4 months ago (1 child)

    I'm very curious how you positioned it. I've seen LOTS of examples of people describing things this way, but when you look at the actual interaction it was way less reasonable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 4 months ago

    I actually, I looked back and it wasn't even me they were snarky with. I had complained earlier in the thread, but it was another user complaining that the documentation on the change was super unclear and incomplete. At one point they suggested we dig into the developer comments on the change process in github. For regular users and not devs?

    They got snarky about the documentation complaint and more or less said the person complaining that it was unclear should fix the documentation themselves. Because we need people who don't understand the changes writing those? I replied that snark was inappropriate for a company with several paid full time devs that said they want to be a real smarthome brand in a recent announcement. And that's when they gave me the volunteer spiel and that the change was made by a volunteer. Who's running the company and cashing the paychecks? It's just such an unprofessional fallback. If the people cashing the paychecks aren't overseeing changes that break widely used functions I'm not sure it will ever break into the regular market.

    It's still hard for me to reccomend it to anyone who's not a real dig in and get dirty kind of techy.

    I will say it's now been a couple years since that incident and I still find documentation after changes lacking from time to time, despite the paid team having grown in that time.

  • permalink
  • fedilink
  • source
  • parent