Thank you for the suggestion of using python3 instead of python. I’ve changed it in the readme and code.

Cool! Thanks for the swift fix!

gizmocuz wrote: ↑Tuesday 03 June 2025 14:24 Are you the same person who created a Github issue?

No, I did not create the issue.

Thanks! Reverting line 85 in www/app/log/RefreshingChart.js returns the broken axis view again. The change (git sha f0cff38a70) was added recently on May 25th by GizMoCuz with message: 'Default area graph type for most day charts'. Not sure which problem this fixes? It is using boolean flag ...

After the last update to the latest version (went smooth, thanks a lot!) I noticed that graphs are not having an axis break, ie. they all show a full y-axis scale starting at 0 to the values measured. I remember vaguely that this was not the case before. See below for an examples without and with ...

Can someone guide me through setting up this plugin? Good news, with 1 battery there is no need for scripting. To install the python plugin see this wiki page: https://wiki.domoticz.com/Using_Python_plugins Consider using the domoticz python plugin manager, as that takes the burden away from the ...

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

Instead of using the P1 device we should add a (Home) Battery device which is providing P1 device like features except for keeping costs and providing 1 set of import and export counters only. Especially for the HomeWizard Battery there should be no cost involved as it only charges using solar power.

gizmocuz wrote: ↑Friday 21 March 2025 10:48 So, the documentation is OK? (I did not create the documentation, but it looks OK to me programming wise )

I think it would be even better when the kWh unit in the text is rephrased to Wh.

gizmocuz wrote: ↑Friday 21 March 2025 10:40 Hmm strange as I read

for instance "123456;78", 123456 being the absolute counter value, 78 being the usage (Wh).

.
With close reading I can now see that I should have interpreted the first kWh mentioned as Wh.

... You can create (or actually should) two kWh sensors and use these for the totals of the imported/exported enery/power This way, you can also use them on the Energy Dashboard Of course, you can create a dzVents script if you like to still make a P1 meter, but I don't think this should be the ...

I think our documentation is pretty accurate as many are using it, but you could be right, but what is wrong with it? Let's focus on the documentation first, I'll address the P1 meter in a separate answer. The comment on device type 243, subtype 33 says: "The first number is the actual power in ...

Why did you use a P1 smart meter? This is a battery device You should use generic kWh meters for the totals I fixed a bug, the totals were not showing as they were added as kWh values instead of Wh values. The counter documentation for device 243, subtype 29 is imho incorrect in that regard. See ...

gizmocuz wrote: ↑Friday 21 March 2025 9:24 Why did you use a P1 smart meter? This is a battery device
You should use generic kWh meters for the totals

Yeah, I know the P1 might be seen as a strange design choice. However, the generic kWh meter does not show import and export as separate values, while the P1 meter does.

assp22 wrote: ↑Thursday 20 March 2025 17:13 thanks, but the totals in the overview are missing

Thanks for the feedback.
Which totals are you referring too? Which counter do you recommend?

I've just created a python plugin for the HomeWizard Battery at https://github.com/etmmvdp/HomeWizard-B ... /tree/main.

See the readme for details how to create a token which is required to run the plugin.
Let me know in case of questions and improvements.

I upgraded to 2024.7 and it keeps running. But with this version the web ui isn’t responsive after a couple of hours.


Edit: The last versions of domoticz had a deadlock problem. When this was fixed a beta version (Version: 2024.7 (build 16286)) of domoticz has been running for weeks without issues.

This occurs after a firmware update of the Homewizard P1 meter. There is an improved version of the python plugin around that also repairs the error at: https://github.com/gettevan/HomeWizard-Wifi-p1-plugin I contacted the original programmer Eraser3 but he didn’t react. According to https://github. ...

I can confirm this observation. I'm running domoticz (version 2023.2) in docker and once every week the docker process is oomed (out-of-memory stopped by the kernel): [Wed Oct 2 08:55:59 2024] Out of memory: Kill process 20609 (domoticz) score 331 or sacrifice child [Wed Oct 2 08:55:59 2024] Killed ...

I have Plugwise-2-py via MQTT to Domoticz running. I started with version 3.x of Domoticz which was able to create all devices in Domoticz and update values. So far so good. I've now upgraded to version 4.9700 and want to run a modified version of the Node-red scripts to read out a rtl-433 device ...