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
So, it's Friday... But will this be a release friday?
This discussion has been closed.
Comments
I want to suggest the following Z-Wave branches to be supported at first, which I use:
- Fibaro
- Qubino
- Aeotec
Also, which I don't get, is the IOS app updated? With presence detection and notification?
Not yet, but a new release is on it's way, including Push notifications and Presence detection.
I sure hope the ETA on the Z-wave rewrite will be met!
Here Hue is dead, android app is dead, Homey going offline for no reason, oops couldn't reach server, nodejs client looses connection, presence detection is a pain in the aars, push notifications are not working (properly), etc etc.
Yesterday my wife took initiative to move bedroom Hue Bloom back to Hue remote. I can tell you is a very big step for here to get the hue remote, search the manual and get the devices paired. She is quite done with it.
So Kaku left the bedroom and WAF is getting lower with the days.
Hopefully this will be fixed in a new version of the hue app or v0.8.39
Till now never missed a push notification.
not yet working is:
- android app ( did work. but after last update stopt working)
- 2 of the 4 somfy blinds are not working properly.
- Geo location not working as supposed.
homey: 0.8.38
App ver. 2.2 build 48
Hopefully this will also fix the somfy blinds.
KaKu(1.1.6) also died, AYCT-102 is not received anymore....
This simple flow is not working anymore.
Test button works and the LED-ring spins, KaKu remote; nothing!
Its almost beer time again
If I say nothing then I'm not cooperating and if I mention bugs (like everybody else do) then I'm a annoying person....
Please tell me how you guys want me to act/react!!
Did I create the bug? Do I let my Homey crash? Did I took the servers offline of break a connection which causes the Oops message(which i experience for the VERY FIRST time?!)? I've heard tons of complains about the Oops message and when I notice/experience it then i'm a .....
@koenmartens;
Please help me with "these bugs"! Please tell me which bugs you are talking about, then I would love to share my experience/fix (if I have one).
Also always fun to see that my help is always forgotten and people always go in "MarcoF bash mode" when I'm experiencing problems.
Did you guys see my App? Is that being negative or is that a thing for the community? It took me a few weeks of my live to create it and it was a big fun/learning experience
O and also not forget my Pull request on the NetAtmo app 5 weeks ago. Athom did, "based on my help/code", a "rewrite" of the App. The Pull request is closed and Baskiers said the new app will be release soon. This new app will bring Multi Sensor support
Just did a cold reboot (pulled the plug (oh not on myself )) and now KaKu is working again
Will let you guys now when its crashed again and what I did to fix it
And it looks like we have more in common then you could imagine:
https://forum.athom.com/discussion/comment/25424/#Comment_25424
and
https://forum.athom.com/discussion/comment/25478/#Comment_25478
(will not ask whats the difference between you and me saying it)
So please let see how we could help @Athom together
@Robin ; commented earlier that the problem with milight was also found.
When will these new apps be released?
Marco,
never thought I would be saying this. But you're not so bad.
Let's make homey, epic...
i can confirm that milight is fixed in the new version that they are going to publish to the store
(running the github version now at the moment that works perfectly)
Happy Birthday !
Thats what we want. Good news or bad news, just an explenation. Great
(and for the rest of the forum; please, no stupid remarks now....)
(and for the rest of the forum; please, don't eat yellow snow...)
((I like the idea of giving valuable live lessons to finish a post!))
I agree with Danee, that it would be nice if we were informed of such situations in advance of it happening, though. So maybe for the future, you could at least mention those few situations in the release notes that you consider possible candidates for 'something breaking'.
And, tbh, I don't think it's wise to choose this particular release to promote to stable. If you pick a release for 'stable', then it should be one that is a (significant) step forward from the previous stable version (in terms of which devices work). Given the feedback I hear on the forum, I don't think you've reached that status yet.