Error opening url: http://127.0.0.1:8080/json.htm?type=graph&sensor=counter&range=month&idx=305 Topic is solved

[Copitano]

After some procrastination, I finally updated to the latest stable version (2025.1) of Domoticz last week.
The things below under attachments haven't worked since minutes after the update.
I've already tried everything, including updating and upgrading the operating system on my Pi (bullseye).
I'm getting this error message in the log.

Code: Select all

2025-08-24 15:13:00.815 Error: Error opening url: http://127.0.0.1:8080/json.htm?type=graph&sensor=counter&range=month&idx=305
2025-08-24 15:13:00.948 Error: dzVents: HTTP/1.1 response: 404 ==>> Not Found
2025-08-24 15:13:00.959 Error: dzVents: Could not get (good) data from domoticz. Error (404)
2025-08-24 15:13:00.959 Error: dzVents: An error occurred when calling event handler YoulessMaand
2025-08-24 15:13:00.959 Error: dzVents: /home/pi/domoticz/scripts/dzVents/scripts/YoulessMaand.lua:53: attempt to index a nil value (global 'domoticz')

Everything runs on:
Version: 2025.1
Build Hash: 89d5c900d
Compile Date: 2025-05-05 09:02:49
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Mar 20 2025, 02:07:39) [GCC 10.2.1 20210110]

Regarding the daily and monthly COP, the first log line says it all. The rest is a processing error. If a basic metric cannot be retrieved, dzVents obviously can't calculate it. idx 305 (heat pump power consumption from a Youless) is updated normally.
As soon as I restore a system backup from a few minutes before the update, it works normally again. But I simply want to update whenever a new stable version is released.

Below is the script for the monthly total, which I didn't write myself, by the way.

Code: Select all

local httpResponses = "monthTotal"

return {
    on      =   {   
                    timer           =   { "every 1 minutes" },
                    httpResponses   =   { httpResponses .. "*" } 
                },

    logging =   {   
                    level           =   domoticz.LOG_DEBUG, -- set to LOG_ERROR when script works as expected
                    marker          =   httpResponse   
                },
                
    execute = function(dz, item)
        -- ****************************** Your settings below this line ***************************************************
        usageDevice = dz.devices(305)          -- Replace xxxx with ID of energyDevice you want to track
        monthTotal = dz.devices(834)        -- Create as virtual managed counter (energy) and change yyyy to the ID of the new device idx was 320
        -- ****************************** No changes required below this line *********************************************
        
        local function logWrite(str,level)
            dz.log(tostring(str),level or dz.LOG_DEBUG)
        end
        
        local function triggerJSON(id, period, delay)
            local delay = delay or 0
            local  URLString   =    dz.settings['Domoticz url'] .. "/json.htm?type=graph&sensor=counter&range=" .. 
                                    period .. "&idx=" .. id 
            dz.openURL({    url = URLString,
                            method = "GET",
                            callback = httpResponses .. "_" .. period}).afterSec(delay)                      
        end
        
        local function calculateMonthTotal(rt)
            local monthTotal = 0
            local currentMonth = dz.time.rawDate:sub(1,7)
            for id, result in  ipairs(rt) do 
                if rt[id].d:sub(1,7) == currentMonth then
                    logWrite(rt[id].d .. " ==>> " .. rt[id].v)
                    monthTotal = monthTotal + rt[id].v
                end
            end
            return monthTotal --* 1000 oorspronkelijk script 
        end    
        
        if not item.isHTTPResponse then
            triggerJSON(usageDevice.id, "month")
        elseif item.ok then                                      -- statusCode == 2xx
            monthTotal.update(0,calculateMonthTotal(item.json.result))
        else
            logWrite("Could not get (good) data from domoticz. Error (" .. (item.statusCode or 999) .. ")"  ,dz.LOG_ERROR)
            logWrite(item.data)
            
            domoticz.log('montTotal: '..monthTotal)
            domoticz.log('currentMonth: '..currentMonth)           
        end
     
    end
    
    
}

Anyone have any ideas how I can fix this annoying problem without doing a fresh install of the whole thing?

