more G-Labs products

Author Topic: Aeotec multisensor (model: DSB05-ZWEU) problem  (Read 11828 times)

April 27, 2014, 08:00:53 PM
Reply #15

Gene

  • *****
  • Information
  • Administrator
  • Posts: 1472
  • Tangible is the future!
    • Yet Another Programmer
The Discovery button has been introduced with r371. Are you running the latest update? Refresh the browser page also... you never know.

Have you had any chance of running HG from a terminal? Logs could help a lot.

Cheers,
g.

April 27, 2014, 08:22:47 PM
Reply #16

leuname

  • *
  • Information
  • Newbie
  • Posts: 11
Gene is normal " ./startup.sh" have a lot of information??? almost 1 hour of information.

April 27, 2014, 08:54:57 PM
Reply #17

Gene

  • *****
  • Information
  • Administrator
  • Posts: 1472
  • Tangible is the future!
    • Yet Another Programmer
What do you mean?
./startup just run the HomeGenie service and all output data you see it's "live" data, it's what's happening in that very moment.

g.

April 27, 2014, 09:06:11 PM
Reply #18

leuname

  • *
  • Information
  • Newbie
  • Posts: 11
well, i have the new update and no "Discovery".

and this is the logs when i press get!

April 27, 2014, 09:23:42 PM
Reply #19

Gene

  • *****
  • Information
  • Administrator
  • Posts: 1472
  • Tangible is the future!
    • Yet Another Programmer
Your device is not replying to the configuration get command.
Well it did reply in the last attempt but it answered with a basic report.
This is an example of a correct transaction:

Code: [Select]
2014-04-27T21:18:10.7112810+02:00       MIG.Gateways.WebServiceGateway  192.168.0.6     api/HomeAutomation.ZWave/4/Config.ParameterGet/1/1398626290837     HTTP    GET
SPO < 01 0A 00 13 04 03 70 05 01 05 59 C9
SPI > 06 01 04 01 13 01 E8
SPO < 06
SPI > 01 05 00 13 59 00 B0
SPO < 06
SPI > 01 0E 00 04 00 04 08 70 06 01 01 00 00 00 00 8F
2014-04-27T21:18:10.9235570+02:00       HomeAutomation.ZWave            4       ZWave Node      ZWaveNode.Variables.1      0

This line SPI > 01 0E 00 04 00 04 08 70 06 01 01 00 00 00 00 8F is the reply to the configuration parameter get (70) command class.

Did you ever update the firmware of the device?
Perhaps it's not receiving sufficient power and so not working well.

Cheers,
g.

April 27, 2014, 09:44:00 PM
Reply #20

leuname

  • *
  • Information
  • Newbie
  • Posts: 11
Yes, I did the update to 1.18. I now noticed that the Configuration Variables, even if you choose 0,1,2 or 3, the operation always timeout! I have it connected via usb so do not know if the problem is the power. Also tried it with batteries and equals.


How can i resolve that?

again, tanks for all!

April 30, 2014, 06:23:25 PM
Reply #21

leuname

  • *
  • Information
  • Newbie
  • Posts: 11
Good afternoon again. Now I can pute temperature, humidity and light appearing on homegenie with the sensor. The only thing I can not do is the motion detector .... and already changed the varialvel 4 to the value of 1. What can do?


Tanks for all

December 02, 2014, 08:03:58 PM
Reply #22

NicoVermeir

  • ****
  • Information
  • Sr. Member
  • Posts: 122
    • My blog
sorry to reply on an old thread but I just got the multisensor and I'm running into the same problem. pressing Get on Variable ID 1 always gives a timeout, even after setting 0

the batteries are brand new and the device is updated to the latest firmware. any ideas?

December 02, 2014, 09:25:03 PM
Reply #23

RoChess

  • ***
  • Information
  • Full Member
  • Posts: 61
sorry to reply on an old thread but I just got the multisensor and I'm running into the same problem. pressing Get on Variable ID 1 always gives a timeout, even after setting 0

I have a few of the US model, but the same should apply. Struggled myself to make it work as well, what eventually did it for me was hitting the Z-Wave button on the sensor 3x quick in succession. This will force the sensor into 10-minutes of staying awake to accept Z-Wave commands.

