Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develco SPLZB-131: power_reactive (VAR) reading #5723

Merged
merged 2 commits into from
May 6, 2023
Merged

Conversation

emandtf
Copy link
Contributor

@emandtf emandtf commented May 5, 2023

Useful to distinguish between Capacitive and Inductive load (negative values are common for negative-energy).

Maybe other Develco SPLZB-13x could have same capability, but I don't have any of them.

@Koenkk Koenkk merged commit af08b1f into Koenkk:master May 6, 2023
1 check passed
@Koenkk
Copy link
Owner

Koenkk commented May 6, 2023

thanks!

@sk-pub
Copy link

sk-pub commented Jun 8, 2023

@emandtf, @Koenkk, it seems that this change caused incorrect power measurements. All my 5 SPLZB-131 devices now report 100 times less power.

@emandtf
Copy link
Contributor Author

emandtf commented Jun 8, 2023

@emandtf, @Koenkk, All my 5 SPLZB-131 devices now report 100 times less power.

There isn't any relation about previous or other types of measurements. This commit regards a NEW value and nothing is changed to normal ones of the way them are retrieved/read/parsed.
I'm using this code/commit for all my 11 SPLZB-131 devices from middle of April and all is working well for all kind of measurements.

@sk-pub
Copy link

sk-pub commented Jun 8, 2023

@emandtf, @Koenkk, All my 5 SPLZB-131 devices now report 100 times less power.

There isn't any relation about previous or other types of measurements. This commit regards a NEW value and nothing is changed to normal ones of the way them are retrieved/read/parsed. I'm using this code/commit for all my 11 SPLZB-131 devices from middle of April and all is working well for all kind of measurements.

I have no better guess – it's the only change for this device in 1.31.0. Downgrading to 1.30.4 solved this problem for me.

@emandtf
Copy link
Contributor Author

emandtf commented Jun 8, 2023

@emandtf, now report 100 times less power.

Please open your "z2m/data/database.db" using a normal Text editor and check for multiplier/divider values for those 131 devices, and check if they are correct or fix it if needed, then restart Z2M.
I had a similar issue 1 year ago when something (I never discovered who and why) changed those values and power was 10-100 times less than the real ones.

For these kind of values:
"activePower": 80
"rmsCurrent": 393
"rmsVoltage": 23772
"acFrequency": 50020
"reactivePower": -5

Correct "database.db" values are:
"acVoltageMultiplier": 1
"acVoltageDivisor": 100
"acCurrentMultiplier": 1
"acCurrentDivisor": 1000
"acPowerMultiplier": 1
"acPowerDivisor": 1
"acFrequencyDivisor": 1000
"acFrequencyMultiplier": 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants