Vera Plus loosing control over newly added devices

Vera Controllers, Services & Devices General Vera Discussions
#1

Hi,

I have several newly added Qubino DIM (ZMNHSD1) and mini(ZMNHHD1) dimmers that after a few days will stop responding to commands (on/off/dim) from the Vera controller. The logs show a message can’t encrypt. Oddly when I turn the switch on manually, the status and wattage are properly updated on the Vera. Re-including and factory reset do not solve the problem.

Any suggestions?

08 03/21/22 12:32:07.446 JobHandler_LuaUPnP::HandleActionRequest device: 91 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x6f813520>
08 03/21/22 12:32:07.446 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=91 <0x6f813520>
08 03/21/22 12:32:07.447 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x6f813520>
08 03/21/22 12:32:07.447 JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x6f813520>
08 03/21/22 12:32:07.447 JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x6f813520>
08 03/21/22 12:32:07.447 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.018034494077427188 <0x6f813520>
02 03/21/22 12:32:07.448 JobHandler_LuaUPnP::ConfirmGlobalActionRules replaced binary on with dim 40 <0x6f813520>
06 03/21/22 12:32:07.448 Device_Variable::m_szValue_set device: 91 service: urn:upnp-org:serviceId:Dimming1 variable: LoadLevelTarget was: 40 now: 40 #hooks: 0 upnp: 0 skip: 0 v:0xbefb40/NONE duplicate:1 <0x6f813520>
02 03/21/22 12:32:18.566 ZWaveSerial::GetFrame 0x764c0844 timed out now 0 m_listGetFramePending 0 <0x764c1520>
01 03/21/22 12:32:18.566 ZWaveNode::GetNonce node 45 failed (nil) <0x764c1520>
01 03/21/22 12:32:18.567 ZWaveNode::EncryptFrame m_iFrameID 267638 cannot get nonce node 45 command class 0x26 command 0x1 <0x764c1520>
02 03/21/22 12:32:18.567 ZWaveSerial::Send m_iFrameID 267638 type 0x0 command 0x13 sent ok - can’t encrypt <0x764c1520>
01 03/21/22 12:32:18.567 ZWJob_SendData::Run done/fail job job#10392 :Level 40 node 45 dev:91 (0x233c128) N:45 P:35 S:7 Id: 10392 took 11117 ms method 2 to node 45 command 38/1 failed 5 retries 0 of 5 <0x764c1520>

Cheers Rene

#2

Hi @reneboer

Do you have more of those devices added to your system? if so, for how long have you had them, and are they working just fine?

It could also be related to the firmware those “new” devices have, meaning that from Qubino something might have changed.

#3

Hi @Leonardo_Soto,

I have more qubino devices on for a long time, also a mini dimmer that I bought the same time as the one I added now. I assume it has to do with the poor to non-existing S2 support on Vera (and Ezlo, on that there is also no S2 and the power reporting does not work). S1/S2 devices have given been issues for the last few years on Vera. Some firmware releases ago it seemed you could add those devices, but now it is really hit and miss.

Cheers Rene