search

enesbcs / rpieasy

Easy MultiSensor device based on Raspberry PI
GNU General Public License v3.0
162 stars 33 forks source link

_P206_PZEM016 problem after upgrade PZEM init failed at address 1 #157

Closed Epik77 closed 4 years ago

Epik77 commented 4 years ago

Hi

I have upgraded my rpieasy but this device not working...

by trying with this script the device works correctly:

Reading PZEM-004t power sensor (new version v3.0) through Modbus-RTU protocol

over TTL UART

Run as:

python3 pzem_004t.py

To install dependencies:

pip install modbus-tk

pip install pyserial

import serial import modbus_tk.defines as cst from modbus_tk import modbus_rtu

Connect to the slave

serial = serial.Serial( port='/dev/ttyUSB0', baudrate=9600, bytesize=8, parity='N', stopbits=1, xonxoff=0 ) master = modbus_rtu.RtuMaster(serial) master.set_timeout(3.0) master.set_verbose(True)

data = master.execute(1, cst.READ_INPUT_REGISTERS, 0, 10)

voltage = data[0] / 10.0 # [V] current = (data[1] + (data[2] << 16)) / 1000.0 # [A] power = (data[3] + (data[4] << 16)) / 10.0 # [W] energy = data[5] + (data[6] << 16) # [Wh] frequency = data[7] / 10.0 # [Hz] powerFactor = data[8] / 100.0 alarm = data[9] # 0 = no alarm

print('Voltage [V]: ', voltage) print('Current [A]: ', current) print('Power [W]: ', power) print('Energy [Wh]: ', energy) print('Frequency [Hz]: ', frequency) print('Power factor []: ', powerFactor) print('Alarm : ', alarm)

Changing alarm W value

master.execute(1, cst.WRITE_SINGLE_REGISTER, 1, output_value=100)

try: master.close() if slave.is_open: slave.close() except: pass

can you help me? Thank's

enesbcs commented 4 years ago

This plugin is working only with the Modbus RS485 PZEM016, you are referring to PZEM004 which is using Modbus Rs232 which is currently not supported. You can add a new issue to implement PZEM004 as new device, but as i did not have any of them it will not be implemented soon. I have got only PZEM016 devices.

Epik77 commented 4 years ago

sorry until yesterday before the upgrade worked properly Has anything changed in serial management?

enesbcs commented 4 years ago

Interesting, could you delete and recreate the P206 plugin for testing? Do you remember from which RPIEasy version did you upgraded?

The serial library changed to search ports aggressively if empty list returned by the pyserial lib, but if the array was not empty, there are no change at all. I've done some changes in plugin.py 3 months ago by adding one variable globally. Also have a minor, cosmetic change in P206 to add com port address to the device list in the webpage.

Epik77 commented 4 years ago

