This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
it has got to do with adaptation/edits/copy of the device firmware itself which they don't want to happen.
example:
i guess we all have seen the neo coolcam devices that look a like (motion sensor in particular), can you imagine having that with the same firmware as the fibaro's?
i don't think a big company that does a lot of research etc like fibaro wants to have that
Or on the editing level, that people will try to change the firmware and totally brick their sensor and come knocking on fibaro's door that "their sensor isn't working anymore".
This is btw not just for fibaro, the other big company Aeotec does exactly the same, even though you can update with an other z-wave stick then their own, you Must use the proprietary software, which only has the 1 device update deeply encoded inside.
the last big z-wave manufacturer (for in europe) qubino i am actually not sure. as i don't have those devices never looked into that, but i don't think it is much different for them.
So will it ever happen for the big companies?
i can asure you, even after the message to "the other department", it will never happen, as they are just too afraid
I send them the following:
And got the following answer:
I even offered to sign a NDA, but that did not matter
But in the end....only thing Athom needs to do is to become a force to be reckoned with.......ie get a shitload of users.
PS.
Just thinking outside the box.......if you (as Athom) approach Fibaro and suggest them to write an App for Homey themselves....??
They can keep the firmware/files in house but still providing support to non HC users.
I really wouldnt want to disconnect the dimmers from homey, connect with HC, update, disconnect from HC, connect with homey.
Went through the process a month ago - using the only way I know about: removing devices from Homey, add them to HCL, getting HCL to update and so on - just as cumbersome as it sounds.
You describe it as it is possible to make some kind of "bridging" between Homey and HCL?
Well other controllers seem to be able to do something like this - but maybe not
I was hoping for something like that though, o well cumbersome it is.
Hope nobody figured out how to update Fibaro-FW without excluding etc. from Homey - and didn't share how - that wouldn't be nice...
And I haven't read anything anywhere about it...
Anyway:
My Fibaro devices are all <6 months old - and I didn't notice anything changed by upgrading the FW - will definitely not go through the trouble again unless I read something somewhere about some really cool feature or something that solves some annoying problems making it worth it...
The only way Fibaro allows to update firmware is when a Fibaro controller is the main controller. So there is no change Homey is allowed to do a firmware update of the devices (for now). I think when the domotica market grows up there are gonna be ways to upgrade firmware of devices without having to own the main controller from the manufacturer (read: without the need of a Hue bridge, ikea bridge, innr bridge, Fibaro HC2 etc. etc.).
Not fibaro devices, and before I was running Homey. So a secondary controller can upgrade firmware.
If homey supported secondary controllers and fibaro HCl was joined as a slave, I would think that re-include wasn't necessary.
https://shop.homeseer.com/products/homeseer-z-flash-z-wave-ota-firmware-update-software
I guess another problem is also getting the actual firmware files for the devices...
I see on bug reports on GitHub for Fibaro, the firmware versions under the node information.
For example here: https://github.com/athombv/com.fibaro/issues/208
But for all my Fibaro devices (including the same device as in the bug report) my firmware versions are shown as blank, or “-“ on the beta smartphone app.
I don't suppose you know if this will be done for existing devices somewhere along the line too?
It's not critical, but can be useful for debugging sometimes, especially with the Dimmer 2 where the older firmwares gave problems. Don't really want to repair all of my devices to get the info.
For example this is a Fibaro Plug. Such Fibaro Firmware does not even exist. This is with every module.
Or is there a way to encrypt this number?
The current Firmware of this should be 2.x according to Fibaro terms.
Once you have the files, would the update protocol work, or could there be subtle differences?
+ Don't you think people would have done so in the many years it is possible?
They even completely found out how zwave works by reverse engineering before there was any documentation public (a.k.a. openZwave).
Getting such a file would be a cinch for those people.
But still it is nowhere to be found.
Has anyone tried adding an HC2 or HCL as a secondary controller / remote gateway in an existing Homey Network?
Or is this currently not possible? See here.
“It is up to gate provider to implement packages of update data for each of devices. Looking realistically not too many gate producers are giving the option to make OTA update of 3rd party. I want to ensure you that we are working right now wit more then 30 gate providers on market to give an option to update our devices with use of other brands gateways.”
Does anybody know if Athom is in contact directly with Fibaro on this?
By default Homey adds the sensor only to association group 1. But the alarms for motion are on group 2, and for tamper on group 3, so when I add homey (device 1) also in group 2 & 3, it works fine.
Please let me know if this could be the solution, or it should work fine with only adding it to group 1.
Not sure why you post that in this topic as it is about firmware updates.
But anyway, it shouldn't matter, all signals are send to group 1.
By adding homey in 2 and 3 it is just sending 2 of the same signals, so it can benefit as 2 signals is easier to notice then only 1, but also be negative, if you have many devices, you pretty much just double the amount of data in the air towards homey and homey also needs to handle these signals.
Zie https://www.robbshop.nl/update-service-fibaro?sqr=fibaro&;
Hopefully this info will help some Fibaro fans !!