Logic Programming

[CatmanV2]

@rafale77 thanks chap. Seems a little unfair (to you!)

I guess there are two issues (so far)

Thermostats don't work properly under Altui. Or at least mine doesn't There's no way of adjusting the set point in the web interface. Works fine in Homewave but....

The other is the licencing issue previously mentioned. A minor peeve.

But this raises some concern that if the UI is not maintained, in a couple of years, how functional will it be?

C

[rafale77]

I would not call it "unmaintained", @amg0 has just recently taken my localcdn updates and has upgraded bootstrap. I can't help with the licensing unfortunately. Maybe @akbooer can. About the setpoint problem with the thermostat, can you provide more details? I don't think this would be an ALTUI issue and more of a vera device file issue since that's what is controlling it. I have personally wrote a plugin to control my thermostat which integrates door/motion sensors/vents (The US mostly use forced air HVAC) and calculates a virtual home temperature. (Kind of like ecobee but much better as it shuts off vents for rooms with open windows, ignores and shuts off unoccupied rooms etc...)... and my thermostat works. What model and what errors/issues are you seeing?

[CatmanV2]

@rafale77

Maybe 'unmaintained' is unfair, not my intention. But if support has stopped (no response to a follow up on my licensing query) and the other issue raiser in 2018 was directed to Vera forum, not sure what's going to happen.

Ref the Thermostat, I guess it may be the device file since it doesn't 'work' in the console either. This is all I get in AltUI

So there's no way to adjust the set point.

C

[rafale77]

Can you show me the device attributes? And action screen? What are you expecting to be able to do? Only change setpoints (heat/cool?) do you need to change also mode?

[CatmanV2]

@rafale77

Here you are

I guess all I expect to change (and display) is the current set point. Heat on and off would be cool as well.

As far as I am aware there is only one (functional) setpoint. Although I suspect it has rather more than that. And only one mode (heat) although again I suspect it has more of them as well. Which is probably a failure in the file attributed to the device?

I can see it has in its variables two CurrentSetpoints. One is probably my fault trying to control it. But it also has Energymodes and Fanspeed.

It's really a very simple on / off stat

Tangentially this feels like the kind of issue that we should be able to provide a quick and easy solution to the average user. You know I'm going to be happy to ask and fire commands, but for basic users, it's a simple device and it's effectively un-usable.

I use it with Homewave (not exactly simple) and Alexa / HA Bridge (not quite user hostile, but verging on it) So I don't need this functionality, it just feels like quite a big miss.

C

[rafale77]

ouch... this is through the z-way bridge. Need @akbooer here. It looks like this device was not recognized by the z-way bridge as a thermostat. I am curious as to what command class it is showing on z-way. Can you please take a look at the expertUI on z-way and show what command classes it is presenting on the interview screen?

[CatmanV2]

@rafale77 of course. Seems to have correctly IDed it

and

C

[rafale77]

I just looked at the z-way bridge code... and it shows that the bridge should create a thermostat device instead of a combo device.
You may have installed this on an older version of the z-way bridge.
Solution:
Update the z-way-bridge if it isn't already the latest version, delete the child device and reload luup.
See what device file you get.

[CatmanV2]

So this is the Z-way plugin on AltUI?

Showing 20.7.14

C

[rafale77]

@catmanv2

The latest development version should be 2021.1.19

[CatmanV2]

OK. If I delete the child device, am I going to lose all my automations and actions around it?

Sorry to be a PITA....

C

[rafale77]

Not on openLuup. That was a vera "feature" luckily openLuup didn't reproduce. Upon luup reload, the device will be recreated and no automation should be broken. Make sure you only delete the thermostat device.

The device created should show you the thermostat temperature and at least one setpoint.

[CatmanV2]

@rafale77

OK
So used the App store to select Github.development
Plugins now shows 21.1.19
Deleted the device that I thought was the Thermostat (i.e. the one I showed you earlier)
Reloaded Luup and I have a device that was recreated in my Z-Way-nnnnnn room
But...

Nothing appears to have changed:

I assume I've done something dumb

C

[rafale77]

Nope... there is something missing: the bridge has linked the variables but did not use the right device files.
Go into attributes and change the device json from ComboDevice1.json to D_HeaterStelpro.json and the device file to D_Heater1.xml

I think that you have a heater rather than a thermostat...

[CatmanV2]

@rafale77

Heheh. Not sure why it would be considered a heater but....

Not much of an improvement... (I reloaded Luup)

C

[rafale77]

hmm - hmmm you have the device files reversed the json file needs to be in the json field... also make sure that these files do exist in your openluup installation. They should come from the vera.

I read the manual for your thermostat and it is indeed a heat only thermostat which for vera is a heater control device... The difference is that it only has one setpoint instead of 2 and terminologies are all around heating.

[CatmanV2]

See it was only a matter of time before I did something stupid

Thanks for all this. Sure when I originally mentioned this it was a feature of AltUI.

Looks much better now. thanks!

C

[CatmanV2]

As a supplementary question, now I have a Heat / Off switch.

Can I make this actually switch my boiler control on? This would neatly solve an issue I've been considering with TRVs.

Currently altering it from 'Off' to 'Heat' does nothing and does not appear to alter the value of the ModeTarget variable which is reflected in the logs.

I also need to chase something down I suspect in HA Bridge as I've managed to re-create another CurrentSetpoint

C

[rafale77]

Looking at the manual and the supported command classes you posted, no, unfortunately the heater does not support mode changing. It is only reporting 3 command classes:

1. Current temperature (49)
2. Temperature Setpoint (67)
3. Battery Level (128)

So to turn the heat on, you need to change the setpoint to be above the current temperature.

[CatmanV2]

Interesting, thanks!

C