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.26 = 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 ...

Thanks, for the new release. No issues after update from 2024.7 to 2025.1. Don't forget to empty cash in browser, otherwise no dashboards etc... Using portainer to update in one stack with Domoticz,Z2M,Vscode,Musquitto etc. Domoticz no probelem with updateing .Homeassistant had problem with P1-meter ...

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..

Hi Walter Unfortunate "last_seen" is nowhere updated and is lost in space with the new 2022.2 version. As a test, I also removed the whole device and did an re- auto-discover. Only the "smoke" and "battery_low" were discovered and inserted in the device table, the "last_seen" was not created. At ...

Hi Walter Some updates. First I have to admit that my C++ knowledge is a little rusty and do not fully understand the flow throw the code. What I can report is that the auto discover of the "last_seen" item is producing a device with that name (LAST_SEEN) but maybe it was already there in the 2022.1 ...

Walter Updateing the auto-discover in Hardware looks okey.... Log file--> 2022-11-14 16:48:15.186 Status: MQTT_local: Connecting to Mosquitto:1883 2022-11-14 16:48:28.322 Status: Zigbee2Mqtt AutoDetect: Connecting to Mosquitto:1883 2022-11-14 16:48:28.525 Status: Zigbee2Mqtt AutoDetect: re-connected ...

Walter, I did use MQTT_exploror to publish the "auto-discover message and got the error below in the log file. 2022-11-14 16:48:30.541 Error: Zigbee2Mqtt AutoDetect: MQTT_Discovery: Invalid/Unhandled data received! (Topic: homeassistant_domoticz/sensor/0x000d6f00166ac2c2/last_seen, Message: { 2022 ...

Walter, Thanks for your reply. Below a dzvent script I used in 2022.1 for tracking "last_seen" using "HTTPJsON" from de Domoticz object in memory to find the updated time. This is than used to update the "updated" time in the dbase for that smoke sensor. I use another script to track all by battery ...

Nope.

Z2M sees the updates and is sending messages . But Domoticz is not picking them up or ?. Tried to birdge the messagages to my broker in Oman to test HA. The messages are received, but only partly picked up by HA and discovered. Little confused....