[App] Aeotec by Athom - main discussion topic

CommunityModerators · August 2017

Aeotec by Athom App - main discussion topic

Main discussion topic to centralize all Questions, Answers and Information around the Aeotec App for the Z-wave devices of Aeotec by Aeon Labs (www.aeotec.com)

Links and information:

Athom Homey apps store: https://apps.athom.com/app/com.aeotec
Aeotec App code repository: https://github.com/athombv/com.aeotec (CLI install how to)

Specific device topics:
<Links to other relevant Aeotec topics, e.g. device topics>

Issue resolution and feature requests:

Please be aware that this topic is not actively monitored by Athom; it is a topic maintained by the community to share knowledge within the community.
In order to keep track of issues and feature requests for the Aeotec app, please them at: https://github.com/athombv/com.aeotec/issues

App contribution and co-development:

This app is actively supported by the following community developers: @caseda and @TedTolboom
Contributions to this app can be made by any community members, more information can be found on: https://github.com/athombv/com.aeotec/blob/master/CONTRIBUTING.md

Aeotec App - Frequently Asked Questions

Which devices are supported by the Aeotec app:
In the app store a list of supported devices is shown with picture and description in the 'Supported devices' list. This list is generated by the actual content of the app.
In the readme of the app store, a more detailed list is maintained by the developers, showing the device numbers and the state in which the device has been implemented (e.g. basic support or fully implemented)

My device is not supported, how do I get it implemented into the Aeotec app:
Most devices are implemented but new devices are being developed by Aeotec. If your device is not supported, check on this topic if there are already plans to add support. In addition create a GitHub issue (see link above) to request to add support for this device.

What is the changelog of the Aeotec App:
The changelog of the app is shown in the readme of the app store (see link above), but can also be derived from the commit overview on the Github repository: https://github.com/athombv/com.aeotec/commits/master

Forum Discussion

Initial Discussion created by @TedTolboom
Ask any Moderator to add/update/correct this Discussion.

MarcoF · September 2016

Mod break: merged old Aeotec topic into new main discussion topic to keep history

Today Athom released there Aeotec/Aeon Labs Z-Wave app;
https://apps.athom.com/app/com.aeotec

Here you can discus the app and sensors

MarcoF · September 2016

The new app isn't supporting the widely spread/used and (in)famous DSB05 4:1 motion sensor and so I create a driver for it.

Afbeeldingsresultaat voor DSB05 41 motion sensor

Afbeeldingsresultaat voor DSB05 41 motion sensor

The pull request is here and now its waiting on the merge and new app version.
https://github.com/athombv/com.aeotec/pull/6

[edit]
- Pull-request is accepted and merged.

blusser · September 2016

Can support for the recessed door sensor (non zwave+) be added as well ?
please find attached the console output when adding the sensor

thanks

MarcoF · September 2016

blusser said:

Can support for the recessed door sensor (non zwave+) be added as well ?
please find attached the console output when adding the sensor

thanks

If I have some time in the upcoming days, then I will give it a try.

[edit]
Could you confirm this is the device we are talking about;
http://www.pepper1.net/zwavedb/device/538
And perhaps with the manual see if the parameters are the same.

mruiter · September 2016

Next to the nothingness the kefob now does it also gives an error on its capabillys when you click it. Any idea when the keyfob gets some flow capa's ?

Image: https://forum.athom.com/uploads/editor/t6/vgt5p08kz17f.jpg

blusser · September 2016

MarcoF said:

blusser said:

Can support for the recessed door sensor (non zwave+) be added as well ?
please find attached the console output when adding the sensor

thanks

If I have some time in the upcoming days, then I will give it a try.

[edit]
Could you confirm this is the device we are talking about;
http://www.pepper1.net/zwavedb/device/538
And perhaps with the manual see if the parameters are the same.

Seem to be correct. Model is the same, other info I can't say because I don't have any info about it.
The manual doesn't describe any command classes or other relevant info (only mounting instructions, adding/removing device and warranty info)
So I think we have to assume the command classes are the same until proved otherwise ?

