Problem turning on a wallplug

Every morning I have problems turning on a Fibaro wallplug.
It dosen’t matter how many times I do it, what helps though is doing a "Heal Network"m then it switches on after a while (I don’t need to manually switch on, it’s like the old commands goes though after the heal network command).

This is what I see in the log:

2017-10-24 07:34:14.235 Info, Node009, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-10-24 07:34:14.235 Info, Node009, SwitchBinary::Set - Setting node 9 to On
2017-10-24 07:34:14.235 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_SWITCH_BINARY
2017-10-24 07:34:14.235 Detail, Node009, Queuing (Send) SwitchBinaryCmd_Set (Node=9): 0x01, 0x0a, 0x00, 0x13, 0x09, 0x03, 0x25, 0x01, 0xff, 0x25, 0x54, 0x46
2017-10-24 07:34:14.235 Detail, Node009, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_SWITCH_BINARY
2017-10-24 07:34:14.235 Detail, Node009, Queuing (Send) SwitchBinaryCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x25, 0x02, 0x25, 0x55, 0xb9

How far is the wallplug from the nearest other powered node? That sounds like a problem where the device is too far away from the controller (or other powered node) for reliable communication.

3cm from another power plug and about 3.5m from HA hub :slight_smile:

Ironically, that could actually be too close to the controller. I doubt it, but you never know (yes, being too close to the transmitter can be a problem for RF).

If it’s the only device that’s a problem, it could be a faulty device. What devices does it show as neighbours (under the Developer tools menu, in <>, look at the zwave. entity.

Pretty much all of them :slight_smile:

node_id: 9
node_name: espresso
manufacturer_name: FIBARO System
product_name: FGWPE/F Wall Plug Gen5
old_entity_id: zwave.espresso_9
new_entity_id: zwave.espresso
query_stage: Complete
is_awake: true
is_ready: true
is_failed: false
is_info_received: true
max_baud_rate: 40000
is_zwave_plus: true
capabilities: listening,routing,beaming
neighbors: 1,4,6,10,11,12,13,14,15,19,20,21,22,23,24,28
sentCnt: 14
sentFailed: 0
retries: 0
receivedCnt: 544
receivedDups: 10
receivedUnsolicited: 533
sentTS: 2017-10-24 07:59:29:438 
receivedTS: 2017-10-24 08:44:13:381 
lastRequestRTT: 49
averageRequestRTT: 67
lastResponseRTT: 129
averageResponseRTT: 198
friendly_name: espresso
custom_ui_state_card: state-card-custom-ui

So, faulty device, or gremlins.

The details look healthy. RTTs are low, no failures. I’ve no idea what’s going on I’m afraid.