apologies

this is what I used:

https://github.com/etmmvdp/HomeWizard-B ... /tree/main

and never had a problem. You create some sensors and of you go.

Added some summary scripts and never had a problem

Regards Rini

see:
viewtopic.php?t=43321

Hi Walter,
Found the solution. Apparently the portainer version was not up to date. Did apt- upgrade, portainer update, restarted docker-ce . After that no http errors and the (weather)devices were added again and hopefully they will be updated with data. I assume, what happened was that domoticz ...

It worked before. I did fill in the lat/lon in de the setup no result. I probably did a rebuild of the container via a stack in portainer (iam not sure anymore). I did also try to setup a pp-manager also that failed with an error in the log file. Checked the plugin directory on read/write was (rwx ...

Meteorologisk institutt Norway (Weather Lookup) gives error :>
"2025-11-30 18:58:59.124 Error: Weather_home: Error getting http data!. "
Deleting the hardware and re-adding gives similar error result. Also all related devices were removed.
It worked until I did a restart of the docker container ...

pulled the release: domoticz/latest that solved the version number problem:

new:
Version: 2025.2 (build 16816)
Build Hash: 298225976

Same here (version 2025.1 build 160804) . Docker stable release installed on a Synology NAS.

Thanks for the example.
Attached I included tthe percentage as well.

Regards

Is there anyone who has a solution for the "total cost" bug if you have fixed rates in the meter settings? (as mentioned earlier).
Walter apparently has the solution for dynamic rates, but the total-costs for the "fixed rates" are wrong in "Energy Dashboard", Reports and graphs.

thanks,

That is the type that is created by the HomeWizard Battery plugin and is called "Active Power" and possible to include in the Electricity Dashboard.
But no possibility to include more than one battery per hardware integration. So you have to do combine them in one single hardware setup,as ...

This is really great stuff. I just received 3 batteries and they work great as they were designed. However the p1-senseor is not selectable from the energy dashboard the "active power" sensor is. This sensor shows the Import-Export power of the battery. Since I had 3 batteries i had to sum them and ...

Giz,

Attached the screenschot of the report and multimeter_calander table ofn the13th of may. I use fixed costs set in the setttings (see above). Both (T1 and T2) set at 0.26 E/kwh and (R1 and R2) set at 0.14 E/kwh.

Therefore I expect :
The costs:
T1= 6.788* 0.26 = 1.76488 Euro
T2= 1.372* 0 ...

Walter I still have a problem with the cost calculation in domoticz 2025.1. The problem seems to be the total cost. The usage and return cost values are calculated correctly with right cost values from the meter/counter settings. However those values don't add up tto give the total-cost. I saw some ...

Had a look in MqttAutoDiscover.cpp and there is a difference between 2024.1 and 2024.4 . In 2024.1 the test on "restart" is not skipped while in 2024.4 its left to a later stage where the button action is unwrapped. Obvious something is wrong there. Below the difference between 2024.1 and 2024.4 at ...

I did remove the switch "restart" , but i don't seem to be able to re-discoverer it with AutoDectect in the new 2024.3 stable version. These are strange entries since they come from the Sonoff dongle (zstack- flashed with Z2M) itself. They don't have entries in the Z2M webpage like normal devices ...

I mean the switch in domoticz's switches tap (z2m-restart_z2m). This is auto created by the z2m auto detected (from the Sonof-dongle). You can push the symbol and than you get the error. In Home Assistant you get the same switch and there it works out-off the box. The ZB_waterpomp is also auto ...

Dear,

Try to use the auto discovered restart button of the the Z2M Sonof dongle but it failed. Same one is used in autodiscovery of Home assistant and there it works without any problem. I have to restart the Z2M so now and then, because of a USB problem on the PI-4 that is still (for years) not ...

Hi Walter
In the mean time I took a big journey into cross compiling domoticz. Frist I ,as explained, commented out the line "last-seen line" in the AUTO_discover.cpp code in the hardware directory. I did it inside a VM using using the "vagrant" example in domoticz documentation. This however was ...

Walter,

After I re-compiled the domoticz source code. I did some more fact finding.
I noticed that after removing the "last_seen" from the exclusion check the following things happen.

a) a new device "last_seen" is created in the the device list.
b) The detector sends out a update message ...

Yes it's there but doesn't get updated from sensors heartbeat (one per hour).


In the mean time i recompiled the source code. and removed the exclusion in the .cpp code. Now it seems to work again....

So maybe a request somewhere to either get it updated in the widget or something like i did..