Domoticz

The Comet seems to work pretty ok for me again, except for the temperature readings not coming in.

scrappy wrote:The Comet seems to work pretty ok for me again, except for the temperature readings not coming in.

Well, only temeperature reading? What about Level and Status updates?
I am able to set the setpoint by plan and it gets executed, but since the temperature reading is incorrect anyway (even if not being updates, still measurement is incorrect), I cannot set the setpoint to desired temperature, but to a higher one. How do you work around this?

The SetPoint readers do seem accurate, so I can set the desired temperature without a problem. I'll use a separate temperature sensor to get readings from the room later, but that's actually not that important for me as long as I can set the desired temp.

scrappy wrote:The SetPoint readers do seem accurate, so I can set the desired temperature without a problem. I'll use a separate temperature sensor to get readings from the room later, but that's actually not that important for me as long as I can set the desired temp.

What you are basically saying is, the temperature sensor built in Comet is showing incorrect results, but in your case, setpoints work with proper temperature in the room? I find it hard to understand. Have you really tested this?
In my case, temperature sensor displays much higher temperature (eg. 25,5) than really is in the room (21) and as a result, if I set setpoint to value 22, the valve is not opening, because Comet thinks, the temperature in the room is higher.
How does it work in your case then?

mKotek wrote:

scrappy wrote:The SetPoint readers do seem accurate, so I can set the desired temperature without a problem. I'll use a separate temperature sensor to get readings from the room later, but that's actually not that important for me as long as I can set the desired temp.

What you are basically saying is, the temperature sensor built in Comet is showing incorrect results, but in your case, setpoints work with proper temperature in the room? I find it hard to understand. Have you really tested this?
In my case, temperature sensor displays much higher temperature (eg. 25,5) than really is in the room (21) and as a result, if I set setpoint to value 22, the valve is not opening, because Comet thinks, the temperature in the room is higher.
How does it work in your case then?

No I'm not saying that any values are incorrect anywhere in my story. The only thing 'wrong' at this moment is that the temperature value from Comet is only retrieved like once a day (with the SensorMultilevelCmd_Get command). No saying that this value is incorrect, just saying that it's not reported every 5 minutes as I would expect (since I set the comet wakeup time to 5 minutes/300seconds).
But I can change the setpoint and the current setpoint is readout properly as well. So I don't have a real problem apart from not being able to readout the temperature myself.

I just looked at the log file and it seems that the current setpoint value is only readout when I set it (so not every 5 minutes on wakeup). However since I'm the only one changing it the value will always be acurate.

I get your point and I am surprised, your temperature readings are correct. In my case, readout is not only not happening at all (not even once a day), but if I look into Control Panel, I can see, the temperature reported is highet than actual in the room. Hence, to set the setpoint, I need to use higher than actual temperature, otherwise Comet does not open valve at all.

In order to get more frequent temperature ratings you need to enable polling (in the setup hardware menu of the Z Wave controller where you get an overview of the nodes).
This seemed to work pretty good for me for at least 1 day, but for some reason now I'm getting temperature readouts of '0'.

scrappy wrote:In order to get more frequent temperature ratings you need to enable polling (in the setup hardware menu of the Z Wave controller where you get an overview of the nodes).
This seemed to work pretty good for me for at least 1 day, but for some reason now I'm getting temperature readouts of '0'.

Do you mean Domoticz polling or OpenZwave polling like here: https://prtscn.in/Ek4wB ?

mKotek wrote:

scrappy wrote:In order to get more frequent temperature ratings you need to enable polling (in the setup hardware menu of the Z Wave controller where you get an overview of the nodes).
This seemed to work pretty good for me for at least 1 day, but for some reason now I'm getting temperature readouts of '0'.

Do you mean Domoticz polling or OpenZwave polling like here: https://prtscn.in/Ek4wB ?

I mean Domoticz polling like here:

Look above, when I had polling set where you have, the device was not sleeping at all (see my comment about dropping battery level rapidly in the first day) - it was active all the time, but I can see in your case, Comet does fall asleep, so I might test it again.

Oh it's definitely falling asleep again. You could have a look at the OZW_Log.txt file to get more details as to what's happening exactly.

I just can't seem to figure out now why the Comet is telling me the temperature is 0 degrees.

My stellaZ returns 0 degrees just after a power-up, until the first proper value is sent (eventually)

I also have this TRV and got it to work... well, kind of.
First, couple of basic things. If you read the manual you will learn some stuff there :
z-wave commands:




So as you can see, you cannot directly control valve open level until you switch the device into REMO mode, Unfortunately, REMO mode is not available neither through Domoticz nor OZW panel. I think it might be bug in OZW.

This device has 3 setpoints: normal (HEAT comfort), economy (HEAT Eco) and furnace. I still didn't figured out what furnace is, but it might be rapid heating mode present in some other devices. Setpoints are working quite ok, considering false reading from temperature sensor.

This device is also equipped with "open window" detection, but I was never able to trigger it. Manual says that it should be triggered when temperature falls 0,5 degree in 1 minute.

As others pointed out, the biggest problem is wake up interval. First thing you should do is to switch it to some reasonable level like 240/300 seconds. If you don't succeed, you should reset the device and try again.

I'm still struggling with setting this TRV and I'm also looking for any feedback

Well after resetting the device again (pulled the batteries and re-inserted them). It seems to work ok again. I hope it continues to work for longer than 2 days (which is currently the 'record')

Seems to have worked for about 8 hours

2016-02-08 21:46:14.104 Detail, Node002, Polling: COMMAND_CLASS_BATTERY index = 0 instance = 1 (poll queue has 0 messages)
2016-02-08 21:46:14.104 Detail, Node002, Queuing (Poll) BatteryCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x80, 0x02, 0x25, 0x78, 0x3a
2016-02-08 21:46:20.624 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)

after that it remains quiet. Can the Comet be flashed with some new (more stable) firmware by any chance?

So now, when it's getting warmer outside my TRV went completely crazy. Today it went up to 28 degrees despite the fact that both modes were set to 16.
I'm still looking at how to control in manually (REMO mode), so I could use external thermometer inside the room to control valve opening. I;m actually considering sending it back as faulty.

Hello,

I have exactly the same issue as in the first post. My device was working correctly until I have changed the batteries. After this, it stopped to report and react on any z-wave command. Changing the set point manually still works OK. I have already tried to remove and add this device again but it didn't help.
Any idea how to debug it?

I found that changing the wake-up interval would get mine reporting again.
Normally it was set to 300, but a change to 360 or 240 seemed to work.
Next time it was back to 360...

Westcott wrote:I found that changing the wake-up interval would get mine reporting again.
Normally it was set to 300, but a change to 360 or 240 seemed to work.
Next time it was back to 360...

Hi!

Is this solved the problem that it stops reporting?
Also, can you please share your battery life with your settings?

I have set mine to report every 10 minutes, but the battery was down by 30% in a week.
Should "polling" be enabled? (Mine is enabled.)

Thanks and Regards,

Brucez

Easypost is a multi-carrier api with quick technological assistance and customer China Post Tracking it is likewise much easier to go ahead with the procedure.