[jvdz]

Do you have 127.0.0.1 in the allowed ip ranges in the setup?

[waltervl]

The API urls have changed since 2023.2 https://wiki.domoticz.com/Domoticz_API/ ... and_newer)

Also check your security settings and make sure API authorisation over http is allowed.
https://wiki.domoticz.com/Security#API_Protection

[Copitano]

Do you have 127.0.0.1 in the allowed ip ranges in the setup?

Yes, 127.0.0.* are allowed as are 192.168.xxx.*

[waltervl]

The API urls have changed since 2023.2 https://wiki.domoticz.com/Domoticz_API/ ... and_newer)

Also check your security settings and make sure API authorisation over http is allowed.
https://wiki.domoticz.com/Security#API_Protection

Perhaps you missed my remark about API url.
/json.htm?type=graph
Should now be
/json.htm?type=command&param=graph

[Copitano]

The API urls have changed since 2023.2 https://wiki.domoticz.com/Domoticz_API/ ... and_newer)

Also check your security settings and make sure API authorisation over http is allowed.
https://wiki.domoticz.com/Security#API_Protection

Perhaps you missed my remark about API url.
/json.htm?type=graph
Should now be
/json.htm?type=command&param=graph

O kolom
No, I did not mis it
As a matter of fact it solved more then half of the problems. For the RPi new devices were made automatically.
So thank you so much for your help.
Only thing left is the result of dCOP calculation from a php script is no longer updated in Domoticz. Also checked that script on the “command&param” part. But that looks okay.

Code: Select all

 #mbus-serial-request-data /dev/ttyUSB0 21
#!home/pi/domoticz/scripts
#!/usr/bin/php
<?php
//***********************************
//Kamstrup Multical 602 with ID:21 readout and send to Domoticz
//***********************************
$output = shell_exec("sudo /usr/local/bin/mbus-serial-request-data -d -b 2400 /dev/ttyUSB0 21"); //usb drv RPi- "m-busadress 21"
$xmloutput=substr($output,strpos($output,'<MBusData>'));
$xmloutput = new SimpleXMLElement($xmloutput);
$counterID=$xmloutput->SlaveInformation->Id;
$energyValue=$xmloutput->DataRecord[1]->Value;
$volumeValue=$xmloutput->DataRecord[2]->Value;
$ontimeValue=$xmloutput->DataRecord[3]->Value;
$flowtemperatureValue=$xmloutput->DataRecord[4]->Value;
$returntemperatureValue=$xmloutput->DataRecord[5]->Value;
$temperaturedifferenceValue=$xmloutput->DataRecord[6]->Value;
$powerValue=$xmloutput->DataRecord[9]->Value;
$volumeflowValue=$xmloutput->DataRecord[10]->Value;
$EnergyValue=$xmloutput->DataRecord[14]->Value;
$MassValue=$xmloutput->DataRecord[19]->Value;
$energyMValue=$xmloutput->DataRecord[22]->Value-1;
$EnergyMValue=$xmloutput->DataRecord[26]->Value;
$timepointValue=$xmloutput->DataRecord[21]->Value;
$timestampValue=$xmloutput->DataRecord[29]->Value;


