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
And now Homey does not recognize any of my z-wave devices anymore. Any tips how to fix this?
so you have to wait 2-3 weeks.
Did not work for me.
I can add a dimmer by using the remote. At the testing fase, testing the dimmer with the remote works. Light turns on and off and the state is displayed correctly. But be switching the light on or off through homey, the light does not switch on or off.
Would like to know if it is a hardware problem on my side or a more general problem.
using:
Motion sensors
Sockets
Remote controle
Contact sensor
Night sensor
Doorbell
Could the transceiver be broken? At least the transmit part?
(btw, is not a work around but just how z-wave works;))
Somehow it crashed after the update, ping replied, ssh gave me a logon prompt, http not responding so I PTP (™ @marcof)
After homey got back I noticed there was no more data logged from my Aeotec MultiSensors. I did a reset with data erase to start from scratch. Added a MultiSensor only to find out it's still not logging data to Insights.
Don't feel like installing all apps again, adding all other devices and recreating all my flows, please wake me at 1.0.0
The not logging everything is a known bug in .39.
The bug includes a lot of things in z-wave, like all triggers not working and automatic refresh of the mobile cards neither.
Kaku stopped working, but not for all devices.
AFR-060 is not working. Not even after reconnecting the device to Homey (the device is recognized by the kaku app, but cannot be switched), not after reinstalling kaku app, not after rebooting Homey.
APIR-2150 is working fine, though
Ok, but as I read it, that was solved after re-adding the devices and applied mostly to KAKU devices.
I'm sorry, but promoting this from experimental to stable is a stupid move with a total lack of respect to the current user beta testing homey and I feel Athom gave me the same thing the British gave the EU.
with kaku, for most devices this is true.
But for z-wave he said the re-add needs to be done when the re-write is done, not with this patch though.
but i agree, .38 was a better candidate for stable
Im experiencing Allot of network losses wich result in my hue not going on or off at the programmed times.
i have to reset homey almost twice a day to reconnect to my wifi network..
Please stay onboard; your effort with the Aeotec sensors is highly appreciated!
I rebooted, made a new flow with notification, but the problem persists.
So just accept this until 1.0.0 is released.
(here zwave never worked as expected, IR (leds) is/are dead, push notifications aren't working, presence detection is failing, devices constantly needs to be fixed, listening needs to be improved big time, zigbee/BT still miles away, almost every homey is behaving differently depending on install apps or used protocols, etc etc and it's all by "design" (I read in the athom blog))
Did two power cycles but still nothing.
Does anyone else have this problem?
And some other 433 MHz devices work as well.
So the problem is not specific to 433 and does not effect all Kaku.