Having walked away and taken time to think it through I'm still stuck. I have fixed: Meter_Calendar Meter DeviceStatus In all of these the highest number stored for my production total is 7114821. looking at the code id seems the api in use is {ip}/production.json?details=1 , which right now is ...

Arghhhh!!!

Fixed the value for device 50 in DeviceStatus and as well, still on restart the values pushed to MQTT are roughly double what my Envoy is reporting as is the new value put into DeviceStatus. What on earth is going on?

How the hell do i fix the data in Domoticz? I've tried downloading the database from backup/restore, fixing the Meter and Meter_Calendar tables and uploading using restore. Result: Meter_Calendar fixed. Meter table uploaded values totally ignored apart from the last one entry provided but Domoticz ...

Version: 2024.7 (SjoerdNLD build) Platform: Pi B+ OS: Buster Lite Hardware: MQTT LAN interface, Enphase Envoy, 1wire (owfs) Something in my system suffered a brain fart yesterday afternoon. Below is an extract from my nightly Domoticz database backup, ID 50 is my solar production, at 15:20 it almost ...

You also did not mention in the github issue that the current Client ID is changing after a new startup of the Domoticz MQTT gateway. If that is fixed it would perhaps help? Does it really change after a new startup of the Domoticz MQTT Hardware Gateway, is the GUID not directly related to the ...

Sorry but no, it isn't possible with the current model. MQTT ACLs are by default deny, if you activate a default ACL file every user and every client is denied access to anything. You have to grant users and/or clients access to topics you want them to be able to read and write therefore you need to ...

I couldn't find clear explanation in the MQTT specification whether Client ID must be unique to the hardware (Domoticz instance) or to the subscription. Making two connections with the same Client ID from the same PC using mosquitto_sub the sessions are unreliable. Therefore I believe that in MQTT ...

Thanks both,

It looks like my understanding is correct. I restarted the same Domoticz instance as above again and different GUIDs are used. Therefore Mosquitto is not able to do the tidying up FireWizard posted.

I'll pop a request in over on github.

Cheers
Sumdum

Hi all, Before I open a suggestion or ticket I just wanted to check - am I correct in thinking there is no way to determine the Client ID Domoticz will use when connecting to an MQTT broker? There's no configuration field on the broker config page and looking in my Mosquitto log I see the following ...

Great, thank you Kedi.

SumDum

Hi, I have, or rather had, a pi zero monitoring the flow & return temperatures of a solar thermal system. The pi died, it's a fairly damp environment it lived in. Rest in peace little one. Now, I have all my domoticz pi set up to backup to a local ftp server every night so I have the database. So I ...

Thank you FireWizard. I think gizmocuz is onto it now over in github.

Thanks for the extra info above, I'll try that if I'm still having problems after tomorrow's build.

I'm not ruling anything out FireWizard. I know that when I first set up the B+ I had no reason to suspect a problem. All the Inverters were imported with a bare serial number as their identity, there was no 'Inv: ' prefix you now get. I edited all their names prefixing their position to make them ...

Hi FireWizard, Hello @SumDum This explains a lot more, but I do not believe, it has something to do with the orientation of the panels. If, it is true, it may happen randomly. I only mentioned the orientation of the panels because if all panels faced the same way I would not know anything was wrong ...

Hi FireWizard, thank you for your response. You should check whether the indication in the Domoticz widget is identical to what is shown in the browser, if you go to: http://192.168.10.40/api/v1/production/inverters Only if you see a difference between, what is shown in your browser and what is ...

Does anyone here have panels facing in two directions? e.g. East & West. I do and I've found domoticz does not always correctly assign data received from the api to the meter devices. If all your panels face the same way and so always produce roughly the same power you won't be able to tell you are ...

Hi, I have Domoticz logging a number of temperatures from 1-wire sensors using an I2C interface. In the local logs the timestamps are always on the 5 minute, near enough: 2022-03-12 17:10:00 67.6 2022-03-12 17:15:00 67.6 2022-03-12 17:20:00 67.5 2022-03-12 17:25:00 67.4 The sensors are also being ...

Hi Brampp,

I've hit the same problem, see my post here
In there you'll find a link to a github bug dating back to August 2018
In that you'll find a link to another similarly old github bug.

In short - known issue

SumDum