Connect via local USB

[RWeers]

Is it possible to add the functionality that a local USB -> Rs485 can be used on the raspberry pi?

[mvdklip]

Hi RWeers, this is quite possible. I have this functionality on a different plugin for Domoticz so I'll have a look if I can borrow and adapt the code.

[mvdklip]

@RWeers just did an internal test version of this and I noticed I kinda have to hardcode the serial communication parameters to 38400 8N1. Would this work for you or would you require being able to change the serial communication parameters? If so I would need to invent a way to pass these parameters into the plugin.

To be clear: this internal test version allows you to specify a serial device (eg /dev/ttyUSB0) but does not allow you to specify the baud rate, parity and stop bits.

[janvdpol]

Looking for the same solution as OP. I have a waveshare USB to RS485 plugged into my raspberry.

If I could specify indeeed /dev/ttyUSB0 somewhere I do not mind the hardcoded communication parameters.

It would be very nice to be able to specify those params also off course. I see in the code that you did not use Mode1 yet. So maybe you could use that for Baudrate in combination with a list of possibilites like:

• 9600–8-N-1
• 38400-8-N-1
• etc.

[janvdpol]

I have made an attempt to add this functionality. See my version of plugin.py for my attempt.

I guess I have done something wrong, since the SerialPort and Mode1 property are not showing after updating this file. It's my first experience with developing a domoticz plugin, so could be my little knowledge of that. You're feedback is greatly appreciated. You are also welcome to incorporate this (not yet working) code into your own development.

[janvdpol]

Ok. Managed to get something syntax error free. But running into runtime issues now:

