altUI
-
-
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?
-
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.
-
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?
@powisquare as you can see, category and subcategory num are not set correctly. Try to set them the same (5, 1).
-
-
Can i set them to (0,0) as the (5,1) misbehaves?
@powisquare Try it!
-
Thanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.
-
Thanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.
@powisquare also, look at variables and post them here. Sometimes it's just some variable missing and creating it by hand will surely help.
-
A lot of the functionality of thermostats is not in the static JSON files, it's actually hardcoded in UI7's interface.js and view.js files. This has been one of my issues with AVT and other thermostat plugins I've tried to do using the standard device types. The UI is so overloaded with kludges and exceptions for devices they specifically support (from Vera) that the generic device type is all but unusable. As I've groused about often in the other forums, they have a hellish mix of "methods" they've used over the years to try to express the capabilities and limitations of the devices, including magic values in state variables (which I think had the best possibility of success had they stuck with it and fixed what they didn't get on the first try, and documented it properly) and then worst... using the actual filename of the static JSON file (not its contents, where you could put anything you want, really) to determine capabilities. It's a mess.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
A lot of the functionality of thermostats is not in the static JSON files, it's actually hardcoded in UI7's interface.js and view.js files. This has been one of my issues with AVT and other thermostat plugins I've tried to do using the standard device types. The UI is so overloaded with kludges and exceptions for devices they specifically support (from Vera) that the generic device type is all but unusable. As I've groused about often in the other forums, they have a hellish mix of "methods" they've used over the years to try to express the capabilities and limitations of the devices, including magic values in state variables (which I think had the best possibility of success had they stuck with it and fixed what they didn't get on the first try, and documented it properly) and then worst... using the actual filename of the static JSON file (not its contents, where you could put anything you want, really) to determine capabilities. It's a mess.
-
May well be different machines, differing firmwares. Frustrating nevertheless. Here's a stab at displaying variables.
-
... Keeping the device support at the command class level for z-wave devices like what z-way does is really much cleaner... What a mess. I had forgotten all about it. As you can see from @CatmanV2, that's all that was needed. If the command classes are recognized and bridged, it will work. It makes it almost impossible to not support a device. huh... to whom have I suggested to do that a long time ago in a galaxy far far away.... I wonder.
-
Curiously, in "Dark Theme", the chevron ^ arrows become white in the white box in the lower-right corner (where you can click to quickly navigate to 1st or last reply of a thread). Hence, as pictured here, they become invisible.
They do become visible as the bar fills with blue, of course, as one scrolls down the discussion. Should always contrast (perhaps black arrows) instead. I use those double-arrows quite often.
Wrong thread?
C
