Help for configure Smart Socket Neo Coolcam

Configuration Z-Wave
1

I’ve bought two of these smart sockets
http://www.gearbest.com/home-gadgets/pp_581312.html

I’ve included successfully in the ZWave network, but i’m not able to switch them on after switched off.
In HASS frontend I see the Neo Coolcam toggle undes Switches group, with on state.
If the socket is on, toggling the switch on HASS turns off the smart socket, but few seconds after, the toggle in the HASS returns to on, leaving the smart socket off… then if i retry to turn it off, nothing happens to the smart socket, and the toggle in HASS returns to on.
Seems that HASS can send the off command but cannot read the state of the smart socket. Here is the Zwave LOG

2017-06-28 20:01:59.642 Info, Node007, SwitchBinary::Set - Setting node 7 to Off
2017-06-28 20:01:59.642 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x25, 0x01, 0x00, 0x25, 0x2a, 0xc9
2017-06-28 20:01:59.642 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x2b, 0xc9
2017-06-28 20:01:59.643 Detail, 
2017-06-28 20:01:59.643 Info, Node007, Sending (Send) message (Callback ID=0x2a, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x25, 0x01, 0x00, 0x25, 0x2a, 0xc9
2017-06-28 20:01:59.649 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 20:01:59.650 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 20:01:59.666 Detail, Node007,   Received: 0x01, 0x05, 0x00, 0x13, 0x2a, 0x00, 0xc3
2017-06-28 20:01:59.666 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x2a received (expected 0x2a)
2017-06-28 20:01:59.666 Info, Node007, Request RTT 22 Average Request RTT 22
2017-06-28 20:01:59.666 Detail,   Expected callbackId was received
2017-06-28 20:01:59.666 Detail,   Expected reply was received
2017-06-28 20:01:59.666 Detail,   Message transaction complete
2017-06-28 20:01:59.666 Detail, 
2017-06-28 20:01:59.666 Detail, Node007, Removing current message
2017-06-28 20:01:59.666 Detail, 
2017-06-28 20:01:59.667 Info, Node007, Sending (Send) message (Callback ID=0x2b, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x2b, 0xc9
2017-06-28 20:01:59.673 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-06-28 20:01:59.673 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2017-06-28 20:01:59.688 Detail, Node007,   Received: 0x01, 0x05, 0x00, 0x13, 0x2b, 0x00, 0xc2
2017-06-28 20:01:59.689 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x2b received (expected 0x2b)
2017-06-28 20:01:59.689 Info, Node007, Request RTT 22 Average Request RTT 22
2017-06-28 20:01:59.689 Detail,   Expected callbackId was received
2017-06-28 20:02:06.290 Detail, Node004, Polling: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (poll queue has 0 messages)
2017-06-28 20:02:06.291 Detail, Node004, Queuing (Poll) SwitchMultilevelCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x26, 0x02, 0x25, 0x2c, 0xce
2017-06-28 20:02:09.667 Error, Node007, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-06-28 20:02:09.668 Detail, Node007, Removing current message
2017-06-28 20:02:09.668 Detail, Node007, Notification: Notification - TimeOut
2017-06-28 20:02:09.676 Error, Node004, ERROR: Dropping command because node is presumed dead
2017-06-28 20:02:09.676 Detail, Node004, Removing current message

Looking at the manual, I see there’s no COMMAND_CLASS_SWITCH_MULTILEVEL in the Command Classes Section
available are:
ZWAVEPLUS_INFO
MANIFACTURER_SPECIFIC
VERSION
ASSOCIATION
ASSOCIATION_GRP_INFO
DEVICE_RESET_LOCALLY
POWERLEVEL
SWITCH_BINARY
NOTIFICATION
METER
CONFIGURATION
SWITCH_ALL
BASIC

(all with prefix COMMAND_CLASS_)

More, in zwave config file there’s no COMMAND_CLASS_SWITCH_MULTILEVEL defined at node 7, but there’s one in node 4 and 2 (both are zwave rollershutters).

3

Sorry, not see that these COMMAND_CLASS_SWITCH_MULTILEVEL was on Node004.

Problem persist. But sometimes the switch works, others not…

4

It’s strange.
Sometimes all Zwave nodes are “Ready”, if I restart HASS always some of them goes on Dead state, then restart Raspberry and they resume to Ready… sometimes doing nothing, the day after all comes to Ready…

With these sockets in particular, I’ve found that, in some situation, switching them on or off with the button on the socket, the update to HASS is instant but if I switch them on or off with HASS, if the plug changes its state, it changes few secs after (or it doesn’t change at all)

I’m near the Aeon Labs USB stick on the raspberry, about 5 meters, behind a single wall with door open when testing these changes.

5

you managed?

I do not have your problems, but wish to know how to check power consumption per day

6

On day basis, I don’t know.
But there’s some sensor on it, like neo_coolcam_power_plug_12a_energy, that seems to read and accumulate power consumption.
In the manual, there’s a reset parameter that shoud be used to reset the counter (param #11 to 1) but I’ve not find how to send this parameter successfully…
Maybe you can read the energy at midmight and then reset the counter …

7

That’s the idea.

But how to reset the counter…?

Have no idea on how to work in Zwave

8

How?
Reset_node_meters
Reset a node’s meter values. Only works if the node supports this.
set_config_parameter
Lets the user set a config parameter to a node. NOTE: Use string for list values. For all others use integer.
soft_reset Tells