altUI
-
CatmanV2replied to powisquare on Mar 10, 2021, 9:35 PM last edited by CatmanV2 Mar 10, 2021, 4:41 PM
@powisquare said in altUI:
Edit.. also there is a SwitchPower1 SetTarget
Yes, that I can control, but it doesn't do anything.
What I think is the problem is that Z-way thinks (probably cos I told it) that the ASR is in fact:
Secure Controls SRT 323 ThermostatCommand classes are:
Basic • SwitchBinary • ThermostatMode • CRC16 • ManufacturerSpecific • Version •But the switch action in Z-way also does nothing.
Any idea how to get the right device in Z-way?
<edit>. Ooooh poking around in Z-way I can turn it on and off manually with the Thermostat mode 'expert' command
C
-
CatmanV2replied to therealdb on Mar 10, 2021, 9:42 PM last edited by CatmanV2 Mar 10, 2021, 4:45 PM
@therealdb Ooooh poking around in Z-way I can turn it on and off manually with the Thermostat mode 'expert' command.
That doesn't appear in AltUI as a variable and has no 'direct' control in Z-Way
Z-Way is using the D_BinaryLight1.xml and .json file which I guess accounts for that.
Is there a 'right' file?
C
-
rafale77replied to CatmanV2 on Mar 10, 2021, 9:46 PM last edited by rafale77 Mar 10, 2021, 4:47 PM
Let's take this in steps:
- Which of the two commands is actually responding? The binary switch? or the Thermostat mode?
- How would like the device to look like on the UI? A heater device or a light switch?
The easy path is to use the device corresponding to the command class so we don't have to do any custom actions. This is one odd device which I am sure the z-way bridge didn't know what to do with but all the command classes are supported so it is a matter of linking the device file with the right actions.
The thermostat mode command class will be actuated by the Heater device. The binary switch will be actuated by the light switch.
-
- Thermostat mode
- Heater device
C
-
Then change the device files like you did for the thermostat. I think it should work. The temperature read back and the set point just won't work... having fun yet?
The technical part: The command class is 64 and is a regular command class thermostat. The z-way bridge is just not set to recognize this type of devices though it is implementing the variables and command class correctly.
-
Could change it to a boiler actuator perhaps ...
-
Then change the device files like you did for the thermostat. I think it should work. The temperature read back and the set point just won't work... having fun yet?
The technical part: The command class is 64 and is a regular command class thermostat. The z-way bridge is just not set to recognize this type of devices though it is implementing the variables and command class correctly.
I'm having a blast :). Probably boring the pants off you though!
Changed the files to the same ones as the stat, but no control of the Thermostat Mode either with the arrows or in the variables...
C
-
@powisquare said in altUI:
Could change it to a boiler actuator paerhaps ...
None of them appear in the drop down of Zway. Feels like it's identifying itself as part of the pair
C
-
Maybe try the more generic D_Heater1.json. Sorry I don't have these devices and don't even have a heater so I am just guessing as to what device file corresponds best.
-
I have one of these thermostats on Vera 3 and another on vera plus. For some reason they have different device_json and behave bit differently. Anything I can do to get them both on D_Heater1.json which suits me better than D_HeaterTempNoOnOff1.json as I don't need cooling? Have tried just replacing the text in Attributes but doesn't seem to save.
-
If you are doing this through the verabridge and reload luup, indeed it will go back to the same file being used by the vera. You need to change this field on the vera then luup reload both the vera and openLuup.
-
powisquarewrote on Mar 10, 2021, 10:32 PM last edited by powisquare Mar 10, 2021, 5:36 PM
Thank you - whereabouts in vera may I do this? Tried in device Params but doesn't seem to save. Do see 'Change property command sent' but after reload it reverts back.
-
Not sure why the vera would do this as you got the right place to make the change... and can't really help anymore since I have not followed the latest firmwares. I can only say that changing the device files used to work... Maybe try using ALTUI on the vera?
-
Unfortunately a lot of devices have hard coded settings, so you’ll loose changes after a reload. I’ve just added virtual devices to map them, in extreme situations (ie a security sensor mapped to a switch, or an heather mapped to a thermostat).
-
Seems odd that it's two different jsons for the same thermostat on separate veras. Perhaps the issue is inherently an altui one anyway. When I use the up down arrows for temp setpoint it starts from the cooling setting ie in this case 0 so its a lot of clicking to get to 20.
The same model thermostat paired to zway displays and behaves correctly with no cooling temps.
But they have the same json?
-
If they're on two different Veras are you sure that the file is not different on each?
Also I can't help but notice they have different category numbers. That made a difference on some Vera devices.
C
-
Sorry I was conflating issues. I have (a) two thermostats on separate veras that have different jsons and (b) one of those thermostats is shown above has the same json as another thermostat (on zway) but different functionality. Kinda got that muddled.
-
I think it depends on the different command classes that the device, but I could well be very wrong!
C
35/59
