v3.5.33-Beta

[ikb42]

Add "update" to manage firmware
Improve sensors and events

---

This discussion was created from the release v3.5.33-Beta.

[xela1]

Hi @ikb42

I've just installed this on my dev instance, I can see the firmware status, but it's on a second instance of the device with the same name

is this expected?

[ikb42]

Hello @xela1 - thanks for the feedback! I'd like to get this version released soon, so this really helps.
Yes this is as expected as it stands, perhaps it can be improved on in future.

[xela1]

I'll run some tests on it to see if it all behaves as expected, I don't think any of my devices need updating at the moment so won't be able to test that just yet (unless there's a way to force a downgrade?)

[ikb42]

Excellent
Downgrade is not an option, but in terms of testing it's general / existing functionality behaving as expected that I'm keen to verify.
My goal is to get this integration HA approved - or "Works with Home Assistant" approved.

[nuttersrest]

Something seems to have gone awry with the upgrade on this.

I now have two LinkPlus Entries with one only having the Firmware and the second one having the rest of the info on the LinkPlus

The switches are similar but also have broken my dashboards and automations as the underlying switch seems to have been renamed. I now have three entries for a switch. One tile has joined the origional two names of the switches, which includes the firmware and actual switches though the underlying switches were just called switch (making it hard to identify and I had to go around and rename everything again. The other two still retaining the origional names and have all the current/power/voltage information.

Although when you update the firmware it impacts the two sockets on a dual socket. It would perhaps, if possible, make things more sensible to have the firmware button duplicated on both switch sockets leaving everything for that socket (switch, power readings and firmware) in one tile. If that is not possible just have the firmware on the first sockets tile.

Thanks for creating and supporting this integration.

[nuttersrest]

Just a small follow up on the above, the actual switches that are renamed revert to being called Switch when HomeAssistant is restarted. Any entity on a dashboard that has used that particular switch name, then reverts back to the parent name (which has the the original two names joined together) making it impossible to know which of the devices are being turned off or on.

[ashy-87]

I’m also seeing the same reverting devices on reboot, they lose their area attributes too. I get a handful of Gen1 devices that ‘reset’ on reboot too, losing their area, name and type. I hope to see a fix, is there anything I can offer to help identify the problem?