Author Topic: Duwi 05443 z-wave wall mounted transmitter problems  (Read 1643 times)

mhorst

  • Veteran
  • ***
  • Posts: 72
    • View Profile
Duwi 05443 z-wave wall mounted transmitter problems
« on: March 30, 2011, 10:22:47 pm »
I'm slowly expanding my z-wave home automation. I bought a wall-mounted transmitter with the intention of placing it next to my front door and using it to  change my house mode when leaving/entering the house.

I managed to include it with my Aeon labs usb stick (press the button on the stick and then press and hold the include button on the transmitter for 2seconds). After that I inserted the usb stick back into my core and did a quick reload of the router.

Unfortunately the ZWave device then crashed:

Code: [Select]
========== NEW LOG SECTION ==========
1 03/30/11 20:03:08 80 (spawning-device) Starting... 50
1 03/30/11 20:03:08 80 (spawning-device) Found /usr/pluto/bin/ZWave
01 03/30/11 20:03:08.755 TranslateSerialUSB pci0000:00/0000:00:0b.0+1 result /dev/ttyUSB0 <0xb71806c0>
36 03/30/11 20:03:08.756 Initialization... <0xb71806c0>
36 03/30/11 20:03:08.756 Open serial port /dev/ttyUSB0 <0xb71806c0>
36 03/30/11 20:03:08.778 Get version <0xb71806c0>
36 03/30/11 20:03:08.778 Get home/node id <0xb71806c0>
36 03/30/11 20:03:08.778 Get capabilities <0xb71806c0>
36 03/30/11 20:03:08.778 Get SUC node id <0xb71806c0>
36 03/30/11 20:03:08.778 Get init data <0xb71806c0>
05 03/30/11 20:03:08.780 Creating child 81 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 82 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 83 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 89 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
36 03/30/11 20:03:08.778 receiveFunction started <0xb717fb90>
40 03/30/11 20:03:08.891 Sending job 0x88c4d20 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb717fb90>
41 03/30/11 20:03:08.896 0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x37 0x38 0x0 0x1 0x9b (####Z-Wave 2.78###) <0xb717fb90>
36 03/30/11 20:03:08.896 Got reply to ZW_VERSION: <0xb717fb90>
01 03/30/11 20:03:08.896 ZWave Version: 2.78 <0xb717fb90>
40 03/30/11 20:03:08.999 Sending job 0x88c53f0 (cb 0) - 0x1 0x3 0x0 0x20 0xdc (### #) <0xb717fb90>
41 03/30/11 20:03:09.004 0x1 0x8 0x1 0x20 0x11 0x11 0x11 0x5d 0x1 0x9b (### ###]##) <0xb717fb90>
36 03/30/11 20:03:09.004 Got reply to ZW_MEMORY_GET_ID: <0xb717fb90>
01 03/30/11 20:03:09.004 Home id: 0x1111115d, our node id: 1 <0xb717fb90>
40 03/30/11 20:03:09.107 Sending job 0x88c5610 (cb 0) - 0x1 0x3 0x0 0x7 0xfb (#####) <0xb717fb90>
41 03/30/11 20:03:09.116 0x1 0x2b 0x1 0x7 0x3 0x7 0x0 0x0 0x0 0x1 0x0 0x1 0xfe 0x80 0xfe 0x88 0xf 0x0 0x0 0x0 0xfb 0x97 0x7f 0x82 0x7 0x0 0x0 0x80 0x0 0x80 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x47 (#+##########################################G) <0xb717fb90>
36 03/30/11 20:03:09.116 Got reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES: <0xb717fb90>
01 03/30/11 20:03:09.116 SerAppV:3,r7,Manf 0,Typ 1,Prod 1 <0xb717fb90>
40 03/30/11 20:03:09.219 Sending job 0x88c5830 (cb 0) - 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb717fb90>
41 03/30/11 20:03:09.226 0x1 0x4 0x1 0x56 0x1 0xad (###V##) <0xb717fb90>
05 03/30/11 20:03:09.227 Got reply to GET_SUC_NODE_ID, node: 1 <0xb717fb90>
40 03/30/11 20:03:09.327 Sending job 0x88c5a50 (cb 0) - 0x1 0x3 0x0 0x2 0xfe (#####) <0xb717fb90>
41 03/30/11 20:03:09.379 0x1 0x25 0x1 0x2 0x5 0x8 0x1d 0x81 0x0 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 0x3 0x1 0x4b (#%#K) <0xb717fb90>
36 03/30/11 20:03:09.380 Got reply to FUNC_ID_SERIAL_API_GET_INIT_DATA: <0xb717fb90>
40 03/30/11 20:03:09.483 Sending job 0x88f1198 (cb 0) - 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb717fb90>
41 03/30/11 20:03:09.488 0x1 0x9 0x1 0x41 0x92 0x16 0x0 0x2 0x2 0x1 0x33 (###A######3) <0xb717fb90>
36 03/30/11 20:03:09.488 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.488 ***FOUND NODE: 1 <0xb717fb90>
36 03/30/11 20:03:09.488 listening node <0xb717fb90>
36 03/30/11 20:03:09.488 BASIC TYPE: Static Controller <0xb717fb90>
36 03/30/11 20:03:09.489 GENERIC TYPE: Static Controller <0xb717fb90>
36 03/30/11 20:03:09.489 SPECIFIC TYPE: 0x1 <0xb717fb90>
36 03/30/11 20:03:09.492 No device capabilities for node: 1 <0xb717fb90>
36 03/30/11 20:03:09.492 Requesting node info from node 1 <0xb717fb90>
40 03/30/11 20:03:09.591 Sending job 0x88f13b8 (cb 0) - 0x1 0x4 0x0 0x41 0x8 0xb2 (###A##) <0xb717fb90>
41 03/30/11 20:03:09.595 0x1 0x9 0x1 0x41 0xd2 0x9c 0x0 0x4 0x11 0x3 0xee (###A#######) <0xb717fb90>
36 03/30/11 20:03:09.596 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.596 ***FOUND NODE: 8 <0xb717fb90>
36 03/30/11 20:03:09.596 listening node <0xb717fb90>
36 03/30/11 20:03:09.596 optional functionality <0xb717fb90>
36 03/30/11 20:03:09.596 BASIC TYPE: Routing Slave <0xb717fb90>
36 03/30/11 20:03:09.597 GENERIC TYPE: Multilevel Switch <0xb717fb90>
36 03/30/11 20:03:09.597 SPECIFIC TYPE: 0x3 <0xb717fb90>
36 03/30/11 20:03:09.600 Device capabilities: 114,134,130,135,117,112,133,39,37,38 <0xb717fb90>
40 03/30/11 20:03:09.700 Sending job 0x88f15d8 (cb 0) - 0x1 0x4 0x0 0x41 0x11 0xab (###A##) <0xb717fb90>
41 03/30/11 20:03:09.703 0x1 0x9 0x1 0x41 0x12 0x96 0x0 0x1 0x1 0x1 0x33 (###A######3) <0xb717fb90>
36 03/30/11 20:03:09.704 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.704 ***FOUND NODE: 17 <0xb717fb90>
36 03/30/11 20:03:09.704 sleeping node <0xb717fb90>
36 03/30/11 20:03:09.704 optional functionality <0xb717fb90>
36 03/30/11 20:03:09.704 BASIC TYPE: Controller <0xb717fb90>
36 03/30/11 20:03:09.705 GENERIC TYPE: Generic Controller <0xb717fb90>
36 03/30/11 20:03:09.705 SPECIFIC TYPE: 0x1 <0xb717fb90>
05 03/30/11 20:03:09.705 ZWave::InternalIDToDevice() No device found for id 17 <0xb717fb90>
Return code: 132
3 03/30/11 20:03:09 80 (spawning-device) Device died... count=50/50 dev=80
Wed Mar 30 20:03:09 CEST 2011 died
3 03/30/11 20:03:19 80 (spawning-device) Aborting restart of device 80...

I have no idea why the crash occurs. If a node id is not found the InternalIDToDevice function returns NULL, but as far as I can see all the clients of the function handle that case.

Anyway, after some fiddling around I got the idea to manually add a child device to my zwave device with the correct node id.
This helped, the zwave device is now starting again. The template I used is "ZWave Controller".

Now I'm still trying to figure out how to make LinuxMCE respond when I press the switch. So far no events are generated and since the switch has the z-wave capabilities 114 (manufacturer specific), 128 (battery) and 133 (association) that doesn't really suprise me.
I could associate the switch with another device and then respond to the status changed events from that device, but that seems pretty inelegant.

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: Duwi 05443 z-wave wall mounted transmitter problems
« Reply #1 on: March 31, 2011, 09:29:17 pm »
this is a bug, please update to the latest Zwave package when it becomes available (in the next hours).

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

mhorst

  • Veteran
  • ***
  • Posts: 72
    • View Profile
Re: Duwi 05443 z-wave wall mounted transmitter problems
« Reply #2 on: April 03, 2011, 01:53:07 pm »
Ah, a missing c_str(). Thanks, that helped.

I did some research, the fact that I don't get events from the module seems to be a problem with the module itself.
Other home automation systems seem to have the same problem (http://www.domoticaforum.eu/viewtopic.php?f=26&t=4757&start=0&hilit=wandzender+event (in dutch)).
The work-around is to associate the module with another device and then use events from that device.

I don't like that work-around since it would mean my LinuxMCE house mode is directly linked to the status of one of my devices.
I.e. some device would have to be either always on or always off when I'm at home. Or I would have to get a separate z-wave module that is not connected to any real device and use that, but that seems like a waste of money.

BTW I updated the wiki page http://wiki.linuxmce.org/index.php/Düwi_Popp_ZW_WS_05443 with the English manual for this module.
I havent added the problem with the events to the page yet, since Valent added there that the module works without caveats. I PM-ed him, hoping he can tell me if he has the event problem too, or found a way around it.

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: Duwi 05443 z-wave wall mounted transmitter problems
« Reply #3 on: April 03, 2011, 08:04:42 pm »
getting live status updates from the device did not work for me either. E.g. with merten switches we get a BASIC ON/OFF when the switch is toggled as the core is associated into group 1 by default (SIS mode). This will then trigger the proper event for floorplan updates and such..

With the Duewi you need to wait till the polling detects a state change..

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

mhorst

  • Veteran
  • ***
  • Posts: 72
    • View Profile
Re: Duwi 05443 z-wave wall mounted transmitter problems
« Reply #4 on: April 21, 2012, 05:11:07 pm »
I now have http://wiki.linuxmce.org/index.php/ZME_06443. Same hardware as the Duewi, but new firmware.
With this new firmware the LinuxMCE core receives device On/Off events from the controller.

Yay :)

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: Duwi 05443 z-wave wall mounted transmitter problems
« Reply #5 on: April 21, 2012, 08:09:19 pm »
yeah the guy doing this firmware is quite smart, I had some discussions with him in the past.
rock your home - http://www.agocontrol.com home automation