ZWave Qubino Flush 2 relays, missing entities

Configuration Z-Wave
1

I have used these for years now, they are great switches but every now and then I loose some nodes off my zwave network (they go dead) and I need to remove and add them again.

When I used to add these guys, I got 3 sets of entities… Switch 1, Switch 2 and a combo switch and control both in unison.

Now when I add the nodes back, I am only getting Switch 1 and the Combo switch… And not switch 2. So I am missing half the entities and I am unable to control the light/thing behind that second switch individually.

Any thoughts on how I can get them joining properly again? I have removed and added back a half a dozen times now and I am starting to go mad.

thanks

I have a full log of adding an entity but it is too large for this forum, let me know if you want it.

2

Ok, so… This got weirder… :\

My original report is incorrect, it is reporting entities different to previously but I am getting the entities for switch one and switch two, not the ‘combo’ switch.

There are two switches ‘value instance’ is 1 and 2. If I switch ‘value instance 1’ this switch works fine and normal. If I switch ‘value instance 2’, this switch will switch both in the UI but physically only one light is turning on (the one it is meant to control). The event bus thinks the other light is being triggered also (even though it is not on) because an automation based on that switch is triggering.

Does that make sense? :slight_smile:

Another way to put it, There are two switches:

Node099, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1
Node099, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 2

if I toggle this in the UI:

Node099, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 2 - True

That switch turns on physically, but Node099, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 turns on in the UI and the event bus thinks it turned on, because an automation based on it triggers.

If I toggle

Node099, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True

in the UI, that switch turns on… and That is it.

Lastly, the automation that is being triggered, is getting triggered many, many times…

2019-09-04 21:18:21 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:23 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:43 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:45 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:55 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:57 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:18:59 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:19:04 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:19:07 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:19:08 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:23:34 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:23:35 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:23:38 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:23:49 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
2019-09-04 21:23:50 INFO (MainThread) [homeassistant.components.automation] Executing bug catcher on/off with the back deck lights
3

Ok, so months have gone by of just wearing this issue, I figured that maybe these zwave GOAP nodes were dying and I should replace them.

Over Christmas I made a change in that since I am using Hassbian I should move on, so I converted my HASS install from venv and use the docker image. I now run it in the container, I did this like dec 28.

Now yesterday, I restarted HASS for some configuration changes related to location (unrelated to this issue) and then I ran into an issue where all of my nodes which run on battery and are sleeping nodes:

2020-01-11 16:23:19 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 41 not ready after 32 seconds, continuing anyway

started doing this, I restarted my PI, reseated the USB dongle… same issue, the thing I noticed was these entites were no longer in the HASS zwave configuration UI but you could see it all working in the logs. I then went around and woke up all of these devices and they joined and all of the entities came good in the UI… but still none of them were in the configuration UI.

Then I noticed these missing entities that I mention in my original post… All back… And all working. I had to rename a few and I did so.

I then braved a HASS restart and it all came back again… Like everything.

Amazing, no idea what is going on here but its super annoying but atleast nothing is failing. I am on 0.103.6 image from dockerhub.

4

I also have the Qubino Flush Relay 2 and this week the switch entities stopped working (are unavailable in HASS, on Docker). The energy metering works fine and I see the change in HASS.

What did you do exactly to get your entities back to working in HASS?
I find in the OZW log the following message:

No Valid Mapping for Basic Command Class and No ValueID Exported. Error?
5

For me it has been a long journey battling a bunch of different symptoms and problems but eventually one day I attempted to do ‘network heal’ and a lot of nodes were disconnected. In frustration I restarted my Pi3 and more nodes were lost or entered a weird state. I then had 3 nodes left connected to the network and it was working great. I came to the conclusion that my Pi3 just did not have the CPU to run a 40+ node ZWave network. I bought an Udoo SBC X86 Ultra II, I have not reintroduced all of my nodes yet but I have around 25 connected and it is perfect. HASS restarts are < 5 minutues usually (Pi3 was 20+).

I do not think I have ever seen this error, but I couldn’t tell you for sure. Maybe the node has failed?

6

Thank you for replying.
I am running on nuc i5 so definitely enough power. It is quite frustrating as I have a second Flush 2 relay which continues to work just fine. I don’t think the error I mentioned relates to the issue as I see similar messages for devices that work fine.
Anyway, thanks for the response.

7

No problems, do consider the fact that the node may have just failed!? :wink: