Remotec ZXT-120 operational questions + my script

B1tMaster · June 22, 2017, 7:35am

Hi all,

I am successfully using Remote ZXT120 HVAC IR blasters.
ZXT-120 manual

I have a couple of questions to the community.

ZXT-120 has cooling, heating, unused4 and unused6 -features on the device. I only using cooling… How to hide the remaining 4 options on HAAS?
Can somebody explain what is the “proper” way to communicate with these devices. One can set “mode_of_operation” to “Cool” , “heat” , “Off” . Then you can set the temperature via “set_temperature” and then of course there is “set_fan_mode”
After playing with it, I found out that just setting “mode_of_operation” does not really work, neither “set_temperature” works on itself all the time. At the end, I wound up building a script, where I send multiple commands to ZXT-120 , to :
Set the operating mode to "cool. 2. set the temperature 3. set the fan mode.
Is this how it supposed to work? there is NO such thing as ONE command to just “turn-on and cool” ?
When I use my Aircon “remote control”, I hear my aircon beep only ONE time. So it must be sending it ONE command.
Also, when you “teach the IR blaster” like Harmony the IR code, (i use it in my living room), I also hear only ONE beep.

With my 3 separate commands I send to ZXT-120, I hear 3-4 beeps obviously, so the way I am doing it is certainly different from what my “remote control” is doing. Am I missing something? Or this is the way it should work.

Also, I was fearing that one of my 3 commands would be lost, so I introduced a “pause” between sending them. Should I be worried, or can just blast all 3 one after another without waiting?

Here is my script that turns the aircon on, sets the temp and fan mode:

   turn_guestroom_aircon_on:
    sequence:
     - service: climate.set_operation_mode
       entity_id: climate.guestroom_climate_control_cooling_1_12_2
       data:
         operation_mode: Cool
     - delay:
         seconds: 1
     - service: climate.set_temperature
       entity_id: climate.guestroom_climate_control_cooling_1_12_2
       data:
         temperature: 22
     - delay:
         seconds: 1
     - service: climate.set_fan_mode
       entity_id: climate.guestroom_climate_control_cooling_1_12_2
       data:
         fan_mode: "Auto Low"

Does anybody know how can I make the ZXT-120 to report temperature more often? I think it only updates the temperature in HAAS when i trigger it with a command. (I use battery power install) . I can’t find an option on the device to report more frequently. With that a sub-question: does this mean, I can’t relay on this device to programmatically turn the aircon OFF once the desired temperature is reached, since it does not seem to update it.

Can I somehow program it to automatically itself to send the “Off” command to the aircon based the temperature or I need to write automation script to trigger the command from HAAS. I could not find any option on the device to do that.