I restored an old version: Build RPIEasy 2.0.131 Libraries Python 3.7.3 (default, Dec 20 2019, 18:57:59) [GCC 8.3.0] Linux-4.19.97 + -armv6l-with-debian-10.3 Plugins 74 Now it is recognized: Init hardware ... Load network settings ... Load GPIO settings ... Creating new pinout Load devices from file Load controllers from file Load notifiers from file 19:27:18: Event: System # Boot 19:27:18: Webserver starting at port 8008 19:27:18: Event: Clock # Time = Tue, 19: 27 19:28:00: Event: Clock # Time = Tue, 19: 28 19:29:00: Event: Clock # Time = Tue, 19: 29 19:30: Event: Clock # Time = Tue, 19:30 19:31:00: Event: Clock # Time = Tue, 19: 31 19:32:00: Event: Clock # Time = Tue, 19: 32 19:33:00: Event: Clock # Time = Tue, 19: 33 19:33:06: PZEM initialized at: / dev / ttyUSB0 / 1 19:33:07: Event: Test # Amper = 1.7 19:33:09: PZEM initialized at: / dev / ttyUSB0 / 1 19:33:37: PZEM initialized at: / dev / ttyUSB0 / 1 19:33:38: Event: Test # Amper = 1.7 19:33:40: PZEM initialized at: / dev / ttyUSB0 / 1 19:33:41: Event: Test # Amper = 1.7 19:34:00: Event: Clock # Time = Tue, 19:34 19:34:43: Event: Test # Amper = 1.7 19:34:48: PZEM initialized at: / dev / ttyUSB0 / 1 19:34:48: Event: Test # Volt = 232.4 19:34:49: Event: Test # Amper = 1.7 19:34:56: PZEM initialized at: / dev / ttyUSB0 / 1 19:34:57: Event: Test # Amper = 1.7 19:35:00: Event: Clock # Time = Tue, 19: 35 19:35:11: PZEM initialized at: / dev / ttyUSB0 / 1 19:35:13: Event: Test # Wh = 173137.0 19:35:18: PZEM initialized at: / dev / ttyUSB0 / 1 19:35:20: Event: Test # Volt = 233.0 19:35:20: Event: Test # Amper = 1.7 19:35:27: Event: Test # Amper = 1.7 19:35:27: Event: Test # Wh = 173138.0 19:35:47: Event: Test # Amper = 1.7 19:35:54: Event: Test # Amper = 1.7 19:36:00: Event: Test # Amper = 1.7 19:36:01: Event: Clock # Time = Tue, 19:36

you could create a plugin with script specifications that I indicated to you?

enesbcs commented 4 years ago

you could create a plugin with script specifications that I indicated to you?

If it was worked before, there are no reason to reinvent the wheel. Just have to figure out why init failed in the newer version.

enesbcs commented 4 years ago

I've added some more checks and debug lines into P206 at commit https://github.com/enesbcs/rpieasy/commit/1a8e69286f0791bb972bf0c124812e6fdd5e2ef2 By the way PZEM016 is working to me: (after i figured out what address i had moved it earlier)


Starting RPIEasy 2.0.168
Init hardware...
Load network settings...
Load GPIO settings...
Load devices from file
Load controllers from file
22:46:32: PZEM initialized at: /dev/ttyUSB0 / 1
Load notifiers from file
Loading rules...
22:46:32: Event: System#Boot
22:46:32: Webserver starting at port 8080
22:46:32: Event: Clock#Time=Tue,22:46
22:46:32: Event: Network#Connected
22:46:46: Event: pz1#Volt=235.2
22:46:46: Event: pz1#Amper=0.0
22:46:46: Event: pz1#Watt=0.0
22:46:46: Event: pz1#Wh=13.0
Epik77 commented 4 years ago

I'm going crazy :-) if I start rpieasy without any task and create a new _P206 task it works properly. If I start rpieasy with other tasks configured _P206 it cannot initialize

enesbcs commented 4 years ago

Please send me your tasks.json somehow. I have added several tasks and P206 still works. Maybe there are only one of the used plugins have an init bug.

Epik77 commented 4 years ago

I sent you the task.json at rpieasy@noreply.github.com It is valid ?

enesbcs commented 4 years ago

I sent you the task.json at rpieasy@noreply.github.com It is valid ?

Nope. You can add it by https://pastebin.com/ or send to rpieasy@altmails.com

Epik77 commented 4 years ago

Hi I sent the task to rpieasy@altmails.com By updating rpieasy and debugging from console enabled:

From https://github.com/enesbcs/rpieasy 61dfe5a..1a8e692 master -> origin/master Updating 61dfe5a..1a8e692 Fast-forward RPIEasy.py | 2 +- _P206_PZEM016.py | 26 ++++++++++++++++++++------ lib/lib_pzem.py | 14 ++++++++++++-- rpieGlobals.py | 2 +- 4 files changed, 34 insertions(+), 10 deletions(-) ./RPIEasy.py Starting RPIEasy 2.0.168 Init hardware... 07:53:42: Pi 1 Model B+ 40 pins Load network settings... Load GPIO settings... Load devices from file Load controllers from file 07:53:46: State preserving is disabled 07:53:46: State preserving is disabled 07:53:46: State preserving is disabled PZEM Exception: No communication with the instrument (no answer) 07:53:47: !PZEM init failed at address 1 07:53:47: !PZEM init failed at address 1 07:53:47: !PZEM init failed at address 1 07:53:47: !PZEM init failed at address 1 07:53:47: Event: Campanello#State=0 07:53:47: Event registered to pin 18 07:53:47: State preserving is disabled 07:53:47: Event: SegnalatoreAcustico#State=0 07:53:47: !Event can not be added, register backup timer You must setup() the GPIO channel as an input first 07:53:47: Event: Volume#Volume=80 07:53:47: BLE scan init ok 07:53:47: Event: LettoreNFC#State=1 07:53:47: BLE scan init ok 07:53:48: Stopping transmission-daemon (via systemctl): transmission-daemon.service. 07:53:48: OS command executed succesfully 07:53:48: Event: Torrent#State=0 07:53:48: BLE scan init ok 07:53:48: Webserver starting at port 8008

Epik77 commented 4 years ago

I commented on these lines: lib_pzem.py [33-36]

testval = self.dev.read_register(self.VOLT,1,4)

if testval == None or testval == False:

self.initialized = False

self.dev = None

Now the device is successfully initialized but it mainly provides only the amper data

Starting RPIEasy 2.0.168 Init hardware... 10:16:24: Pi 1 Model B+ 40 pins Load network settings... Load GPIO settings... Load devices from file Load controllers from file 10:16:26: PZEM initialized at: /dev/ttyUSB0 / 1 10:16:26: PZEM initialized at: /dev/ttyUSB0 / 1 10:16:26: Event: DomoMQTT#Disconnected 10:16:26: MQTT: Try to connect 10:16:26: Set MQTT password 10:16:26: Event: DomoMQTT#Connected Load notifiers from file Loading rules... 10:16:26: Event: System#Boot 10:16:26: CMD: lcdcmd,on 10:16:26: !Unknown command: lcdcmd,on 10:16:26: Webserver starting at port 8008 10:16:27: Event: Clock#Time=Wed,10:16 10:16:32: Event: TEst4#Amper=1.5 10:16:32: Event: TEst4#Amper=1.5 10:16:36: Event: TEst4#Amper=1.5 10:16:42: Event: TEst4#Amper=1.5 10:16:44: Event: test#Hz=50.0 10:16:47: Event: TEst4#Amper=1.5 10:16:51: Event: TEst4#Amper=1.5 10:16:53: Event: test#Wh=178078.0 10:16:56: Event: TEst4#Amper=1.5 10:16:57: Event: TEst4#Wh=178078.0 10:17:00: Event: Clock#Time=Wed,10:17 10:17:06: Event: TEst4#Amper=1.5 10:17:21: Event: TEst4#Amper=1.5 10:17:26: Event: TEst4#Amper=1.5 10:17:29: Event: test#Watt=242.9

I need the system to detect amperes and watts equally

enesbcs commented 4 years ago

I commented on these lines: lib_pzem.py [33-36]

testval = self.dev.read_register(self.VOLT,1,4)

if testval == None or testval == False:

self.initialized = False

self.dev = None

Now the device is successfully initialized

This means that the first read from Modbus device was not succesful, and with disabling testing it can read sometimes. This line tells the whole story: "PZEM Exception: No communication with the instrument (no answer)" Maybe i can add some settings to modify timeout and retry count.

but it mainly provides only the amper data

If no answer, there were no values, for sure.

enesbcs commented 4 years ago

Added a new "Increase timeout for slow PZEM004 compatibility" checkbox at commit https://github.com/enesbcs/rpieasy/commit/3d7b64f996e9a9e121fbc3afee2f9b651df1c5b4 This will setup 3 seconds timeout - as in your example - and 3 retry count if no result at read. I hope it solves the problem. RS485 PZEM016 has no problem with 0.1s timeout, it is fast.

enesbcs commented 4 years ago

I sent the task to rpieasy@altmails.com

