Hi Pieter,

I use Node-Red solely to 'inject' values from MQTT into Domoticz, and maybe you do that as well. So I'm no expert in how to inject from Domoticz --> Node-Red, but perhaps you have to use the 'MQTT Client Gateway with LAN interface' in the Hardware tab.

Remote Server: in your case the ...

In your graphs you will see 2 datapoints on a single date (assuming all old data matches the new database settings).
As you state is might be tricky...
If there is a mismatch you will flood your log with error messages that a certain line in the database is corrupt or cannot be read.
On the other ...

In the 'control-panel' of the zwave-js-ui you will find all devices. By clicking a specific device it will unfold additional settings. Depending on the node there will be: switch, sensor, meter and configuration. By clicking that specific setting it will unfold the available options under that ...

I migrated somewhere spring last year from a Pine64 to my QNAP NAS. Took me a lot of searching because the Z wave stick was not recognized at first and had to install an additional driver. After that a similar problem as you mentioned and I solved it (again: for a QNAP) by using "devices: /dev ...

From your .yml file I gather that you are dutch. Node-red has a Buienradar node available https://flows.nodered.org/node/node-red ... buienradar if that helps

Hi there,
I'm afraid I can't help with your question with the plugin.
I do recognize your observation on answers taking longer or not coming at all. When I started back in 2017 I found a lot of answers on my questions so no need to ask for myself. Meantime I experimented my way through al lot of new ...

Perhaps not the intended solution, but what worked for me (working from Portainer)

After initial Docker Domoticz creation the '/opt/...' was created

In my /home/pi/domoticz/plugins folder I added the required plugins (git clone '...')

Then 'deploy the container' in Portainer and the added plugins ...

Following up on this post:
After a lot of testing I migrated the 'traditional' Domoticz to a Docker set up, managed to get everything up and running (Zwave2MQTT in Docker, Speedtest in Docker, plugins for Buienradar, Presence detection, Pi-hole and Kodi, scripts for backup and SNMP monitoring, P1 ...

Hello Remco,
A little late reply, but I now stumble upon your post. I have similar problems with this device. Mine drops out appr. once a month, although the Z-wave network is strong and there are plenty of nodes within 3 meters. The way I kind of keep it to the once a month is that I set timers to ...

Son brought back the Windows laptop and I could copy my 'live' Z-wave stick to the 'spare' Z-wave stick. That made all the difference! Thx @mgugu.

So for now I'm able to experiment on a spare system while the live system runs the smart house ;-)

Next up is running everything in Dockers (not ...

Thx, I planned to do that over X-mas holidays (but without the copy to the other stick) and now even more because our son is using our windows laptop since his one crashed. I will try the copy route just out of curiosity: if that makes a difference with the way I now made a 'copy' from one stick to ...

In the screenshot there are a 'receive configuration...' and a 'send configuration... '. This is how I 'cloned'. When I plug in the 'cloned' stick it shows up as a 'Static PC controller' as you can see in the screenshot. So I guess that they have different ID's. My setup is similar to yours 1 ...

Updating is meant for both Domoticz and Zwave-JS-UI. So I guess the broker between Zwave-JS-UI and Domoticz works fine. Still wondering if the main controller (OZW) with connection to all nodes has priority (or is the sole connection) over the secondary controller in Zwave-JS-UI. I could (as mgugu ...

Don't know if this is the right topic but since @heggink is offering help I'll give it a go:
Happy user for 5 years and I also started with z-wave devices before extending to P1, OTGW, Speedtest, NAS monitoring, etc. etc.

In the latest update I read about the depreciating OZW and thus the migration ...

Perhaps a little late, but I had not experienced this up till 2 weeks ago, when I did a clean install of my NUC (Ubuntu 20.04) and installed Domoticz and SBFspot.
Everything as smooth as one could wish for except SBFspot: no kWh generation in Domoticz but upload to PVoutput without a glitch. Tried ...

I checked again the exact interval I set in the timer: I started with every 2 hours, then stretched to 3 hours and now it's 4. Originally I planned to go to 5 or 6 hours, but forgot. I do agree it's far from ideal, but for me it works.

My (not so elegant) solution works. I can control the thermostat. I did so in April, just make sure you increase the setpoint 1 whole degree or more, won't accept 0,5 degree.

Skippy

Hi,
I originally started out with Windows box, but due to this problem I moved to Linux. It is working fine now but after every update, system crash or whatever restart I have to check if my FGS223's are responding. If not I stop and start Domoticz and check again. Occaisonally I have to do this 2 ...

Hi
I installed this in March (when it was cold) and it I experienced frequent dropouts. I suspected it had to do with overheating. My (crude) solution: an old fashioned timer in the wall socket which turns off the OTGW every 4 hours for 15 minutes. This solved the problem, although the you will see ...

Hello all,

Last week I was able to connect the Nodo Shop OTGW with NodeMCU. All went pretty smoothly. I found some instructions on how to change my boiler to the OpenTherm protocol. Some hardware modifications to the boiler were mentioned, but when the OTGW lost connection (yesterday afternoon when ...