One of the 3 of these devices in the bedroom, does not seem to work well. (i.e.: it seem to lose one or sometimes two of the 3 commands I am sending. Interesting thing is that as soon as I bring it to another room it works perfectly and sends all the commands and can shut down aircon. When I bring it back to my bedroom, initially it continue to work perfectly. But in the morning, after sitting in the bedroom for a while, it can still turn on the air , but failing to shut it off. As if command never arrives. It seem it somehow related to my Zwave network and it’s location on it, but I can’t quite put my finger on it, because it works 50% of the time OK. Any ideas?

jonathanp · June 27, 2017, 1:39am

I too am using the ZXT 120 with my split system wall unit and have had some similar issues.

Firstly, to report the temperature more often and thus allow you to run automations based on the current temp, I think you need to ensure the device is in “always listening mode” not “frequently listening” although I am not sure it will do that on battery power. I have mine using USB power but need to exclude it from my network and then make the change. I’m thinking this will cause a few issues that I’ve just not had the time to be able to work on so I’ve put it off for a while. Maybe I can try this weekend and report back.

Second or sub issue as you mentioned, the ability to turn off your unit via the ZXT 120. Again I have this issue as well even when I try to simply turn off the unit at a set time in the evening. For some reason it just doesn’t sent the command to my ac unit. I did notice in ZWave control panel that it referred to False not Off but again I still need to see if that is the key to this thing.

Otherwise I do have to admit this piece of hardware is pretty darn good at what it does.

I’m thinking of getting a multisensor 6 soon so I may just end up using that for the temperature reading to trigger the automations instead but it’d be nice to make it work with the ZXT 120

jonathanp · June 27, 2017, 1:44am

By the way, I have automations with all 3 settings included in the action, operation mode, fan mode and temperature and when it fires, I only get one beep and all the commands are transferred.

Can I ask why you’ve added the delay of 1 second to your sequence above?

I’m happy to post my automations later when I get home if that is of any assistance.

B1tMaster · June 27, 2017, 7:48am

Hi Jonath,
Thank you for replying. Hope we can tackle this issue together.

I have answer for your question of things being reported “False” vs “Off”
I think Python treats it as boolean instead of a string. So to fix that , just put it in single quotes like: ‘Off’
This will fix your issue.

Ok, so you send all 3 commands as well. Did you look into the Zwave log to see that indeed all 3 go through?
I definately get a separate “beep” for each command. in 3 of my rooms. But additional beeps are being lost in the “problem” room. Since you report only “one” beep, I wonder if you also loose additional commands being sent.

With the AC OFF commands, things are really weird as if I move my device to one of the “good” rooms, it works perfectly and I also get all 3 beeps. it also turns the aircon off in all other rooms… When I move it back to the “problem” room, it works normally for a while, but reverts for NOT turning off the AC in a few hours and also back to one beep only to turn it ON. Very confused.

The reason I added 1 second delay for commands was tha I was worried I send them too quickly and maybe that’s why they are lost. but this did not make a difference, so I may take the delay out as it does not help.

I really suspect that it has something to do with Zwave network itself. Will post my Zwave log later today

jonathanp · June 27, 2017, 8:14am

Just checked my automations and I have off as ‘off’ but it doesn’t seem to work for me still for some reason.

- alias: Turn off heater at 10pm
  trigger:
    platform: time
    at: "22:00:00"
  action:
    - service: climate.set_operation_mode
      entity_id: climate.remotec_zxt120au_heating_1_2_1
      data:
        operation_mode: 'Off'

As for the 3 beeps, I did encounter this once before and it was after I did a complete reboot and the ZXT 120 became a probe not a node. You can check this in the Z Wave section on the UI. But it definitely only beeps once to turn the unit on with the correct mode, temp and fan speed once it’s a node.

I’m really thinking the turning it into an ‘always listening device’ might solve some of this. I plan to do it early next week as my wife and kids are away for a couple of days and if I have to turn on the heater (it’s winter here in Melbourne Australia) manually while I sort it out then so be it.

How many other items have you got on your Z Wave network? This is currently my only device (along with the Z Stick) so wondering if I don’t just try and start it all from scratch again, especially in version 47 where I can rename them all

tbrasser · June 27, 2017, 8:54am

Thanks for both of your info on the ZXT-120, I am looking to buy maybe 1 or 2. Is it possible to choose which device should be controlled from which IR blaster? (for example, split unit 1 from the ZXT-120 main device, and split unit 2 from the attached IR blaster on a wire).

B1tMaster · June 27, 2017, 1:10pm

Hi,
I have 12 nodes in my Zwave network and once I’m done, there will be about 18.

I am thinking as well to find a way to plug them in and turn into “always listen” mode as you are suggesting as well.
Just don’t have a socket nearby, so will need to see how to run power to it.

Hmm, strange about beeping. I have 3 of these IR blasters and as I mentioned, they all beep once for each command I issue. (it makes sense as setting the fan mode is typically a different button on a remote and completely different command send to an aircon.
Same for temperature. I did some research and actually there is a totally separate command exist for each degree.
So again, as you increase or decrease the temp on your unit, does it not beep every time you change by one degree?

To me, it makes perfect sense , it should beep 3 times as those are totally different commands. The fact that it only beeps once, may mean that the “operation_mode” = heat goes thru and the other commands are lost.
The fact that it still seem to work is because the aircon / heater already set to a particular degree and fan setting. So it just using whatever it was set to…

To prove to yourself that all your commands are coming thru, set the temperature to very high degree or low degree. Something very different from what you have now. send all 3 commands and see if aircon actually took all the new settings.

How far away is your IR blaster from the Zwave stick? Also is there any thick walls between the stick and the room where IR blaster is?

Overall , I do like the device… though one thing was a nightmare was selecting the correct code number from a list of numbers for my aircon manufacturer name. They just list a bunch of numbers and let you try until it works. That really sucks.

Of course you can “teach” the device \remote commands from your remote, but that would take a long time too for each button.

B1tMaster · June 27, 2017, 1:10pm

No problem mate. This is what this forum is for. It’s fun , but can be frustrating when it’s not working.

jonathanp · June 27, 2017, 11:20pm

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.

B1tMaster · June 28, 2017, 12:08am

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 - TimeOut

B1tMaster · June 28, 2017, 12:32am

Just 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: ValueChanged

B1tMaster · June 29, 2017, 12:08pm

I 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.

turbokongen · June 29, 2017, 7:32pm

That is the issue😉

B1tMaster · June 30, 2017, 3:25am

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.

nongagf · August 8, 2017, 11:21pm

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…

turbokongen · August 9, 2017, 4:34pm

I have a ZME-UZB1 and have the same issues. But sometimes, only sometimes the device works without problems.

hulkhaugen · October 17, 2017, 12:47pm

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…

B1tMaster · March 3, 2018, 1:35am

Problem is still there. Did anybody find a good workaround? I am on haas.io now…

found another tread discussing this:

sergi.suarezj · July 31, 2018, 9:33am

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.

brendan · August 1, 2018, 11:02pm

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.