Ghosted on ghost issue. How do I create/submit a support ticket?

Go to each device page and click the "Events" tab at the top. Look for the command-on events, and the "Triggered By" column is what app issues the command.

If you only see an "on" event triggered by the device itself, then it was turned on by some external source.

Alexa integration? Maybe Alexa Hunches?

If it was turned on by Alexa it would show in the Triggered by. When I say external, I mean something that does not route through an HE app/command. For many cases this would only be a physical tap on the switch.

In all the posts I had seen before that were resolved by turning off Alexa Hunches, there was no trace of the Alexa app in the logs. That is why it was the first thing that popped into my head.

How do I turn off Alexa hunches?

It would not be in the logs, but it would be on the Event table, since a few versions ago when they added the "Triggered By" column. Before that, it was just a guess as to how a device got triggered.

Looks like the easiest way is to just say "Alexa disable Hunches"

https://www.amazon.com/gp/help/customer/display.html?nodeId=G63YSH7WU32D9GW9

2 Likes

Thanks. Alexa said hunches are now off. But she also said the Mercedes is paid for, the check is in the mail, and I wasn't exactly sure what the last one she said was.

1 Like

If you just go to the device page and then look on the "Events" tab I described you will know exactly what triggered the devices to come on, assuming the command came through HE. Instead of guessing and hoping it was hunches. Or did you already confirm Alexa was the culprit?

It wasn't Alexa Hunches as I turned those off and it just did it again (i.e. turned on all devices in my den).

What does it show in the events tab on one of the devices?

Sorry to have been away so long. I was able to get one problem fixed, and that was my room turning everything on. I was able to track that down to an Alexa routine that was turning it all on at Sunset. I'm the only who ever does any automations and I'm 100% I didn't intentionally create it. I don't know if it was an Alexa hunch or suggestion and I said OK to it or what. But, in any event, that's resolved.

So today (Feb 4, 2024) I wanted to try to resolve the issue where I have a device with a route, but no name. That was 4B a/k/a 75.

My plan was to follow these steps:


OK, since you have PC Controller and since the device appears to be a switch based off your screenshot, go to the Network Management tab, select device 75, then click "Basic Set ON" and then go around your house looking for the switch or light that just turned on.

You can alternately hit the ON and OFF commands to help you locate the device. This will help you identify WHAT device is device 75.

Then, in Hubitat, create a virtual device, but select the appropriate type for that device, ie "Generic ZWave Switch", or whatever is appropriate.

Create the device, then change the network ID. You'll have to tell Hubitat that you think you know what you're doing. Then you'll enter "4B" in the ID box (without the quotes. 4B represents 75 if hex).

After you do this, save the device, then immediately hit initialize or configure at the top of the device page. It should sync Hubitat with the switch and you should be golden.


The first issue I have is that controller appeared as 129 and 131. 129 is in Hubitat, but not 131

But in the PC Controller it looks like 129 isn't working, but 131 is.
Screen Shot 2024-02-04 at 3.12.27 PM

I don't know if that is the reason, but for whatever reason, with 75 selected clicik on Basic Set On did nothing:

The next step said " You can alternately hit the ON and OFF commands to help you locate the device." But I don't know what that means as there are no buttons that say just "ON" or "OFF", Just the Basic Set On and Basic Set Off. So I couldn't try that as I couldn't find any such button.

I then started looking on my Hubitat Devices page and noticed one was missing, my Master Bathroom Toilet Fan. This device is an Inovelli Black On/Off. Since I have others just like it I went into one and saw the Device was an Inovelli Switch LZW30.

So I created a virtual device with that driver and made the ID 4B. (I added "AA AA" to the name so it would sort to the top.

I saved it and then quickly press the Configure button (as I didn't see one called "Initalize")

I saw this in the logs after I pressed Configure:

I then went to the Devices page and 4B is now my virtual device:

When I'm inside the virtual device in Hubitat pushing the On or Off button does not generate anything in the logs and the Current States remains blank.

As a test I changed the drive to Generic Z-Wave Plus Switch:

And since there is no Initialize button I immediately pressed the Configure button again.

But as you can see above, I still have nothing under the Current States and it doesn't show up in the logs at all. BTW, I did create a virtual device a long time ago to act as a place holder for my Inovelli Red Series dimmers for times when I would have to take a device offline and didn't want to re-do apps. Pressing the on/off button for that does change the Current States and shows up in the logs. So this vitrual device isn't working.

So I am not "golden". Hubitat still doesn't know that is the Master Bathroom Toilet fan.

So what do I do now?

You probably just need to remove that node 0x4B and pair that device again.

1 Like

What is the best way to remove it?

You can try doing a normal exclusion on the device first. If the device is still attached to that hub node it should take it out with the exclusion.
If that does not work you can try refresh/remove from the hub, and last resort would be using PC Controller. This has instructions for the hub removal method and PC Controller: How To: Remove Z-Wave Ghosts (including using a UZB Stick)

I am trying to follow the instructions on how to have Hubitat remove a ghost. I'm not 100% sure if it is considered a ghost as it has a path, but no device.

I'm 99% sure which device it is and pulled the air gap. I then clicked the refresh button. As you see it says "Pending". I was read the part that said I should be patient and not push it again too fast. I've waited 2 hours 50 and it still says Pending. So I don't think the screen has refreshed yet. How long should I wait? Can I press Remove now?

As this is my bathroom fan I can't leave the air gap pulled indefinitely.

BTW, I have a 2nd one the is a classic ghost. However, I have no idea what device it is. So I had tried turning off every device and using the PC Stick but that didn't work.

I don't want to click the Refresh, Remove or Discover buttons until the Pending is cleared from the other one. Or is it OK to click one of those now? If so, which should I click?

They both have neighbors listed, the hub will never be able to remove it unless the only neighbor is the hub itself. Some sort of bug (or feature?) with the z-wave SDK.

Probably only way to get rid of them will be a USB stick.

Why not? Error? Or what happened? I have never had this NOT work.

Nothing happened. I threw the breakers to all of my devices at once and unplugged all of my smart plugs and using the PC Stick did nothing as detailed above.

That's totally unnecessary, especially using the USB stick.

I would exclude the stick then reset it and include it fresh. Then try again. Make sure you are on the correct node using the dec number from within the ( ) in the z-wave details page on the hub (not the hex 0x number).

What step does "nothing" happen? There are multiple steps, is the fail check working? It should be telling you something in the status bar, it also has logs you can open. "Nothing happened" is not helpful, its doing something...

2 Likes

I ended up with a Ghost PC stick as you'll see below:

How do I exclude them?

Should I take the USB out of the computer first?

Unplug the stick from your computer.

Shut down your hub, at the red LED pull power, wait 30 seconds, restore power and let it boot up.

Go to Z-Wave details, hit Refresh for the ghost UZB stick. The Remove button should appear, hit that.

2 Likes