This is also the default setting when you insert/replace batteries, but since I run on USB power for most of mine I guess that changed things a little.

It did not always work, but with some trial, and error I eventually made it work to push the button on the sensor right before I would make the adjustment inside HomeGenie, and right afterwards. Eventually the "Get" would show the updated info to confirm that it worked.

December 02, 2014, 09:50:57 PM
Reply #24

NicoVermeir

  • ****
  • Information
  • Sr. Member
  • Posts: 122
    • My blog
sorry to reply on an old thread but I just got the multisensor and I'm running into the same problem. pressing Get on Variable ID 1 always gives a timeout, even after setting 0

I have a few of the US model, but the same should apply. Struggled myself to make it work as well, what eventually did it for me was hitting the Z-Wave button on the sensor 3x quick in succession. This will force the sensor into 10-minutes of staying awake to accept Z-Wave commands.

This is also the default setting when you insert/replace batteries, but since I run on USB power for most of mine I guess that changed things a little.

It did not always work, but with some trial, and error I eventually made it work to push the button on the sensor right before I would make the adjustment inside HomeGenie, and right afterwards. Eventually the "Get" would show the updated info to confirm that it worked.

no luck... also, the widget just says "Level 1", how can I get it to show the values from the sensors?

December 03, 2014, 12:46:39 AM
Reply #25

RoChess

  • ***
  • Information
  • Full Member
  • Posts: 61
no luck... also, the widget just says "Level 1", how can I get it to show the values from the sensors?

They populate automatic once HomeGenie has retrieved more info. Did you click the "Get" button for the Manufacturer specific info to show? Does it show the correct ID for you now in xxxx:xxxx:xxxx format? Try pushing the Aeon sensor button during this process to ensure all the Z-Wave communication occurs.

Also be sure to add it to group 1 for association, and in worst case unpair it from the interface again to clear any old associations the sensor might have retained, and then re-add it.

December 03, 2014, 08:05:14 AM
Reply #26

NicoVermeir

  • ****
  • Information
  • Sr. Member
  • Posts: 122
    • My blog
everything else seems to work fine, all the get / set commands work except for those commands

December 03, 2014, 07:43:31 PM
Reply #27

NicoVermeir

  • ****
  • Information
  • Sr. Member
  • Posts: 122
    • My blog
did some network sniffing on this.
setting the value calls this url
/api/HomeAutomation.ZWave/6/Config.ParameterSet/1/0/1417628908607?_=1417628390946

this returns http status code 200

clicking the get button calls this url
/api/HomeAutomation.ZWave/6/Config.ParameterGet/1/1417628749880?_=1417628390929
also returns status code 200 with this as json result:
[{ "ResponseValue" : "" }]

can I get an insight in what the values in the urls are? and is it normal that get and set use different values?

December 03, 2014, 10:19:43 PM
Reply #28

faramir

  • *
  • Information
  • Newbie
  • Posts: 2
I'm having the same issue with my Aeotec 4 in 1 sensor.  I am able to add it as a node and set all the variables except Variable ID 1.  Anytime I "Get" that variable I get (operation timeout!).  Setting the variable does nothing (as far as I can tell).  I've tried waking the sensor with it's button (which seems to be required and works for the other variables), but it does no good on Variable ID 1.  I've removed the sensor as a node and replaced multiple time with no luck. 

I thought I might have a defective one until I found this thread and some others that indicated setting up this sensor can be problematic.

December 03, 2014, 10:42:07 PM
Reply #29

nolio

  • *****
  • Information
  • Global Moderator
  • Posts: 544
Hi,
I try on my side and i have the same issue.
I enable my log and take a look and it seems that the id is not the same for each request. I have this for the same device :
Code: [Select]
Config.ParameterGet/101/1417637715311
Config.ParameterGet/101/1417637717242
Config.ParameterGet/101/1417637726347
So i don't think this is the problem. 2 examples in my log :
ID 2 (ok)
HTTP request :
Code: [Select]
Config.ParameterGet/2/1417637708409Zwave :
Code: [Select]
ZWaveNode.Variables.2 1ID 1 (ko)
HTTP request :
Code: [Select]
Config.ParameterGet/1/1417637712200Zwave :
Code: [Select]
///No response///
I am nearly sure that i can do that in a past version of HG ... (probably more than 6 month ..)
Bye