Skip to content
This repository has been archived by the owner. It is now read-only.

KaKu Flow's are dead. #682

Closed
posthok opened this issue Jun 10, 2016 · 64 comments

Comments

@posthok
Copy link

commented Jun 10, 2016

What is your Homey version (Settings → System)?

0.8.38

What did you try to achieve?
Nothing, only working flows

Please include detailed steps how we can reproduce the issue
after updating to 8.38 flows aren't working anymore.
Devices work when i trigger them in devices, but the flows don't trigger anything anymore.

What was the result?
a fully non functional Homey
...

What did you expect as result?
A working device
...

Any other remarks
I have did a reboot. Power off and on. Turned off kaku and on again. Deleted KaKu rebooted and reinstalled but no result.

...

@djeskoswe

This comment has been minimized.

Copy link

commented Jun 10, 2016

Same here, all Kaku devices are dead..

@Arjanvde

This comment has been minimized.

Copy link

commented Jun 10, 2016

Did you try a cold reboot (remove power for 30 seconds), fixed the issue in my case.

@djeskoswe

This comment has been minimized.

Copy link

commented Jun 10, 2016

Cold reboot did the trick to add new units, but no go in flow!

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 10, 2016

did a cold start too. Flows are still dead

@djeskoswe

This comment has been minimized.

Copy link

commented Jun 10, 2016

When using 433 wallswitch the flow triggers but with 433 remote or zwave socket hardware on/off no flow triggers.

@Dijker

This comment has been minimized.

Copy link
Contributor

commented Jun 10, 2016

Very strange,

  • 4 testflows that react on a KAKU button (Doorbell, AWST8802 , AYCT-2102) ALL still work after updating to 0.8.38 (Pulse Ring, increment Better Logic value )
  • tested two functional flows, one with a KAKU door contact disabling the thermosmart and one other AWST8802 triggering the start of KAKU ASUN650 screen. Both dead as you mentioned.
    But still possible to test the flow to move the KAKU ASUN650 screen, it works and the flows (4) for the doorcontact also work

Send Logs:
5FD83A3CBF

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 10, 2016

all flows working with the test button. That's also the only way to trigger.

Send also a log 7536201BA1

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 10, 2016

Just made a timer flow and let homey say the time. This trigger worked.
Seems Kaku related.

@bvdbos

This comment has been minimized.

Copy link

commented Jun 11, 2016

KaKu door sensor AMST606 can be added but it doesn't work in flows.
KaKu remote AYCT102 remote can be added and does work in flows.
KaKu remote APA3-1500R can be added but doesn't work in flows (but other reason: channel 0 can't be selected in the trigger-column)

Bitflip doesn't trigger.
Kaku-socket doesn't trigger...
NFC does trigger
build-in variable does trigger

@glijie

This comment has been minimized.

Copy link

commented Jun 11, 2016

sensor AMST606 stopt working,
Kaku motion sensor stopt working
and the virtual buttons (sockets) stopt working.

therefore most flows i use stopt working.

Kaku which added with a remote signal are working
doorbell is working

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 11, 2016

tried the doorbell as well and indeed the doorbell does his job. Strange.
As the doorbell is also kaku.
Also kaku switch triggers a flow and turn's on the light.

@bvdbos

This comment has been minimized.

Copy link

commented Jun 11, 2016

Which switch and which doorbell?

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 11, 2016

homey doorbell
Kaku doorbell

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 11, 2016

i did a little experiment with a flow. Added the same kaku doorsensor (which not worked in a flow) to homey but now with the smartwares app . And now this doorsensor works in a flow.
Doorsensor open lights on. Doorsensor closed lights off.
It seems some kaku signals don't come trhought in the if section.

@posthok posthok changed the title Flow's are dead. KaKu Flow's are dead. Jun 11, 2016

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 11, 2016

And her's another or maybe the same issue.
homey insights
This picture shows only a couple of my device's

homey flow devices
but on the left are all my devices

@bvdbos

This comment has been minimized.

Copy link

commented Jun 11, 2016

The devices which can't be used as a trigger are the same devices which don't show in insights?

@MdeRhoter

This comment has been minimized.

Copy link

commented Jun 11, 2016

Just to chime in here, I have what looks like the same issue.

My repro:

