No problem mate. This is what this forum is for. Itās fun , but can be frustrating when itās not working. 
Yes I was thinking the same thing about the 3 beeps as opposed to one, so I have tried this morning to set the tempo and fan speed on a different setting and then turning the unit off and awaiting the automation to trigger. Low and behold, all 3 commands came through and set the unit up correctly with only the single beep. Perhaps it has something to do with the make of the actual ac unit. Mine is a Midea.
As for powering the ZXT 120, I use USB power from a power board. I would love to have it on battery power just to ensure there isnāt one more item sucking electricity but Iām sure it cannot be always listening and on battery power.
Will advise how things go with removing it from the network and setting it into always listening mode.
Here is my Zwave and HAAS Logs from this morning: (Node 8 is the IR blaster).
It seems that the aircon OFF command was sent, but I do not understand from this log is Node008 was the target of this message or this log comes from the Node008 itself. The fact that it has āsetā and āgetStatusā commands may mean that this is not coming from Node008. Maybe it is expecting Node008 to respond with status and not receiving any status update back?
Anyways, the aircon was never turned off. it kept runningā¦ It was turned-on by that same node last night just fine.
I wonder if there are any clues in these logsā¦ There was some second command in this log that failed. I am not sure what it is.
HAAS Log:
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1973265712-191, service=turn_off, domain=input_boolean, service_data=entity_id=input_boolean.bedroom_aircon>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state input_boolean.bedroom_aircon=off; friendly_name=Bedroom Aircon, icon=mdi:car @ 2017-06-28T07:07:18.120912+08:00>, old_state=<state input_boolean.bedroom_aircon=on; friendly_name=Bedroom Aircon, icon=mdi:car @ 2017-06-28T00:07:45.511577+08:00>, entity_id=input_boolean.bedroom_aircon>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.components.automation] Executing Bedroom Aircon OFF
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event logbook_entry[L]: name=Bedroom Aircon OFF, message=has been triggered, domain=automation, entity_id=automation.bedroom_aircon_off>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.helpers.script] Script Bedroom Aircon OFF: Running script
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.helpers.script] Script Bedroom Aircon OFF: Executing step call service
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=1973265712-192, service=set_operation_mode, domain=climate, service_data=operation_mode=Off, entity_id=['climate.bedroom_climate_control_cooling_1_8_2']>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1973265712-191>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_executed[L]: service_call_id=1973265712-192>
2017-06-28 07:07:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state automation.bedroom_aircon_off=on; friendly_name=Bedroom Aircon OFF, last_triggered=2017-06-28T07:07:18.289201+08:00 @ 2017-06-27T21:48:43.788120+08:00>, old_state=<state automation.bedroom_aircon_off=on; friendly_name=Bedroom Aircon OFF, last_triggered=2017-06-27T12:52:36.759409+00:00 @ 2017-06-27T21:48:43.788120+08:00>, entity_id=automation.bedroom_aircon_off>
Zwave Log:
2017-06-28 07:07:18.211 Info, Node008, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Off
2017-06-28 07:07:18.211 Detail, Node008, Queuing (Send) ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x00, 0x25, 0x79, 0xf0
2017-06-28 07:07:18.211 Detail, Node008, Queuing (Send) ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x7a, 0xf2
2017-06-28 07:07:18.211 Detail,
2017-06-28 07:07:18.211 Info, Node008, Sending (Send) message (Callback ID=0x79, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x00, 0x25, 0x79, 0xf0
2017-06-28 07:07:18.228 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 07:07:18.228 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 07:07:19.453 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x79, 0x00, 0x00, 0x7c, 0xee
2017-06-28 07:07:19.453 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x79 received (expected 0x79)
2017-06-28 07:07:19.453 Info, Node008, Request RTT 1241 Average Request RTT 740
2017-06-28 07:07:19.453 Detail, Expected callbackId was received
2017-06-28 07:07:19.453 Detail, Expected reply was received
2017-06-28 07:07:19.453 Detail, Message transaction complete
2017-06-28 07:07:19.454 Detail,
2017-06-28 07:07:19.454 Detail, Node008, Removing current message
2017-06-28 07:07:19.454 Detail,
2017-06-28 07:07:19.454 Info, Node008, Sending (Send) message (Callback ID=0x7a, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x7a, 0xf2
2017-06-28 07:07:19.462 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 07:07:19.462 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 07:07:19.479 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x7a, 0x00, 0x00, 0x02, 0x93
2017-06-28 07:07:19.480 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x7a received (expected 0x7a)
2017-06-28 07:07:19.480 Info, Node008, Request RTT 25 Average Request RTT 382
2017-06-28 07:07:19.480 Detail, Expected callbackId was received
2017-06-28 07:07:25.609 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x80, 0x03, 0x49, 0x33
2017-06-28 07:07:25.609 Detail,
2017-06-28 07:07:25.609 Info, Node008, Response RTT 6154 Average Response RTT 5916
2017-06-28 07:07:25.609 Info, Node008, Received Battery report from node 8: level=73
2017-06-28 07:07:25.609 Detail, Node008, Refreshed Value: old value=74, new value=73, type=byte
2017-06-28 07:07:25.609 Detail, Node008, Changes to this value are not verified
2017-06-28 07:07:25.609 Detail, Node008, Notification: ValueChanged
2017-06-28 07:07:29.455 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-28 07:07:29.455 Detail, Node008, Removing current message
2017-06-28 07:07:29.455 Detail, Node008, Notification: Notification - TimeOutJust moved that SAME IR blaster to the study and it works perfectly. I will let it sit all day in the study and see if it stops working after few hours. If it does, it something to do with the blaster. If it still works fine, than it something to do with the location on where it is in the bedroom. I also moved my āstudyā IR blaster into the bedroom. If it āstopsā working properly by tonight, it will confirm the Zwave network is the issue. (Will update)
Here are the logs of WORKING execution of the ON and OFF commands:
Successful Aircon ON in study:
2017-06-28 08:24:49.823 Info, Node008, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Cool
2017-06-28 08:24:49.823 Detail, Node008, Queuing (Send) ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x02, 0x25, 0x82, 0x09
2017-06-28 08:24:49.823 Detail, Node008, Queuing (Send) ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x83, 0x0b
2017-06-28 08:24:49.823 Detail,
2017-06-28 08:24:49.824 Info, Node008, Sending (Send) message (Callback ID=0x82, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x02, 0x25, 0x82, 0x09
2017-06-28 08:24:49.832 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:24:49.832 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:24:52.223 Info, Node008, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Cooling 1 - 2 - 1 - 21
2017-06-28 08:24:52.223 Detail, Node008, Queuing (Send) ThermostatSetpointCmd_Set (Node=8): 0x01, 0x0c, 0x00, 0x13, 0x08, 0x05, 0x43, 0x01, 0x02, 0x01, 0x15, 0x25, 0x84, 0x18
2017-06-28 08:24:52.223 Info, Node008, ThermostatSetpointCmd_Get Not Supported on this node
2017-06-28 08:24:55.224 Info, Node008, Value::Set - COMMAND_CLASS_THERMOSTAT_FAN_MODE - Fan Mode - 0 - 1 - Auto Low
2017-06-28 08:24:55.224 Detail, Node008, Queuing (Send) ThermostatFanModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x44, 0x01, 0x00, 0x25, 0x85, 0x08
2017-06-28 08:24:55.224 Detail, Node008, Queuing (Send) ThermostatFanModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x44, 0x02, 0x25, 0x86, 0x0a
2017-06-28 08:24:58.282 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x82, 0x00, 0x03, 0x4d, 0x27
2017-06-28 08:24:58.282 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x82 received (expected 0x82)
2017-06-28 08:24:58.282 Info, Node008, Request RTT 8459 Average Request RTT 4420
2017-06-28 08:24:58.282 Detail, Expected callbackId was received
2017-06-28 08:24:58.283 Detail, Expected reply was received
2017-06-28 08:24:58.283 Detail, Message transaction complete
2017-06-28 08:24:58.283 Detail,
2017-06-28 08:24:58.283 Detail, Node008, Removing current message
2017-06-28 08:24:58.283 Detail,
2017-06-28 08:24:58.283 Info, Node008, Sending (Send) message (Callback ID=0x83, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x83, 0x0b
2017-06-28 08:24:58.292 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:24:58.292 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:24:58.340 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x83, 0x00, 0x00, 0x05, 0x6d
2017-06-28 08:24:58.340 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x83 received (expected 0x83)
2017-06-28 08:24:58.340 Info, Node008, Request RTT 56 Average Request RTT 2238
2017-06-28 08:24:58.340 Detail, Expected callbackId was received
2017-06-28 08:24:59.068 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x40, 0x03, 0x02, 0xb8
2017-06-28 08:24:59.068 Detail,
2017-06-28 08:24:59.068 Info, Node008, Response RTT 785 Average Response RTT 3350
2017-06-28 08:24:59.068 Detail, Node008, Refreshed Value: old value=2, new value=2, type=list
2017-06-28 08:24:59.068 Detail, Node008, Changes to this value are not verified
2017-06-28 08:24:59.068 Info, Node008, Received thermostat mode: Cool
2017-06-28 08:24:59.068 Detail, Node008, Expected reply and command class was received
2017-06-28 08:24:59.068 Detail, Node008, Message transaction complete
2017-06-28 08:24:59.068 Detail,
2017-06-28 08:24:59.069 Detail, Node008, Removing current message
2017-06-28 08:24:59.069 Detail, Node008, Notification: ValueChanged
2017-06-28 08:24:59.107 Detail,
2017-06-28 08:24:59.107 Info, Node008, Sending (Send) message (Callback ID=0x84, Expected Reply=0x13) - ThermostatSetpointCmd_Set (Node=8): 0x01, 0x0c, 0x00, 0x13, 0x08, 0x05, 0x43, 0x01, 0x02, 0x01, 0x15, 0x25, 0x84, 0x18
2017-06-28 08:24:59.115 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:24:59.115 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:24:59.366 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x84, 0x00, 0x00, 0x1a, 0x75
2017-06-28 08:24:59.366 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x84 received (expected 0x84)
2017-06-28 08:24:59.366 Info, Node008, Request RTT 259 Average Request RTT 1248
2017-06-28 08:24:59.366 Detail, Expected callbackId was received
2017-06-28 08:24:59.366 Detail, Expected reply was received
2017-06-28 08:24:59.366 Detail, Message transaction complete
2017-06-28 08:24:59.367 Detail,
2017-06-28 08:24:59.367 Detail, Node008, Removing current message
2017-06-28 08:24:59.367 Detail,
2017-06-28 08:24:59.367 Info, Node008, Sending (Send) message (Callback ID=0x85, Expected Reply=0x13) - ThermostatFanModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x44, 0x01, 0x00, 0x25, 0x85, 0x08
2017-06-28 08:24:59.376 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:24:59.376 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:24:59.470 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x85, 0x00, 0x00, 0x0a, 0x64
2017-06-28 08:24:59.470 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x85 received (expected 0x85)
2017-06-28 08:24:59.470 Info, Node008, Request RTT 102 Average Request RTT 675
2017-06-28 08:24:59.470 Detail, Expected callbackId was received
2017-06-28 08:24:59.470 Detail, Expected reply was received
2017-06-28 08:24:59.470 Detail, Message transaction complete
2017-06-28 08:24:59.470 Detail,
2017-06-28 08:24:59.470 Detail, Node008, Removing current message
2017-06-28 08:24:59.471 Detail,
2017-06-28 08:24:59.471 Info, Node008, Sending (Send) message (Callback ID=0x86, Expected Reply=0x04) - ThermostatFanModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x44, 0x02, 0x25, 0x86, 0x0a
2017-06-28 08:24:59.480 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:24:59.480 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:24:59.527 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x86, 0x00, 0x00, 0x06, 0x6b
2017-06-28 08:24:59.528 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x86 received (expected 0x86)
2017-06-28 08:24:59.528 Info, Node008, Request RTT 56 Average Request RTT 365
2017-06-28 08:24:59.528 Detail, Expected callbackId was received
2017-06-28 08:25:02.654 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x08, 0x03, 0x80, 0x03, 0x42, 0x28
2017-06-28 08:25:02.654 Detail,
2017-06-28 08:25:02.654 Info, Node008, Response RTT 3183 Average Response RTT 3266
2017-06-28 08:25:02.654 Info, Node008, Received Battery report from node 8: level=66
2017-06-28 08:25:02.654 Detail, Node008, Refreshed Value: old value=73, new value=66, type=byte
2017-06-28 08:25:02.655 Detail, Node008, Changes to this value are not verified
2017-06-28 08:25:02.655 Detail, Node008, Notification: ValueChanged
2017-06-28 08:25:03.088 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x08, 0x03, 0x80, 0x03, 0x42, 0x28
2017-06-28 08:25:03.088 Detail,
2017-06-28 08:25:03.088 Info, Node008, Response RTT 3618 Average Response RTT 3442
2017-06-28 08:25:03.088 Info, Node008, Received Battery report from node 8: level=66
2017-06-28 08:25:03.088 Detail, Node008, Refreshed Value: old value=66, new value=66, type=byte
2017-06-28 08:25:03.089 Detail, Node008, Changes to this value are not verified
2017-06-28 08:25:03.089 Detail, Node008, Notification: ValueChanged
2017-06-28 08:25:03.593 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x10, 0x08, 0x03, 0x80, 0x03, 0x42, 0x28
2017-06-28 08:25:03.593 Detail,
2017-06-28 08:25:03.593 Info, Node008, Response RTT 4122 Average Response RTT 3782
2017-06-28 08:25:03.594 Info, Node008, Received Battery report from node 8: level=66
2017-06-28 08:25:03.594 Detail, Node008, Refreshed Value: old value=66, new value=66, type=byte
2017-06-28 08:25:03.594 Detail, Node008, Changes to this value are not verified
2017-06-28 08:25:03.594 Detail, Node008, Notification: ValueChanged
2017-06-28 08:25:04.491 Detail, Node008, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x08, 0x05, 0x31, 0x05, 0x01, 0x01, 0x19, 0xd0
2017-06-28 08:25:04.491 Detail,
2017-06-28 08:25:04.491 Info, Node008, Response RTT 5020 Average Response RTT 4401
2017-06-28 08:25:04.491 Info, Node008, Received SensorMultiLevel report from node 8, instance 1, Temperature: value=25C
2017-06-28 08:25:04.492 Detail, Node008, Refreshed Value: old value=25, new value=25, type=decimal
2017-06-28 08:25:04.492 Detail, Node008, Changes to this value are not verified
2017-06-28 08:25:04.492 Detail, Node008, Notification: ValueChanged
2017-06-28 08:25:09.471 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-28 08:25:09.471 Detail, Node008, Removing current message
2017-06-28 08:25:09.472 Detail, Node008, Notification: Notification - TimeOut
Successful Aircon OFF:
2017-06-28 08:27:30.025 Info, Node008, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Off
2017-06-28 08:27:30.025 Detail, Node008, Queuing (Send) ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x00, 0x25, 0x87, 0x0e
2017-06-28 08:27:30.025 Detail, Node008, Queuing (Send) ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x88, 0x00
2017-06-28 08:27:30.025 Detail,
2017-06-28 08:27:30.025 Info, Node008, Sending (Send) message (Callback ID=0x87, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x40, 0x01, 0x00, 0x25, 0x87, 0x0e
2017-06-28 08:27:30.034 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:27:30.035 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:27:31.490 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x87, 0x00, 0x00, 0x92, 0xfe
2017-06-28 08:27:31.491 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x87 received (expected 0x87)
2017-06-28 08:27:31.491 Info, Node008, Request RTT 1465 Average Request RTT 915
2017-06-28 08:27:31.491 Detail, Expected callbackId was received
2017-06-28 08:27:31.491 Detail, Expected reply was received
2017-06-28 08:27:31.491 Detail, Message transaction complete
2017-06-28 08:27:31.491 Detail,
2017-06-28 08:27:31.491 Detail, Node008, Removing current message
2017-06-28 08:27:31.491 Detail,
2017-06-28 08:27:31.492 Info, Node008, Sending (Send) message (Callback ID=0x88, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x40, 0x02, 0x25, 0x88, 0x00
2017-06-28 08:27:31.500 Detail, Node008, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 08:27:31.501 Detail, Node008, ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 08:27:31.556 Detail, Node008, Received: 0x01, 0x07, 0x00, 0x13, 0x88, 0x00, 0x00, 0x07, 0x64
2017-06-28 08:27:31.556 Detail, Node008, ZW_SEND_DATA Request with callback ID 0x88 received (expected 0x88)
2017-06-28 08:27:31.556 Info, Node008, Request RTT 64 Average Request RTT 489
2017-06-28 08:27:31.556 Detail, Expected callbackId was received
2017-06-28 08:27:32.206 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x40, 0x03, 0x00, 0xba
2017-06-28 08:27:32.206 Detail,
2017-06-28 08:27:32.206 Info, Node008, Response RTT 715 Average Response RTT 2558
2017-06-28 08:27:32.207 Detail, Node008, Refreshed Value: old value=2, new value=0, type=list
2017-06-28 08:27:32.207 Detail, Node008, Changes to this value are not verified
2017-06-28 08:27:32.207 Info, Node008, Received thermostat mode: Off
2017-06-28 08:27:32.207 Detail, Node008, Expected reply and command class was received
2017-06-28 08:27:32.207 Detail, Node008, Message transaction complete
2017-06-28 08:27:32.207 Detail,
2017-06-28 08:27:32.207 Detail, Node008, Removing current message
2017-06-28 08:27:32.207 Detail, Node008, Notification: ValueChanged
2017-06-28 08:27:34.009 Detail, Node008, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x08, 0x03, 0x80, 0x03, 0x49, 0x33
2017-06-28 08:27:34.009 Detail,
2017-06-28 08:27:34.009 Info, Node008, Received Battery report from node 8: level=73
2017-06-28 08:27:34.009 Detail, Node008, Refreshed Value: old value=66, new value=73, type=byte
2017-06-28 08:27:34.009 Detail, Node008, Changes to this value are not verified
2017-06-28 08:27:34.010 Detail, Node008, Notification: ValueChangedI swapped two devices (bedroom and study) both started working perfectly in their new locations. I renamed them and thought the problem solved. But after I woke up the next morning, the problem now exist on the new device that I moved from the study into the bedroom and the old device (now sitting in the study still works perfectly).
So the conclusion is it is Zwave network issueā¦ But not sure what it is.
Bedroom is much closer to the Zwave controller (just behind the wall), so reception should be better there.
Also bedroom has a zwave switch, that could also forward the message.
Totally confused, what the problem may beā¦
If anybody has any idea how to debug this, it would be greatly appreciated.
My next try will be to connect it to permanent power (change the listening mode etcā¦ ). But I really hoped NOT having to do that and be able to operate off the battery power.
That is the issueš
2 Likes
Thank you. The error in my log is exactly what is being discussed in that pull request.
It seems that work-around code was merged into Open Zwave just a few days ago to fix this issue, but it requries manual update of the Zwave config file, which would be overwritten upon every start of HAAS and bring the problem back.
I wonder if HAAS 0.49 is even using the version of Open Zwave that has that code change.
And even if it did, I guess it would not help in general as setting the āPacketDelayā is a manual change which would be overwritten by HAAS.
Will look into it at homeā¦ thanks for pointing this out.
Actually we are still waiting for the fix to be merged with the main branch, and then for a new release of OZW 
Is everybody having this issue using an Aeotec Zstick Gen 5? Iām debating whether I should buy another stickā¦
I have a ZME-UZB1 and have the same issues. But sometimes, only sometimes the device works without problems.
Hey! How are you guys progressing with this thing? Iām a few steps behind you all it seems. I had this working earlier, but as I recently upgraded Jessie to Stretch, Python to 3.6.3 and HA 0.55 to 0.55.1, all my Z-Wave stuff got reset to scratch. The ZXT-120 was not properly re-added. I fiddled with the button while reading the manual, and suddenly (without any logic behind) it āworksā. At least itās listed with the proper name etc.
But this is as far as I get. Iām unable to even set new config parameters. The big one is parameter 27, which I need to figure out which is correct for my Panasonic AC. Itās set at 0, and OZW Z-Wave manager suggest āA short between 4294934528 and 32767ā. Doesnāt make any sense, iām suppose to set a 2 or 3 digit code. And whatever i input, thereās no sign of that code even being received. Iām able to switch between FLIRS and Always Listening on the device, but that doesnāt get me very farā¦
Problem is still there. Did anybody find a good workaround? I am on haas.io nowā¦
found another tread discussing this:
Hello.
Like all of you Iām unable to control the device. I even tried to compile ooenzwave with the modified code that still is not merged, changing the config folder in configuration.yaml and added the field in zwave node information file. Just worked the first operation I tried after that the timeout error came again.
I donāt want to put pressure to anybody here, but Iām seeing this issue in other systems (domoticz) relying in ooenzwave more than one year and a half without solution.
IMO if the project leaders want this to be successful they canāt rely on thirth party systems that donāt fix their issues and fork ooenzwave.
I know this is very easy to tell and difficult to do and more in an open source project that is done by devs spare time.
Just my 50 cents and congratulations for this system is really wonderful.
Thanks.
It seems this issue has been present for over 2 years and is related to OpenZWave. A few āpatchesā have been put forward, but it seems nothing acceptable to the OpenZWave team.
I am just putting my head in here to watch as I have a Remotec ZXT-120 and have Time Out errors in the log for all functions with the exception of setting the temperature, which does work.
I can not change mode, can not turn the aircon off or anything else.
Using Aeotec Z-Stick Gen 5 (Au model) and ZXT-120AU.
I am considering building a seperate āhackedā version of HA just for these devices and MQTT link my main clean build hub for the rest. Has anyone else done this? Is it worth the extra effort or just I just hack away 
@smart
I would suggest to focus on the OpenZWave issue. Once you fix that, HASS will behave normally.
The timeout is in the OpenZWave log and is a ZWave timeout, not actually HASS.
Other systems, like OpenHAB, that use OpenZWave have the same issue with these devices :).
B.
Well as someone coming from openhab I can assure you they donāt have this issue since time ago. I donāt think they use the ooenzwave library but some kind of fork.
I also have zxt and was wondering how we can get a stable and reliable deviceā¦ IT#s like the devoce is randomly workingā¦ what always seems to work is to set temp. each time i get the beep. On / off are more sporadically .
- It is always listening mode with USB plugged-in
- in zwave+ network
- Aeotec gen 5 USB stick
Iām really upset. I bought 4!!! devices and somehow they just wont react to my commandsā¦ I just cant figure out what the henk is going on ā¦ fact is that i set for example operation mode OFF and receive previous operation mode from zxt.
Is here anybody with a more or less stable zxt running and maybe even setup ?
As far as I understood from openhab community is affecting fast computers. Probably with a saturated pi would work perfect. With 4 of them I would try with a pi zero.
I doubt it has anything to do with speed of the computer to be honest.
The issue is timeout issues. OpenZwave log shows it clearly.
Maybe OpenHAB are using a fork with the patch in it. If I reboot Hass (full reboot not just restart Hass) the device will work properly for one command, then go back to working to change temp only.
That happens no matter what computing device is used.
There are PRs that were not actioned on OpenZwave GitHub indicating a fix, but guessing they were not clean enough to merge.
The issue seems to be a timing issue to when the end āno more dataā is sent.
I donāt know enough about the technical side of zwave to guess more though.
Not an expert neither but I remember fast computers send the get signal too fast for the ZXT still working on the previous set command and then ignoring the get. So the timeout.
The patch developed but Iām unable to make it working in HA was a wait time between the set and the get.
Just for info it was working on my PI but when I moved to a fastest laptop stoped working.
If someone more experienced than me would work with me to patch the openzwave and apply locally I could create the workaround manual. Even if nobody can help me and I succeed I will make the workaround manual anyway.