Maybe the Thing Label Type is a bit long?
The text in the parenthesis is repeated in Thing Type Description.
Just tried ON/OFF yet and the relay is clicking
Cannot set parameter 22 & 24. They should have the Option 0 entry deleted in the database.
I was not able to do this myself.
2 questions.
After starting this latest dev binding, a new Z-Wave USB dongle appeared in my inbox.
Should that be used instead of the old one? (Z-Wave serial controller)
The z-trm2 display brightness settings are configuration parameters. If I wanted to change intensity from day to night is that possible from a rule?
Observation: every time I select a thing in habmin, the following ERROR appears in the log: 2018-06-04 21:35:53.836 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
Great - it sounds like things are basically working
Please remove the name, or change the name to DELETE ME, or somthing, and I’ll delete it.
No - you don’t need to. This is a new features where the binding is discovering dongles, but (at the moment) it doesn’t tie in with manually configured dongles. I would suggest for now to ignore it…
Yes, it’s possible. We need to create a channel in the CONFIGURATION command class with the type config_decimal and with the parameter parameter set to the parameter number (eg parameter=23 to control parameter 23.
Cool, but I have played around with it a bit changing config, and it seems not to work.
Locally in the menu is OK.
Also, when I set the heating setpoint from habmin, it apperas on the device display, but the Setpoint (Heating) channel does not follow. When trying to set a value through the channel, logs say:
2018-06-04 23:42:55.734 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 85: Command received with no implementation (QuantityType).
Given the horrible firmware problems with the original heatit device I am watching with interest to find out how much fun you guys have with the z-trm2.
In short, the device was advertised as having an internal temperature sensor. It worked amazingly badly. They then disabled it in later units’ firmware without telling anyone.
And the device was supposed to provide a command class giving the ON/OFF status of the thermostat, but didn’t.
Finally, the LCD screen sometimes randomly lights up odd segments.
I’m away from my PC but you can hopefully find those posts on the forum
Test update:
PaperUI lists setpoint as Number:Temperature:
However, using that type in the .items file does not work.
Hence, setting the setPoint directly from PaperUI or habMin doesn’t work either.
These .items works fine:
// HVAC 1
Switch heatit1Switch (hvacSwitches) { channel = "zwave:device:f180343d:node85:switch_binary1" }
Number heatit1Volts (hvac) { channel = "zwave:device:f180343d:node85:meter_voltage" }
Number heatit1Watts (hvac) { channel = "zwave:device:f180343d:node85:meter_watts" }
Number heatit1kWh (hvac) { channel = "zwave:device:f180343d:node85:meter_kwh" }
Number heatit1Mode (hvac) { channel = "zwave:device:f180343d:node85:thermostat_mode" }
Number heatit1setPoint (hvac) { channel = "zwave:device:f180343d:node85:thermostat_setpoint_heating" }
Number heatit1tempAir (hvac) { channel = "zwave:device:f180343d:node85:sensor_temperature2" }
Number heatit1tempFloor (hvac) { channel = "zwave:device:f180343d:node85:sensor_temperature3" }
Number heatit1tempExt (hvac) { channel = "zwave:device:f180343d:node85:sensor_temperature4" }
Set setPoint from a rule:
sendCommand(heatit1setPoint, 22.5) (any .1 increment is accepted)
Log updates:
rule 'heatit1Switch'
when
Item heatit1Switch received update
then
logInfo("heatit1Switch", "Update: heatit1Switch=" + heatit1Switch.state)
end
rule 'hvac1setPoint'
when
Item heatit1setPoint received update
then
logInfo("heatit1setPoint", "Update: heatit1setPoint=" + heatit1setPoint.state)
end
rule 'hvac1tempAir'
when
Item heatit1tempAir received update
then
logInfo("heatit1tempAir", "Update: heatit1tempAir=" + heatit1tempAir.state)
end
Sitemap next
Observation: only binary_switch1 reports the relay switch state. It can also be controlled, but unsure how long it will stick.
The whole thermostat can be turned off using the thermostat_mode channel, or if using floor- or external sensor just set the setPoint low and it will just show the current temperature.
The next database update will fix parameter 4.
So guess that is it. Item included in snapshot and development binding.
What doesn’t work? I know people are using this item type in other ZWave things - at least for temperature sensors I know it is working. Maybe there is an issue with commanding - I did ask for confirmation of this when I added UOM, but no-one responded.
When trying to set the setPoint directly from paperUI/habmin I got the error quoted.
After that, it was no longer possible to try again. (Had to restart browser)
From the rule with item defined as Number:Temperature, sendCommand(item, 22.0|“℃”) setting did not take on device. (unsure if I got an error)
Update rule log for temperature sent from device logged as 22.5 - ?
I’ve made a change to support QuantityType commands (I hope!). I can’t properly test this, so please can you give this version a try and see if this helps
Maybe, but somehow this needs to be sorted so that it works properly with the different units. I’m not overly familiar with this myself - and certainly not on the command side (the sensor side I can test ok).
Yes please. I’d like to see if the command gets to the binding or not. I added some tests that seem to show it should be processed ok, so maybe the issue is outside the binding… Let’s see, the logs should help at least.
Ok, here is what I did:
Restored the Number:Temperature as in .items file above.
Enabled debug for zwave. This is node 85.
Saved a rule file with this in the System started rule:
One question before I look too much further - when you updated the binding, did you delete the thing and add it back again (don’t exclude/include - just delete, inbox/search, and add)?
I forgot to mention this, but this needs to be done to update the thing/channel definition (this isn’t required for the parameter configuration).
.
