return { on = { devices = {'Usage L1'}, -- set device trigger }, logging = { level = domoticz.LOG_DEBUG, marker = 'Amperage', }, execute = function(dz) -- Change below between the quotes to names reflecting the devicenames in your system local l1Usage = dz.devices('Usage L1').actualWatt local ...

THese are the devices I have now... 114 Smart Meter 0001 1 Power P1 Smart Meter Energy 115 Smart Meter 0001 2 Gas P1 Smart Meter Gas 1034 Smart Meter 0000000 1 Usage L1 Usage Electric 1035 Smart Meter 0000000 4 Delivery L1 Usage Electric 1110 Smart Meter 00000001 1 Voltage L1 General Voltage 1111 ...

Oh really!? I have SMR5 meter for 1.5 year but got the P1 devices made when I added P1 to Domoticz when I had still an older meter - could that be the issue here? How can I have it recreate the Current devices now too without loosing all history on the others?

Is there a reason the Instantaneous Currents for L1, L2, L3 are not supported in Domoticz? Is there a way to add these myself? Could you elaborate a bit more on the Node-Red and MQTT option for this? I mean I know what they are but how can we use this to add more values coming from P1 port to ...

Hi Guys, I have been using Modbus READ plugin successfully for some time now. As I need to add new Hardware for each register I want to read I was looking at the Modbus DEVICE plugin. However, I am not getting it to work... When I use it as is I get a few errors that seems easily fixable. The ...

Thanks, However, that's not really solving the issue. I already found again what is the answer to this... I have solved this now with the lines: if (devicechanged[sensor] == 'On') then commandArray[#commandArray + 1] = { [light] = 'On' } commandArray[#commandArray + 1] = { [light] = 'Off AFTER 300 ...

Keep in mind that if you submit the "On FOR" command a second time while the light is already on, it will not switch off again. Not sure if this is a bug or a "works as designed"... :-( Add a condition that the device needs to be off (or not on) prior turning it on again. That would leave the timer ...

Hmm, I just looked at the Daikin App and it shows the same - so nothing wrong with the script. Apparently the unit is using some energy for whatever reason every day (each 20 hours)??! I also see that I tested your script on Wednesday apparently. Strange that I don't see it in the Domoticz diagram ...

Hi, I have installed your dzVents script couple of days ago. Thanks for it! However, I do see some strange behavior... I have tested the script once on Thursday around 14:00 by heating this unit for a while. This nicely shows in the diagram. But strange enough, this usage repeats itself each day ...

The URL seems to be changed in the translation from get_day_power_ex into get_Electric_power_ex and this seems to break the script. Is this a typo or translation mistake or am I missing someting?

I believe it is shown in the /aircon/get_model_info which shows 'en_mompow=0' so it seems it is disabled somehow. Can you check if you see 'en_mompow=1' when you do a get_model_info? Just not sure how to enable it if at all possible. Maybe it is a firmware thing as there seems no easy way to change ...

Right, that's exactly what I see. I am still missing the 'mompow' though. They must still have a sensor for it as they measure it but maybe they don't expose it anymore. Do you see this current power usage 'mompow' in the Daikin app at some screen? I don't see it but maybe I am missing it. In that ...

None of the commands listed there work for my models (floor model FVXM and Stylish FTXA). I have now used Packet Capture to see what commands the Daikin app is using. And it is all clear to me now... these are the commands that work for me with its output samples: /aircon/ get_day_power_ex ret=OK ...

That looks promising. However, I just tried the get_sensor_info URL again and all I get is this: ret=OK,htemp=24.0,hhum=60,otemp=20.0,err=0,cmpfreq=17 I tried it on our two different models and neither shows a 'mompow'. Nevertheless, the Daikin app is showing great logs for the power usage so it ...

Hi guys, Great work! and have been using the Daikin integration successfully for 2 weeks now. Just one think I am confused about. What does the LED Indicator do? I was thinking this would (hopefully) turn off the On/Off LED on my unit, even when the unit is turned On. But it doesn't seem to do that ...

I am confused... I copied the script (that is now using darksky but I believe that is irrelevant for my observation) to my Domoticz instance. The values for Solar Altitude and Azimuth seem to be very realistic. However, from the graphs I observed Azimuth was going through 0 degrees sometime between ...

Well, about right.. however, what was not working in my script is the lower couple of lines in the snippet below: setpoint = My.GetValue(otherdevices_svalues['Room'],2) room_mode = My.GetValue(otherdevices_svalues['Room'],3) time_until = My.GetValue(otherdevices_svalues['Room'],4) I use it later on ...

Thank you so much!! I just reconfigured to have temp precision same as controller and that did the trick! I will stick to the 0.5 degrees accuracy until the next stable release then so at least my scripts will work. Thanks again!!!

Rene.

The state of Evohome devices goes to the state as shown in the picture... Image2.jpg Also the Temperature devices show offline and a broken icon... Image4.jpg This has been a long standing problem for me where I can't rely on the state of these devices (TemporaryOverride, PermanentOverride, Auto ...

I am running (again) latest stable version of Domoticz. After every (re)start of Domoticz, my configured Evohome goes offline 15 minutes later. Until then it looks OK with updates every 60 seconds: 2019-12-30 19:14:59.598 (Evohome) fetch data from server After 15 minutes I get the following log ...