[Model Certification] - Electricity Energy Monitor PJ-1203A Dongguan Pnija Technology

[IW2FAG-11]

PJ-1203A Dongguan Pnija Technology
1. Provide the URL where you have purchase the device

Current A & Current B
Power A & Power B
Power Factor A & Power Factor B
Forward Energy A & Forward Energy B
Frequency
Voltage

export.json

Thanks for Great Job You are doing

[pipiche38]

I'm currently waiting for an other model ( see #16 ), but in between you might want to try

git checkout wip-stable7-1-005
sudo python3 -m pip install -r requirements.txt --upgrade

then restart the plugin and redo the pairing (make sure that there is no remaining of the device)

[IW2FAG-11]

ok i'll try. seems same Il giorno gio 2 nov 2023 alle 22:28 Pipiche ***@***.***> ha scritto:

…

I'm currently waiting for an other model ( see #16 <#16> ), but in between you might want to try git checkout wip-stable7-1-005 sudo python3 -m pip install -r requirements.txt --upgrade then restart the plugin and redo the pairing (make sure that there is no remaining of the device) — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOPU4QVBWYTVS52JW23QZ3YCQGADAVCNFSM6AAAAAA63QE3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJRGU3DEMZZG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[IW2FAG-11]

Looks working only if I stay on stable 7 with database 2.125
If Upgrade to wip-stable7-1-005 with database 2.125, device look not pairing

[pipiche38]

Any messages in the Domoticz or Plugin logs ?

when upgrading, you must do

sudo python3 -m pip install -r requirements.txt --upgrade

[IW2FAG-11]

As You write i do :
git checkout wip-stable7-1-005 in mine plugind domoticz folder
sudo python3 -m pip install -r requirements.txt --upgrade
Then i restarted all mine Rpi 3.
In this case pairing was not workig.
Then i downgrade
git checkout stable7 in mine plugind domoticz folder
sudo python3 -m pip install -r requirements.txt --upgrade
rebooted mine Rpi3
Now pairing was ok.

Now i delete all device
redo upgrade
git checkout wip-stable7-1-005 in mine plugind domoticz folder
sudo python3 -m pip install -r requirements.txt --upgrade
Then i restarted all mine Rpi 3.
In this case pairing was not workig.
Down here recursive message on domoticz during pairing tentative
2023-11-03 10:21:53.110 Zigate: Assisted Pairing: Polling: []
2023-11-03 10:21:53.110 Zigate: --> Empty queue

[pipiche38]

please provide the file Logs/PluginLog-xx.log

[IW2FAG-11]

Uploading PluginZigbee_09.zip…

[pipiche38]

doesn't work !

[IW2FAG-11]

Voltage is reported ok Il giorno ven 3 nov 2023 alle 12:06 Pipiche ***@***.***> ha scritto:

…

doesn't work ! — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOPU4TWS3XY5IOOLEUG4GDYCTF2NAVCNFSM6AAAAAA63QE3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJSGI2DOOBVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pipiche38]

If Voltage is ok, would you mind providing once more the export.json with the device info

[IW2FAG-11]

export.json
export(1).json

[IW2FAG-11]

[IW2FAG-11]

_PluginZigbee_09(1).zip
Now with attatched power probe.
Some message with only prob A, and then with every two probe

[pipiche38]

I think we should fine tune , did you know what was the power expected on A ?

[IW2FAG-11]

Current is 1000 time to big
Power is 10 time to big

[pipiche38]

ok, try to update the database and simply restart the plugin.

For Power Factor. Is that something requires / important ?

[IW2FAG-11]

i'm doing. All data are interesting. In Ac V x I = VA V x I x power factor is W real power V x I x (1-power factor) is W reactive power reactive power is dissipated and non produce any elettici job work. Now power looks ok. Il giorno ven 3 nov 2023 alle 14:53 Pipiche ***@***.***> ha scritto:

…

ok, try to update the database and simply restart the plugin. For Power Factor. Is that something requires / important ? — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOPU4WJAQVDRDH6LQBLCBTYCTZPFAVCNFSM6AAAAAA63QE3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJSGQ3TQNJSHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pipiche38]

Ok. I did implement PowerFactor ;-)

git pull
sudo python3 -m pip install -r requirements.txt --upgrade

If you want to prevent having to repair, you can do the following:

• Remove all related widget minus one. Keep one widget (so the device is not removed)
• Go to WebUI > Provisioning > Recreate widget(s) of existing device
  => It will re-create all widgets and the Power Fcator. You will have only the widget you have not removed duplicated.

[IW2FAG-11]

Good morning, I am sorry to disturb you again.
I am doing some more tests.

• I delete all the widgets on the new Tuya_601, start with stable and then upgrade to certified device 2.123, the device is paired and I see some widgets.
• I delete all but one widget, update to wip-stable7-1-005, update to certified device 2.123, have the missing widgets recreated and they show up as for stable7, but I still don't see the one for PoweFactor.
• I delete all the widgets, staying with wip-stable7-1-005, try to pair the meter and the Domoticz log shows ......

2023-11-04 10:02:21.524 Zigate: Assisted Pairing: Polling: []
2023-11-04 10:02:21.524 Zigate: --> Empty queue

