Remotec ZXT-800 IR Blaster (Z-Wave for AC & AV use cases)

[ZeGhostbear]

I need some help to allow me to use the AV control buttons. As mentioned above, the ones I am trying to use initially are:

"ZAv Control" -> avbutton: Power
"ZVol Down"
"ZVol Up"

Was expecting this to be possible through buttons on a dashboard, like with the CoCoHue bridge driver for my lights for example, but I cannot figure out how for this device.

Has someone used this and can point me in the right direction?

[rlithgow1]

@ZeGhostbear

Has someone used this and can point me in the right direction?

Once the ir controls are programmed into the unit, you will see them as attributes on the devices' page. Create dash, add ir blaster to dashboard availability. Create button and use the attribute template that corresponds what command you want to use.

[ZeGhostbear]

Hi Rick. Thank you for your reply. I am still stuck. Here is what I did yesterday:
-Updated the device to the latest firmware (V30) which wipes out any IR codes and Z-Wave settings
-Programmed the device for ONKYO IR codes (Side note: When I first got the device the codes from the database did not work and I had to program manually. This time the only set of ONKYO codes in the database worked.)
-Tested the functionality from the manufacturer's app. Power ON/OFF, Volume Up and Volume Down all worked.
-Deleted the device from Hubitat (without an exclusion since it got wiped)
-Created a fresh Z-Wave device with driver version 1.1
-Tested the functionality from the Hubitat device page. Power ON/OFF, Volume Up and Volume Down all worked. (Side note: The first stored AV device is 2, so for Power on you go to Z Av Control -> Avchannel: 2 -> Avbutton: Power; for Volume Up it's Z Vol Up -> Volup: 2)
-Created a fresh Hubitat Dashboard to which I added the device
-Tried to add a "device" type tile but I do not see any "attribute" templates whose labels resemble any of the AV functions.

[rlithgow1]

On the device page, what's it showing for attributes?

[ZeGhostbear]

The "Get Attributes App" by C Steele reports the following attributes for the device:

[battery, supportedThermostatModes, thermostatSetpoint, heatingSetpoint, supportedThermostatFanModes, swingMode, internalInfrared, schedule, thermostatSetpoint, temperatureOffset, temperature, temperature, supportedThermostatModes, thermostatFanMode, coolingSetpoint, thermostatMode, thermostatFanMode, remoteCode, supportedThermostatFanModes, heatingSetpoint, thermostatMode, coolingSetpoint, reportTempLevel, switch, thermostatOperatingState, reportTime, temperature]

[rlithgow1]

What driver are you using with it? It looks like a thermostat driver vs the actual zxt driver and use the device page to see what ones are showing there

[ZeGhostbear]

I am using the driver that Yong Huang posted on GitHub above (post #45):

Remotec ZXT-800 IR Blaster (Z-Wave for AC & AV use cases)

Here is the driver

[rlithgow1]

The driver needs to report the AV attributes in order to use them, it's only providing thermostat attributes. I would post in the driver thread.

[ZeGhostbear]

Thanks for having a look.

The functions I am interested in are only listed as commands and not attributes as far as I can tell from the code.

Don't think there is another thread for just the driver.

Will try to get in touch with Yong Huang, the developer.

[rlithgow1]

This one Remotec ZXT-800 IR Blaster (Z-Wave for AC & AV use cases) - #45 by yong_huang

Just tag @yong_huang

[Cramezul]

@yong_huang I've been using your drivr for a while to control my AC and it works fine. There's only one thing that I encounter. I try to set a fan mode in the Thermostat Scheduler built-in app and the app throws an error.

I've found this thread that suggests that there might be a problem with the way supported modes are defined in the driver.

Thermostat scheduler unable to set fan or mode

That driver is out of date, and its author should update it. The supportedThermostatModes and supportedThermostatFanModes attributes have bad values. For each, the individual words need to be in quotes. To fix it follow these steps: Temporarily change the driver to Virtual Thermostat, hit Save Device. Then put this string in the command box for setSupportedThermostatModes ["auto","off","heat","emergency heat","cool"] and hit the command button. Then put this string in the setSupportedThe…

[RickyV]

I got I am working with a Remotec ZXT-800 and I am having an issue with the Dashboard not reflecting the correct thermostat state.
The device is sending commands correctly:

• When I change mode, fan, or setpoint, the AC unit responds as expected.

However:

• The attributes like thermostatMode, thermostatFanMode and thermostatSetpoint do not update automatically.
• The Dashboard only shows the correct state after I manually execute a refresh() on the device.

This is causing inconsistency since the AC is reacting but the Dashboard does not reflect the change.

I would appreciate any guidance or best practices on how to keep the device state in sync without relying on manual refresh.

[bikesquid]

Just moved and have inherited about 8 mitz minisplits and trying to decide whether to go this route or the kumo route. All i have now is the stupid IR remotes. My experience with kumo is meh at best and wonder if anyone has an opinion to share on this integration?
Thx in advance.

[rlithgow1]

You can get these and use any thermostat (including z-wave and zigbee) to control them. You'll still need the remotes to adjust louvers and what not

Mitsubishi 3rd Party Thermostat Interface PAC-US445CN1 (Connect to Nes

[bikesquid]

Thx @rlithgow1. I suppose that would eliminate my main concern with the blaster tech, which is no way to poll the head-unit and know what it's doing. From what I gather, the blaster... blasts, and you just cross your fingers and hope the mitz unit is doing as told.

[rlithgow1]

@bikesquid

blasts, and you just cross your fingers and hope the mitz unit is doing as told.

Yep. With the dry contact interface you get realtime feedback from the unit and then the thermostat feeds hubitat. (and vice versa)