2024-01-07 20:29:30.035 Status: Hewalex PCWU 3.0 KW: Started. 2024-01-07 20:29:30.035 Status: Hewalex PCWU 3.0 KW: Entering work loop. 2024-01-07 20:29:30.237 Status: Hewalex PCWU 3.0 KW: Initialized version 0.8.0, author 'mvdklip' 2024-01-07 20:29:30.264 Hewalex PCWU 3.0 KW: Debug logging mask set to: PYTHON PLUGIN QUEUE IMAGE DEVICE CONNECTION MESSAGE ALL 2024-01-07 20:29:30.264 Hewalex PCWU 3.0 KW: Serial config is set to baudrate: 38400, bytesize: 8, parity: N, stopbits: 1 2024-01-07 20:29:30.265 Hewalex PCWU 3.0 KW: Controller Ids set to 5, 5 2024-01-07 20:29:30.265 Hewalex PCWU 3.0 KW: Device Ids set to 2, 2 2024-01-07 20:29:30.265 Hewalex PCWU 3.0 KW: 'HardwareID':'11' 2024-01-07 20:29:30.266 Hewalex PCWU 3.0 KW: 'HomeFolder':'/opt/domoticz/userdata/plugins/Domoticz-Hewalex/' 2024-01-07 20:29:30.266 Hewalex PCWU 3.0 KW: 'StartupFolder':'/opt/domoticz/' 2024-01-07 20:29:30.266 Hewalex PCWU 3.0 KW: 'UserDataFolder':'/opt/domoticz/userdata/' 2024-01-07 20:29:30.266 Hewalex PCWU 3.0 KW: 'Database':'/opt/domoticz/userdata/domoticz.db' 2024-01-07 20:29:30.266 Hewalex PCWU 3.0 KW: 'Language':'en' 2024-01-07 20:29:30.267 Hewalex PCWU 3.0 KW: 'Version':'0.8.0' 2024-01-07 20:29:30.267 Hewalex PCWU 3.0 KW: 'Author':'mvdklip' 2024-01-07 20:29:30.267 Hewalex PCWU 3.0 KW: 'Name':'Hewalex PCWU 3.0 KW' 2024-01-07 20:29:30.267 Hewalex PCWU 3.0 KW: 'Port':'8899' 2024-01-07 20:29:30.267 Hewalex PCWU 3.0 KW: 'SerialPort':'/dev/ttyUSB0' 2024-01-07 20:29:30.268 Hewalex PCWU 3.0 KW: 'Key':'Hewalex' 2024-01-07 20:29:30.268 Hewalex PCWU 3.0 KW: 'Mode1':'384096' 2024-01-07 20:29:30.268 Hewalex PCWU 3.0 KW: 'Mode2':'1' 2024-01-07 20:29:30.268 Hewalex PCWU 3.0 KW: 'Mode3':'6' 2024-01-07 20:29:30.268 Hewalex PCWU 3.0 KW: 'Mode4':'5,5;2,2' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: 'Mode5':'Disabled' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: 'Mode6':'Debug' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: 'DomoticzVersion':'2024.1' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: 'DomoticzHash':'5279c8261' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: 'DomoticzBuildTime':'2024-01-01 12:59:22' 2024-01-07 20:29:30.269 Hewalex PCWU 3.0 KW: Device count: 16 2024-01-07 20:29:30.270 Hewalex PCWU 3.0 KW: Device: 1 - ID: 861, Name: 'Hewalex PCWU 3.0 KW - T1 (ambient)', nValue: 0, sValue: '' 2024-01-07 20:29:30.270 Hewalex PCWU 3.0 KW: Device ID: '861' 2024-01-07 20:29:30.270 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T1 (ambient)' 2024-01-07 20:29:30.270 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.271 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.271 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.271 Hewalex PCWU 3.0 KW: Device: 2 - ID: 862, Name: 'Hewalex PCWU 3.0 KW - T2 (tank bottom)', nValue: 0, sValue: '' 2024-01-07 20:29:30.271 Hewalex PCWU 3.0 KW: Device ID: '862' 2024-01-07 20:29:30.271 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T2 (tank bottom)' 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device: 3 - ID: 863, Name: 'Hewalex PCWU 3.0 KW - T3 (tank top)', nValue: 0, sValue: '' 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device ID: '863' 2024-01-07 20:29:30.272 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T3 (tank top)' 2024-01-07 20:29:30.273 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.273 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.273 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.273 Hewalex PCWU 3.0 KW: Device: 4 - ID: 872, Name: 'Hewalex PCWU 3.0 KW - Heatpump Enabled', nValue: 0, sValue: '' 2024-01-07 20:29:30.273 Hewalex PCWU 3.0 KW: Device ID: '872' 2024-01-07 20:29:30.274 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - Heatpump Enabled' 2024-01-07 20:29:30.274 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.274 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.274 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.274 Hewalex PCWU 3.0 KW: Device: 5 - ID: 871, Name: 'Hewalex PCWU 3.0 KW - Tap Water Temp', nValue: 0, sValue: '' 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device ID: '871' 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - Tap Water Temp' 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.275 Hewalex PCWU 3.0 KW: Device: 6 - ID: 864, Name: 'Hewalex PCWU 3.0 KW - T4 (solid fuel boiler)', nValue: 0, sValue: '' 2024-01-07 20:29:30.276 Hewalex PCWU 3.0 KW: Device ID: '864' 2024-01-07 20:29:30.276 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T4 (solid fuel boiler)' 2024-01-07 20:29:30.276 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.276 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.276 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device: 7 - ID: 865, Name: 'Hewalex PCWU 3.0 KW - T5 (void)', nValue: 0, sValue: '' 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device ID: '865' 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T5 (void)' 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.277 Hewalex PCWU 3.0 KW: Device: 8 - ID: 866, Name: 'Hewalex PCWU 3.0 KW - T6 (water inlet)', nValue: 0, sValue: '' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device ID: '866' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T6 (water inlet)' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device: 9 - ID: 867, Name: 'Hewalex PCWU 3.0 KW - T7 (water outlet)', nValue: 0, sValue: '' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device ID: '867' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T7 (water outlet)' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.278 Hewalex PCWU 3.0 KW: Device: 10 - ID: 868, Name: 'Hewalex PCWU 3.0 KW - T8 (evaporator)', nValue: 0, sValue: '' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device ID: '868' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T8 (evaporator)' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device: 11 - ID: 869, Name: 'Hewalex PCWU 3.0 KW - T9 (before compressor)', nValue: 0, sValue: '' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device ID: '869' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T9 (before compressor)' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.279 Hewalex PCWU 3.0 KW: Device: 12 - ID: 870, Name: 'Hewalex PCWU 3.0 KW - T10 (after compressor)', nValue: 0, sValue: '' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device ID: '870' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - T10 (after compressor)' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device: 25 - ID: 873, Name: 'Hewalex PCWU 3.0 KW - CompressorON - Count', nValue: 0, sValue: '' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device ID: '873' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - CompressorON - Count' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.280 Hewalex PCWU 3.0 KW: Device: 26 - ID: 874, Name: 'Hewalex PCWU 3.0 KW - CompressorON - Time', nValue: 0, sValue: '' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device ID: '874' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - CompressorON - Time' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device: 27 - ID: 875, Name: 'Hewalex PCWU 3.0 KW - EV1', nValue: 0, sValue: '' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device ID: '875' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - EV1' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device: 28 - ID: 876, Name: 'Hewalex PCWU 3.0 KW - Delta T', nValue: 0, sValue: '' 2024-01-07 20:29:30.281 Hewalex PCWU 3.0 KW: Device ID: '876' 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Device Name: 'Hewalex PCWU 3.0 KW - Delta T' 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Device nValue: 0 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Device sValue: '' 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Device LastLevel: 0 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Pushing 'PollIntervalDirective' on to queue 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Acquiring GIL for 'onStartCallback' 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Processing 'PollIntervalDirective' message 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Acquiring GIL for 'PollIntervalDirective' 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Heartbeat interval set to: 5. 2024-01-07 20:29:30.282 Hewalex PCWU 3.0 KW: Acquiring GIL for 'PollIntervalDirective' 2024-01-07 20:29:35.042 Hewalex PCWU 3.0 KW: Pushing 'onHeartbeatCallback' on to queue 2024-01-07 20:29:35.093 Hewalex PCWU 3.0 KW: Processing 'onHeartbeatCallback' message 2024-01-07 20:29:35.093 Hewalex PCWU 3.0 KW: Acquiring GIL for 'onHeartbeatCallback' 2024-01-07 20:29:35.093 Hewalex PCWU 3.0 KW: Calling message handler 'onHeartbeat' on 'module' type object. 2024-01-07 20:29:35.093 Hewalex PCWU 3.0 KW: onHeartbeat called 0 2024-01-07 20:29:35.093 Hewalex PCWU 3.0 KW: Serial config is set to baudrate: 38400, bytesize: 8, parity: N, stopbits: 1 2024-01-07 20:29:37.128 Hewalex PCWU 3.0 KW: Exception from /dev/ttyUSB0; Invalid soft message len 2024-01-07 20:29:37.130 Hewalex PCWU 3.0 KW: Previous attempt failed, trying again... 2024-01-07 20:29:37.130 Hewalex PCWU 3.0 KW: Serial config is set to baudrate: 38400, bytesize: 8, parity: N, stopbits: 1 2024-01-07 20:29:38.537 Hewalex PCWU 3.0 KW: Exception from /dev/ttyUSB0; Invalid soft message len 2024-01-07 20:29:38.539 Hewalex PCWU 3.0 KW: Previous attempt failed, trying again... 2024-01-07 20:29:38.539 Hewalex PCWU 3.0 KW: Serial config is set to baudrate: 38400, bytesize: 8, parity: N, stopbits: 1

