This patch is doing what I want:


diff --git a/main/SQLHelper.cpp b/main/SQLHelper.cpp
index e6bafa88a..91b351fee 100644
--- a/main/SQLHelper.cpp
+++ b/main/SQLHelper.cpp
@@ -3750,6 +3750,14 @@ bool CSQLHelper::OpenDatabase()
{
UpdatePreferencesVar("P1DisplayType", 0);
}
+ if ...

thanks for the array tip

What you are really asking is to read the state of any device in Domoticz by the plugin.


No.


Cost T1 and T2 are no settings, only tariffs (as discussed before).


I'm not english native, maybe I have difficulties to make you understand what I think.
The offpeak start and offpeak end I'm ...

I suppose your device "Teleinfo Tarif en cours" has the setting.


You're right


A python plugin can have no direct interaction with other devices, it is not designed for that. It would make things very complicated to move the plugin from one user to the other.


That's why I wanted to add ...

As I said, I'm creating a plugin to smart charge my car.
I want everyone to be able to use my plugin and I don't want to ask for offpeak hours in the plugin settings. Not everyone have a TIC device or a sensor with offpeak data.

I would like to find it, as habahabahaba is able to do it with HTTP ...

I'm using plugin "Teleinfo EDF", which creates a P1 smart meter, and 1 low tariff counter, and 1 high tariff counter:

Please define offpeak hours.
Is that the hours with lowest energy tariffs?


For my usage, yes.

I'm working on a plugin to smart charge my EV car.
In France, most of users are with the national company, EDF.
Within this company, you can choose different contracts, for different power, single or ...

Please make off-peak hours available in Domoticz Settings so that plugins and scripts can use the values

Some people may have up to 3 off-peak hours per day, in my country

Thanks.

On the page https://wiki.domoticz.com/Developing_a_Python_plugin#Available_Device_Types
there is an error about sensor type 29

"sValue are two numbers separated by semicolon like "123;123456" The first number is the actual power in Watt, the second number is actual energy in kWh."

it's ...

I think it should work for local Shelly devices (wifi or rj45, no cloud) with energy mesurement, and if there is at least 1 switch
The provided API is global for all devices (at least Gen2)

I'm open to modify the plugin if needed

https://wiki.domoticz.com/Using_Python_ ... g_a_plugin

I got a Shelly Pro 1PM device, and I writed a simple plugin to poll datas (energy, frequency, switch state)
it is connected with RJ45 for me (no wifi, no bluetooth, no cloud, no mqtt)

https://github.com/lemassykoi/Domoticz-Shelly-Plugin/tree/main

It has been written from https://shelly-api-docs ...

I'm trying to update Domoticz Wiki, but I'm unable to login.

I recovered my account from MediaWiki, but I'm unable to login with my username and password from mediawiki.
and when clicking on "Help with logging in", it opens a webpage on mediawiki.org, where I'm already logged in.

Any idea? Thanks.

Thanks. I'm rewriting it to not make a fresh connection each update time. I got "locked" because too much sessions opened at once, after few days

The rewriting will use the token until it expires (3 months)

I'm sorry, but, again, this is not true

you can create a device without options. It will indeed be created with energymetermode set to 0

THEN when you update your sensor with real first value, you pass value AND options to update method, like I wrote earlier, and from now, energymetermode is set ...

I'm not 100% sure that the Option for EnergyMeterMode is made to be set during device creation


Capture d’écran du 2025-09-06 17-19-08.png
source: https://wiki.domoticz.com/Developing_a_Python_plugin#Available_Device_Types

I don't understand why you absolutely want to set options at device ...

Hi,

a friend of mine have a MG Marvel R

I created a plugin to gather datas from SAIC API : https://github.com/lemassykoi/Domoticz-MG-Plugin

Workaround was to first create with EnergyMeterMode equal to 0, then assign a value (so the field is no longer empty) and then switch to EnergyMeterMode 1. Any further updates to the field are then processed correctly.


This is not correct.

No need to assign a value, and no need to "switch ...

I tried some tests:

Creating a device with Typename or Type and Subtype, with EnergyMeterMode set to 1 at device creation will always fail the sensor

The only way to create a working sensor is to omit EnergyMeterMode during creation and specify it only for value updates:


devices_to_create ...

As I really don't like MQTT, I created an other plugin to poll my OpenDTU device (solar production)
OpenDTU is connected directly to inverters: https://github.com/tbnobody/OpenDTU

https://github.com/lemassykoi/Domoticz- ... Plugin.git