Hi Firewizard, I did only change the output part of the flow, did not change anything on the scraping part. No changes to the software of the ECU-3, still version 4.1, I have not seen a newer version. I have attached the last version I worked with in Domoticz. Replaced the IP addresses by 192.168 ...

HI Firewizard, Yes still working as a charm. I know there is an API what I understood is that this works with ECU - C if I am not mistaken. I tried an intergration in HA based on it and that did not work. That is why I re-worked the Flow to output for each parameter a topic as that is how it works ...

Hi, I use that flow still although I have moved over to HA. When using HA I noticed that the MQTT broker of HA was not able to handle all the ID's send by node red. Would receive complete information from 3 inverters and number 4 only a few parameters. I modified the flow so it sends out information ...

That is a good question, I thought that my network would keep the same node ID which in OZW can be found under Hardware settings of z-wave device for domoticz. From there I was planning to name my devices again into something logical like kitchen light etc. Can someone that has made the move already ...

I am at the same stage as you are, more or less ready to take the plunge in the deep end...
My guess is that current devices will have to be migrated to the new ID's found by Zwave-JS-UI.
Done via the replace option on devices. At least that is what I had in mind to do.

HI I am still reading into this change tho ZWave-JS-UI. I noticed that in one go ZWave-JS-UI is installed on the PI directly and in another guide it is installed in a docker / as docker image. What would the benefit be to install in Docker? My setup has MQTT and node red running to scrape my solar ...

El Zorro,

Thank you for sharing, I will look into and let this thread know if I was able to get it working.

Bernard

Of course enable new devices.... Did that and found the new water meter device. Updated the meterstand_water.txt and now total is correct. I was to quick in deleting the old watermeter, should have replaced it to keep history.... But that is to late now. Thank you for your help and pointing me in ...

Wondering if there is a somewhat more detailed manual: The basics steps I made were: 1. Backup Z-Wave data 2. Install Mosquitto 3. Install Snap 4. Install Z-Wave JS UI 5. Disable OpenZwave gateway 6. Configure Z-Wave JS UI 7. Install MQTT Auto Discover Client gateway in Domoticz 8. Replace old Z ...

Thank you, saw that plugin too, so as I did not get the script updated and working under Python 3 I installed the plugin This appeared to work fine. Could create the hardware. Did not see a new 'apparaat' (device) so I figured it pickup on the existing watermeter (IDX 1992) Is my assumption correct ...

Thanks for this tip, problem is that I need to order stuff and work out how to use the ESP8266 Proximity sensor.
The python script has worked for many years very so I would like to stick to it.

Need to sort out many other things as well, from PI 3 to PI 4 was not as straight forward as I thought.

Hi Anyone updated the Python script to work with Python 3? Needed to replace my PI, so took the opportunity to upgrade to PI 4 and latest version software. When rebuilding config and installing the watermeter.py script again I got an error message: Traceback (most recent call last): File "/home ...

Hi, I am a NOOB on scripts and LUA, most what I wanted I have created in Blocky and that works understandable and does most what I need. Now I have a 'problem' that I automate lights on in the living room to 45% when the dusk sensor is switched to on. In Blocky I have this working, only thing I ...

To set different levels for different events I have created dummy switches which get turned on.

HI

Does the write to log function work? I tried this a while back to get some details on what is going on but nothing got written to log.
In my blocky's I always have the device = on (or off) then the time I want it to do a time specific thing.

Hi,

In the first if statement it should be or instead of and as this is not on the same day (at least that is how I have it).

Bernard

Hi,

Indeed I searched many times and I have not found any upgrade file for the ECU-3.
Strangely the box offers an option to do so.
In 4.1 under Administration --> Firmware upload --> upload packege...

Good luck with getting it to work!

Problem solved :) New ECU-3 and straight away: Lifetime generation 12.1 kWh Last System Power 172 W Generation of Current Day 12.1 kWh Last Connection to website 2021-07-02 20:13:05 Number of Inverters 6 Last Number of Inverters Online 6 Current Software Version V4.1 Inverter Comm. Signal Level 5 So ...

No idea. Mine was in meterkast, and that has been working for over 3 years, distance 12 - 15 meters. Signal strength used to be 5, and I noticed since trouble started 2. I connected the ECU-3 direct on the point where the invertbus is connected to power cable to the meterkast and there also signal ...

last update: After feedback from AP, they suggested ECU-3 was to far from inverters and not on the same bus. ECU-3 was on same bus but not direct next to panels. Did move the ECU-3 and same result, no data. AP was willing to test ECU-3 so shipped it, they could not see what was wrong with it and ...