Dear forum members I've purchased the new qubino thermostat but I'm experiencing some strange behavior.. after an update has send from the node the temperature is set back to "zero" after some seconds. When looking at the openzwave control panel I see the same behavior. This will result in a unrealistic domoticz temp. Log. For the information I've included some print screens.
I was wondering if this is a normal behavior for the qubino thermostat?
Small note, the boiler control is working as it should. So it won't start heating if the temp is set back to "zero"
And of course I've excluded/included the node several times... with same result.
My domoticz (last beta) is running on a Pi 2b with razberry 2.0 zwave+
Hope someone can help me on this one,
Last edited by geezerrr on Thursday 22 September 2016 19:05, edited 4 times in total.
I use this device and I see this behaviour when I set parameter 120 (Digital temperature sensor reporting) to 1 (report when temp change 0,1º C). I had not realize about it before.
I'll try to see more about this behaviour.
It's strange. My graphics log doesn't show the zero value when I set parameter 120 to 1, but some times Control Panel shows zero.
I hace activate debug in controller to see the log and what I see is
2016-10-01 12:29:41.044 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xeb, 0x06
2016-10-01 12:29:41.044 Detail,
2016-10-01 12:29:41.044 Info, Node011, Received SensorMultiLevel report from node 11, instance 1, Temperature: value=23.5C
2016-10-01 12:29:41.044 Detail, Node011, Refreshed Value: old value=23.6, new value=23.5, type=decimal
2016-10-01 12:29:41.045 Detail, Node011, Changes to this value are not verified
2016-10-01 12:29:41.045 Detail, Node011, Notification: ValueChanged
2016-10-01 12:29:41.091 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd15e57b9
2016-10-01 12:29:41.871 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0x00, 0xed
2016-10-01 12:29:41.871 Detail,
2016-10-01 12:29:41.871 Info, Node011, Received SensorMultiLevel report from node 11, instance 1, Temperature: value=0.0C
2016-10-01 12:29:41.871 Detail, Node011, Refreshed Value: old value=23.5, new value=0.0, type=decimal
2016-10-01 12:29:41.871 Detail, Node011, Changes to this value are not verified
2016-10-01 12:29:41.872 Detail, Node011, Notification: ValueChanged
2016-10-01 12:29:43.049 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xec, 0x01
2016-10-01 12:29:43.049 Detail,
2016-10-01 12:29:43.049 Info, Node011, Received SensorMultiLevel report from node 11, instance 1, Temperature: value=23.6C
2016-10-01 12:29:43.049 Detail, Node011, Refreshed Value: old value=0.0, new value=23.6, type=decimal
2016-10-01 12:29:43.049 Detail, Node011, Changes to this value are not verified
2016-10-01 12:29:43.050 Detail, Node011, Notification: ValueChanged
2016-10-01 12:29:43.867 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0x00, 0xed
2016-10-01 12:29:43.867 Detail,
2016-10-01 12:29:43.867 Info, Node011, Received SensorMultiLevel report from node 11, instance 1, Temperature: value=0.0C
2016-10-01 12:29:43.867 Detail, Node011, Refreshed Value: old value=23.6, new value=0.0, type=decimal
2016-10-01 12:29:43.867 Detail, Node011, Changes to this value are not verified
2016-10-01 12:29:43.868 Detail, Node011, Notification: ValueChanged
As you can see device sends actual value then 0.0.
I don't know if this is normal, but Domoticz doesn't show these changes in my graphic log.
Perhaps it' would be a good idea to send the question to Qubino.
Bye
Hi juankar, thans for your info! I'm seeing the same in my log, first actual temperature and than a 0.0 is send... So I was thinking as well it might be a question for Qubino. So I created a ticket on there website (technical information) but it's taken care by intellihome.be (didn't know that) they told me the following: "we're going to bring Domoticz in contact with Qubino but haven't had any response yet".
For now I will try to change the temp report (parameter 120) to a bigger one. I have indeed report at 0.1C. Will try 0.5... and see what will happen.
Well, I've sent the question to Qubino.
But what I can not understand is that your graphics logs show the cero value and my graphic log doesn't.
And Control Panel shows a temp value different from Domoticz dashboard, and the last seen value is different from the las seen time in Control Panel... why?
I have news about this issue.
I sent the issue to Google OpenZwave Group and I received an answer: Check Association
Well, I deleted association of group 9, so group 9 has no association. Now the double reading has disappeared.
Why? I don't understand, so I have to study associations again
Hmm, i have Group 9 associated to the lifeline 1. After checking group 9 is for "sensor multilevel (triggered by change of temp)". So I suggested that it was ok in the lifeline. I did a quick check and indeed after removing al associations from group 9 it didn't switching back to 0,0C after a reading.
But it don't make since to me at all.
Yes, it sounds strange. But we have a ZWave+ (PLUS) device and associations works different from ZWave.
It looks like with ZWave+ the only neccesary association is the lifeline (node 1) and all brands works in the same way. So group 9 association is not necessary,
