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
Just to manage expectations, the ALMDT-2000 is a complete other device than the currently supported kaku devices as this one is using 2 way communication on 868 MHz.
This device is from the security system line where all others from kaku are communicating of 433 MHz and are from the wireless switches / domotica line.
Chances are things will take more time and is only possible if they have enough information about the used protocol. All other 433 devices don't use encryption or security.
Support for the Homey would be awesome. +1
https://github.com/athombv/node-homey-433/blob/master/HOWTO_CREATE_SIGNAL.md
I tried to fix my situation with the current Homey functionality, but I did not succeed:
This issue can be fixed by adding a master/slave feature as it exists in Domoticz, or we could have to add a "set status" action to all KAKU receivers. This would only change the status of the receivers without actually sending the signal.
Homey sees when the wall switches are used and can set the status according the signal it received.
Gr. Remco
when i klik on the button i get the notification Invalid_device_error and then the broken sign of the button
how do you use the KAKU as Virtual Button? What device is it and did you generate a code?
And does it work if you create a new Device and create a flow with trigger?
If i make a new one that one works, But I really don't want to make new ones, the ones i have i use in many flows.
It would be a hell of a job to adjust all those flows.
If I restart the KAKU app then the buttons are regonized , but after klikking on them they change in Invalid_device_error
The more info they have the faster they are able to fix it.
They are configured in a flow to turn on 30 minutes before sunset and have done so everynight until tonight.
In the same flow i have one Hur Ambiance Candle and that turns on.
I see in the Atom store that the KlikAanKlikUit app was updated today so I guess that's what did it.
[Edit] Saw now that the app updated twice today, first to 4.0.1 and later to 4.0.2.
if it still happens after a fresh boot, Search on Github to see if other alread reported the same and provide information (Your devices, errors you see, etc ) and send a Log from Homey and from the App .
Obviously, something went wrong in the updates on July 31. Is it possible to roll back to the previous version, or create a new version based on the old one? A solution where users are forced to remove any malfunctioning devices, re-add and then also create many flows to get it working again is not ideal at all!!
the developer has found the problem?
or let users CLi load the old app
Due to the fact that this bugfix fixed a lot of issues with controlling official KaKu devices with the KaKu app, we cannot roll this update back.
I know a lot of people use the KaKu app as a "workaround" because we do not have an official Nexa/Telldus app yet, but the fact is that this is a risk everybody took by using this "workaround".
We are of course very sorry that this has happened. We had a small meeting with the dev team yesterday and we have decided to speed up the proces of releasing an official Telldus app and hopefully right after that an official Nexa app. I'm hoping that I can start testing the Telldus app this week so we can release it next week. I do not have a timeline for the Nexa app right now.
For now there are two options for the users who were using the KaKu "workaround":
1.) re-pair your devices with the current KaKu app
2.) Wait until we release the official apps for these brands
If someone wants to help me test the Telldus app, please pm me so we can speed up the proces even more. And of course feel free to contact me if you have any other questions
They show up but its impossible to get any Flow running if i have them in.
So it doesnt help to just re-add them.
Its pretty bad that you havnt made any app for nexa/telldus before, when you know many of us uses those devices (as you wrote yourself). And as you already know that many of us uses the app for Nexa/Telldus you could have tested with those devices before releasing any update. And release the update when you had an official Nexa and Telldus app ready to launch at the same time.
I would be helped if I can replace the software with the previous version which worked very well for me.
We are with a very small team so we continuously need to monitor our priorities. The official Nexa/Telldus app was already fairly high on our priority list but we dont have the development power at the moment to develop all of our high priority apps.
Thank you for the feedback Bram and good news you finally decided to release separate Telldus and Nexas apps.
I would love to test the Telldus (and Nexas) app.
is the telldus / nexa app soon ?
my dad's homey are now turned off because he was only using nexa stuff.
and please answers why we cannot sideload the app!
You can of course side load the old version of the KaKu app in the meantime (Keep in mind that we cannot offer any support on this version because a new version is already released).
Link to the .zip file
I know that you guys have told people in the community NOT to develop an Nexa app, because you didnt want an user made app. Why stoppning people from helping you guys out? Im starting to think that you make bad priorities.
Now there is MANY people with Big problems because of those bad decisions.