|
Domodude
Guest
|
 |
« on: March 29, 2009, 09:38:57 pm » |
|
Hi, I am running a 0710 install with a new ZWave driver from Hari. Immediately after install, things worked fine (if not just a tad bit sluggish). However, after an hour or so and several ZWave commands, the whole ZWave system seems to have stopped completely. Let me show the log before describing my setup: 40 03/29/09 22:23:05.794 Sending job 0x845cd20 (cb 74) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4a 0x75 (###### ##Ju) <0xb794cb90>
41 03/29/09 22:23:05.798 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:23:05.798 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:23:05.798 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:23:08.918 No callback received: await_callback: 74 timer: 31 <0xb794cb90>
40 03/29/09 22:23:09.018 Sending job 0x845cd20 (cb 74) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4a 0x75 (###### ##Ju) <0xb794cb90>
41 03/29/09 22:23:09.022 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:23:09.022 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:23:09.022 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:23:12.146 No callback received: await_callback: 74 timer: 31 <0xb794cb90>
40 03/29/09 22:23:12.246 Sending job 0x845cd20 (cb 74) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4a 0x75 (###### ##Ju) <0xb794cb90>
41 03/29/09 22:23:12.250 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:23:12.250 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:23:12.250 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:23:15.374 No callback received: await_callback: 74 timer: 31 <0xb794cb90>
36 03/29/09 22:23:15.374 ERROR: Dropping command, no callback received after three resends <0xb794cb90>
The setup is a bit special. I own some Merten equipment, among which the Radio Central Unit ( http://wiki.linuxmce.org/index.php/Merten_5059xx_Connect_Radio_Central_Unit). What I did was set everything up using the Merten software, then update the routing table at the location of the LMCE Core, and then quit the Merten software. This transfers the config to a battery-operated pushbutton. I then went to a MiCasaVerde Vera, and selected the transfer of configuration. This can be initiated by the usual three-times-tap on the Merten pushbutton that is the Primary Controller. This action transfered the config into the MCV stick. The stick was then placed into a USB slot of the Core. LMCE detects the stick, recognizes my lights, and all is well (I think). But all is not well anymore. If I try to turn off the lights in the study, I get this: .....
36 03/29/09 22:25:11.854 No callback received: await_callback: 77 timer: 31 <0xb794cb90>
40 03/29/09 22:25:11.954 Sending job 0x845d380 (cb 77) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4d 0x72 (###### ##Mr) <0xb794cb90>
41 03/29/09 22:25:11.958 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:25:11.958 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:25:11.958 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:25:15.078 No callback received: await_callback: 77 timer: 31 <0xb794cb90>
36 03/29/09 22:25:15.078 ERROR: Dropping command, no callback received after three resends <0xb794cb90>
[b]10 03/29/09 22:25:18.463 Receive string: MESSAGE 67 <0xb694ab90>[/b]
10 03/29/09 22:25:18.463 Received MESSAGE 67 0x807a790 device: 71 <0xb694ab90>
10 03/29/09 22:25:18.464 Received Message type 1 ID 193 from 94 to 85 (device: 71) resp 0 <0xb694ab90>
36 03/29/09 22:25:18.464 Received command for child <0xb694ab90>
36 03/29/09 22:25:18.464 OFF RECEIVED FOR CHILD 25 <0xb694ab90>
10 03/29/09 22:25:18.504 Receive string: MESSAGE 67 <0xb694ab90>
10 03/29/09 22:25:18.504 Received MESSAGE 67 0x807a790 device: 71 <0xb694ab90>
10 03/29/09 22:25:18.505 Received Message type 1 ID 193 from 94 to 86 (device: 71) resp 0 <0xb694ab90>
36 03/29/09 22:25:18.505 Received command for child <0xb694ab90>
36 03/29/09 22:25:18.505 OFF RECEIVED FOR CHILD 26 <0xb694ab90>
36 03/29/09 22:25:45.238 We have been idle for 30 seconds, polling device states <0xb794cb90>
40 03/29/09 22:25:45.338 Sending job 0x845d5a0 (cb 78) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4e 0x71 (###### ##Nq) <0xb794cb90>
41 03/29/09 22:25:45.342 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:25:45.342 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:25:45.342 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:25:48.442 No callback received: await_callback: 78 timer: 31 <0xb794cb90>
40 03/29/09 22:25:48.542 Sending job 0x845d5a0 (cb 78) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4e 0x71 (###### ##Nq) <0xb794cb90>
41 03/29/09 22:25:48.546 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:25:48.546 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:25:48.546 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:25:51.666 No callback received: await_callback: 78 timer: 31 <0xb794cb90>
40 03/29/09 22:25:51.766 Sending job 0x845d5a0 (cb 78) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4e 0x71 (###### ##Nq) <0xb794cb90>
41 03/29/09 22:25:51.770 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:25:51.770 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:25:51.770 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:25:54.878 No callback received: await_callback: 78 timer: 31 <0xb794cb90>
36 03/29/09 22:25:54.878 ERROR: Dropping command, no callback received after three resends <0xb794cb90>
36 03/29/09 22:26:25.122 We have been idle for 30 seconds, polling device states <0xb794cb90>
40 03/29/09 22:26:25.222 Sending job 0x845d7c0 (cb 79) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4f 0x70 (###### ##Op) <0xb794cb90>
41 03/29/09 22:26:25.226 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:26:25.226 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:26:25.226 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:26:28.346 No callback received: await_callback: 79 timer: 31 <0xb794cb90>
40 03/29/09 22:26:28.446 Sending job 0x845d7c0 (cb 79) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4f 0x70 (###### ##Op) <0xb794cb90>
41 03/29/09 22:26:28.450 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:26:28.450 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:26:28.450 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:26:31.570 No callback received: await_callback: 79 timer: 31 <0xb794cb90>
40 03/29/09 22:26:31.670 Sending job 0x845d7c0 (cb 79) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x4f 0x70 (###### ##Op) <0xb794cb90>
41 03/29/09 22:26:31.674 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:26:31.674 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:26:31.674 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:26:34.786 No callback received: await_callback: 79 timer: 31 <0xb794cb90>
36 03/29/09 22:26:34.786 ERROR: Dropping command, no callback received after three resends <0xb794cb90>
36 03/29/09 22:27:04.966 We have been idle for 30 seconds, polling device states <0xb794cb90>
40 03/29/09 22:27:05.066 Sending job 0x845d9e0 (cb 80) - 0x1 0x9 0x0 0x13 0xff 0x2 0x20 0x2 0x5 0x50 0x6f (###### ##Po) <0xb794cb90>
41 03/29/09 22:27:05.070 ACK RECEIVED <0xb794cb90>
41 03/29/09 22:27:05.070 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:27:05.070 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
36 03/29/09 22:27:08.194 No callback received: await_callback: 80 timer: 31 <0xb794cb90>
I am not sure why things stopped working. Is it the way I set it all up? Could it be the driver? Maybe something else? I will gladly post any other information that will help solve this problem! Thanks Mark |
|
|
|
|
Logged
|
|
|
|
|
hari
|
|
« Reply #1 on: March 30, 2009, 12:37:19 pm » |
|
it is surely not the driver. It tried 3 sends, the zensys chip replies with an error:
41 03/29/09 22:23:09.022 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb794cb90>
36 03/29/09 22:23:09.022 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb794cb90>
There is a bug in some recent chips that affect healing/mesh calculation. I do not recommend to transfer roles/move devices around. Dunno if this is related but you seem to have a low level z-wave issue. I've also seen this with some ACT plug units disappearing for a few seconds (other nodes in the network are reachable).
So you are not able to send commands to any device?
best regards,
Hari
|
|
|
|
|
Logged
|
|
|
|
|
Domodude
Guest
|
|
« Reply #2 on: March 31, 2009, 08:13:16 am » |
|
it is surely not the driver.
...
I do not recommend to transfer roles/move devices around.
....
So you are not able to send commands to any device?
Hi Hari, Good to know that it isn't the driver. As far as the transfer, I am not sure how else I could still have the central unit included in the system, so I am motivated to see if this can work. It initially DID work, only after a while it failed. I will try to send commands to the other nodes in a more systematic manner tonight, but every light that I tried recently did not reply to a zwave command from the core. The central unit controls everything fine. Mark Oh... I assume Merten is still as tight as a clam shell  when it comes to programming their central unit using software other than their own? |
|
|
|
|
Logged
|
|
|
|
|
Domodude
Guest
|
|
« Reply #3 on: March 31, 2009, 08:22:59 am » |
|
There is a bug in some recent chips that affect healing/mesh calculation.... Dunno if this is related but you seem to have a low level z-wave issue. I forgot to ask -- do you know if the MCV-stick chip is affected by this bug? Before my most recent routing table recalc, some lights would work but only with a vveerrryyy long delay. It is quite possible that this has to do with a bad mesh, I'd say. The Merten stick itself is not currently supported by your driver ATM, correct? Thanks Mark |
|
|
|
|
Logged
|
|
|
|
|
hari
|
|
« Reply #4 on: March 31, 2009, 02:16:39 pm » |
|
unfortunately I still got no answer on the Q about the usb serial chipset used..
regarding MCV, i'll try to check that.
|
|
|
|
|
Logged
|
|
|
|
|
huh
|
|
« Reply #5 on: April 12, 2010, 02:58:24 am » |
|
I too am having trouble with my ZWave not always working... the light on the floorplan illuminates and turns off as expected, but the actual light does not respond. The fix has been to unplug my MCV ZWave stick and plugging it back in.... was hoping for something more permanent. Usually the above fix works for 5-7 days (I think) and then the lights fail to work. I notice the problem most times when my lamppost fails to turn on at sundown. I only mentioned this incase the Respond to Events has something to do with it... Here's part of my log- 05 04/11/10 20:41:47.745 ^[[33;1mNo callback received: await_callback: 198 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:41:50.955 ^[[33;1mNo callback received: await_callback: 198 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:41:54.163 ^[[33;1mNo callback received: await_callback: 198 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:41:54.163 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:42:27.468 ^[[33;1mNo callback received: await_callback: 199 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:42:30.672 ^[[33;1mNo callback received: await_callback: 199 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:42:33.879 ^[[33;1mNo callback received: await_callback: 199 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:42:33.879 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:42:37.087 ^[[33;1mNo callback received: await_callback: 200 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:42:40.291 ^[[33;1mNo callback received: await_callback: 200 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:42:43.499 ^[[33;1mNo callback received: await_callback: 200 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:42:43.499 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:43:16.816 ^[[33;1mNo callback received: await_callback: 201 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:43:20.023 ^[[33;1mNo callback received: await_callback: 201 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:43:23.235 ^[[33;1mNo callback received: await_callback: 201 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:43:23.235 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:43:26.443 ^[[33;1mNo callback received: await_callback: 202 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:43:29.647 ^[[33;1mNo callback received: await_callback: 202 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:43:32.859 ^[[33;1mNo callback received: await_callback: 202 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:43:32.859 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:44:06.220 ^[[33;1mNo callback received: await_callback: 203 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:44:09.424 ^[[33;1mNo callback received: await_callback: 203 timer: 31^[[0m <0xb71afb90>
05 04/11/10 20:44:12.639 ^[[33;1mNo callback received: await_callback: 203 timer: 31^[[0m <0xb71afb90>
01 04/11/10 20:44:12.639 ^[[31;1mERROR: Dropping command, no callback received after three resends^[[0m <0xb7$
05 04/11/10 20:44:15.844 ^[[33;1mNo callback received: await_callback: 204 timer: 31^[[0m <0xb71afb90>
|
|
|
|
|
Logged
|
|
|
|
|
huh
|
|
« Reply #6 on: April 17, 2010, 04:17:02 am » |
|
Well, only thing that I know changed is that I ran that command to turn off the unix extensions- the problem that wouldn't allow MDs to play media. Looks like that may have also fixed my zwave. Have not rebooted or replugged in the zwave device or anything else.
Anyone else see this?
|
|
|
|
« Last Edit: April 17, 2010, 04:28:18 am by huh »
|
Logged
|
|
|
|
|
chrisbirkinshaw
|
|
« Reply #7 on: July 27, 2010, 08:12:38 pm » |
|
What was "that command"? I have upgraded my core to a new motherboard and now also see the No callback received errors. Sending the reset command to the zwave interface form the web admin fixes it for a while: 1 07/27/10 20:06:11.627 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:06:14.826 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
05 07/27/10 20:06:18.026 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
05 07/27/10 20:06:21.226 No callback received: await_callback: 156 timer: 31 <0xb727cb90>
01 07/27/10 20:06:21.227 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:06:54.552 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
05 07/27/10 20:06:57.750 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
05 07/27/10 20:07:00.950 No callback received: await_callback: 157 timer: 31 <0xb727cb90>
01 07/27/10 20:07:00.951 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:04.151 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
05 07/27/10 20:07:07.354 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
05 07/27/10 20:07:10.559 No callback received: await_callback: 158 timer: 31 <0xb727cb90>
01 07/27/10 20:07:10.559 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:43.867 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
05 07/27/10 20:07:47.066 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
05 07/27/10 20:07:50.267 No callback received: await_callback: 159 timer: 31 <0xb727cb90>
01 07/27/10 20:07:50.268 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:07:53.467 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
05 07/27/10 20:07:56.666 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
05 07/27/10 20:07:59.867 No callback received: await_callback: 160 timer: 31 <0xb727cb90>
01 07/27/10 20:07:59.868 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:08:13.082 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
05 07/27/10 20:08:16.282 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
05 07/27/10 20:08:19.483 No callback received: await_callback: 161 timer: 31 <0xb727cb90>
01 07/27/10 20:08:19.484 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:08:52.811 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
05 07/27/10 20:08:56.012 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
05 07/27/10 20:08:59.215 No callback received: await_callback: 162 timer: 31 <0xb727cb90>
01 07/27/10 20:08:59.215 ERROR: Dropping command, no callback received after three resends <0xb727cb90>
05 07/27/10 20:09:02.410 No callback received: await_callback: 163 timer: 31 <0xb727cb90>
05 07/27/10 20:09:03.046 Got a reload command from 0 <0xb627ab90>
05 07/27/10 20:09:03.297 void ClientSocket::Disconnect() on this socket: 0x96f7090 (m_Socket: 7) <0xb727d6c0>
Return code: 2
2 07/27/10 20:09:03 40 (spawning-device) Device requests restart... count=1/50 dev=40
Tue Jul 27 20:09:03 BST 2010 Restart
========== NEW LOG SECTION ==========
1 07/27/10 20:09:11 40 (spawning-device) Starting... 1
1 07/27/10 20:09:11 40 (spawning-device) Found /usr/pluto/bin/ZWave
05 07/27/10 20:09:12.103 Creating child 41 <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.103 Creating child 42 <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.103 Note: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 43 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 1945 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 1945 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 44 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 45 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:12.104 Creating child 46 <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom event handler for. It will not fire events. <0xb71b16c0>
05 07/27/10 20:09:12.104 Note: Device manager has attached a device of type 38 that this has no custom handler for. This is normal for IR. <0xb71b16c0>
05 07/27/10 20:09:15.199 No callback received: await_callback: 147199752 timer: 31 <0xb71b0b90>
05 07/27/10 20:09:15.419 Got reply to ZW_MEMORY_GET_ID, Home id: 0x00d8c4d8, our node id: 1 <0xb71b0b90>
05 07/27/10 20:09:15.633 Got reply to GET_SUC_NODE_ID, node: 1 <0xb71b0b90>
05 07/27/10 20:09:16.225 Finished building node list: <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 9 basic: 0x4 generic: 0x11 specific: 0x1 pluto: 38 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 11 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb71b0b90>
05 07/27/10 20:09:16.225 Node: 14 basic: 0x3 generic: 0x11 specific: 0x0 pluto: 38 <0xb71b0b90>
If this is a bug I will put in a trac ticket. Anyone know if this is already known? |
|
|
|
|
Logged
|
|
|
|
|
hari
|
|
« Reply #8 on: July 27, 2010, 08:34:20 pm » |
|
Some mcv sticks have a hardware bug, the dingle just gets stuck. There was a replacement program. This looks exactly like that issue.
Br Hari
|
|
|
|
|
Logged
|
|
|
|
|
chrisbirkinshaw
|
|
« Reply #9 on: July 27, 2010, 09:01:47 pm » |
|
I have the tricklestar one. Is that the same?
If it's a hardware issue then how come doing a software reset of the LMCE Zwave device from the web interface fixes it? Couldn't the driver do this reset itself after a bunch of these errors are recognised?
Thanks,
Chris
|
|
|
|
|
Logged
|
|
|
|
|
davegravy
|
|
« Reply #10 on: July 27, 2010, 10:35:32 pm » |
|
I've had this problem for a while too. It could be coincidence, but when I unplug all my other USB peripherals the problem goes away.
Another "cure" i've found is to remove the Z-stick, delete the Z-wave interface device through webadmin, reboot, and then replace the Z-stick. It happens every couple weeks for me.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
hari
|
|
« Reply #12 on: July 28, 2010, 03:01:29 pm » |
|
I have the tricklestar one. Is that the same?
If it's a hardware issue then how come doing a software reset of the LinuxMCE Zwave device from the web interface fixes it? Couldn't the driver do this reset itself after a bunch of these errors are recognised?
Thanks,
Chris
hmm, then something must be messing with the serial port/usb on your machine. I've never seen this (and I've done/seen quite many installations). One thing I did encounter recently, I think I don't do an exclusive open on the serial port.. maybe that would be a good idea.. br Hari |
|
|
|
|
Logged
|
|
|
|
|
hari
|
|
« Reply #13 on: July 28, 2010, 08:44:56 pm » |
|
just checked the code, it *does* flock() the file..
br Hari
|
|
|
|
|
Logged
|
|
|
|
|
chrisbirkinshaw
|
|
« Reply #14 on: July 29, 2010, 08:30:40 pm » |
|
I did a clean install from DVD snapshot on an Asus AT3N7A-I which I know a lot of people are using.
Don't see anything odd in dmesg. I just rebooted and this started happening immediately after the device starts up.
I have a couple of USB-serial adapters, a USB-UIRT, and a WinTv Nova USB attached. Maybe I will try removing these.
|
|
|
|
|
Logged
|
|
|
|
|
