NEO Coolcam NAS-WR01ZE Z-wave EU Smart Power Plug Socket

Hehe, I’m in bed in Yorkshire as I type!


Sent from my iPhone using Tapatalk Pro

Peter,

I have been looking around the web and not finding much but a few things I noticed are the plug is supposed to give Voltage and Current but all Indigo can see is Watts and kWh. I also found a bit of 'code' from the Homey site.

This Plug provides line voltage, current load, power consumption and energy
consumption measuring. 
Voltage – The Supply Power Voltage For Plug.
Current – The Current for the Electric Device Connect to Plug Consumption.
Power – Power Consumed by an Electric Device in an instant, unit: Watt (W).
Energy – Energy Consumed by an Electric Device through a Time Period. Most
commonly measured in Kilowatt-hours (kWh). One kilowatt-hour is Equal to One
Kilowatt of Power Consumed over a Period of One Hour, 1kWh = 1000Wh.0Wh.

https://github.com/mruiter/com.neo/blob/7e46998825a4a3a34cd120488f7932d4276bb7ea/node_modules/homey-zwavedriver/README.md

const ZwaveDriver = require('homey-zwavedriver');

module.exports = new ZwaveDriver('mydriver', {
debug: false, // set to true to view all incoming events
capabilities: {
'onoff': {
'command_class' : 'COMMAND_CLASS_SWITCH_BINARY',
'command_get' : 'SWITCH_BINARY_GET',
'command_set' : 'SWITCH_BINARY_SET',
'command_set_parser' : function( value ){
return {
'Switch Value': value
}
},
'command_report' : 'SWITCH_BINARY_REPORT',
'command_report_parser' : function( report ){
return report['Value'] === 'on/enable';
}
},
'measure_power': {
'command_class' : 'COMMAND_CLASS_SENSOR_MULTILEVEL',
'command_get' : 'SENSOR_MULTILEVEL_GET',
'command_report' : 'SENSOR_MULTILEVEL_REPORT',
'command_report_parser' : function( report ){
return report['Sensor Value (Parsed)'];
}

And also this below that mentions Endpoints (and I know you love Endpoints ) and it is formatted better at

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/397

Association Groups
Group ID 1
Label Group 1
Description is assigned to Plugs status - On/Off. Allows for receiving control command from trigger devices whenever the Plug is turned On or Off.
Maximum Nodes 1
Controller Yes
Overview NOTIFICATION_REPORT_V4
METER_REPORT_V4
SWITCH_BINARY_REPORT
DEVICE_RESET_LOCALLY_NOTIFICATION
Group ID 2
Label Group 2
Description Sending control commands to associated devices. If current load is over the max current defined in parameter #3, the Plug will send a BASIC_SET (0xFF) to associated devices. When current load is normal, plug will send a BASIC_SET (0x00).
Maximum Nodes 5
Controller No
Overview BASIC_SET
Group ID 3
Label Group 3
Description Send Notification to associated devices.
Maximum Nodes 5
Controller No
Overview NOTIFICATION_REPORT_V4
Endpoints
Endpoint Name Endpoint 0
Endpoint Number 0
Basic Class BASIC_TYPE_ROUTING_SLAVE
Generic Class GENERIC_TYPE_SWITCH_BINARY
Specific Class SPECIFIC_TYPE_POWER_SWITCH_BINARY
Command Classes
Class Ver Basic NIF Sec UnSec
NO_OPERATION 1
BASIC 1
SWITCH_BINARY 1
Switch
SWITCH_ALL 1
METER 3
Electric meter (amps)
Electric meter (kWh)
Electric meter (watts)
Electric meter (volts)
ASSOCIATION_GROUP_INFO 1
DEVICE_RESET_LOCALLY 1
ZWAVE_PLUS_INFO 1
CONFIGURATION 1
ALARM 3
Alarm (power)
MANUFACTURER_SPECIFIC 1
POWERLEVEL 1
ASSOCIATION 1
VERSION 1

Yeah, I noticed it gives v and a but nobody’s asked for it so I didn’t add it; the code is only 2 more lines each to do so.

I’m already using the endpoints to get all the values.


Sent from my iPhone using Tapatalk Pro

I got the same problem as all of the others in this topic.

24. okt. 2017, 20:02:16
Z-Wave sent "Stue og kjøkken - Lys Mamma" off
Z-Wave sent "Stue og kjøkken - Lys Mamma" on
Z-Wave sent "Stue og kjøkken - Lys Mamma" status request
Z-Wave sent "Stue og kjøkken - Lys Mamma" energy status request
Z-Wave received "Stue og kjøkken - Lys Mamma" energy total to 0.00 kWh
Z-Wave received "Stue og kjøkken - Lys Mamma" energy total to 236.86 kWh
Z-Wave received "Stue og kjøkken - Lys Mamma" energy total to 0.00 kWh

Yeah, I noticed it gives v and a but nobody’s asked for it so I didn’t add it; the code is only 2 more lines each to do so.

I’m already using the endpoints to get all the values.


Sent from my iPhone using Tapatalk Pro

Peter,

Can I be the first to ask for Volts and Amps please

Updated and now error free
My settings are

1 = 1
2 = 300
3 =. 13
4 =. 12
5 =. 1
6 =. 5
7 =. 1
8 =. 0
9 =. 150
10 =. 1
11 =. 0
12 =. 1

How did you get it error free?

Updated and now error free

How did you get it error free?

Error free was referring to the updated power sensor plugin by @howartp but I have a reasonable readout now by
changing these settings

parameter 1 value: 0 (size 1)
parameter 2 value: 32767 (size 2)
parameter 6 value: 100 (size 1)

That turns off updates and then I have a trigger to fire when Device State Changed, Total Usage (kWh, Has any change which then Requests a Full Status Update so every time it jumps to 240kWh's it resets to the correct settings.

I also scheduled every 10 minutes to also do a Request Full Status Update but have turned that off.

It is not very pretty but it works, just wish I could find out how Domoticz gets Power, Voltage, Current all working fine but I just cannot get Domoticz to work with my Everspring SA413 Z-Wave Plus USB Adapter and find the whole software horrible.

was in contact with the Chinees supplier of NEO Coolcam.
They are not aware of any software bugs and the switch should work for the power monitoring.

3 out of 3 not working is not a "marginal". So who is right, INDIGO or NEO?

I think I may have worked out why the Neo Power Switch is giving weird updates, the problem is Indigo is interpreting the Voltage and Amperage readings as Watts and kWh.

It seems that the Neo is ‘very’ close to a Dome On/Off Plug-In Switch and Dome give a lot of details concerning the command classes.

The 240’ish readings we see overwriting the 'Total Usage' is actually the Voltage, which in the UK/Europe would be correct (240Vac) and explains why Domoticz gets all 4 outputs correct and Indigo does not.

From my logs

Z-Wave Sensor Logger Debug Raw command: 01 14 00 04 00 8B 0E 32 02 21 54 00 00 14 AE 00 1F 00 00 15 22 BD
Z-Wave Sensor Logger Debug Bitmask: 54, DP: 2, Scale: 2, ByteLength: 4
Z-Wave Sensor Logger Debug Power Reported: 52.94 w
Which is correct as 21 54 is Watts

Z-Wave Sensor Logger Debug Raw command: 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 2B 00 1F 00 00 00 2B 20
Z-Wave Sensor Logger Debug Bitmask: 44, DP: 2, Scale: 0, ByteLength: 4
Z-Wave Sensor Logger Debug Energy Reported: 0.43 kWh
Which is correct as 21 44 is kWh

Z-Wave Sensor Logger Debug Raw command: 01 10 00 04 00 8B 0A 32 02 A1 4A 00 20 00 1F 00 21 AF
Z-Wave Sensor Logger Debug Bitmask: 4A, DP: 2, Scale: 1, ByteLength: 2
Z-Wave Sensor Logger Debug Energy Reported: 0.32 kVAh
Which is incorrect as A1 4A is Amps

Z-Wave Sensor Logger Debug Raw command: 01 10 00 04 00 8B 0A 32 02 A1 42 5D 1C 03 18 5E 09 B4
Z-Wave Sensor Logger Debug Bitmask: 42, DP: 2, Scale: 0, ByteLength: 2
Z-Wave Sensor Logger Debug Energy Reported: 238.36 kWh
Which is incorrect as A1 42 is Volts and it is overwriting the 'Total Usage' which it should not and why we see the switching .

I’ll come back later and re-read this but all those are done with my plugin which intentionally doesn’t handle a or kva yet. (It’s ready to add, which is why I think I asked about it earlier on this thread but I don’t think I got a reply?)

I checked Indigo’s interpretation of your original values when I joined this thread and they all calculated correctly (w, kWh, whatever) at that point.



Sent from my iPhone using Tapatalk Pro

Yeah, I noticed it gives v and a but nobody’s asked for it so I didn’t add it; the code is only 2 more lines each to do so.

I’m already using the endpoints to get all the values.


Sent from my iPhone using Tapatalk Pro

Peter,

Can I be the first to ask for Volts and Amps please

I did ask and would love to see the additions and also the definition updated in a future release.

me too, I really would like to see the Volts and Amps

me too, I really would like to see the Volts and Amps

Especially in the Device Details in the GUI, Volts,Amps,Watts and kWh so hopefully when 7.1.1 arrives it will have the 'preliminary support' updated to show them.

Have a look at the Dome Docs page, 100% compatible to Neo (except Dome are US frequency only), full details for the Neo Door/Window Sensor, Neo Siren, Neo Motion Detector, Neo Leak Sensor and the Neo Power Plug.

https://docs.domeha.com/#dome-devices

I think I may have worked out why the Neo Power Switch is giving weird updates, the problem is Indigo is interpreting the Voltage and Amperage readings as Watts and kWh.

From my logs

Z-Wave Sensor Logger Debug Raw command: 01 14 00 04 00 8B 0E 32 02 21 54 00 00 14 AE 00 1F 00 00 15 22 BD
Z-Wave Sensor Logger Debug Bitmask: 54, DP: 2, Scale: 2, ByteLength: 4
Z-Wave Sensor Logger Debug Power Reported: 52.94 w
Which is correct as 21 54 is Watts

Z-Wave Sensor Logger Debug Raw command: 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 2B 00 1F 00 00 00 2B 20
Z-Wave Sensor Logger Debug Bitmask: 44, DP: 2, Scale: 0, ByteLength: 4
Z-Wave Sensor Logger Debug Energy Reported: 0.43 kWh
Which is correct as 21 44 is kWh

Z-Wave Sensor Logger Debug Raw command: 01 10 00 04 00 8B 0A 32 02 A1 4A 00 20 00 1F 00 21 AF
Z-Wave Sensor Logger Debug Bitmask: 4A, DP: 2, Scale: 1, ByteLength: 2
Z-Wave Sensor Logger Debug Energy Reported: 0.32 kVAh
Which is incorrect as A1 4A is Amps

Z-Wave Sensor Logger Debug Raw command: 01 10 00 04 00 8B 0A 32 02 A1 42 5D 1C 03 18 5E 09 B4
Z-Wave Sensor Logger Debug Bitmask: 42, DP: 2, Scale: 0, ByteLength: 2
Z-Wave Sensor Logger Debug Energy Reported: 238.36 kWh
Which is incorrect as A1 42 is Volts and it is overwriting the 'Total Usage' which it should not and why we see the switching .

Ah.

Yes, you're right - both myself and (I presume) Matt have been reading just the second of those bytes.

In earlier versions of the Meter class the "Scale" (which ZWave calls the Kwh, W, Amp... etc readings) only used the second byte. The first byte was essentially fixed at 21 for electric meters. In later versions of the Meter class (your device is v3 and v5 is most recent) they use both bytes to form the scale. If you ignore the first byte you can't possibly get V or A readings because there's not enough bits in the byte. To allow more scales they've allowed 21 to change to A1.

I'll fix my code tomorrow night - it needs redoing as it's only coded to one byte at the moment.

Matt, one for you to look at in next release?

Peter

Peter,

Just updated to v1.0.24 of the ZWave Sensor Logger and you have nailed it 100%.

I have modified it to output the log below. and it now gets Volts and Amps correctly were as Indigo will need updating in a future version to stop the Volts incorrectly updating the Total Usage and also to report Volts and Amps on a status request.

Well worth another 10 points for the Village Hall total from my other half

I did get one error with BBEdit and that was

Incorrectly formed UTF-8
The UTF-8 file “plugin.py” is damaged or incorrectly formed; please proceed with caution.

and it got upset with the Celsius and farenheight lines that have the inverted 7 character ( I know -- Don't play with the code !!)


5 Nov 2017, 11:45:27
Z-Wave sent "Motorhome Neo Charger Socket" on
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 71 00 25 00 00 00 71 1A
Z-Wave Sensor Logger Energy Reported: 1.13 kWh
Z-Wave Sensor Logger
Z-Wave received "Motorhome Neo Charger Socket" energy total to 238.30 kWh
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 10 00 04 00 8B 0A 32 02 A1 42 5D 16 00 25 5C CF 44
Z-Wave Sensor Logger Voltage Reported: 238.3 v
Z-Wave Sensor Logger
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 10 00 04 00 8B 0A 32 02 A1 4A 00 08 00 25 00 00 9C
Z-Wave Sensor Logger Current Reported: 0.08 a
Z-Wave Sensor Logger
Z-Wave received "Motorhome Neo Charger Socket" energy total to 1.13 kWh
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 71 00 25 00 00 00 71 1A
Z-Wave Sensor Logger Energy Reported: 1.13 kWh
Z-Wave Sensor Logger
Z-Wave received "Motorhome Neo Charger Socket" power load to 13.39 W
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 54 00 00 05 3B 00 25 00 00 00 00 34
Z-Wave Sensor Logger Power Reported: 13.39 w
Z-Wave Sensor Logger
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 71 00 08 00 00 00 71 37
Z-Wave Sensor Logger Energy Reported: 1.13 kWh
Z-Wave Sensor Logger
Z-Wave received "Motorhome Neo Charger Socket" power load to 104.33 W
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 54 00 00 28 C1 00 08 00 00 05 3B F0
Z-Wave Sensor Logger Power Reported: 104.33 w
Z-Wave Sensor Logger
Z-Wave received "Motorhome Neo Charger Socket" energy total to 237.43 kWh
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 10 00 04 00 8B 0A 32 02 A1 42 5C BF 00 08 5D 16 19
Z-Wave Sensor Logger Voltage Reported: 237.43 v
Z-Wave Sensor Logger
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 10 00 04 00 8B 0A 32 02 A1 4A 00 3D 00 08 00 08 8C
Z-Wave Sensor Logger Current Reported: 0.61 a
Z-Wave Sensor Logger

Z-Wave sent "Motorhome Neo Charger Socket" status request
Z-Wave sent "Motorhome Neo Charger Socket" energy status request
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 09 00 04 00 8B 03 25 03 FF A3
Z-Wave received "Motorhome Neo Charger Socket" energy total to 1.15 kWh
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 44 00 00 00 73 00 08 00 00 00 72 36
Z-Wave Sensor Logger Energy Reported: 1.15 kWh
Z-Wave Sensor Logger
Z-Wave Sensor Logger
Z-Wave Sensor Logger Raw command received (Node 139): 01 14 00 04 00 8B 0E 32 02 21 54 00 00 28 C1 00 08 00 00 05 3B F0
Z-Wave Sensor Logger Power Reported: 104.33 w
Z-Wave Sensor Logger

I did get one error with BBEdit and that was

Incorrectly formed UTF-8
The UTF-8 file “plugin.py” is damaged or incorrectly formed; please proceed with caution.

and it got upset with the Celsius and farenheight lines that have the inverted 7 character ( I know -- Don't play with the code !!)

Yeah, so did I which is why I took it back out until I worked out the correct way of doing it!

I also started changing what was logged/debugged but I stopped and waited to make sure it was working for you first.

Peter