I've received it, and works OK on my Raspberry PI Zero W. I saw that almost all task slots (47) are used in your config which is amazing, never saw similar before.

Be advised that PZEM004 is a relatively slow device, 1 data read / second is the most what you can get. So if you have 6 tasks which reads the same RS232 device you can not use Interval:1 second in any of your tasks, it will block communication line from the other tasks. (as your Amper device)

I need the system to detect amperes and watts equally

Solutions:

  1. Do not use lower intervals than 10seconds in your Tasks
  2. Do not use more tasks for the same device
  3. Buy a PZEM016 which is faster
Epik77 commented 4 years ago

I created several tasks because so I can send them to the controller in separate domoticz devices

I applied the patch, the situation is better. however, the problem remains that consumption watts it is not aligned with amps.

The script I passed you in the first answer gives me all the updated values in a single query

Loading rules... 17:25:48: Unit alive: 2 17:25:59: PZEM initialized at: /dev/ttyUSB0 / 1 BLE error: Device disconnected 17:26:01: Event: MiBandLorenzo#Online=0 17:26:01: BLE scan ended 17:26:01: Event: Clock#Time=Wed,17:26 17:26:02: Event: TemperaturaDevil03#Temp=42.2 17:26:03: Event: Pzem#Volt=234.6 17:26:04: Event: CPU#Load=65.8 17:26:04: PZEM initialized at: /dev/ttyUSB0 / 1 17:26:04: Event: Pzem#Amper=4.2 17:26:05: Event: Ampere#Amper=4.1 17:26:06: Event: IphoneEnzoPing#State=0 17:26:09: Event: IphoneMaryPing#State=0 17:26:10: Event: Ampere#Amper=4.1 17:26:14: Event: Ampere#Amper=4.0 17:26:19: Event: Ampere#Amper=3.8 17:26:23: Event: Ampere#Amper=3.8 17:26:27: Event: Ampere#Amper=3.8 17:26:31: PZEM initialized at: /dev/ttyUSB0 / 1 17:26:32: Event: Pzem#Amper=3.9 17:26:34: Event: Ampere#Amper=3.9 17:26:39: Event: Ampere#Amper=4.0 17:26:43: Event: Ampere#Amper=3.7 17:26:45: Event: Pzem#Amper=3.7 17:26:47: PZEM initialized at: /dev/ttyUSB0 / 1 17:26:49: Event: Pzem#Wh=181810.0 17:26:49: Event: Ampere#Amper=3.8 17:26:53: Event: Ampere#Amper=3.8 17:26:57: Event: IphoneLorenzoPing#State=0 17:26:57: Event: LettoreNFC#State=1 17:26:57: Parsed condition: if 1 == 0 False 17:26:57: Parsed condition: if 1 == 1 True 17:26:57: CMD: gpio,13,1 17:26:57: BCM13 set to 1 17:26:57: Event: NFC#State=1 17:26:57: Event: Ampere#Amper=4.0 17:27:00: PZEM initialized at: /dev/ttyUSB0 / 1 17:27:01: Event: Clock#Time=Wed,17:27 17:27:03: Event: TemperaturaDevil03#Temp=42.8 17:27:06: Event: CPU#Load=39.6 17:27:06: Event: FattorePotenza#CosF=1.0 17:27:07: BLE scan started 17:27:07: Event: Ampere#Amper=3.8 17:27:08: PZEM initialized at: /dev/ttyUSB0 / 1 17:27:10: Event: IphoneEnzoPing#State=0 17:27:18: Unit alive: 2 17:27:37: PZEM initialized at: /dev/ttyUSB0 / 1 17:27:42: PZEM initialized at: /dev/ttyUSB0 / 1 17:27:48: Unit alive: 2 BLE error: Device disconnected 17:28:07: BLE scan ended 17:28:07: Event: Clock#Time=Wed,17:28 17:28:08: BLE connection initiated to a4:c1:38:23:2a:bd 17:28:08: Event: TemperaturaDevil03#Temp=42.8 17:28:09: Event: Pzem#Amper=3.6 17:28:10: Event: CPU#Load=63.8 17:28:10: Event: IphoneRosyPing#State=0 17:28:10: Event: Ampere#Amper=3.6 17:28:12: Event: Consumo#Wh=181830.0 17:28:15: Event: IphoneMaryPing#State=0 17:28:16: Event: Ampere#Amper=3.5 17:28:18: Unit alive: 2 17:28:19: Event: IphoneEnzoPing#State=0 17:28:20: BLE connected to a4:c1:38:23:2a:bd 17:28:23: Event: Temperatura_Bagno#Temperature=22.1 17:28:23: Event: Temperatura_Bagno#Humidity=84.0 17:28:25: Event: Ampere#Amper=3.6 17:28:32: Event: Ampere#Amper=3.5 17:28:37: PZEM initialized at: /dev/ttyUSB0 / 1 17:28:37: Event: Ampere#Amper=3.6 17:28:43: PZEM initialized at: /dev/ttyUSB0 / 1 17:28:44: Event: Ampere#Amper=3.8 17:28:51: Event: Ampere#Amper=4.0 17:28:57: Event: Ampere#Amper=4.0 17:28:59: Event: Energia#Watt=878.8 17:29:00: Event: Clock#Time=Wed,17:29 17:29:04: Event: Ampere#Amper=3.9 17:29:09: Event: TemperaturaDevil03#Temp=43.3 17:29:11: Event: Pzem#Volt=233.0 17:29:11: Event: CPU#Load=20.0 17:29:11: Event: Pzem#Amper=3.9 17:29:13: Event: Ampere#Amper=3.9 17:29:14: !DHT read failed, using cached value! 17:29:14: BLE scan started 17:29:19: PZEM initialized at: /dev/ttyUSB0 / 1 17:29:34: PZEM initialized at: /dev/ttyUSB0 / 1 17:29:37: Unit alive: 2 17:30:07: Unit alive: 2 17:30:11: PZEM initialized at: /dev/ttyUSB0 / 1 BLE error: Device disconnected 17:30:15: BLE scan ended 17:30:15: Event: Clock#Time=Wed,17:30 17:30:16: Event: TemperaturaDevil03#Temp=42.8 17:30:17: Event: Ampere#Amper=4.0 17:30:17: PZEM initialized at: /dev/ttyUSB0 / 1 17:30:17: Event: CPU#Load=25.0 17:30:19: Event: IphoneEnzoPing#State=0 17:30:19: Event: IphoneMaryPing#State=0 17:30:21: Event: Energia#Watt=895.3 17:30:23: Event: Ampere#Amper=4.1 17:30:29: Event: Ampere#Amper=4.1 17:30:35: Event: Ampere#Amper=4.0 17:30:42: Event: Ampere#Amper=4.0 17:30:48: Event: Ampere#Amper=4.0 17:30:54: !DHT read failed, using cached value! 17:30:56: Event: Ampere#Amper=4.1 17:31:01: Event: Clock#Time=Wed,17:31 17:31:02: Event: Ampere#Amper=4.0 17:31:09: Event: Ampere#Amper=3.9 17:31:13: Event: IphoneRosyPing#State=0 17:31:15: BLE connection initiated to 4c:65:a8:dc:01:54 17:31:16: Event: Ampere#Amper=4.2 17:31:17: Event: TemperaturaDevil03#Temp=42.8 17:31:19: Event: CPU#Load=14.7 17:31:23: Event: IphoneEnzoPing#State=0 17:31:25: Event: Ampere#Amper=3.9 17:31:26: !BLE connection failed 4c:65:a8:dc:01:54 17:31:26: BLE connection initiated to 4c:65:a8:dc:01:54 17:31:30: BLE connected to 4c:65:a8:dc:01:54 17:31:30: Event: Temperatura_disimpegno#Temperature=25.4 17:31:30: Event: Temperatura_disimpegno#Humidity=62.5 17:31:31: Event: Temperatura_disimpegno#Battery=69.0 17:31:31: BLE scan started 17:31:31: Event: Ampere#Amper=3.9 17:31:38: Unit alive: 2 17:32:08: Unit alive: 2 BLE error: Device disconnected 17:32:31: BLE scan ended 17:32:31: Event: Clock#Time=Wed,17:32 17:32:32: Event: IphoneLorenzoPing#State=0 17:32:32: Event: LettoreNFC#State=1 17:32:32: Parsed condition: if 1 == 0 False 17:32:32: Parsed condition: if 1 == 1 True 17:32:32: CMD: gpio,13,1 17:32:32: Event: TemperaturaDevil03#Temp=42.8 17:32:32: BCM13 set to 1 17:32:33: Event: NFC#State=1 17:32:33: Event: Faradiba-umidita#percentuale=None 17:32:33: Event: Faradiba-Batteria#percentuale=99 17:32:34: Event: CPU#Load=113.0 17:32:35: Event: Ampere#Amper=4.0 17:32:35: Event: IphoneEnzoPing#State=0 17:32:37: Event: Faradiba-Luminosita#Lux=71 17:32:39: Event: IphoneMaryPing#State=0 17:32:40: Event: Ampere#Amper=3.9 17:32:47: Event: Ampere#Amper=3.8 17:32:52: Event: Ampere#Amper=4.2 17:32:59: Event: Ampere#Amper=3.8 17:33:00: Event: Clock#Time=Wed,17:33 17:33:05: Event: Ampere#Amper=3.9 17:33:12: Event: Ampere#Amper=3.9 17:33:19: Event: Ampere#Amper=4.2 17:33:25: Event: Ampere#Amper=4.3 17:33:32: Event: Ampere#Amper=4.4 17:33:35: Event: TemperaturaDevil03#Temp=42.8 17:33:35: Event: CPU#Load=31.2 17:33:36: Event: Consumo#Wh=181910.0 17:33:37: BLE scan started 17:33:39: Unit alive: 2 17:33:40: Event: IphoneEnzoPing#State=0 17:34:09: Unit alive: 2 BLE error: Device disconnected 17:34:37: BLE scan ended 17:34:37: Event: Clock#Time=Wed,17:34 17:34:38: BLE connection initiated to a4:c1:38:23:2a:bd 17:34:39: !DHT read failed, using cached value! 17:34:39: Event: TemperaturaDevil03#Temp=43.3 17:34:40: Event: CPU#Load=44.3 17:34:40: Event: IphoneRosyPing#State=0 17:34:41: Event: Ampere#Amper=4.3 17:34:42: Event: IphoneMaryPing#State=0 17:34:45: Event: IphoneEnzoPing#State=0 17:34:48: Event: Ampere#Amper=4.4 17:34:50: Unit alive: 2 17:34:55: Event: Ampere#Amper=4.5 Failed to connect to peripheral a4:c1:38:23:2a:bd, addr type: public 17:34:56: BLE connection failed a4:c1:38:23:2a:bd 17:34:58: BLE connection initiated to a4:c1:38:23:2a:bd 17:35:00: Event: Clock#Time=Wed,17:35 17:35:01: Event: Ampere#Amper=4.6 17:35:04: BLE connected to a4:c1:38:23:2a:bd 17:35:08: Event: Temperatura_Bagno#Temperature=22.1 17:35:08: Event: Temperatura_Bagno#Humidity=84.0 17:35:08: Event: Ampere#Amper=4.4 17:35:15: Event: Ampere#Amper=4.4 17:35:21: Unit alive: 2 17:35:21: Event: Ampere#Amper=4.4 17:35:28: Event: Ampere#Amper=4.5 17:35:33: Event: Energia#Watt=1040.5 17:35:34: Event: Ampere#Amper=4.4 17:35:41: Event: TemperaturaDevil03#Temp=42.8 17:35:41: Event: CPU#Load=20.5 17:35:41: Event: Consumo#Wh=181945.0 17:35:42: Event: Ampere#Amper=4.1 17:35:43: BLE scan started 17:35:43: Event: FattorePotenza#CosF=1.0 BLE error: Device disconnected 17:36:43: BLE scan ended 17:36:43: Event: Clock#Time=Wed,17:36 17:36:44: Event: TemperaturaDevil03#Temp=42.8 17:36:46: Event: Ampere#Amper=4.1 17:36:46: Event: CPU#Load=25.6 17:36:46: Event: Consumo#Wh=181963.0 17:36:47: Event: IphoneEnzoPing#State=0 17:36:48: Event: IphoneMaryPing#State=0 17:36:50: Unit alive: 2 17:36:57: Event: Faradiba-Fertilizzante#Us=120 17:37:03: Event: Faradiba-Temperatura#Gradi=24.9 17:37:04: Event: Clock#Time=Wed,17:37 17:37:11: Event: Ampere#Amper=4.1 17:37:18: Event: Ampere#Amper=4.1 17:37:21: Unit alive: 2 17:37:24: Event: Ampere#Amper=4.0 17:37:31: Event: Ampere#Amper=4.1 17:37:34: Event: Temperatura_taverna#Temperature=24.0 17:37:34: Event: Temperatura_taverna#Humidity=64.0 17:37:34: Event: IphoneLorenzoPing#State=0 17:37:34: Event: LettoreNFC#State=1 17:37:34: Parsed condition: if 1 == 0 False 17:37:34: Parsed condition: if 1 == 1 True 17:37:34: CMD: gpio,13,1 17:37:34: BCM13 set to 1 17:37:34: Event: NFC#State=1 17:37:37: Event: Ampere#Amper=3.9 17:37:43: Event: IphoneRosyPing#State=0 17:37:44: Event: Ampere#Amper=4.3 17:37:45: BLE connection initiated to 4c:65:a8:dc:01:54 17:37:45: Event: TemperaturaDevil03#Temp=42.8 17:37:48: Event: CPU#Load=45.2 17:37:52: Event: IphoneEnzoPing#State=0 17:37:54: Event: Ampere#Amper=4.0 17:37:56: !BLE connection failed 4c:65:a8:dc:01:54 17:37:57: BLE connection initiated to 4c:65:a8:dc:01:54 17:38:00: Event: Ampere#Amper=4.2 17:38:00: Event: Clock#Time=Wed,17:38 17:38:06: Event: Ampere#Amper=4.1 17:38:12: !BLE connection failed 4c:65:a8:dc:01:54 17:38:13: BLE connection initiated to 4c:65:a8:dc:01:54 17:38:13: Event: Ampere#Amper=4.2 17:38:18: BLE connected to 4c:65:a8:dc:01:54 17:38:19: Event: Ampere#Amper=4.4 17:38:21: Event: Temperatura_disimpegno#Temperature=25.3 17:38:21: Event: Temperatura_disimpegno#Humidity=62.0 17:38:21: Event: Temperatura_disimpegno#Battery=69.0 17:38:25: Event: IphoneMaryPing#State=0 17:38:26: BLE scan started 17:38:26: Event: Ampere#Amper=4.2 17:38:51: Unit alive: 2 17:39:22: Unit alive: 2 BLE error: Device disconnected 17:39:26: BLE scan ended 17:39:26: Event: Clock#Time=Wed,17:39 17:39:28: Event: TemperaturaDevil03#Temp=42.8 17:39:29: Event: CPU#Load=45.9 17:39:30: Event: Ampere#Amper=4.3 17:39:31: Event: IphoneEnzoPing#State=0 17:39:36: Event: Ampere#Amper=4.2 17:39:40: !DHT read failed, using cached value! 17:39:42: Event: Ampere#Amper=4.1 17:39:54: Event: Ampere#Amper=4.1

enesbcs commented 4 years ago

I see. Honestly this plugin was never ment to be used with PZEM004, it is made for PZEM016 and it works well with it.

I've opened a new issue for a new plugin, which may be added someday, if i see a cheap pzem004 for testing. https://github.com/enesbcs/rpieasy/issues/158