for what is worth : FCC ID XBADSB54
version 501005400001-AA (don't know what this version is about, but it's mentioned in the manual)

Robin · September 2016

@mruiter ;
What does the error message say? Hard to read this way. And what Homey version are you on?

The flow functionality has no eta as of yet. Tried it, but could make it work yet.

TinCup · September 2016

I tried to add two "Recessed Door Sensor Gen5" (zwave+ model ZW089-C, http://www.pepper1.net/zwavedb/device/833) after installing the app, but no success....

pressed the button when asked, but got a timeout and did not add them :-(

Console output:

status WAIT

VM1429:1 status ADD_NODE_STATUS_LEARN_READY

VM1429:1 status ADD_NODE_STATUS_DONE

VM1602:1 status WAIT

VM1602:1 status ADD_NODE_STATUS_LEARN_READY

VM1602:1 status ADD_NODE_STATUS_DONE

device should be supported. Whats going wrong?

Robin · September 2016

Are you sure the devices are not still somehow hooked up to a different controller? Or previous Homey version? I'd try a full hard reset of the devices and then pair again. If that fails the devices might have different productId's.

TinCup · September 2016

Robin said:

Are you sure the devices are not still somehow hooked up to a different controller? Or previous Homey version? I'd try a full hard reset of the devices and then pair again. If that fails the devices might have different productId's.

I did Hard Reset both sensors (press button for 20 secs) tried to add them again, same result.
Powered off/on Homey, tried again., same result.
Tried to add them as generic zwave device, same result. :-(

According to "Engineering Specifications and Advanced Functions for Developers (V1.10) ":

5.3 Z-Wave Plus Info Report Command Class
Parameter Value
Z-Wave Plus Version 1
Role Type 6 (ZWAVEPLUS_INFO_REPORT_ROLE_TYPE_SLAVE_SLEEPING_REPORTING)
Node Type 0 (ZWAVEPLUS_INFO_REPORT_NODE_TYPE_ZWAVEPLUS_NODE)
Installer Icon Type 0x0C00 (ICON_TYPE_GENERIC_SENSOR_NOTIFICATION)
User Icon Type 0x0C00 (ICON_TYPE_GENERIC_SENSOR_NOTIFICATION)

5.4 Manufacturer Specific Report
Parameter Value
Manufacturer ID 1 0x00
Manufacturer ID 2 0x86
Product Type ID 1 EU=0x00, US=0x01, AU=0x02.
Product Type ID 2 0x02
Product ID 1 0x00
Product ID 2 0x59

Is this device supported?

Robin · September 2016

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

TinCup · September 2016

Robin said:

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

I can't find how to enable on debug mode.... i suppose in the athom cli?

MarcoF · September 2016

TinCup said:

Robin said:

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

I can't find how to enable on debug mode.... i suppose in the athom cli?

Navigate to the driver you want to debug.
Open the file driver.js
Look for a section like this:

        module.exports = new ZwaveDriver(path.basename(__dirname), {
            debug: true,
            capabilities: {

Make sure the line in the middle "debug: true," is there.
If it says "debug: false," then change it to "debug: true,"

Then run the app with "athom project --run"

TinCup · September 2016

MarcoF said:
TinCup said:

Robin said:

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

I can't find how to enable on debug mode.... i suppose in the athom cli?

Navigate to the driver you want to debug.
Open the file driver.js
Look for a section like this:
        module.exports = new ZwaveDriver(path.basename(__dirname), {
            debug: true,
            capabilities: {
Make sure the line in the middle "debug: true," is there.
If it says "debug: false," then change it to "debug: true,"

Then run the app with "athom project --run"

I'm not experienced in this. (i only really know REXX pgm language

). I did install the Aeotec app from the app-store, so i think i have to download the pgm-source somehow (github?) to be able to do some debugging? Do i have to uninstall the installed app first?

DaneeDeKruyff · September 2016

TinCup said:
Tried to add them as generic zwave device, same result. :-(

Is this device supported?

Yes, I have no problem with this sensor (2 off them)
The fact your sensor can also not be added as a generic zwave device indicates to me it is not an app issue, but a lower level zwave issue.

RobinVanKekem · September 2016

TinCup said:
I'm not experienced in this. (i only really know REXX pgm language ). I did install the Aeotec app from the app-store, so i think i have to download the pgm-source somehow (github?) to be able to do some debugging? Do i have to uninstall the installed app first?

Download the source with this link: https://github.com/athombv/com.aeotec/archive/master.zip
Install Athom CLI from here: https://developers.athom.com/

TinCup · September 2016

RobinVanKekem said:

TinCup said:
I'm not experienced in this. (i only really know REXX pgm language ). I did install the Aeotec app from the app-store, so i think i have to download the pgm-source somehow (github?) to be able to do some debugging? Do i have to uninstall the installed app first?

Download the source with this link: https://github.com/athombv/com.aeotec/archive/master.zip
Install Athom CLI from here: https://developers.athom.com/

downloaded and extracted the zip file, Athom CLI i had rinsttaled already. Where to put some statements to do some debugging? Then just run the project?

mruiter · September 2016

Robin said:

@mruiter ;
What does the error message say? Hard to read this way. And what Homey version are you on?

The flow functionality has no eta as of yet. Tried it, but could make it work yet.

Sorry for the late response, did not check in last night

The error is : onoff:driver.capabilities:onoff does not exist
So a json file that has the onoff defined i guess.

The keyfob being able to use in flows would be a great asset. My whole already ready alarm system on Homey is awaiting the support.
Then i can start my tests if Homey is already a trustworthy replacement for my powermax.

And yes.. My ISP connection and wifi are backed by UPS.
My homey is connected with a UPS in the USB cable to keep it up for almost half a day without power. Check

RobinVanKekem · September 2016

MarcoF said:
TinCup said:

Robin said:

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

I can't find how to enable on debug mode.... i suppose in the athom cli?

Navigate to the driver you want to debug.
Open the file driver.js
Look for a section like this:
        module.exports = new ZwaveDriver(path.basename(__dirname), {
            debug: true,
            capabilities: {
Make sure the line in the middle "debug: true," is there.
If it says "debug: false," then change it to "debug: true,"

Then run the app with "athom project --run"

TinCup said:

RobinVanKekem said:

TinCup said:
I'm not experienced in this. (i only really know REXX pgm language ). I did install the Aeotec app from the app-store, so i think i have to download the pgm-source somehow (github?) to be able to do some debugging? Do i have to uninstall the installed app first?

Download the source with this link: https://github.com/athombv/com.aeotec/archive/master.zip
Install Athom CLI from here: https://developers.athom.com/

downloaded and extracted the zip file, Athom CLI i had rinsttaled already. Where to put some statements to do some debugging? Then just run the project?

Do as MarcoF said.

TinCup · September 2016

RobinVanKekem said:
MarcoF said:
TinCup said:

Robin said:

The productId matches. But this is not proof that your device has that same productId, only way to find that out is by running the app via command line with debug mode enabled.

I can't find how to enable on debug mode.... i suppose in the athom cli?

Navigate to the driver you want to debug.
Open the file driver.js
Look for a section like this:
        module.exports = new ZwaveDriver(path.basename(__dirname), {
            debug: true,
            capabilities: {
Make sure the line in the middle "debug: true," is there.
If it says "debug: false," then change it to "debug: true,"

Then run the app with "athom project --run"
TinCup said:

RobinVanKekem said:

TinCup said:
I'm not experienced in this. (i only really know REXX pgm language ). I did install the Aeotec app from the app-store, so i think i have to download the pgm-source somehow (github?) to be able to do some debugging? Do i have to uninstall the installed app first?

Download the source with this link: https://github.com/athombv/com.aeotec/archive/master.zip
Install Athom CLI from here: https://developers.athom.com/

downloaded and extracted the zip file, Athom CLI i had rinsttaled already. Where to put some statements to do some debugging? Then just run the project?

Do as MarcoF said.

1/4 - Archiving...

2/4 - Uploading to Homey @ 192.168.1.156:80...

3/4 - Running `com.aeotec`, press CTRL+C to abort...

4/4 - Debugging...

-------------------------------------------------

com.aeotec running...

Error: Cannot find module 'homey-zwavedriver'

at Function.Module._resolveFilename (module.js:325:15)

at Function.Module._load (module.js:276:25)

at Module.require (module.js:353:17)

at require (internal/module.js:12:17)

at Object.<anonymous> (/drivers/DSB05-ZWEU/driver.js:3:21)

at Module._compile (module.js:409:26)

at Object.Module._extensions..js (module.js:416:10)

at Module.load (module.js:343:32)

at Function.Module._load (module.js:300:12)

at Module.require (module.js:353:17)

--- INFO: com.aeotec has been killed ---

TinCup · September 2016

\com.aeotec-master\com.aeotec-master\node_modules\homey-zwavedriver directory is empty, what is missing in the zip-file @RobinVanKekem ?

DaneeDeKruyff · September 2016

This is the missing part: https://github.com/athombv/node-homey-zwavedriver/tree/7a4a147c6237ac30f00b41b1915b8a057b3c576d

It is linked at github here: https://github.com/athombv/com.aeotec/tree/master/node_modules

TinCup · September 2016

DaneeDeKruyff said:

This is the missing part: https://github.com/athombv/node-homey-zwavedriver/tree/7a4a147c6237ac30f00b41b1915b8a057b3c576d
It is linked at github here: https://github.com/athombv/com.aeotec/tree/master/node_modules

okay, i added the zwave driver, added debug: true in \drivers\ZW089\driver.js -> athom project --run ->

com.aeotec running... -> opened console in browser --> add device -> pressed button -> timeout, no device added.

no debug output in console or cli.

should debug placed in some other place?

DaneeDeKruyff · September 2016

I think I'll have to revert to my earlier reply, I think it's a lower level zwave issue. Not sure how to help you with that.

TinCup · September 2016

DaneeDeKruyff said:

I think I'll have to revert to my earlier reply, I think it's a lower level zwave issue. Not sure how to help you with that.

Thanks for your help on this. Maybe Athom (@robin) has any idea on how to tackle this issue?

MarcoF · September 2016

Which device do you try to pair?

[edit]
Nevermind.

Here's a zip with(!) Z-Wave driver and(!) all device drivers with debug enabled.

Unzip the file, go to the unzip folder and run "athom project --run"
Try to pair the device and about 1 min. after the pair, copy whats inside the Command screen and post it here to @Robin ;

TinCup · September 2016

MarcoF said:

Which device do you try to pair?

[edit]
Nevermind.

Here's a zip with(!) Z-Wave driver and(!) all device drivers with debug enabled.

Unzip the file, go to the unzip folder and run "athom project --run"
Try to pair the device and about 1 min. after the pair, copy whats inside the Command screen and post it here to @Robin ;

Again, no output in console and Command screen. I changed debug to true in ZwaveDriver.js also:

class ZwaveDriver extends events.EventEmitter {

constructor( driver_id, options ) {

super();

this.driver = findWhere( Homey.manifest.drivers, { id: driver_id } );

this.options = Object.assign({

debug : true,

capabilities : {}

}, options);

did not help either, still no output. pffff

kludon · September 2016

I have the minimote from Aeotec. Will this be supported in de future / is it on the roadmap?

cautje · September 2016

Hi, my multisensor 6 stays in alarm status movement.
It seems to be connected ok, temp and lux are ok.
Does someone know what is wrong?
THX!

Image: https://forum.athom.com/uploads/editor/24/fomuobe9lpq4.jpg

MarcoF · September 2016

@cautje ;
Is the sensor placed in a situation where there's constant movement? Also check all parameters with the manual to see if, for example, the "movement/tamper off" changes are send. I know, because of the philio development, not all sensor automatically send the off signal.