@slagle did this happen? I’ve had zero Z-Wave functionality since this weekend, and support hasn’t responded to my ticket yet. I’m trying to discern if I have a site-specific problem or if I’m “part of the herd” on this one.
3 Likes
Hey guys, I was out of band yesterday, I’ll check when I get to the office on the changes and their schedule.
I have the exact same issue in the same timeframe.
I’ve been getting all sorts of Z-wave repair issues and general flakiness lately as well. WTF is going on!?
The z-wave repair is currently broken. We are waiting for @slagle to… [quote=“slagle, post:22, topic:44080”]
get to the office
[/quote]
…so he can provide us with an update on when we can run repairs…
2 Likes
like I said earlier. Its funny you guys are getting failures and I have not gotten one since the issues began. I bet its not doing a damn thing so it just doesnt report failures
Where do you see that info? In the app or ideas? In the ideal when I do zwave repair and click on the logging it never finishes
There is a method that I use that works, using the IDE.
First, start a z-wave repair in the IDE. It will offer a link to log. Click on that link. Immediately clear the Name Filter field so that it is blank. Bookmark this page.
At that point, with the filter cleared, you will see all Hub log events. It’s interesting stuff. Ping every 5 minutes.
For z-wave repair on V2 hub you will see each device report during the repair. And you will see any failures, and the repair finish.
In the future, open two tabs, one with the hub logs from the bookmark with the filter cleared. The other with Hub Utilities. Launch the z-wave repair, and in the log you will see it start.
5 Likes
Thanks Bruce,
In the above picture that would be under the displayed text column? Could someone post what a successful repair on a device looks like? It’s been running for 10 minutes and I haven’t seen anything say failed, but I don’t know what the successful message looks like either -
I don’t get each device report. Only failures if I get any. 99% of the time I get two messages at the begining then one or two pings followed by cloud connected devices and then two messages at the end. Repair finished and ready. @slagle said that repair will fail and that he’ll let us know when we can run. I ran it today and got no failures…
1 Like
Maybe I had z-wave debug turned on, but I don’t think so. I haven’t done it since the meltdown started.
There really is no reason that z-wave repair should fail due to the millisecond problem. It’s a hub function, once started, it just runs. It’s only interaction with the cloud is to send logs.
1 Like
would it say device type 04: mac address followed by a network address? because that pretty much all i’m seeing, well that and pings
No, it’s obvious. Hmmmm. Something has changed from 3 weeks ago.
That’s odd. I didn’t know that could happen.
Before, you would see start twice, then nothing for however long, except for failures would show up, and then finished twice. It was a no-news-is-good-news sort of log.
I’m not touching it for now.
1 Like
That’s all I had from the begining with v2, it would be interesting to know what kind of debug you had turned on before and how you enabled it…
I don’t think I had it turned on. But, here it is:
!https://graph.api.smartthings.com/hub/zwaveDebugOff/[hubid]
You need to grab your hubid from some other url in the IDE, and paste it into that. It doesn’t show very much, mostly the hub polling your devices VERY slowly.
Watch out for the exclamation point I put in above to stop it from being a URL. Copy from https on.
1 Like
Hmm, I wonder if I need to reboot after enabling it, or do I stay on the page that displays “{“message”:“Z-Wave debug mode enabled”}”
You can just blow off that page. Rebooting turns it off. That’s all running that url does, is give you that one message. Same when you turn debugging off.
well I think i’m done for now on this, i’m still only getting the device id 04 mac stuff showing up
Isn’t that 04 stuff the local LAN ping? Nothing to do with zwave.
2 Likes