Seems to have worked for about 8 hours :x 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 ...

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')

Not sure if this is already possible and just me doing something wrong or a new suggestion but: I'm using the free certificates from StartSSL for basically all the services running on my box. StartSSL only allows you to create certificates for subdomains. So I can create a certificate for: domoticz ...

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.

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 ...

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'.

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 ...

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.

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

Also interested how the danfoss is working for you. I haven't given up on the Comet yet. For some reason I see communication between the stick and the Comet in the Control Panel logs, but the devices in Domoticz aren't updated.

rickvanakkeren wrote:The thermostat isnt working here with a zwave stick and domoticz. I spoke to the reseller and will switch this one for a danfoss zwave

The reseller isn't robbshop by any chance?

Thanks for your reply. I couldn't get it to work. I also tried it to make it happen on my laptop, so I installed the Z-wave stick into m laptop and installed HomeGenie. Same there: I can see the node, but whatever command I'm sending, I get a time-out... Start thinking one of those two devices is ...

I can't seem to get the temperature sensor back now. I'll try to delete and re-add the device probably tomorrow.

Ah yeah the wake-up interval that was a headache for me as well. I noticed that controlling the Comet works better in the 'Control Panel'. To reach the control panel go to setup->hardware and enter the setup of the OpenZWave device. There's a 'Node Management' button at the top right of the table ...

Hi Rick, to remove the devices go to the devices screen, select the devices you want to remove and then press the uber-small-hardly-visible-trash-can-icon (the one next to the invert-selection arrow in the header of the table, look closely, it took me ages to find it). I don't know what exactly ...

I'm trying to get the Comet Z-Wave working with my Aeon Labs Gen-5 usb stick and it seems to function OK using the Domoticz OpenZWave Control Panel. I set the wakeup time to the minimum 240 seconds (4 minutes) and in the Control Panel is see the device waking up every 4 minutes, however in Domoticz ...