[APP] SmartStart Manager for Z-Wave (Long Range support)

Hi.

Just got me 6 ZEN04 LR's and want to sprinkle some around for house for reliability purposes, ie, some are powered off for long times (less mesh confusion upon re-power), and some "mission critical".

This thread seems like the "go to" thread for LR, correct? Or is there another? (I'll have to look, as well.)

I probably should augment my qr codes in a plastic bag approach I've used with the two LR contact sensors I have, lol, so I'll likely be using this app.

What's the best way to check firmware version on a brandy new ZEN04, since I sort of remember there's been an update? Nothing's on the box. Include as LR, check, exclude, then include as mesh if update needed?

edit: Found some LR stuff in Documentation. I should go there more often I guess, lol.
edit2: Paired with SmartStart perfectly (side note, had to stop android app and reopen to get it off the schneid). Version 2.20 is latest, 9/23, per Zooz changelog, so I'm good to go. Next stop: check out the app.

1 Like

Hi Jeff.

Used the app for the first time.
Didn't read the thread, lol.
I wonder if you could take a look at my list, below.

Apparently the Hubitat app keeps putting in "package bin" for Name; I guess I can edit that in your app.

Also, what's the story with the S2 Manual Boot Mode for (the real) Package Bin (device name)? Should I change it to SmartStart LR, like the other ZSE18 (mailbox)?

Thanks.

1 Like

If you are using the Android app I think I reported the issue with the duplicate names multiple times now and it has not been fixed that I know of. It just pops the name from the last device in there when you scan a new code. SmartStart used the same name/location as previously joined device for a new device - #4 by jtp10181

Must have been set to that on accident after you included it. It does not impact anything once the device is included but if you ever were to exclude it and try to include again it would be an issue. So yes, you can change it now to avoid any future confusion.

One more question, for the moment, lol:
What's with the 5 X's at the start of the DSK?
The DSK is not complete without the number, is it?
Thanks.
@jtp10181 ?

edit: Found it!

image

Hi Jeff.

I'm about finished with LR for now.

I wonder if you could take a look at my list, below?

The 3 ZEN34 wireless switches have security = none. I can see that. Consistant.

However one ZEN04 (House Gen Inlet 120V) also was paired with security = none
I don't understand that. All the other ZEN04 plugs paired with security = S2 Authenticated.

Thanks.

Hm, that's not supposed to be possible. LR requires S2.
Check and see what it shows on the Z-Wave details page.

I meant Z-Wave details in the hub settings.
But that does show it paired with grants of (2) which is S2 Authenticated.

My app pulls from the same endpoint as the z-wave details so I was curious to see what that shows.

1 Like

Holy Crap!
On a whim, I sorted the Z-wave device details by node:
I got, maybe, 50, 50, Unknown LR devices! Sample below.
What the hell is going on??????

edit: I went to my go-to move, shutdown/power cycle, and they all went away! Got an alert for high hub load, probably just as a result of the shutdown/power cycle. Might do it again for giggles.

Summary

x0110 (272) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown

None 01 -> 0110 100kbps
0x0111 (273) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0111 100kbps
0x0112 (274) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0112 100kbps
0x0115 (277) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0115 100kbps
0x0119 (281) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0119 100kbps
0x011b (283) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 011B 100kbps
0x0121 (289) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0121 100kbps
0x0123 (291) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0123 100kbps
0x0124 (292) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0124 100kbps
0x0125 (293) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0125 100kbps
0x0126 (294) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0126 100kbps
0x0128 (296) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0128 100kbps
0x0129 (297) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0129 100kbps
0x012b (299) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 012B 100kbps
0x012d (301) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 012D 100kbps
0x012e (302) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 012E 100kbps
0x012f (303) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 012F 100kbps
0x0130 (304) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0130 100kbps
0x0131 (305) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0131 100kbps
0x0132 (306) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0132 100kbps
0x0135 (309) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0135 100kbps
0x0136 (310) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0136 100kbps
0x0137 (311) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0137 100kbps
0x0138 (312) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0138 100kbps
0x0139 (313) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0139 100kbps
0x013a (314) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 013A 100kbps
0x013b (315) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 013B 100kbps
0x013c (316) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 013C 100kbps
0x013e (318) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 013E 100kbps
0x0140 (320) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0140 100kbps
0x0141 (321) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0141 100kbps
0x0142 (322) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0142 100kbps
0x0143 (323) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0143 100kbps
0x0144 (324) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0144 100kbps
0x0145 (325) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0145 100kbps
0x0146 (326) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0146 100kbps
0x0147 (327) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0147 100kbps
0x0148 (328) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0148 100kbps
0x0149 (329) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0149 100kbps
0x014e (334) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 014E 100kbps
0x0150 (336) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0150 100kbps
0x0156 (342) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0156 100kbps
0x0157 (343) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0157 100kbps
0x0158 (344) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0158 100kbps
0x0161 (353) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0161 100kbps
0x016e (366) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 016E 100kbps
0x0171 (369) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0171 100kbps
0x0174 (372) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0174 100kbps
0x0177 (375) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0177 100kbps
0x0179 (377) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0179 100kbps
0x017b (379) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 017B 100kbps
0x017c (380) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 017C 100kbps
0x017d (381) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 017D 100kbps
0x017e (382) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 017E 100kbps
0x017f (383) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 017F 100kbps
0x0180 (384) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0180 100kbps
0x0181 (385) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0181 100kbps
0x0186 (390) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0186 100kbps
0x0187 (391) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0187 100kbps
0x0189 (393) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 0189 100kbps
0x018a (394) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 018A 100kbps
0x018b (395) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown
None 01 -> 018B 100kbps
0x018c (396) LR PER: , RTT Avg: ms, LWR RSSI: N/A
Neighbors: undefined, Route Changes: undefined Unknown

None 01 -> 018C 100kb

Hey Jeff, the shutdown/power cycle also appears to have cleared up the security thing. EVERYTHING LR is now S2 Authenticated, even the ZEN34's!

Yes both the fake ghost nodes and the security showing wrong are issues that get resolved by a shutdown or even just a reboot sometimes. Now that I think about I believe the security showing wrong was a known issue that never got fully resolved. Seems to just be best practice to restart the hub after pairing LR at the moment, until they get things worked out more.

2 Likes

My SmartStart database must've gotten corrupted somehow.
I've been adding devices, successfully.
The table was fully populated yesterday.
I have no idea what I did.
The devices and rules still work fine.
So far I've rebooted.
edit: and shutdown/power cycled.
I'm not sure how old my SS backup is.
edit: It's a week old.
Any other suggestions?

Restoring a SS backup wont do anything. I have no idea how the hub determines if the device is already included or not. The app just pulls the info from an endpoint on the hub and matches it up with the z-wave details endpoint data. Usually you can even remove something from SS and add it back and it will still remember it.

You could try activating some of the devices to see if that helps but I dont think it will. Best thing to do at this point if they dont re-populate with the node info would just be to disable them in SS so the hub is not looking for those devices.

1 Like

No it didn't. I tried power cycling a plug, but that didn't do anything. They are included already, after all.

I think that's a good idea.

I don't know if @bcopeland would respond on this thread, but if you think spinning it off to another standalone thread, that'd be fine with me.

SmartStart is not that smart.

I have a LR device I added via Smart Start. After install, I came to the conclusion that it would actually be better to install as a non LR device so that it can be part of the mesh network to help a light switch even further get better signal.

Is there a way to convert the LR to Non-LR/Mesh without removing the device and reinstalling it as non-LR?

Pretty sure that is a no.

No, has to excluded and re-included. Make sure you either disable/delete in SS or change the boot mode BEFORE you exclude, or it will just include itself as LR again immediately.

If you have a bunch of apps tied to it already and want to avoid breaking them, the simplest way is to create a virtual device placeholder, and use Swap Apps to move everything to the virtual device before you exclude. Then swap again to new device after included again.

There is another way to do this without using a virtual device by editing the DNI but its more complicated to explain.

2 Likes

Bummer....

I removed the LR device and was able to re add it non-LR no problem. I do, however, still have the device shoing up in my "Z Wave Details" page. And in the "Device" colum it just has "discover"? Is this something to be concerned about?

When you exclude LR sometimes they leave a temporary ghost. If you shut the hub down and unplug for 30 seconds usually that ghost will be gone when you boot back up. Actually usually just a reboot clears it out if you dont want to deal with unplugging it.

1 Like