BUG: Qubino ZMNHTDx Smart meter S4 S5 S6 missing binary switches

Hi,
I’ve installed a Qubino ZMNHTDx SmartMeter to meter the energy consumption and switch a HVAC circuit breaker. It seams there are no binary switches to turn ON/OFF the device available in Hass.io for this device.
I’ve tested in Domoticz with the same hardware & configuration and the switches are available.

I’m using version Hass.io 0.67.1 on a raspberry pi3 with a Aeotec Z-Stick Gen5.
Bellow is the zwcfg_xxxxxxx.xml configuration (the z-wave node_id is 9 ).
THANKS!

zwcfg_xxxxxxx.xml (216.6 KB)

Reviving this thread, did you make the switch work? I didn’t even know there was a switch in it also. But I assume you got it working with the metering-values correctly in hassio?

I’m about to buy this one and would love to know before I buy :slight_smile:

Works great! No issues now

Great! Thanks :slight_smile:

Hi @Mattie I’m running version HASSIO 0.87.1 and I’ve just noticed that what was running beautifully is now no longer working . All switches are visible but I get no results (ON/OFF).

Any news here? Running Hassbian 0.84.3 and binary switches aren’t shown. Also the device reports 9 sensors regarding to its manufacturer, but only 7 are detected (one unknown). Anybody experiencing this same behaviour?

@Dixietoom I have the same issue… No longer working the switches. Unfortunately no one picks up this issue

Just got myself a Qubino Smart Meter (1-phase) and was wondering if anyone was able to resolve the issue of the switches in HA? I can see the switches, but for some reason they do not function as they should, the switches turn on after clicking them in the UI, but after a while switch back off. I’m also unable to make any sense from the Z-wave log that could help here.

Pasting it here for others as well (Node14):

> 2020-12-21 17:38:39.086 Info, Node014, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
> 2020-12-21 17:38:39.086 Info, Node014, SwitchBinary::Set - Setting node 14 to On
> 2020-12-21 17:38:39.086 Detail, Node014, Queuing (Send) SwitchBinaryCmd_Set (Node=14): 0x01, 0x0a, 0x00, 0x13, 0x0e, 0x03, 0x25, 0x01, 0xff, 0x25, 0x7a, 0x6f
> 2020-12-21 17:38:39.087 Detail, Node014, Queuing (Send) SwitchBinaryCmd_Get (Node=14): 0x01, 0x09, 0x00, 0x13, 0x0e, 0x02, 0x25, 0x02, 0x25, 0x7b, 0x90
> 2020-12-21 17:38:39.087 Detail,
> 2020-12-21 17:38:39.087 Info, Node014, Sending (Send) message (Callback ID=0x7a, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=14): 0x01, 0x0a, 0x00, 0x13, 0x0e, 0x03, 0x25, 0x01, 0xff, 0x25, 0x7a, 0x6f
> 2020-12-21 17:38:39.094 Detail, Node014,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
> 2020-12-21 17:38:39.094 Detail, Node014,   ZW_SEND_DATA delivered to Z-Wave stack
> 2020-12-21 17:38:39.138 Detail, Node014,   Received: 0x01, 0x07, 0x00, 0x13, 0x7a, 0x00, 0x00, 0x05, 0x94
> 2020-12-21 17:38:39.138 Detail, Node014,   ZW_SEND_DATA Request with callback ID 0x7a received (expected 0x7a)
> 2020-12-21 17:38:39.138 Info, Node014, Request RTT 51 Average Request RTT 65
> 2020-12-21 17:38:39.138 Detail,   Expected callbackId was received
> 2020-12-21 17:38:39.138 Detail,   Expected reply was received
> 2020-12-21 17:38:39.138 Detail,   Message transaction complete
> 2020-12-21 17:38:39.138 Detail,
> 2020-12-21 17:38:39.138 Detail, Node014, Removing current message
> 2020-12-21 17:38:39.138 Detail,
> 2020-12-21 17:38:39.138 Info, Node014, Sending (Send) message (Callback ID=0x7b, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=14): 0x01, 0x09, 0x00, 0x13, 0x0e, 0x02, 0x25, 0x02, 0x25, 0x7b, 0x90
> 2020-12-21 17:38:39.147 Detail, Node014,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
> 2020-12-21 17:38:39.147 Detail, Node014,   ZW_SEND_DATA delivered to Z-Wave stack
> 2020-12-21 17:38:39.209 Detail, Node014,   Received: 0x01, 0x07, 0x00, 0x13, 0x7b, 0x00, 0x00, 0x07, 0x97
> 2020-12-21 17:38:39.209 Detail, Node014,   ZW_SEND_DATA Request with callback ID 0x7b received (expected 0x7b)
> 2020-12-21 17:38:39.209 Info, Node014, Request RTT 70 Average Request RTT 67
> 2020-12-21 17:38:39.210 Detail,   Expected callbackId was received
> 2020-12-21 17:38:39.282 Detail, Node014,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0e, 0x03, 0x25, 0x03, 0x00, 0xd9
> 2020-12-21 17:38:39.283 Detail,
> 2020-12-21 17:38:39.283 Info, Node014, Response RTT 144 Average Response RTT 149
> 2020-12-21 17:38:39.283 Info, Node014, Received SwitchBinary report from node 14: level=Off
> 2020-12-21 17:38:39.283 Detail, Node014, Refreshed Value: old value=false, new value=false, type=bool
> 2020-12-21 17:38:39.283 Detail, Node014, Changes to this value are not verified
> 2020-12-21 17:38:39.283 Detail, Node014,   Expected reply and command class was received
> 2020-12-21 17:38:39.283 Detail, Node014,   Message transaction complete
> 2020-12-21 17:38:39.283 Detail,
> 2020-12-21 17:38:39.283 Detail, Node014, Removing current message
> 2020-12-21 17:38:39.283 Detail, Node014, Notification: ValueChanged

Hello all, I had the same issue with the missing entity for the swich.
I fix this by changing parameter 100 AND exclude and reinclude the device.
See my exchange with Qubino support :

On Fri, 8 Oct at 5:38 PM , Francois wrote:

Hi have successfully added the Smat meter to my home assitant using an usb stick Aeotec ZW090 on RasberyPi.

As you can see in attachment I have a full list of entity to monitor the smartmeter.

I have also set the parameter 100 to 1 EP IR external relay dsbld, External relay enbld.

The module IKA232 is correctly wired to pin 4 and 5.

But I’m not able to find any entity to control 'on/off) the switch in home assitant.

Could you please assist me ?

Le lun. 11 oct. 2021 à 09:05, Qubino Support [email protected] a écrit :
Hello Francois,

Thank you very much for reaching out to us,

Once you set the parameter you must exclude (without reset it to defaults) and re-include the Smart Meter to make the change active. The device must do the integration (inclusion) since is at that point that the gateway do the interview with the Smart Meter and according to that generate all the entities.

I hope I was able to help you, if you have any additional questions please don’t hesitate to ask.

Hi @vilpponen
After fixing the issue below (not having the switch button).
Now I’m facing the same issue as yours (switch back to off).
Did you manage to fix this ?

Thanks

François

Hi @Francois_Bietlot - unfortunately I did not get this fixed. I had another member of the forum direct me that (if my memory serves me correctly) Qubino did admit a firmware issue and had sent a new unit to this other member. While I’m not able to use the switch, I’m still using Qubino to collect usage data in a higher wattage setup, so it works for me.

1 Like