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

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #90 on: April 26, 2009, 05:26:17 pm »
Hi again,

what I forgot. The remote does also not charge when attached to an USB port.

Greetings
Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #91 on: April 27, 2009, 09:20:07 am »
Hi Hari,

* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle). We've seen two occurences of the Tricklestar stick to suddenly suspend operation. For a rock solid install use either the seluxit (EU) or the intermatic (US) dongle. The problems are big enough that zensys even forked the 4.x version for the latest chips..

How do I check what firmware I have ? And where can we find a 4.x for the Tricklestar 300ZW-EU-W ? (google and tricklestar homepage did not give me any hints)

Quote
* The Tricklestar remote has issues in SIS mode. The add node procedure stops working after a few inclusions (no clear pattern yet). 0710 has no direct workaround, 0810 allows to do a "remove node" and "add node" to re-include it as inclusion controller (exclude, factory reset, include again). 0710 users can do the same with a "z-wave tool".

Will that also help if the remote does not do anything anymore. Meaning no lights when pressing the button ?

Greetings
Viking

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #92 on: April 28, 2009, 05:09:44 pm »
Will that also help if the remote does not do anything anymore. Meaning no lights when pressing the button ?

in config mode? that sounds way broken. When my remote locks up it behaves as intended, just does not include stuff (blinks red instead of green).
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 #93 on: April 28, 2009, 05:13:23 pm »
just as a note, the issues are not yet fully investigated:
* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle).
Hi,
Just received a tricklestar dongle. I used to have lots of issues with my MCV dongle, mainly zwave functionality suddenly disappearing. I had someone suggest the tricklestar, but some strange things happen with it. If you have a minute, look at this:

oh, you are the first one reporting problems with the MCV dongle. It has the same library version as the Tricklestar (5.02 iirc). I'll look at the network HAIL command, maybe it helps in that regard. The author of the MCV z-wave stack told me that he had similiar problems recently, I'll try to find out how they worked around (I assume "HAIL" but I have to look more closely after my hollidays).

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

totallymaxed

  • LinuxMCE God
  • ****
  • Posts: 4660
  • Smart Home Consulting
    • View Profile
    • Dianemo - at home with technology
Re: New Z-Wave driver
« Reply #94 on: May 03, 2009, 05:22:00 pm »
Just received a tricklestar dongle. I used to have lots of issues with my MCV dongle, mainly zwave functionality suddenly disappearing.
oh, you are the first one reporting problems with the MCV dongle. It has the same library version as the Tricklestar (5.02 iirc). I'll look at the network HAIL command, maybe it helps in that regard. The author of the MCV z-wave stack told me that he had similiar problems recently, I'll try to find out how they worked around (I assume "HAIL" but I have to look more closely after my hollidays).

Well,  I do agree it is probably related to the stack/library combo, as I now have totally similar behaviour from the Tricklestar, like this:
Code: [Select]
41      04/29/09 19:22:35.429           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:35.429           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:35.429           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:38.545           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
40      04/29/09 19:22:38.645           Sending job 0x81db210 (cb 212) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xd4 0xeb (###### ####) <0xb791cb90>
41      04/29/09 19:22:38.649           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:38.649           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:38.649           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:41.773           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
40      04/29/09 19:22:41.873           Sending job 0x81db210 (cb 212) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xd4 0xeb (###### ####) <0xb791cb90>
41      04/29/09 19:22:41.877           ACK RECEIVED <0xb791cb90>
41      04/29/09 19:22:41.877           0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb791cb90>
36      04/29/09 19:22:41.877           ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb791cb90>
36      04/29/09 19:22:45.005           No callback received: await_callback: 212 timer: 31 <0xb791cb90>
36      04/29/09 19:22:45.005           ERROR: Dropping command, no callback received after three resends <0xb791cb90>

Since it only happens after a while, and the zwave stack returns "Error: ZW_SEND failed, retrying <0xb793fb90>" many times before these delivery errors, could it be that the zwave driver be "flooded" with stacked commands?

I will check out the MCV forum, too. Have a nice holiday!


EDIT:  Aaron B let me know that MCV Vera checks if the USB dongle fails to connect to all nodes, and if such is the case, it sends a ZW_Softreset to the dongle. That gets things working again.
I tried to do this (perhaps I made a mistake), but I got a "not implemented" result. Not sure, really, if a ZW_softreset should be the final solution but it is a viable workaround until something better comes up. We can think about the trigger, because if you have 20+ nodes and a polling interval of 30s it would take 10 minutes to discover that the USB stick is messed up...



We've never seen this... so I wonder why that would be?

Andrew
Andy Herron,
CHT Ltd

For Dianemo/LinuxMCE consulting advice;
@herron on Twitter, totallymaxed+inquiries@gmail.com via email or PM me here.

Get Dianemo-Rpi2 ARM Licenses http://forum.linuxmce.org/index.php?topic=14026.0

Get RaspSqueeze-CEC or Raspbmc-CEC for Dianemo/LinuxMCE: http://wp.me/P4KgIc-5P

Facebook: https://www.facebook.com/pages/Dianemo-Home-Automation/226019387454465

http://www.dianemo.co.uk

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #95 on: May 05, 2009, 06:33:46 pm »
the new driver supports the deactivation of polling, but the DCE command is only in 0810 (SetPollingState iirc).

But it's easy to patch that in. But to solve the problem, I'm thinking about an error counter, giving more weight to errors if multiple devices are "failing", with a soft reset if the overall error counter gets too high. I'll play a bit with that this weekend.

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

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #96 on: May 07, 2009, 10:24:34 am »
Hi Hari,
just as a note, the issues are not yet fully investigated:

* The recent 5.x firmwares can be problematic (MCV, tricklestar dongle). We've seen two occurences of the Tricklestar stick to suddenly suspend operation. For a rock solid install use either the seluxit (EU) or the intermatic (US) dongle. The problems are big enough that zensys even forked the 4.x version for the latest chips..

I am going to go crazy ... It seem I have really bad luck with my LinuxMCE hardware :(

This now also happened to me. The trickelstar 300ZW-EU-W stopped working a couple of days ago :( It worked for a couple of days and then stopped doing anything :(

Can I somehow find out what firmware I have and mayby downgrade it ?


Here is a log part from now trying to turn a light on.

Code: [Select]
2       05/07/09 10:07:03       35 (spawning-device)    Device requests restart... count=1/50 dev=35
Thu May  7 10:07:03 CEST 2009 Restart
========== NEW LOG SECTION ==========
1       05/07/09 10:07:11       35 (spawning-device)    Starting... 1
1       05/07/09 10:07:11       35 (spawning-device)    Found /usr/pluto/bin/ZWave
36      05/07/09 10:07:25.477           Initialization... <0xb797a6c0>
36      05/07/09 10:07:25.477           Open serial port /dev/ttyUSB0 <0xb797a6c0>
36      05/07/09 10:07:25.514           Get version <0xb797a6c0>
36      05/07/09 10:07:25.514           Get home/node id <0xb797a6c0>
36      05/07/09 10:07:25.514           Get capabilities <0xb797a6c0>
36      05/07/09 10:07:25.514           Get SUC node id <0xb797a6c0>
36      05/07/09 10:07:25.514           Get init data <0xb797a6c0>
36      05/07/09 10:07:25.514           receiveFunction started <0xb7979b90>
36      05/07/09 10:07:28.686           No callback received: await_callback: 134718256 timer: 31 <0xb7979b90>
40      05/07/09 10:07:28.786           Sending job 0x8082b00 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb7979b90>
05      05/07/09 10:07:37.524           Creating child 36 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>
05      05/07/09 10:07:37.524           Creating child 37 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>
05      05/07/09 10:07:37.524           Creating child 99 <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb797a6c0>
05      05/07/09 10:07:37.524           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb797a6c0>

36      05/07/09 10:08:22.747           Received command for child <0xb6977b90>
36      05/07/09 10:08:22.747           SET LEVEL RECEIVED FOR CHILD 8, level: 100 <0xb6977b90>
That's all there came.

Greetings
Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #97 on: May 07, 2009, 11:01:06 am »
HI again,

I unplugged the Tricklestar and inserted it again (and confirmed that it is a zwave device on orbiter). Now it works again.

Still I would like to know how to downgrade firmware and find out what version I have :)

Greetings
Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #98 on: May 12, 2009, 10:16:32 am »
Hi again,

yesterday the stick stopped working again :
Code: [Select]
36 05/11/09 16:59:01.390  We have been idle for 30 seconds, polling device states <0xb78bab90>
40 05/11/09 16:59:01.490  Sending job 0x8336fe8 (cb 19) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x13 0x2c (###### ###,) <0xb78bab90>
41 05/11/09 16:59:01.498  ACK RECEIVED <0xb78bab90>
41 05/11/09 16:59:01.498  0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bab90>
36 05/11/09 16:59:01.498  ZW_SEND delivered to Z-Wave stack <0xb78bab90>
41 05/11/09 16:59:01.518  0x1 0x5 0x0 0x13 0x13 0x0 0xfa (#######) <0xb78bab90>
36 05/11/09 16:59:01.518  ZW_SEND Response with callback 19 received <0xb78bab90>
36 05/11/09 16:59:01.518  ZW_SEND was successful, removing job <0xb78bab90>
41 05/11/09 16:59:01.586  0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0x0 0xd8 (#####\n# ###) <0xb78bab90>
36 05/11/09 16:59:01.586  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:01.586  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:01.586  Got basic report from node 10, value: 0 <0xb78bab90>
36 05/11/09 16:59:32.051  We have been idle for 30 seconds, polling device states <0xb78bab90>
40 05/11/09 16:59:32.151  Sending job 0x8337208 (cb 20) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x14 0x2b (###### ###+) <0xb78bab90>
41 05/11/09 16:59:32.155  ACK RECEIVED <0xb78bab90>
41 05/11/09 16:59:32.155  0x1 0x4 0x1 0x13 0x1 0xe8 (######) <0xb78bab90>
36 05/11/09 16:59:32.155  ZW_SEND delivered to Z-Wave stack <0xb78bab90>
41 05/11/09 16:59:32.183  0x1 0x5 0x0 0x13 0x14 0x0 0xfd (#######) <0xb78bab90>
36 05/11/09 16:59:32.184  ZW_SEND Response with callback 20 received <0xb78bab90>
36 05/11/09 16:59:32.184  ZW_SEND was successful, removing job <0xb78bab90>
41 05/11/09 16:59:32.207  0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (####### ###) <0xb78bab90>
36 05/11/09 16:59:32.208  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:32.208  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:32.208  Got basic report from node 2, value: 0 <0xb78bab90>
41 05/11/09 16:59:32.331  0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0x0 0xd8 (#####\n# ###) <0xb78bab90>
36 05/11/09 16:59:32.332  FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78bab90>
36 05/11/09 16:59:32.332  COMMAND_CLASS_BASIC -  <0xb78bab90>
36 05/11/09 16:59:32.332  Got basic report from node 10, value: 0 <0xb78bab90>
05 05/11/09 17:00:01.818  void ClientSocket::Disconnect() on this socket: 0x807a1c0 (m_Socket: 7) <0xb78bb6c0>
Return code: 0
2 05/11/09 17:00:01 35 (spawning-device) Shutting down... count=2/50 dev=35
Mon May 11 17:00:01 CEST 2009 Shutdown

Did not use Linuxmce at all yesterday. And today I was told to reload router - and after that the ZWave stick was detected again and I was asked if it is an Serial or ZWave device.

The restart I have posted here. It seems to work after the quick reload, but it is very anoying.

Posted the log of the restart here :
http://pastebin.com/f6b61b6e7

I don't understand why it found 16 nodes !?  I had some trouble getting the new Inclusion stick working so I added some of the devces and removed them afain a couple of times. But the highest number of my three devices I have added until now is 10 !?
Maybe someone can enlighten me !?

Greetings
Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #99 on: May 14, 2009, 01:26:39 pm »
Hi,

sometime the commands does not work, like this. Node 2 and node 10 (outside lights) are turned on af sunset and node 10 is turned off again at sunrise. (Node 2 is turned off at midnight and that worked, but just to be sure also at sunrise)

The command off is sent, but it is not turned off. As you can see in the last line where it delivers a value of 255.

Any ideas ?

Node 10 is an Merten 507001
Node 2 is an ACT ZRP-200

I am using the ZWave-0.0.2-0710-32bit.bz2 version.
Should I try a newer version of the ZWave programm ? I could setup a developement system on VMware and compile it. But will it work ? And whet version ? Newest or some trunk ?

Code: [Select]
36      05/14/09 5:09:01.160            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:01.160            Got basic report from node 10, value: 255 <0xb78d9b90>
36      05/14/09 5:09:01.579            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.579            OFF RECEIVED FOR CHILD 2 <0xb68d7b90>
36      05/14/09 5:09:01.590            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.590            OFF RECEIVED FOR CHILD 10 <0xb68d7b90>
40      05/14/09 5:09:01.659            Sending job 0x81503b0 (cb 179) - 0x1 0xa 0x0 0x13 0x2 0x3 0x20 0x1 0x0 0x5 0xb3 0x70 (ESC[31;1m#\n#### ####pESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.663            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.671            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.672            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.716            0x1 0x5 0x0 0x13 0xb3 0x0 0x5a (ESC[33;1m######ZESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND Response with callback 179 received <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/14/09 5:09:01.816            Sending job 0x81505d0 (cb 180) - 0x1 0xa 0x0 0x13 0xa 0x3 0x20 0x1 0x0 0x5 0xb4 0x7f (ESC[31;1m#\n##\n# #####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.824            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.824            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.824            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.988            0x1 0x5 0x0 0x13 0xb4 0x0 0x5d (ESC[33;1m######]ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND Response with callback 180 received <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/14/09 5:09:32.809            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/14/09 5:09:32.913            Sending job 0x81507f0 (cb 181) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb5 0x8a (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:32.921            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:32.921            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.921            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:32.945            0x1 0x5 0x0 0x13 0xb5 0x0 0x5c (ESC[33;1m######\ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND Response with callback 181 received <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/14/09 5:09:32.965            0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.965            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:32.965            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:32.965            Got basic report from node 2, value: 0 <0xb78d9b90>
41      05/14/09 5:09:33.209            0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0xff 0x27 (ESC[33;1m#####\n# ##'ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:33.209            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:33.209            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:33.209            Got basic report from node 10, value: 255 <0xb78d9b90>

Greetings
Viking

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #100 on: May 14, 2009, 01:33:49 pm »
the merten got switched off, but not the ACT. I don't see any errors in the logs. I'd suggest to replace the ZRP. I also have one going havoc here sometimes..

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

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #101 on: May 18, 2009, 04:35:30 pm »
the merten got switched off, but not the ACT. I don't see any errors in the logs. I'd suggest to replace the ZRP. I also have one going havoc here sometimes..

Well, I now have ordered an Innovus - I really hope thats better ...

Thanks for your efforts on this :)

BTW. would it make sence to compile a newer version of your ZWave program and test that ?

Greetings
Viking

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2428
    • View Profile
    • ago control
Re: New Z-Wave driver
« Reply #102 on: May 18, 2009, 05:51:16 pm »
the latest driver has some improvements and bugfixes.. so it is always worth compiling if you ask me :-) Look at the changelog in trac for specific changes.

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

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #103 on: May 21, 2009, 12:09:49 am »
Hi Hari,

what do I do to get the new Innovus running. Can I resuse the config in the SIS inclusion remote or do I have to
1. exclude all devices again
2. reset the SIS remote ?
3. remove the old ZWave controller
4. add the new ZWave controller
5. and then folow the SIS "manual" instructions from the wiki.

I tried just unplugging the old Zwave controller and plugging the inovus in. But the SIS remote did not want to enter configuration mode (hold up key and then press up short). It always gave me a red light.

Thanks
Viking

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Re: New Z-Wave driver
« Reply #104 on: May 28, 2009, 09:35:33 am »
Hi,

this problem is not fixed using the Innovus controller.

Hi,

sometime the commands does not work, like this. Node 2 and node 10 (outside lights) are turned on af sunset and node 10 is turned off again at sunrise. (Node 2 is turned off at midnight and that worked, but just to be sure also at sunrise)

The command off is sent, but it is not turned off. As you can see in the last line where it delivers a value of 255.

Any ideas ?

Node 10 is an Merten 507001
Node 2 is an ACT ZRP-200

I am using the ZWave-0.0.2-0710-32bit.bz2 version.
Should I try a newer version of the ZWave programm ? I could setup a developement system on VMware and compile it. But will it work ? And whet version ? Newest or some trunk ?

Code: [Select]
36      05/14/09 5:09:01.160            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:01.160            Got basic report from node 10, value: 255 <0xb78d9b90>
36      05/14/09 5:09:01.579            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.579            OFF RECEIVED FOR CHILD 2 <0xb68d7b90>
36      05/14/09 5:09:01.590            Received command for child <0xb68d7b90>
36      05/14/09 5:09:01.590            OFF RECEIVED FOR CHILD 10 <0xb68d7b90>
40      05/14/09 5:09:01.659            Sending job 0x81503b0 (cb 179) - 0x1 0xa 0x0 0x13 0x2 0x3 0x20 0x1 0x0 0x5 0xb3 0x70 (ESC[31;1m#\n#### ####pESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.663            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.671            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.672            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.716            0x1 0x5 0x0 0x13 0xb3 0x0 0x5a (ESC[33;1m######ZESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND Response with callback 179 received <0xb78d9b90>
36      05/14/09 5:09:01.716            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/14/09 5:09:01.816            Sending job 0x81505d0 (cb 180) - 0x1 0xa 0x0 0x13 0xa 0x3 0x20 0x1 0x0 0x5 0xb4 0x7f (ESC[31;1m#\n##\n# #####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:01.824            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:01.824            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.824            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:01.988            0x1 0x5 0x0 0x13 0xb4 0x0 0x5d (ESC[33;1m######]ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND Response with callback 180 received <0xb78d9b90>
36      05/14/09 5:09:01.988            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/14/09 5:09:32.809            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/14/09 5:09:32.913            Sending job 0x81507f0 (cb 181) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb5 0x8a (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/14/09 5:09:32.921            ACK RECEIVED <0xb78d9b90>
41      05/14/09 5:09:32.921            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.921            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/14/09 5:09:32.945            0x1 0x5 0x0 0x13 0xb5 0x0 0x5c (ESC[33;1m######\ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND Response with callback 181 received <0xb78d9b90>
36      05/14/09 5:09:32.945            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/14/09 5:09:32.965            0x1 0x9 0x0 0x4 0x0 0x2 0x3 0x20 0x3 0x0 0xd0 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:32.965            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:32.965            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:32.965            Got basic report from node 2, value: 0 <0xb78d9b90>
41      05/14/09 5:09:33.209            0x1 0x9 0x0 0x4 0x0 0xa 0x3 0x20 0x3 0xff 0x27 (ESC[33;1m#####\n# ##'ESC[0m) <0xb78d9b90>
36      05/14/09 5:09:33.209            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/14/09 5:09:33.209            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/14/09 5:09:33.209            Got basic report from node 10, value: 255 <0xb78d9b90>

Greetings
Viking

I am now using the Innovus instead of the Tricklestar controller. But unfortunately it also does not wok stable :(

On the Orbiter I got the message "changes happend, I need to reload" - could it be the reason that it did not work ? What could be the reason for this ? Can I somewhere find out what happened that made LinuxMCE want to do a quick reload ?
I did not change anything myself.

Now :
Node 4 is the Merten 507001
Node 3 is the ACT ZRP-200

Node 3 was turned off at midnight (but to be sure it is also turned off at sunrise). And Node 4 should turn off at sunrise - what it not did :(

here are the logs
Code: [Select]
36      05/28/09 4:46:50.165            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:46:50.265            Sending job 0x8479ac8 (cb 183) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb7 0x88 (ESC[31;1m###### ####ESC[0m
) <0xb78d9b90>
41      05/28/09 4:46:50.266            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:46:50.268            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.268            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:46:50.290            0x1 0x5 0x0 0x13 0xb7 0x0 0x5e (ESC[33;1m######^ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.290            ZW_SEND Response with callback 183 received <0xb78d9b90>
36      05/28/09 4:46:50.290            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:46:50.314            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.314            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:46:50.314            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:46:50.314            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:46:50.395            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:46:50.396            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:46:50.396            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:46:50.396            Got basic report from node 4, value: 255 <0xb78d9b90>
36      05/28/09 4:47:20.930            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:47:21.030            Sending job 0x8479ce8 (cb 184) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xb8 0x87 (ESC[31;1m###### ####ESC[0m
) <0xb78d9b90>
41      05/28/09 4:47:21.032            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:21.034            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.034            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:21.054            0x1 0x5 0x0 0x13 0xb8 0x0 0x51 (ESC[33;1m######QESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.055            ZW_SEND Response with callback 184 received <0xb78d9b90>
36      05/28/09 4:47:21.055            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:47:21.079            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.079            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:21.079            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:21.079            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:47:21.161            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:21.161            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:21.161            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:21.161            Got basic report from node 4, value: 255 <0xb78d9b90>
36      05/28/09 4:47:22.283            Received command for child <0xb68d7b90>
36      05/28/09 4:47:22.284            OFF RECEIVED FOR CHILD 4 <0xb68d7b90>
36      05/28/09 4:47:22.285            Received command for child <0xb68d7b90>
36      05/28/09 4:47:22.285            OFF RECEIVED FOR CHILD 3 <0xb68d7b90>
40      05/28/09 4:47:22.286            Sending job 0x8479f08 (cb 185) - 0x1 0xa 0x0 0x13 0x4 0x3 0x20 0x1 0x0 0x5 0xb9 0x7c (ESC[31;1m#\n#### ####|ESC[0m) <0xb78d9b90>
41      05/28/09 4:47:22.288            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:22.291            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.291            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:22.334            0x1 0x5 0x0 0x13 0xb9 0x0 0x50 (ESC[33;1m######PESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.334            ZW_SEND Response with callback 185 received <0xb78d9b90>
36      05/28/09 4:47:22.334            ZW_SEND was successful, removing job <0xb78d9b90>
40      05/28/09 4:47:22.439            Sending job 0x847a128 (cb 186) - 0x1 0xa 0x0 0x13 0x3 0x3 0x20 0x1 0x0 0x5 0xba 0x78 (ESC[31;1m#\n#### ####xESC[0m) <0xb78d9b90>
41      05/28/09 4:47:22.442            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:22.444            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.444            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:22.487            0x1 0x5 0x0 0x13 0xba 0x0 0x53 (ESC[33;1m######SESC[0m) <0xb78d9b90>
36      05/28/09 4:47:22.487            ZW_SEND Response with callback 186 received <0xb78d9b90>
36      05/28/09 4:47:22.487            ZW_SEND was successful, removing job <0xb78d9b90>
36      05/28/09 4:47:52.927            We have been idle for 30 seconds, polling device states <0xb78d9b90>
40      05/28/09 4:47:53.028            Sending job 0x847a348 (cb 187) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0xbb 0x84 (ESC[31;1m###### ####ESC[0m) <0xb78d9b90>
41      05/28/09 4:47:53.029            ACK RECEIVED <0xb78d9b90>
41      05/28/09 4:47:53.031            0x1 0x4 0x1 0x13 0x1 0xe8 (ESC[33;1m######ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.031            ZW_SEND delivered to Z-Wave stack <0xb78d9b90>
41      05/28/09 4:47:53.052            0x1 0x5 0x0 0x13 0xbb 0x0 0x52 (ESC[33;1m######RESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.052            ZW_SEND Response with callback 187 received <0xb78d9b90>
36      05/28/09 4:47:53.052            ZW_SEND was successful, removing job <0xb78d9b90>
41      05/28/09 4:47:53.076            0x1 0x9 0x0 0x4 0x0 0x3 0x3 0x20 0x3 0x0 0xd1 (ESC[33;1m####### ###ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.076            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:53.076            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:53.076            Got basic report from node 3, value: 0 <0xb78d9b90>
41      05/28/09 4:47:53.234            0x1 0x9 0x0 0x4 0x0 0x4 0x3 0x20 0x3 0xff 0x29 (ESC[33;1m####### ##)ESC[0m) <0xb78d9b90>
36      05/28/09 4:47:53.234            FUNC_ID_APPLICATION_COMMAND_HANDLER: <0xb78d9b90>
36      05/28/09 4:47:53.234            COMMAND_CLASS_BASIC -  <0xb78d9b90>
36      05/28/09 4:47:53.234            Got basic report from node 4, value: 255 <0xb78d9b90>

Greetings
Viking