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
@jwoudenberg it was a typo and correct now on the latest version on github.
If you could test for me i will push this version to the appstore
But after some futher testing (i only tested the 1 push flows) it seems that none of the double press flows are working.
Or do i need to change a setting on the device settings for this to work ?
- single press key 1
- double press key 2
- single press key 3
- double press key 4
Based on this log, I can check that Popp is following the default Central Scene implementation (or not) and advise @m-ruiter (again) how to modify the driver....
It seems that button 2 doesn't generate any logs when double pressing key 2.
Are you sure that the parameters set are corresponding to the settings required for double press and central scene in the manual? Can you show them?
manual: http://www.popp.eu/wp-content/uploads/2015/11/Manual_KFOB_POPP-C_En.pdf
I've tested the following, default (8) and all buttons using (4) send scenes.
Only single clicks work, not double.
Yes, that are the default settings i also had. But with these settings it does not work.
The kfob is probably working a lot like/the same as the Zwave.Me ones?
Which on their turn work the same as the WALLC-S controller?
Maybe have a look at the Zwave.Me driver? or is one already a copy of the other?
I'm awaiting some z-wave stuff to get in so i can test.
- Saving settings fails (only when a setting is changed), after 2 minutes of waiting I get the error message "Homey offline".
- It doesn't update the status(on/off) when using the device button, I think polling should occur every 5? seconds.
Never mind, it seems like the Düwi wall plug switch(054375) is shipped with different firmware then the Popp version(which has the same manufacturerId/productTypeId/productId). My "Saving settings fails"-issue comes due to the fact that my Düwi switch does not implements the "Configuration"-command class(confirmed by pepper1).throw err;
^
at Function.Module._resolveFilename (module.js:489:15)
at Function.Module._load (module.js:439:25)
at Module.require (module.js:517:17)
at Module.require (/opt/homey-client/system/manager/ManagerApps/bootstrap/sdk/v2/index.js:1:253)
at require (internal/module.js:11:18)
at Object.<anonymous> (/node_modules/homey-meshdriver/lib/util/color.js:3:15)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
The non-beta app works fine!
This is the stack trace:
const nodeCommandClassVersion = nodeCommandClass.version;
^
at P004001._getCapabilityObj (/node_modules/homey-meshdriver/lib/zwave/ZwaveDevice.js:346:51)
at P004001._registerCapabilityRealtime (/node_modules/homey-meshdriver/lib/zwave/ZwaveDevice.js:274:36)
at P004001.registerCapability (/node_modules/homey-meshdriver/lib/zwave/ZwaveDevice.js:423:8)
at P004001.onMeshInit (/drivers/004001/device.js:11:8)
at P004001.once (/node_modules/homey-meshdriver/lib/zwave/ZwaveDevice.js:28:28)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:105:13)
at P004001.emit (events.js:207:7)
at process.nextTick (/node_modules/homey-meshdriver/lib/MeshDevice.js:43:11)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
Are you able to run a debug session and post the output ?
Like when downloaded from my github then do athom project --run ?
This might be fixed in the meshdriver now, as the line number where it happened (346) is way lower then it is now (542).
Up try updating the mesh driver module
I've the POPP Z-weather device for detecting windspeeds, but it won't show the windspeed values in Homey. So also not sure if it's working correct to get my shutters up when there's too much wind.
I created a flow which checks the changed windspeed like this:
This log is what I have about the device. Not sure if you need this.
And are you running on the normal or the beta version of the app ?
I'm running the normal version of the app. Do you recommend first installing the beta to see if things get fixed?
Not sure how to go in debug mode yet? Can I install athom cli from he app store or do I have to do everything via the terminal (I'm running macOS)? I can do the latter with a step to step guideline. Not confident enough to do it on my own commandline skills...
Cheers...
Bit hesitant, since I have to remove them all from the ceiling in that case.
Smoke detectors cannot be selected as input device anymore, only output(alarm):
(so I have some broken alarm flows right now indeed)
Also the (backup)battery status seems to have disappeared when compared to the 1.1.7 version:
Things tried so far: re-include the device in the Zwave network(remove - add) for 1 device
This did not change the behaviour of the device.
Smokedetector still behave as alarm when selected as output device though.
Hope you can fix these things.
are you on slack so we can troubleshoot ?
Battery status now comes in only when device reports so it can take a day.
My popp valves only report in once a week with battery
I can proceed tonight when I get home if that's ok with you
I am willing to participate in troubleshooting, just tell me what to do, I am able to have a look at it either tonight or tomorrow afternoon/evening
edit: just checking, these 2.x drivers are supposed to work on Homey 1.5.x versions right...? or are they intended for the Homey 2.x beta?
Second acording the technical information. its hase a no and nc contact. But its the otherway round the drawing says.
When instaling it like this i have a nc contact, so using the other contact so having the normaly open. Could it be that therefor it drain the batt??
Did also make a github isseu for it