Single AWST-6000 motion detector, used in a flow to change a variable.
In the Devices section I can see that it detects motion (on motion, it switches on, then off, as it should)

However, the variable in the flow doesn't change, because the flow doesn't trigger.

Other KaKu devices that do trigger a flow successfully:

  • AYCT-102 remote control
  • ACDB-7000BC doorbell

So it doesn't seem to affect all KaKu transmitters, just some. Rebooting, cold or otherwise, doesn't help. Neither does re-adding the devices.

@Dijker

This comment has been minimized.

Copy link
Contributor

commented Jun 11, 2016

@MdeRhoter
It is the same I see. Some work some don't

@bvdbos

This comment has been minimized.

Copy link

commented Jun 11, 2016

For me this also (seems to) happen with a bitflip device. On the forum Djesko claims also zwave experiences this. Timer does trigger, some Kaku's do trigger. Dijker, you are sure the AWST8802 does trigger in certain flows and doesn't trigger in other? Do the triggers show up in the log of you all?

@Dijker

This comment has been minimized.

Copy link
Contributor

commented Jun 11, 2016

Yes,
I have two AWST8802, the one that is installed triggers a nonexistent virtual socket in Homey normal to let the asun650 SunScreen go 26 seconds down. This one doesn't work any more . So it is the socket defined in the flow.
The other on my desk counts to test the KAKU debouncer and still works, a better logic value increase with every button pressed.
The motion sensor and contact sensor both also stopped working.
I replaced the contact sensor with the AWST8802 button for the time being.
The doorbell still works.

@bvdbos

This comment has been minimized.

Copy link

commented Jun 11, 2016

Ah, that explains it. The AWST8802 works as it should but the virtual socket doesn't. I have a virtual socket too which doesn't work. Contact-sensor AMST606 also? I don't know if there's multiple motion-sensors but do you know which typenumber this is?

@Dijker

This comment has been minimized.

Copy link
Contributor

commented Jun 11, 2016

@posthok
As strange my contact sensor amst606 from KAKU stopped also, I could re-add it but stop no flow that triggers. I could also add it has a smart wares learning is still ok and the working is verified opening the device card. But still no trigger, it doesn't work for me :(

@MdeRhoter

This comment has been minimized.

Copy link

commented Jun 11, 2016

It would be useful to find out if this worked in versions older than 0.8.38 - if anyone can test this, please do! It may just be the Kaku-app, since that also got bumped a few times recently.

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 11, 2016

@bvdbos Yes the contact sensor showed in insides is the only trigger that worked

@matjaz

This comment has been minimized.

Copy link

commented Jun 12, 2016

I experience same behaviour with Aldi app on .38.

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 12, 2016

Turned off all apps. Did a reboot, turned on all apps. Now all devices in insights are gone.
But in Zones and Devices they are still present.

@glijie

This comment has been minimized.

Copy link

commented Jun 14, 2016

@MdeRhoter on 08.36 everything worked just fine after update 0.8.38 some kaku stopt working.

@MdeRhoter

This comment has been minimized.

Copy link

commented Jun 14, 2016

Looks like it. Win some, lose some! @Dennishacq - could you take a look?

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 14, 2016

Dusk sensor (schemerschakelaar) and doorcontact sensors still don't work after kaku update 1.14

@MdeRhoter

This comment has been minimized.

Copy link

commented Jun 14, 2016

Changing the brightness of a dimmable Kaku socket in the Devices section does work. A dimmable socket does can't be switched on or off though.

@bvdbos

This comment has been minimized.

Copy link

commented Jun 14, 2016

doorcontact works for me...

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 14, 2016

@bvdbos In a flow in the if section?
if door open lights on?

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 14, 2016

homey sfeerlicht
This flow is working. Homey said: "sfeerlicht aan". but the lightslevel does not change.

homey open door

In devices i'll see the door getting open but the flow won't trigger.

@BasPost

This comment has been minimized.

Copy link

commented Jun 15, 2016

All my KaKu modules stopped working after the update 1.1.4 on 0.8.38 last night. I can't send any on/off commands.
Everything worked fine before update. I disabled and enabled the app, reboot and powercycle, but issue remains

@glijie

This comment has been minimized.

Copy link

commented Jun 15, 2016

only the sockets which where added with a remote control from kaku stopped working.
all other kaku works overhere.

