Author Topic: New Z-Wave driver  (Read 79331 times)

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #30 on: November 11, 2008, 05:11:39 pm »
Many thanks for this release, it's working pretty nicely now  :P!
nice to hear, you are welcome :-)

Quote
I tested the dimmer and the binary switch, and both are sending the correct infos in the orbiter. Great job  :)! If you need some logs from the binary switch just tell me.
perfect, I was not sure about the binary. Yes, a few log lines for final QA would be nice.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

yannko

  • Regular Poster
  • **
  • Posts: 22
    • View Profile
Re: New Z-Wave driver
« Reply #31 on: November 13, 2008, 02:20:01 pm »
Here are the logs for the binary switch:

When turned on:
Code: [Select]
41 11/13/08 14:16:23.799 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0xff 0x2c (####### ##,) <0xb7995b90>
36 11/13/08 14:16:23.800 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7995b90>
36 11/13/08 14:16:23.800 COMMAND_CLASS_BASIC -  <0xb7995b90>
36 11/13/08 14:16:23.800 Got BASIC_SET from node 3, value 255 <0xb7995b90>
36 11/13/08 14:16:23.800 State changed, send light changed event <0xb7995b90>
36 11/13/08 14:16:23.800 ZWave::SendLightChangedEvents sending commands/events <0xb7995b90>
36 11/13/08 14:16:23.800 Sending EVENT_State_Changed_CONST event from node 3, level 255 <0xb7995b90>


And when turned off:
Code: [Select]
41 11/13/08 14:15:04.686 0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x1 0x0 0xd3 (####### ###) <0xb7995b90>
36 11/13/08 14:15:04.686 FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb7995b90>
36 11/13/08 14:15:04.686 COMMAND_CLASS_BASIC -  <0xb7995b90>
36 11/13/08 14:15:04.686 Got BASIC_SET from node 3, value 0 <0xb7995b90>
36 11/13/08 14:15:04.686 State changed, send light changed event <0xb7995b90>
36 11/13/08 14:15:04.686 ZWave::SendLightChangedEvents sending commands/events <0xb7995b90>
36 11/13/08 14:15:04.686 Sending EVENT_State_Changed_CONST event from node 3, level 0 <0xb7995b90>

That works smoothly for now  :), many thanks!

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #32 on: November 13, 2008, 03:07:43 pm »
cool, exactly as I've expected.

br, Hari
rock your home - http://www.agocontrol.com home automation

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #33 on: November 14, 2008, 07:41:56 pm »
I have a merten dimmer installed at the moment (thanks possy :-) ), I'm sure I can work that out this weekend.

Hari, any progress on the Merten stick? (Hopefully I did not miss an announcement!)
If you still need one, I could lend you mine for a while.

Cheers
Mark
I've received the dongle this week.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

habazot

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: New Z-Wave driver
« Reply #34 on: November 23, 2008, 11:14:16 pm »
Hi, do you have a 64bit version of the new ZWave binary as well..?.
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #35 on: November 23, 2008, 11:23:49 pm »
Hi, do you have a 64bit version of the new ZWave binary as well..?.
no.

Quote
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
if you ask me, yes.

br, Hari
rock your home - http://www.agocontrol.com home automation

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #36 on: November 30, 2008, 11:21:42 pm »
good news, the creation of the open Z-Wave driver package is now included in the build process. 0810alpha has Z-Wave :-)

br, Hari
rock your home - http://www.agocontrol.com home automation

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #37 on: January 02, 2009, 09:04:59 pm »
you should see speed improvements. E.g. the fiire chief with multiple lamps in the same room now works much better.

br, Hari
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #38 on: January 25, 2009, 10:11:40 pm »
Hi, do you have a 64bit version of the new ZWave binary as well..?.
no.

Quote
On a general note: is using 64bit LMCE going to cause me more pain than gain..?..
if you ask me, yes.

br, Hari

Can you please explain why you think 64 bit is not as good as 32.
I will most probarbly do a reinstall shortly(system cannot find device-logfiles etc from webadmin so I have destroyed something) and are using "64 bit hw" and 64 lmce now so any input is interesting to know.

Also I wonder if I want to convert the 32bit driver you have done to suit 64 bit hardware. What process should I google? (compile?)

Still Very thankful(glad) for the help I got with the Connect hw selection.(it works!) but config is sometimes lost..
Best Regards
johan

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #39 on: January 25, 2009, 11:54:17 pm »
to stay on topic: they should _not_ forget the config. Go and have them replaced.

the 32/64bit thing does not belong here.. there are other threads where the topic is discussed.

br, Hari
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #40 on: January 26, 2009, 09:51:15 am »
Ok, I will let the system run for a few days and evaluate. Could also just being me doing something wrongly maybe..
Sorry for the OT. was not sure how to treat it since it was related to the driver, will start another thread about that.  :)

edit. will not start another thread since I did more thourough searches on the matter and are now convinced to install the 32bit instead.

-johan
« Last Edit: January 26, 2009, 10:02:12 am by johanr »

KingCrab

  • Regular Poster
  • **
  • Posts: 45
    • View Profile
Re: New Z-Wave driver
« Reply #41 on: January 30, 2009, 09:57:37 am »
Hi,

I've just started rebuilding my Linuxmce system and I'm thinking to include a new set of zwave devices to it.

As Merten inwall devices seem to be the best choice for me, I want to ask if there is any progress on the Merten Usb stick right now?
Alternatively, is it possible to start only with two inwall devices and the Tricklestar combi (stick + remote) or do I need an additional static controller?

I'm an absolutely newbie with the whole zwave thing, please be kind  ;)

Thanks in advance

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #42 on: January 30, 2009, 12:53:12 pm »
the tricklestar is no "combi" thing, you mix that with the MCV stick.

I usually recommend SIS mode, read a recent remote (like the tricklestar) and a static controller. If you don't want to use a remote get the MCV stick, it has an include button.

The merten usb chip is not supported by the linux kernel, so I have no way to access the zensys chip. Better get another dongle.

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

johanr

  • Veteran
  • ***
  • Posts: 144
    • View Profile
Re: New Z-Wave driver
« Reply #43 on: February 01, 2009, 12:12:27 am »
Hi!

reinstalled and I am now running 32bit. Lmce found my previously added zwave devices and I added them back. Then after functioncheck I changed to the updated driver.
For some reason the Seluxit wont respond. Made a restart of the system(after a few quick reloads) but it did not help.
Rolled back the driver and after restart everything was fine again =/ hmm.
Got a thought that maybe I need to add the devices with the new driver. So all devices has been excluded but I just cannot get them back by including.
 Nor do the Seluxit give a response "OK" on the download config.
Maybe like some other guy here that had problem and it was related to a group id. However I cannot figure out the node id and the rest so..
Here's a print from when I sent "download config" from LMCE Admin and never got a respons back and onwards since it seem to have made a restart.

Hope you or someone that hopefully understand the output can help me get it working.