Is it possible to reduce the polling frequency by values?
Is it possible to make a "request" from the API via script in LUA or Pyton Domoticz to the device and update as required by the user ?

§§ Another question, I see that with Domoticz Version: 2023.2 (build 15589)
messages appear

2023-11-04 10:04:07.800 [WebServer] Deprecated RType (devices) for API request. Handled via fallback (getdevices), please use correct API Command! (192.168.0.100)

I looked at my LUA & Py scripts and I don't seem to be using the old API format, does it come from the Domoticz-Zigbee plugin?

Thanks

[IW2FAG-11]

_PluginZigbee_09.log
During failing pairing

[pipiche38]

Good morning, I am sorry to disturb you again. I am doing some more tests.

* I delete all the widgets on the new Tuya_601, start with stable and then upgrade to certified device 2.123, the device is paired and I see some widgets.

* I delete all but one widget, update to wip-stable7-1-005, update to certified device 2.123, have the missing widgets recreated and they show up as for stable7, but I still don't see the one for PoweFactor.

* I delete all the widgets, staying with wip-stable7-1-005, try to pair the meter and the Domoticz log shows ......

2023-11-04 10:02:21.524 Zigate: Assisted Pairing: Polling: [] 2023-11-04 10:02:21.524 Zigate: --> Empty queue

This looks very strange, and I do not see any issue on the log. Sniffing would be good to understand, what is happening.
I'll try to do some testing on my side.

Is it possible to reduce the polling frequency by values? Is it possible to make a "request" from the API via script in LUA or Pyton Domoticz to the device and update as required by the user ?

The device itself is doing the reporting, I know that there is an Update Frequency mecanism, but I'm waiting for the similar device as you to understand how it works with teh Tuya GW.

§§ Another question, I see that with Domoticz Version: 2023.2 (build 15589) messages appear

2023-11-04 10:04:07.800 [WebServer] Deprecated RType (devices) for API request. Handled via fallback (getdevices), please use correct API Command! (192.168.0.100)

I looked at my LUA & Py scripts and I don't seem to be using the old API format, does it come from the Domoticz-Zigbee plugin?

Normaly the plugin z4d should be clean. Did you check also your dzVents scripts ?

[pipiche38]

There is a bug on ZNP which prevent pairing with the current working branch. Sorry, I need to fix it before moving forward

zigpy/zigpy-znp#231

[IW2FAG-11]

Don't worry we are here to help you .... on this great job !! Il giorno sab 4 nov 2023 alle 15:24 Pipiche ***@***.***> ha scritto:

…

There is a bug on ZNP which prevent pairing with the current working branch. Sorry, I need to fix it before moving forward — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOPU4WLQTNKIDYA32JPCG3YCZFYPAVCNFSM6AAAAAA63QE3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGQ2TMOBVGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[pipiche38]

You should be able to pair now with the updated wip-stable7-1-005

[IW2FAG-11]

Yehaaaa now pairing is ok.
Still some problem on data..... I'll try to test.

[IW2FAG-11]

I did some tests, now it's pairing but I see some problems.
Without loads I read PowerFactor 100% and it matches, then I see Power (usage) at 100W while it should be at '0' as it reads in the device log.
Putting a load of about 450W, I see that the current is shown at 1.9A, the PowerFactor goes to 90% while the Power (usage) which I guess is the instantaneous one shows 90W. It seems that the Power widget still shows the powerfactor.
Reading again in the log, the processed data seems to be correct.

Then paying closer attention, I notice that .....
Voltage refresh occurs, current, for a fraction of time it reads 400W in the Power which is then rewritten with the powerfactor value.

def ts0601_power_factor(self, Devices, nwkid, ep, value):
self.log.logging( "Tuya0601", "Debug", "ts0601_current - Current %s %s" % (nwkid, ep, value), nwkid, )
MajDomoDevice(self, Devices, nwkid, ep, "PowerFactor", value)
store_tuya_attribute(self, nwkid, "PowerFactor_%s" %ep, value)

Does it return or is there a mismatch in the argument list ?

[pipiche38]

I have updated the code, it was just a mistake in the logging (bad copy paste).
I also think that I understand the issue of mixing Power and PowerFcator

Just pushed an update. So if you can simply do a git pull that would be enough

[IW2FAG-11]

Ok, now all widget are responsive.
Tomorro i'll test if they are calbrated.
I already know that voltage is perfect but frequency isn't.

[pipiche38]

@IW2FAG-11 what is the out come ?

[IW2FAG-11]

Sorry i have had some problem and i'd never do any precision measure.
Item looks like ok.

[pipiche38]

so we can close the issue ?
I think in all case measuring the PowerFactor with the clamp is not the best way ...

[IW2FAG-11]

yes. You can close. Thanks. I think that also frequency is reported with high error. With this device i saw 49.13 Hz but with frequencimeter i read about 50.00Hz. So the device report data also if is not tooo precise. Il giorno mer 15 nov 2023 alle 13:58 Pipiche ***@***.***> ha scritto:

…

so we can close the issue ? I think in all case measuring the PowerFactor with the clamp is not the best way ... — Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQOPU4XH4KUSWD3ET2OL3WTYES355AVCNFSM6AAAAAA63QE3J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSGQ4TEMBYGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>