$DomoticzIP="http://192.168.2.247:8080/";
$IDXEnergy=199; //in Domoticz: type custom sensor J
$IDXEnergy2=311; //Test RFX sensor kWn
$IDXEnergy2new=362; //Test RFX sensor MJ
$IDXdCOP=319; //Test in Domoticz: type custom sensor kWh/kWh
$IDXOn_Time=95;  //in Domoticz: type custom sensor Uren
$IDXVolume=104; //in Domoticz: type custom sensor M^3
$IDXVolumeFlow=97; //in Domoticz: type waterflow
$IDXTaanvoer=98; //in Domoticz: type temperature
$IDXTretour=99; //in Domoticz: type temperature
$IDXTdiff=100; //in Domoticz: type temperature
$IDXPower=101; //in Domoticz: type type custom sensor Watt
$IDXTimepoint=102;  //in Domoticz: type custom sensor Jaar
$IDXTimestamp=103;  //in Domoticz: type custom sensor Tijd
$IDXMass=198; //in Domoticz: type custom sensor kg
$IDXCoolEnergy=200; //in Domoticz: type custom sensor J
$IDXDay_COP=363; //In Domoticz: Type Counter RFX Meter
$IDXEnergyM=313; //in Domoticz: type custom sensor J
$IDXCoolEnergyM=314; //in Domoticz: type custom sensor J

 // kWh from Elektra WP Today
 $json_string = file_get_contents("http://192.168.2.247:8080/json.htm?type=command&param=devices&rid=305");
 $parsed_json = json_decode($json_string, true);
 $parsed_json = $parsed_json['result'][0];
 $WP_kWh_E = $parsed_json['CounterToday'];

 // kWh from Kamstrup Today
 $json_string = file_get_contents("http://192.168.2.247:8080/json.htm?type=command&param=devices&rid=311");
 $parsed_json = json_decode($json_string, true);
 $parsed_json = $parsed_json['result'][0];
 $WP_kWh_H = $parsed_json['CounterToday'];

 // GJ from Kamstrup Today
 $json_string = file_get_contents("http://192.168.2.247:8080/json.htm?type=command&param=devices&rid=362");
 $parsed_json = json_decode($json_string, true);
 $parsed_json = $parsed_json['result'][0];
 $WP_MJ_H = $parsed_json['CounterToday'];

//Function to send to Domoticz
    function ud($idx,$nvalue,$svalue,$name=""){
        print "  --- UPDATE ".$idx." ".$name." ".$nvalue." ".$svalue."
    ";
        file_get_contents("http://192.168.2.247:8080/".'json.htm?type=command&param=udevice&idx='.$idx.'&nvalue='.$nvalue.'&svalue='.$svalue);
        usleep(250000);
    }

//Function counter to send to Domoticz
    function uc($idx,$svalue,$name=""){
        print "  --- UPDATE ".$idx." ".$name." ".$svalue."
    ";
        file_get_contents("http://198.168.2.247:8080/".'json.htm?type=command&param=udevice&idx='.$idx.'&svalue='.$svalue);
        usleep(250000);
    }

// Instant Taanvoer (C) to Domoticz (kamstrup Reg 4)
ud($IDXTaanvoer,0,$flowtemperatureValue/100,0);

// Instant Tretour (C) to Domoticz (kamstrup Reg 5)
ud($IDXTretour,0,$returntemperatureValue/100,0);

// Instant Tdiff (C) to Domoticz (kamstrup Reg 6)
ud($IDXTdiff,0,$temperaturedifferenceValue/100,0);

// Instant Energy (J) to Domoticz (kamstrup Reg 1)
ud($IDXEnergy,0,$energyValue*10000000,0);
// Instant Energy test (kwh) to domoticz)
ud($IDXEnergy2,0,$energyValue/0.36,0);
// Instant Energy test (GJ) to domoticz)
ud($IDXEnergy2new,0,$energyValue,0);

// Instant Energy (J) to Domoticz (kamstrup Reg 22)
ud($IDXEnergyM,0,$energyMValue*10000000,0);

// Instant VolumeFlow (ltr/h) Domoticz (kamstrup Reg 10)
ud($IDXVolumeFlow,0,$volumeflowValue,0);

// Instand Volume (M^3) to Domoticz (kamstrup Reg 2)
ud($IDXVolume,0,$volumeValue/100,0);

// Instant Power (watt) to Domoticz (kamstrup Reg 9)
ud($IDXPower,0,$powerValue*100,0);

// Instant On Time (hours) to Domoticz (kamstrup Reg 3)
ud($IDXOn_Time,0,$ontimeValue,0);

// Instant Timepoint (time &amp; date) to Domoticz (kamstrup Reg 21)
ud($IDXTimepoint,0,$timepointValue,0);

// Instant timestamp (time &amp; date) to Domoticz (kamstrup Reg 29)
ud($IDXTimestamp,0,$timestampValue,0);

// Instant Mass (10 kg) to Domoticz (kamstrup Reg 19)
ud($IDXMass,0,$MassValue*10,0);

