They say that developers can implement OTA updates (also for Zigbee), but they donāt explain how or provide any example code, nor do they implement firmware updates for any of their own apps. Theyāre basically putting the blame on the developers for not implementing this feature, which IMO is really bad (but typical).
Until Athom shows us an actual working example, Iām calling BS that itās even possible.
I cannot judge that, but if the situation is as you are writing it really unfortunate for the end customers. On the other hand or would be pretty easy for the manufacturers to provide firmware updates through a basic smartphone app. I have the Zigbee power switches where Bluetooth is used to push a new firmware to the device.
But letās stay optimistic that the situation will change in the future.
But that assumes that all Zigbee devices also have Bluetooth, and most of them donāt.
With protocols that arenāt supported directly by smartphones (Zigbee, Z-Wave) you have to rely on hubs like Homey to provide OTA update functionality.
Itās a question of design, starting with the developments of such devices.
If companies would take information security and customer centricity serious we wouldnāt be in the situation we are. I am well aware that this would be a best case scenario, but that not only one company comes even close to that scenarioā¦
I would suggest that this is exactly why weāre in this situation: most brands are very reluctant to provide information about their devices to make them work with other hubs, because they cannot control those hubs.
Who would a user blame if they perform a firmware update through a third-party hub which bricks the device? My guess is that in 90% of cases that will be either the device manufacturer or the deviceās seller (as a warranty claim).
So most manufacturers think that keeping this information (including firmware updates) secret benefits the user, or will at least prevent warranty claims (and yes, you can argue whether this train of thought is correct, and itās probably not).
Providing an alternative method of firmware updates, like your Zigbee device that also has Bluetooth, costs money and, if you consider that the manufacturer assumes that users will use their hub anyway, unnecessary.
Just chiming in to say that the Innr SP240 plugs are still not reliably reporting power consumption stats as of November 2024. Repairing works for a time until the power is cut for any random reason (or notā¦).
Apologies for the random tag @Doekse , but it is possible to add a note about this issue in the Best Buy guide until this issue is fully resolved? I tried to find Dino on the forum here, but no luck figuring out what his handle is.
Same here. Iām not so happy with INNR these days, I started with some SP120ās which still work perfectly and do measuresment, next came the SP220ās which lacked the reporting completely. I was happy to see they included measurment in the new SP240 untill I received them and realized how bulky they are. Itās so bulky it blocks the second outlet to be used
Maybe we should all send back these newer models and ask them to go back to the SP120 revision!
I have been in contact with INNRās support desk (and to a lesser extent with the INNR Homey app developer) over the last four months on two issues with all of my SP240 plugs:
Homey stops reporting power measuring data after unplugging the SP240 plug (on/off function still works). A re-pair is required in Homey to re-enable the power measuring reporting;
After every restart of Homey, the current value displayed by Homey is 1000x higher than the actual value reported by de SP240 plug. Again, re-pairing the plug solves this issue, until the next reboot.
Apparently this behavior is caused by bugs in the SP240ās firmware. All my SP240 plugs are on firmware version 1.4.3.
There is a new version of the firmware available though (v1.7.22) that should solve these issues. However:
You need INNRās bridge/hub to update the firmware;
This bridge currently does not support the update process. INNR is working on that.
I understand that an alternative is to update those plugs via HA/Zigbee2MQTT (as the new firmware is publicly available). Of course you need such a hardware setup to do that, which I donāt have.
In my case, INNR sent my one of their bridges, while I wait for them to enable the software update functionality.
If INNR would support firmware updates via Homey that would be awesome. I would then hope for other manufacturer to follow this example. This could be a game changer for the support of Zigbee devices on Homey.
If Homey would support Zigbee firmware updates, that would be awesome.
Athom keeps saying that technically itās possible for apps to implement firmware updates for Zigbee devices, but no one has ever seen an app that supports it, not even Athom apps themselves.
Although I do agree zigbee firmware updating should be supported out-of-the-box, but āgamechangerā is not the word I would use myself
I did not have to / did not felt the need to update firmware of any my zigbee devices in the last 4 years.
Of course it all depends on the devices used.
SCNR - so you are confirming my statement if INNR would support firmware updates via Homey.
Nevertheless, semantics. I take now a very end user centric position. I do not care who needs to make it happen. To have IoT devices where the firmware cannot be updated (assuming vendors are providing firmware updates) should not even be a discussion point in 2024.
Well, I am forced by the industry to either have a multitude of hubs from different vendors or allow IoT devices with firmwares that cannot be updated. More hubs connected to the internet is increasing my risk profile in terms of information security. Having unpatchable end devices also. Game changer might be a bit hefty, but it would be big, at least for me.