Hello Everyone, I have been using Domoticz for a lot of years now with a system that came up to around 700 devices. It has always been fun and I liked it a lot, but I feel its lifecycle is coming to an end now, following the deprecation of OZW and an interface that seems to be too outdated. Over the ...

Like in the shelly thread, with Node-Red, which has been my weapon of choice for some years now... ;) It provides modbus nodes for r/w access so you can easily get into things. However, the details depend on the box manufacturers specs for the rgisters, so the implementation is device specific. The ...

As for the architecture approach: I used to have one generic flow per device typ (shelly). This was accomplished by setting the topic prefix in the shelly device to the corresponding Domoticz IDX (in MQTT settings of the shelly device). So it was (example): shellies/IDX/relay/0/command. This way I ...

sure thing, here you go :) Please note, the bottom portion that ends in the node labelled 'test' is an integration to InfluxDB to record energy consumption. If you don't have that, you can just delete that part. It goes without saying trhat you will need to adapt the flow to your system (Shelly ID ...

Happy to help. For a shelly Plug S, the NR integration looks as simple as the pic below. All it really does, is 'translating' MQTT from Shelly to MQTT for Domoticz. The devices I create manually (one Switch and one Smart Meter). For shelly 1 it's even easier, because it doesn't measure power ...

A quick update on this one. I wanted to implement solar excess charging for my car and quickly reached the limits of the OCPP protocol, which is -in my mind- the most stupid protocoll ever. I decommisioned all of it, got me the modbus documentation from the manufacturer (Schneider SE) and started ...

I have (and always will) integrated every shelly device manually via Node-Red MQTT. I got a flow template for the types I'm using (PLug S, Shelly 1, Shelly 1PM, Shelly flood, Shelly button) and every new device takes me about 2 minutes to set up. This has been working ever since my first one and I ...

In case of battery operated devices this may take some time. You can try to wake them up by briefly removing the battery and reinserting it, then click on Re-Interview Node in the 'advanced' menu of that node. I had to do this for a few devices, others cam up after half a day or so, depending on the ...

I had the same issue I think. I could set them manually from the dashbord but any updates from the internal automation (blockly in my case) just seized to function after the update. No errors were given. I simply sorted that out by moving the automation tasks (like controlling thermostate based on ...

One thing I came across today:

if you want to give your devices 'meaningful names' in zwJS, you better do that, before you map them in Domoticz.
I did it today for some cleanup, and they stopped working.
Solved by a reboot.

I migrated my system on the weekend. I already had all installations done a while ago, so I only had to move and replace my devices. All went smoothly and it seems that this is now a bit faster. The most time consuming task is to replace the old devices with the new ones. I took screenshots from my ...

yep, that would be the way. Installation of NR on a RPI is a matter of minutes only, the same goes for the MQTT Broker (preferably Mosquitto) on the same machine. As for the Domoticz portion, set the topic of the MQTT message to the standard 'domoticz/in' and check the API document for the required ...

Me again
I'm using Telegram to receive status updates upon request (Ip address and other) as a fallback in case my VPN won't work.
But again, I'm doing this via Node-Red.

Node-Red can do that for you.
Very simple to set up and you can then trigger <whatever> using MQTT.

(just wondering what will happen if someone else starts to send random emails there....)

Nick, thanks for all the years of keeping this up and especially for your quick support at any time.
I've moved to a local Alexa-Node-Red integration for the few things I'm actually using.

Glad you sorted that out :) I just had a brief look at the code of this fork. I am curious if this runs stable over a period. The websocket connection will be terminated from the server side every 120 minutes. From what I see, the ws thread then will simply be terminated, while the rest of the ...

Error in your config file.
Typo or wrong path?

same here. No 'cloud' or internet service involved, everything is running locally, even my Solar inverter is blocked from the internet. Outside access only via VPN. As for the hardware, if it requires regular internet access or comes with some chinese app, I simply don't buy it. Bonus point, as long ...

As promised i've sum up a step by step tutorial to make the migration from Open ZWave to Z-Wave JS UI using the Docker compose method. Here is a link to the tutorial Tutorial Thanks a lot for the useful tutorial. I am still shy of migrating due to the several reported flaws here. I understand that ...

Yes, that's kind of it. You may want to change the storage location (or use the one that's given). I have: volumes: - /home/thomas/docker/zwjs/store:/usr/src/app/store first portion is my local storage in the home dir, second is the mount point in the docker image (don't change that). But that is ...