I am looking to capture the codes too, but the latest version of Domoticz just shows me 67, 68 etc for the Coco gdr2 switch codes .. this is probably the house code (A,B,C,D) .. no idea what the rest of the transmitted codes look like (there is also a unit number, a long preamble, and presumably an ...

My problems seem to be related to corrupted ozwcache_0x....xml file in the /config folder. Deleted it and the networks is slowly rebuilding a working version, although still missing power number for a recent fibaro type G wallplug .. I think there is no .xml for it in the config folder.

No power data from my wallplugs either.. Both fibaro gen 6 uk, and aeotec equivalent. Also no power numbers coming back from aeotec CT clamp power meter zw095.. Seems like all power values have vanished. Ozw control panel shows the devices, they talk, but no data values are shown. Can I / we roll ...

Several of my zwave devices get themselves into offline/error state after a few days (or weeks) or running. Disabling and then enabling the ZWave device sorts it (they were not really dead then) but I can't see how to do that automagically using LUA event or similar. If I restart the whole Domoticz ...

Yes, just saw the same problem. Apparently Domoticz is using local time for the X axis of the graphs and tables, and doesn't cope at all well when 01:00 happens all over again at 02:00. Maybe Dom should record all its data using UTC, and sort out local time axis if the user really wants it later ...

In the end I set them up using 'manual switch', type rfxcom, coco gdr2, and then input the appropriate channel (A->D and 1-4) and tested them. That works OK. You may have to hunt to find the correct setup .. this worked for energenie and the SMJ devices, but I couldn't get some older Lloytron models ...

I looked through the forum and found recommendations for the Bresser sensor (£16 in the UK from Amazon .. https://www.amazon.co.uk/gp/product/B0076JGK7U) but I have equally good luck with much cheaper TS-WS-07-XF from ebay (half the price) .. although the ebay model uses AAA cells, and is a bit ...

The new WU API seems to be vaporware so far. How stupid do you have to be to pull the plug on the old one before the replacement is up, running, and fully tested.

An old thread, but this seems closest to what I need. I have two TKB TZ68 (uk model) wall plugs in my system and in both of them the LED setting is exactly backwards from what OZW/Dom think it is .. i.e. 'on indicator' setting puts the LED on when the load is off, and 'night light' puts the LED on ...

I have a bunch of these, which I can register with Dom using the supplied remote and a RFXCOM transceiver, but (as others have noted) on/off are actually sent to the relays as two separate channel/ID 'on' commands. Has anyone got an elegant solution (plugin or otherwise) for making a Dom 'switch ...

That just solved it for me too, with z-stick and aeotec multi sensor. Apparently the 'get device info' receipt/response was harder to achieve than the normal data transfer ( you can see ozw try, and fail, at 20m range).

The problem is that that is just causing LUA extra work to read/write an unchanged sensor value, to get around the problem of fixed timeout. Yes, it works, but No, it isn't what I'd call 'elegant'.

Afaict the 'usage' part of electricity/gas/etc counters will only graph (and show, if you download the data table) at hourly intervals. You can get a 5 minute plot of other meter types, so my (inelegant) solution is to use a LUA script to read the 'energy' (or whatever) usage value from the second ...

Late to the party but I'd like to be able to specify different timeout for some sensors too (as the OP says, virtual one in particular .. I can't even see a way to use a script fake out the lastupdate value for them,. unless I read and rewrite their actual values in LUA script).

Linuz/ubuntu etc noob here (Windoze I can do) .. is there some file name incantation which will let file:write in an LUA script actually put the data someplace I can find it (either on a shared space on the server, or better yet on the PC shared folders). As far as I can tell, whatever I put in for ...

I had no end of trouble with the zwave controller of that type, most of which went away when I upgraded to an Aeon Zenstick 5. And I am not alone .. check out: https://www.uk-automation.co.uk/z-wave-usb-stick/ As someone already mentioned, being able to walk up to the remote item and pair it with a ...

I have a problem with my Aeotec Gen5 energy meter on Synology - it doesn't seem to create any devices when it starts. On the PC version it starts fine. Here are the appropriate bits of the logs .. can someone suggest a fix? I upgraded the synology install to the latest beta version, but no ...

On synology the log is 'elsewhere' and you can review it from the package centre synology package, rather than inside the setup tab on Domoticz itself. Click the Domotiz package (I'm using 6.x but I assume other versions are similar) and then select 'view log' (at the bottom). No, I don't know why ...

Another issue I could use help with .. I had the Aeontec HEM gen5 working just fine, for a while, but at about 20:45 last night the devices stopped receiving data, and I can't get them to revive (I have not disconnected them from the Z-wave network, but I've tried everything else). I can get them ...

Thanks for the hint about the sun .. I KNEW the worker didn't query the server when it was dark, but failed to add 2+2. 8>. Just a suggestion - whoever owns the worker code might like to query the server anyway (to generate the new devices) whether it is dark or not when you first add the hardware?