// Instant Energy (J) to Domoticz (kamstrup Reg 14)
ud ($IDXCoolEnergy,0,$EnergyValue*10000000,0);

// Instant Energy (J) to Domoticz (kamstrup Reg 26)
ud ($IDXCoolEnergyM,0,$EnergyMValue*10000000,0);

// Day_COP (kWh/kWh) to Domoticz
ud($IDXDay_COP,0,round($WP_kWh_H/$WP_kWh_E,2),0);

// dCOP (kWh/kWh) to Domoticz
ud($IDXdCOP,0,round(($WP_MJ_H/0.36)/$WP_kWh_E,2),0);

[waltervl]

Dus you also check the security settings for API http authorization?

[Copitano]

Dus you also check the security settings for API http authorization?

yes allowed for 127.0.0.*;192.168.xxx.* and checkbox and basic-auth on.

[waltervl]

Then it should work. None of the devices are updated by the php script? Input is working? Perhaps you can add some debug statements... Or try some url yourself from the same system where the php script runs.

You also can rewrite this to dzvents but that is another topic....

[Copitano]

Then it should work. None of the devices are updated by the php script? Input is working? Perhaps you can add some debug statements... Or try some url yourself from the same system where the php script runs.

You also can rewrite this to dzvents but that is another topic....

No all are updated except Day_COP and dCOP. I’ll try your other suggestions tomorrow. And yes a dzVents script would solve the problem but not understanding whats (not) happening under 2025.1 and ran with no problem under 2024.7

[jvdz]

So to make sure I understand: the http://127.0.0.1:8080/json.htm is now working and now only the "http://192.168.2.247:8080/json.htm?" is not working yet....right?

The shown script updates many devices. Are none of these updates working?

[Copitano]

So to make sure I understand: the http://127.0.0.1:8080/json.htm is now working and now only the "http://192.168.2.247:8080/json.htm?" is not working yet....right?

The shown script updates many devices. Are none of these updates working?

Sorry for the late response.
All devices were updated except dCOP and Day_COP. In the script, I just replaced 192.168.2.247 with 127.0.0.1. After that, no more devices were updated via the script. So back to 192.168.2.247. Now no devices are updated anymore. I don't understand it anymore what is going on.

[waltervl]

Check the script for typing errors.
Also try manually to use the API call from a browser on the same system as where the php script is running, to see if you get an OK or Error on the response.

[Copitano]

Check the script for typing errors.
Also try manually to use the API call from a browser on the same system as where the php script is running, to see if you get an OK or Error on the response.

Unfortunately, I'm getting an error. The script hasn't been changed since Domoticz version 2024.7. So I don't understand why it suddenly stopped working after updating to 2025.1.
By the way, a number of motherboard devices also stopped updating after the update

[waltervl]

If you get an error and you are sure the API call is correct, you have to check the security settings.

Your call seems wrong, it should be param=getdevices like

Code: Select all

/json.htm?type=command&param=getdevices&rid=305

[Copitano]

Your call seems wrong, it should be param=getdevices like

Code: Select all

/json.htm?type=command&param=getdevices&rid=305

This solved the problem. All devices are updated now. Thank you very much
Motherboard sensors stil not updated.

[waltervl]

Great!
There was a change in motherboard sensors for harddisks order and new HDD devices are created but not activated.
So check the motherboard devices in menu setup - devices and activate the new HDD devices (click on green arrow) and remove the old, not updated, ones.

[Copitano]

Great!
There was a change in motherboard sensors for harddisks order and new HDD devices are created but not activated.
So check the motherboard devices in menu setup - devices and activate the new HDD devices (click on green arrow) and remove the old, not updated, ones.

Ahhh, that explains a lot. I merged (replaced) those with the old ones. The new ones were automatically deleted, so the old ones still don't work. Can I fix that?

[waltervl]

Delete the not updating devices. They should recreated again after a restart of the mother board sensors gateway (press on update to restart it)

[Copitano]

Delete the not updating devices. They should recreated again after a restart of the mother board sensors gateway (press on update to restart it)

Okay, but that means I will lose my history right?