Any idea how to fix this? FYI I have added a 3 wire to the connector of LAN modem (A, B and GND) to my Waveshare RS485 to USB device.

[mvdklip]

Hi Jan,

Thanks for your suggestions wrt encoding the serial parameters. I will have a look later as I'm quite busy at the moment. I'm actually selling the house with Hewalex equipment in it pretty soon so that will also mean I will no longer have access to it.

That invalid soft message len error could mean two things IMO:

1) There's corruption on the serial line because of unshielded, unterminated connections. 2) You are trying to use a piece of hardware with a slightly different version of the protocol.

What kind of hardware with which software version are you trying to communicate with?

[janvdpol]

This is the hardware that I have: https://www.waveshare.com/usb-to-rs485.htm

How I have connected things is as follows:

PWCU GECO MODEM RS485 to USB |__________________|_______________________|

On the GECO MODEM I have extended the wires (A, B and GND) to the RS485 side. Should there be done something more?

[janvdpol]

Ooops. My mistake. I switched A and B in the wiring. Fixed it and with Direct comms I have now the temperatures.

[janvdpol]

Pull request to merge it back into your code base: https://github.com/mvdklip/Domoticz-Hewalex/pull/5

I'm unable to check whether it still works with IP device. Maybe you can do that before selling the house.

