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.
Closed
Homey 1.5.8 and 1.5.9
This discussion has been closed.
Comments
https://github.com/athombv/com.fibaro/issues
Call Me crazy, but why on earth would users of a device that promises to connect about everything with a transmitter and your coffeemachine, and is sold at Mediamarkt among thousands of other consumer electronics devices have to sign up to Github to report flaws in releases of software which are pushed automatically when deemed stable by Athom.
If the product isn't ready for everyday use then by all means don't sell it at Mediamarkt and other consumer outlets. I am using the Homey stable releases to assess if Homey is mature enough to recommend to customers. Well, frankly, I can't redcommend it right now. Personally I don't mind waiting a bit (up to a point) and I understand some of the complexity of what Athom (and app developers) are trying to achieve and I really appreciate the hard work. But looking at it from the perspective of potential everyday users, however, this kind of slip ups (and customer care) are not helping building trust or creating satisfied customers and could ruin the Homey name in no time.
Has anyone from Athom even acknowledged there is something wrong and what is being done about it? In plain, understandable English (or rather Dutch as most of your consumers are for now), and not hidden on geek hideouts like Github or Trello. Simple PR: major fault detected? (especially in stable releases): email to all registered users with findings, hold rollout of the os version or instruct customers to disable automatic updates, and keep up to date on progress solving the problem. Communicate!
The only way forward is make sure the core functionality is rock solid and differentiating between good, easy access customer service on the one hand and the more tech oriented Forum, Trello, Github sources for more in depth discussions for those who are able and willing to participate there.
Hi Bram, I understand that completely, that's not the point, even the other "established" home automation solutions don't always work as promised, so no news there. Neither do pc's and even Microsoft and Apple push updates they shouldn't have (or fail to fix longstanding problems) so you are in good company there.
It's not only about perfection, but also about how you respond to the imperfections, and in this case, It's not my environment that has changed over the past week, its Homey's firmware that has...
I hardly ever get updates on a computer that promise exiting new features and, for instance, wrecking USB functionality at the same time.. And that is exactly what I'm experiencing right now: a flaw is one of the key functionalities of Homey, Z-Wave, with no opportunity to revert back to a situation that worked.
It's not my environment that has changed over the past week, its Homey's firmware that has. Z-Wave is failing to pair new devices, which is probably a key prerequisite for enabling the use of Z-Wave devices in the first place, where the previous firmware version did not have this problem.
I think that is a major issue that deserves proper and prompt handling and communication on Athom's behalf. I fully understand that your are trying to achieve something very complicated and already are, with limited resources, well along the way to achieving it. I would be very sorry if Homey ends up in a situation where it's reputation is damaged because it cannot deliver on it's promises, which is essential for wider acceptance. And that is what we all want to see happening after all.
Thanks, Mark
Customer feedback (because realise that they are paying customers) should be appreciated and embraced to its fullest extent. Problems like this, communication should be acknowledged (I mean come on, this is not something that only popped up yesterday by one user) and improved upon. Or at least show the willingness and effort that goes into trying to improve it...
Since the release it has been very quiet from Athom side while some common and persistent issues have been reported by multiple users. Nobody really knows if Athom is aware of it and working on them... Only that 2.0 will not see any development on voice and see a new take on music... Don't think that is the main priority for most Homey users right now (although I cannot speak for them), it is stability of core domotic protocols.
@Flight777 @Computerblues We can all keep it short, just read the forum rules and look that this is a community forum, so Athom has no responsibility at the forum, they respond at github/support contact. If you want support you know the ways, report at github or contact support@athom.com.
If you all don't want to do that it's also fine, but issues will stay there and so your complains
Personal i don't recognize the problems with Homey, running 1.5.8 stable since it did hit the DP channel with 30+ zwave and 70+ zigbee. I'm not saying there are no problems (see the github issues i posted) but when i have a problem i act on it and let Athom know
Never had this issue before, as if, Homey is more busy.
Looks at top of page: Welcome to the Athom Community Forum! This is a place to share ideas, ask for help and discuss about Homey in general.
But this being a "community forum", shouldn't a company like Athom be interacting with its community?
Like they say on their webpage: Our community made us big, and is where our heart lies.
And these complaints amazingly aren't on the things that could get Athom sued.. selling 'built in' features that have never left the brains of developers. The rest that did.. they are now killing off those key features. I don't disagree with why myself. They're admitting incompetence in delivering music and other features like speech.
But they have let the customer down drastically. And the customer is rightfully using the tools they provided, to ask for clarity on these matters
Disclaimer: this is just my opinion
Next offtopic posts will be deleted. If u have any problems with that plz feel free to contact me.
- [BLE] Various bugfixes for SDKv2 apps
- [Alarms] Fixed a bug that could cause disabled alarms to still trigger flows
- [Z-Wave] Multichannel node-IDs are now accessible in SDKv2 app
We continue in this discussion.I do really would like a update that fix the issue with 433 and Oregon sensors.
I will look into the packets if that is related. Could have nothing to do with the update but has anyone experienced this (before)?
Same here, but with a KlikAanKlikUit switch.
Edit: I noticed this behaviour also since this update.
And this is a log from the last couple of minutes: I don't know for sure what is going on. But as stated before the network is