@jordenc

This comment has been minimized.

Copy link

commented Jun 15, 2016

I still can't pair the doorbell ACDB-7000AC

It worked before the 0.8.37 / 0.8.38 update

@jordenc

This comment has been minimized.

Copy link

commented Jun 15, 2016

Update: I pulled the plug on Homey and then booted it up. Afterwards I was able to pair.

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 15, 2016

Kaku is now completely dead. does'nt work anymore
Kaku 1.14 continuesly crashing.
Also the test button doesn't work anymore.
One step forward two steps back!!!!
Stack trace:

TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_contact.get (/drivers/switch/driver.js:129:28)
at Object. (/drivers/switch/flows.js:51:39)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7),TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_motion.get (/drivers/switch/driver.js:117:28)
at Object. (/drivers/switch/flows.js:37:38)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

@Dennishacq

This comment has been minimized.

Copy link

commented Jun 15, 2016

I updated KaKu to 1.1.5 which should solve the issues.

@posthok Repairing your device should fix this error.

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 15, 2016

Thanx Will try

@caseda

This comment has been minimized.

Copy link

commented Jun 15, 2016

I'm getting the same error as @posthok with the app crashing.

It only happens when you activate a flow with the door sensor in it (either as trigger or as "AND" capability)
You can still see the status of the sensor in the mobile card before it is crashing, so it is just a trigger/status problem.

It start with a smaller error:

Stack trace:

TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_contact.get (/drivers/switch/driver.js:129:28)
at Object. (/drivers/switch/flows.js:51:39)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

But in time it generates the error @posthok is showing.

This includes in app version 1.1.5 (@ Homey FW 0.8.38)
Cold (few minutes) boot doesn't help.
Readding (all) sensor's doesn't work.
Reinstalling doen't work.

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 15, 2016

@caseda: Can confirm this
Kaku App 1.15 Still brings no solution.
Stack trace:

TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_night.get (/drivers/switch/driver.js:123:28)
at Object. (/drivers/switch/flows.js:44:37)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

Send a log 08181EE31A

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

@caseda Turning off the power, wait a few minutes and start again. This helps.

@posthok posthok closed this Jun 16, 2016

@caseda

This comment has been minimized.

Copy link

commented Jun 16, 2016

This did not work for me, like I mentioned in my previous post.
Had it off the power for atleast 5 minutes.

Will try longer periode when I get home

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

@caseda yes you are right still doesn't right
@Dennishacq whe have still a problem with 1.15. Opened a new issue #689
TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_contact.get (/drivers/switch/driver.js:129:28)
at Object. (/drivers/switch/flows.js:51:39)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7),TypeError: Cannot read property 'variables' of undefined
at Object.module.exports.self.capabilities.alarm_motion.get (/drivers/switch/driver.js:117:28)
at Object. (/drivers/switch/flows.js:37:38)
at emitThree (events.js:102:20)
at Object.emit (events.js:175:7)
at /homey-app/manager/flow.js:1:194
at /homey-app/helpers/client.js:1:868
at Array.forEach (native)
at process. (/homey-app/helpers/client.js:1:835)
at emitTwo (events.js:87:13)
at process.emit (events.js:172:7)

removing sensors an readding them brings no solution.

@Dennishacq

This comment has been minimized.

Copy link

commented Jun 16, 2016

Hey guys, this is indeed a bug that still exists in v1.0.5.
I'm working on a fix that should be online later today.

@Dennishacq Dennishacq reopened this Jun 16, 2016

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

great thanx

@Dennishacq

This comment has been minimized.

Copy link

commented Jun 16, 2016

The update is online ;)

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

Yes Thanx updated the app allready.

@caseda

This comment has been minimized.

Copy link

commented Jun 16, 2016

Already did notice it.
And it fixes the bug perfectly (YAY!)

Thank you @Dennishacq for these quick fixes

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

Did a quick test. Everything is working again. Thanx Dennis!!!

@posthok posthok closed this Jun 16, 2016

@Dennishacq

This comment has been minimized.

Copy link

commented Jun 16, 2016

I'm very glad to hear it's working again. Sorry for the inconvenience guys!

@posthok

This comment has been minimized.

Copy link
Author

commented Jun 16, 2016

boton_me_gusta svg

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
You can’t perform that action at this time.