You're absolutely right and I use it all the time. But it doesn't show on the Dashboard and not as a counter for total daily cost. When I saw the Enever hardware gateway, with its metered/countered device called Daily Energy Cost, I just thought this would do daily energy costs including counting ...

I know. There is nothing wrong with the docs, I just expected cost calculation to be part of Enever and read the docs as such. The existence of a Meter/Counter device named "Daily Electricity/Gas Price" got me tripped up. I will quietly wait for the program to have those features and use my own ...

Thanks for explaining. Even after rereading the docs I still needed your explanation understanding this is a future asset. I had already written my own Python program doing the cost calculation per hour, so I have a device counter showing today's total cost in Utilities and a cost line in Log. The ...

I installed the Enever hardware gateway. All 4 devices appear and actual energy/gas prices are correctly displayed. However, both other devices, containing the counter/daily cost just display a copy of the actual price.

The script runs fine but there is a thought error. Mains is only called once at the first of multiple batteries. The idea is that the first battery will contain all the mains info, but that is not necessarily correct. Various batteries can be connected to different phases. Therefore, you have to ...

No, but my 2 devices are and I am otherwise using the same code. Only, the virtual device containing the added kWh's is not hit.

Edit: The answer is in the docs, as always. I just had not found where to search for this answer. Solved.

Thank you!

I am trying to use this. I have added 2 kWh values of 2 devices (solar batteries) into variable Totaal and want to put this total into a virtual sensor, idx 315, type=General, subtype=kWh. I tried your suggestion using: domoticz.devices(315).computed = Totaal It runs fine but nothing happens to my ...

I fully agree about the docs, it's all there and it is quite concise, but also a bit exhausting. After your earlier mail I reread the docs and found good clarification of the problem, which had escaped me at first reading. dzVents looks very powerful and not that difficult to grasp. While longtime ...

That makes sense, thank you, another time saver. Such things are not easy to find out for a beginner as you would expect the interpreter to be more explicit in such cases. It was a great idea to integrate LUA into Domoticz but I will now quickly change over to dzVents as I expect a more seamless ...

Strangely, this code commandArray = {} if devicechanged['Sessy1 batterijvermogen']=~nil or devicechanged['Sessy2 batterijvermogen']=~nil then local value1=otherdevices['Sessy1 batterijvermogen'] local value2=otherdevices['Sessy2 batterijvermogen'] local value3=value1+value2 --> or incase the value ...

Thank you, zicht, for correcting my first steps, I was going into the wrong direction. This was exactly what I wanted to accomplish and without your help it would have taken a long time to achieve that.

I just started learning lua with dzVents in mind later. For starters I took a very simple problem of reading the value of 2 Domoticz devices, add both values and put the result back into a third (virtual) device, all this running every minute. After reading the docs I assumed the following most ...

OK, thank you Walter. As this post is about DADEP, not Enever, I will stick to that and try to solve the problems I encountered. I will change over to Enever if I don't solve those problems in real time. My second problem, about Telegram notification, still exists, but when I change DADEP for Enever ...

That says I should configure Enever in Settings|Meters/Counters, but I don't have that.
Edit: Sorry, that is new hardware to be installed, the docs are not quite clear about that.
But I still wonder why this should be necessary. DADEP does exactly that.

Quite silly, but: No. I must be missing something. I don't have Enever in Settings|Meters/Counters. I filled the 3 lines in table (Dynamische) Prijsberekening and I assumed DADEP would take care of the rest fetching prices from ENTSOE and EEX. I didn't see a reason for Enever this way, but I am ...

Just started using this script and I like it. Some minor things: 1. Gas prices for today and tomorrow are seemingly not coming in. 2. In dadep.lua the line dz.helpers.telegramnote(dz, message) returns a Domoticz error: Error: dzVents: DADEP: /home/pi/domoticz/scripts/dzVents/scripts/dadep.lua:316 ...

I called it solved and it was, but now I made the same error again and now I understand what happened. Problem was I had changed the hostname of the RPi. That's the way I work: start an upgrade on another RPi and when it works OK, change back the hostname. But that makes existing calls to external ...

Solved. I decided the problem must be in the RPi, so I rebuilt the RPi from scratch and put back my existing Domoticz files. That worked. I still assume something must have happened to the RPi when upgrading to Domoticz 2024.2, but I leave that for now. You were right about the internal web server ...

Indeed, https://my.tado.com/webapp/env.js will use port 443, but WeatherChannel probably uses port 80 as per the error message. I am still confused why these services suddenly stopped working without any changes from my side besides updating Domoticz.