Code: [Select]
41   01/31/09 23:59:09.810              ACK RECEIVED <0xb78bcb90>
41   01/31/09 23:59:09.812              0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bcb90>
36   01/31/09 23:59:09.812              ZW_SEND delivered to Z-Wave stack <0xb78bcb90>
41   01/31/09 23:59:09.833              0x1 0x5 0x0 0x13 0x5 0x0 0xec (#######) <0xb78bcb90>
36   01/31/09 23:59:09.833              ZW_SEND Response with callback 5 received <0xb78bcb90>
36   01/31/09 23:59:09.833              ZW_SEND was successful, removing job <0xb78bcb90>
36   01/31/09 23:59:10.162              Received command #757 - Download Configuration <0xb68bab90>
36   01/31/09 23:59:10.162              Download configuration start <0xb68bab90>
36   01/31/09 23:59:10.162              Replicate controller start <0xb68bab90>
40   01/31/09 23:59:10.233              Sending job 0x80a0700 (cb 0) - 0x1 0x4 0x0 0x50 0x1 0xaa (###P##) <0xb78bcb90>
41   01/31/09 23:59:10.234              ACK RECEIVED <0xb78bcb90>
36   01/31/09 23:59:40.453              We have been idle for 30 seconds, polling device states <0xb78bcb90>
40   01/31/09 23:59:40.553              Sending job 0x80a0920 (cb 6) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x6 0x39 (###### ###9) <0xb78bcb90>
41   01/31/09 23:59:40.554              ACK RECEIVED <0xb78bcb90>
41   01/31/09 23:59:40.556              0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bcb90>
36   01/31/09 23:59:40.556              ZW_SEND delivered to Z-Wave stack <0xb78bcb90>
41   01/31/09 23:59:40.577              0x1 0x5 0x0 0x13 0x6 0x0 0xef (#######) <0xb78bcb90>
36   01/31/09 23:59:40.577              ZW_SEND Response with callback 6 received <0xb78bcb90>
36   01/31/09 23:59:40.577              ZW_SEND was successful, removing job <0xb78bcb90>
36   02/01/09 0:00:10.162               Download configuration end <0xb68bab90>
36   02/01/09 0:00:10.162               Replicate controller end <0xb68bab90>
36   02/01/09 0:00:10.162               Get new init data after replication <0xb68bab90>
05   02/01/09 0:00:10.163               Socket::ReceiveData 0x807a2c0 failed, bytes left 0 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #31 <0xb68bab90>
01   02/01/09 0:00:10.164               Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Dumping 1 locks <0xb68bab90>
05   02/01/09 0:00:10.164               finished check for exceptions <0xb68bab90>
05   02/01/09 0:00:10.164               OL: (0x807a40c) (>104) MessageQueue Command_Impl.cpp l:822 time: 1:00:00a (1233442810 s) thread: 3070999440 Rel: Y Got: Y <0xb68bab90>
Return code: 2
2 02/01/09 00:00:10     31 (spawning-device)    Device requests restart... count=3/50 dev=31
Sun Feb  1 00:00:10 CET 2009 Restart
========== NEW LOG SECTION ==========
1 02/01/09 00:00:18     31 (spawning-device)    Starting... 3
1 02/01/09 00:00:18     31 (spawning-device)    Found /usr/pluto/bin/ZWave
36   02/01/09 0:00:18.493               Initialization... <0xb79976c0>
36   02/01/09 0:00:18.493               Open serial port /dev/ttyACM0 <0xb79976c0>
36   02/01/09 0:00:18.496               receiveFunction started <0xb7996b90>
36   02/01/09 0:00:18.496               Get version <0xb79976c0>
36   02/01/09 0:00:18.496               Get home/node id <0xb79976c0>
36   02/01/09 0:00:18.496               Get capabilities <0xb79976c0>
36   02/01/09 0:00:18.496               Get SUC node id <0xb79976c0>
36   02/01/09 0:00:18.496               Get init data <0xb79976c0>
36   02/01/09 0:00:21.621               No callback received: await_callback: 134720552 timer: 31 <0xb7996b90>
40   02/01/09 0:00:21.721               Sending job 0x80825f8 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb7996b90>
41   02/01/09 0:00:21.722               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.723               0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x34 0x30 0x0 0x1 0x90 (####Z-Wave 2.40###) <0xb7996b90>
36   02/01/09 0:00:21.724               TODO: handle response for 0x15  <0xb7996b90>
40   02/01/09 0:00:21.821               Sending job 0x8082818 (cb 0) - 0x1 0x3 0x0 0x20 0xdc (### #) <0xb7996b90>
41   02/01/09 0:00:21.822               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.823               0x1 0x8 0x1 0x20 0x0 0x5b 0x93 0x75 0x1 0x6a (### #[#u#j) <0xb7996b90>
36   02/01/09 0:00:21.824               Got reply to ZW_MEMORY_GET_ID, Home id: 0x005b9375, our node id: 1 <0xb7996b90>
40   02/01/09 0:00:21.921               Sending job 0x8082a38 (cb 0) - 0x1 0x3 0x0 0x7 0xfb (#####) <0xb7996b90>
41   02/01/09 0:00:21.922               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:21.954               0x1 0x2b 0x1 0x7 0x2 0x4c 0x0 0x0 0x0 0x1 0x0 0x1 0xfe 0x80 0xfe 0x88 0xf 0x0 0x0 0x0 0xfb 0x9f 0x7f 0x80 0x7 0x0 0x0 0x0 0x0 0x80 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x87 (#+###L#######################################) <0xb7996b90>
36   02/01/09 0:00:21.954               TODO: handle response for 0x7  <0xb7996b90>
40   02/01/09 0:00:22.053               Sending job 0x8082c58 (cb 0) - 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb7996b90>
41   02/01/09 0:00:22.054               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.055               0x1 0x4 0x1 0x56 0x1 0xad (###V##) <0xb7996b90>
36   02/01/09 0:00:22.055               Got reply to GET_SUC_NODE_ID, node: 1 <0xb7996b90>
40   02/01/09 0:00:22.153               Sending job 0x8082e78 (cb 0) - 0x1 0x3 0x0 0x2 0xfe (#####) <0xb7996b90>
41   02/01/09 0:00:22.154               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.201               0x1 0x25 0x1 0x2 0x4 0x8 0x1d 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 0x1 0xca (#%#) <0xb7996b90>
36   02/01/09 0:00:22.202               Got reply to FUNC_ID_SERIAL_API_GET_INIT_DATA: <0xb7996b90>
36   02/01/09 0:00:22.202               found node 1 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 2 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 3 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 4 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 5 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 6 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 7 <0xb7996b90>
36   02/01/09 0:00:22.202               found node 8 <0xb7996b90>
40   02/01/09 0:00:22.301               Sending job 0x8083098 (cb 0) - 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb7996b90>
41   02/01/09 0:00:22.302               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.303               0x1 0x9 0x1 0x41 0xd2 0x6 0x0 0x2 0x2 0x1 0x63 (###A######c) <0xb7996b90>
36   02/01/09 0:00:22.304               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.304               ***FOUND NODE: 1 <0xb7996b90>
36   02/01/09 0:00:22.304               listening node <0xb7996b90>
36   02/01/09 0:00:22.304               optional functionality <0xb7996b90>
36   02/01/09 0:00:22.304               BASIC TYPE: Static Controller <0xb7996b90>
36   02/01/09 0:00:22.304               GENERIC TYPE: Static Controller <0xb7996b90>
36   02/01/09 0:00:22.304               SPECIFIC TYPE: 1 <0xb7996b90>
40   02/01/09 0:00:22.401               Sending job 0x80832b8 (cb 0) - 0x1 0x4 0x0 0x41 0x2 0xb8 (###A##) <0xb7996b90>
41   02/01/09 0:00:22.402               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.403               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.404               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.404               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.501               Sending job 0x80834d8 (cb 0) - 0x1 0x4 0x0 0x41 0x3 0xb9 (###A##) <0xb7996b90>
41   02/01/09 0:00:22.502               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.503               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.503               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.504               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.601               Sending job 0x80836f8 (cb 0) - 0x1 0x4 0x0 0x41 0x4 0xbe (###A##) <0xb7996b90>
41   02/01/09 0:00:22.602               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.603               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.603               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.604               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.701               Sending job 0x8083918 (cb 0) - 0x1 0x4 0x0 0x41 0x5 0xbf (###A##) <0xb7996b90>
41   02/01/09 0:00:22.702               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.703               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.703               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.704               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.801               Sending job 0x809afc0 (cb 0) - 0x1 0x4 0x0 0x41 0x6 0xbc (###A##) <0xb7996b90>
41   02/01/09 0:00:22.802               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.803               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.803               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.804               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:22.901               Sending job 0x809b1e0 (cb 0) - 0x1 0x4 0x0 0x41 0x7 0xbd (###A##) <0xb7996b90>
41   02/01/09 0:00:22.902               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:22.903               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:22.903               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:22.904               Invalid generic class (0), ignoring device <0xb7996b90>
40   02/01/09 0:00:23.001               Sending job 0x809b400 (cb 0) - 0x1 0x4 0x0 0x41 0x8 0xb2 (###A##) <0xb7996b90>
41   02/01/09 0:00:23.002               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:23.003               0x1 0x9 0x1 0x41 0x0 0x0 0x0 0x3 0x0 0x0 0xb5 (###A#######) <0xb7996b90>
36   02/01/09 0:00:23.003               Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb7996b90>
36   02/01/09 0:00:23.003               Invalid generic class (0), ignoring device <0xb7996b90>
36   02/01/09 0:00:23.004               Finished building node list: <0xb7996b90>
36   02/01/09 0:00:23.004               Node: 1 basic: 2 generic: 2 specific: 1 pluto: 0 <0xb7996b90>
36   02/01/09 0:00:23.004               Received command #756 - Report Child Devices <0xb7996b90>
36   02/01/09 0:00:23.004               Reporting child devices <0xb7996b90>
05   02/01/09 0:00:30.498               Creating child 32 <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb79976c0>
05   02/01/09 0:00:30.498               Creating child 33 <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb79976c0>
05   02/01/09 0:00:30.498               Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb79976c0>
36   02/01/09 0:00:53.185               We have been idle for 30 seconds, polling device states <0xb7996b90>
40   02/01/09 0:00:53.285               Sending job 0x809fa60 (cb 1) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x1 0x3e (###### ###>) <0xb7996b90>
41   02/01/09 0:00:53.286               ACK RECEIVED <0xb7996b90>
41   02/01/09 0:00:53.288               0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb7996b90>
36   02/01/09 0:00:53.288               ZW_SEND delivered to Z-Wave stack <0xb7996b90>
41   02/01/09 0:00:53.309               0x1 0x5 0x0 0x13 0x1 0x0 0xe8 (#######) <0xb7996b90>
36   02/01/09 0:00:53.309               ZW_SEND Response with callback 1 received <0xb7996b90>
36   02/01/09 0:00:53.309               ZW_SEND was successful, removing job <0xb7996b90>

linuxmce@dcerouter:/var/log/pluto$
-johan
« Last Edit: February 01, 2009, 12:26:24 am by johanr »

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #44 on: February 01, 2009, 10:27:07 am »
Quote
05   02/01/09 0:00:10.163               Socket::ReceiveData 0x807a2c0 failed, bytes left 0 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Command_Impl1 Dev #31 <0xb68bab90>
05   02/01/09 0:00:10.164               Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #31 <0xb68bab90>
01   02/01/09 0:00:10.164               Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #31 <0xb68bab90>

that error looks strange... the DCErouter sends us crap. This is a fresh 0710?

br, Hari
rock your home - http://www.agocontrol.com home automation