[mvdklip]

Hi Jan,

If I understand correctly you have extended the wires of the GECO control unit to the waveshare RS485 device. You are mentioning the word "modem" but I guess you just mean the normal GECO display which was delivered with the PCWU. In this setup you should not run the plugin in direct comms mode actually because that would mean that two devices (the GECO and Domoticz) are setup as a master on a single RS485 connection. That will give conflicts. So you need to either use eavesdropping mode or move the Waveshare to the internal second RS485 connection for it to work properly.

I will have a look at you suggestions for using Mode1 for the serial parameters. I think I can come up with a working version before leaving the Hewalex behind.

[janvdpol]

Hi Matthijs,

Thanks for your effort on this project and helping me in particular. I meant EKO-LAN Modem which is connected to the internal second RS485. Therefore it works on Direct comms. I get some errors like: Error: Hewalex PCWU 3.0 KW: Failed to retrieve data from None, cancelling... But this is only occasionally (4 times in last 5 minutes, with updates every 15 sec.). Most likely when it tries to do communication at the same time as the EKO-LAN Modem.

Best regards,

Jan

[mvdklip]

Hi Jan,

I was kind of afraid of that already. Please understand that a minor error during some reads of data is pretty harmless but if both devices try to write at the same time this could lead to data corruption and overwriting undocumented registers in the PCWU which in turn can lead to physical damage of the unit. So please do change the setup if you want to make sure that everything keeps working. Unfortunately there is no third RS485 port so there is no way you can have three master (write capable) devices active at the same time.

Greets,

Matthijs

On Tue, 9 Jan 2024, 20:57 janvdpol, @.***> wrote:

Hi Matthijs,

Thanks for your effort on this project and helping me in particular. I meant EKO-LAN Modem https://dawi.eu/product/hewalex-ekontrol-eko-lan-modem/ which is connected to the internal second RS485. Therefore it works on Direct comms. I get some errors like: Error: Hewalex PCWU 3.0 KW: Failed to retrieve data from None, cancelling... But this is only occasionally (4 times in last 5 minutes, with updates every 15 sec.). Most likely when it tries to do communication at the same time as the EKO-LAN Modem.

Best regards,

Jan

— Reply to this email directly, view it on GitHub https://github.com/mvdklip/Domoticz-Hewalex/issues/4#issuecomment-1883691412, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABQ47QJZ2W5AIW5F5G6A2TYNWOI7AVCNFSM6AAAAAA7FEOTZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTGY4TCNBRGI . You are receiving this because you commented.Message ID: @.***>

[janvdpol]

Hi Matthijs,

Thanks for the heads up on this. I studied the protocol a little and found out there were two CRC's involved, so I assumed that when those CRC's were not correct, the whole message would be ignored. I will change it though to the first RS485 port and use eaves dropping.

Best regards,

Jan

[mvdklip]

Hi Jan, just released version 0.8.0 which uses Mode1 just like your PR. The code is quite different though.

[mvdklip]

@janvdpol Would be great if you let me know whether version 0.8.0 actually works. I have no RS485 over USB devices laying around currently so tested it only up until a certain point.

[RWeers]

Is it also possible to read all the temperatures instead of the first three?

Op wo 10 jan. 2024 13:08 schreef Matthijs van der Klip < @.***>:

Hi Jan, just released version 0.8.0 which uses Mode1 just like your PR. The code is quite different though.

— Reply to this email directly, view it on GitHub https://github.com/mvdklip/Domoticz-Hewalex/issues/4#issuecomment-1884728964, or unsubscribe https://github.com/notifications/unsubscribe-auth/BD3MB3OG5LCLRMDHCSE4SSLYN2AE3AVCNFSM6AAAAAA7FEOTZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBUG4ZDQOJWGQ . You are receiving this because you were mentioned.Message ID: @.***>

[mvdklip]

@RWeers could you open a separate issue for your question? And please describe it a bit better because right now I don't really understand what you mean. Don't forget to mention whether you're talking PCWU or ZPS too.