But in any case, since you've added the app code via HPM, all you need to do is go to the Apps tab, select the button, and choose the SmartStart app from the list to install it. Then it will appear in your list of installed apps.
Dang it! I should have known that!!! Thanks for the fast response ...
So ... the real problem that I am trying to solve is that I have tried to add two (and I have seven more) Zooz ZSE42 800LR_800 Series Water Leak XS Sensor Z-Wave Long Range. This was hours ago. I used the following method:
Hubitat 2.0 mobile app: go to Devices > + (plus icon) > Add SmartStart Devices
Select Smart Start
This will take you to the smart start inclusion list. Devices will be displayed there that are in the process of inclusion through Smart Start.
Select the QR symbol in the top right to open the camera for the DSK scan; scan the QR code printed on the back cover of the sensor.
Power the device (important to do this AFTER QR scan)
The device integration will begin. The window will appear asking you to name the device; click Save after naming
Finishing inclusion may take a few minutes
So what I see is that the sensors are pending and not on the Z-Wave mesh:
Open live logs in another browser tab.
Then either factory reset or do an exclusion on one of the devices.
If you do the exclusion the hub should say "unknown device excluded"
Either of those should kick the device into the smart start pairing.
Watch the log for a message something about SmartStart pairing.... then just wait a minute, usually within around 30 seconds you should see some debug logs from the device being configured.
Or... you might see warn logs with errors. Hopefully not the dreaded bootstrapping error.
Jeff ... thanks for chiming in ... Apparently I am a little too stressed with the Z-Wave pairing at the moment ... so I am going to revert to drinking ... and try pairing again tomorrow.
I will report back ... Although I understand ... that could be considered a threat!!!
Only known fix is to reset the z-wave radio and re-include all your devices. Requires more steps than that to avoid DNI collisions when adding devices back though.
In the past I have had the worst luck with SmartStart. I decided to bite the bullet tonight and convert 12 LR devices from mesh to LR mode. I had two device types (button controller and smart plug). I happen to have spares(*) of each not in service yet so I used real matching devices to do the swap apps dance. This was very helpful with all the rules attached to multi-button devices I have.
(*) Not really spares just devices I have not got around to installing / setting up yet.
The conversion went smooth with each LR device self-adding instantly upon mesh exclusion, faster than I could get from the exclusion dialogue back to the devices screen on my iPhone. I used the iPhone Hubitat app for scanning in the QR codes and the browser on the iPhone for swap apps and configuration management.
Quite satisfied other than my Z-Wave mesh looks so much smaller with 12 missing devices. It would be nice if the Z-Wave topology graph showed LR even if that are pure star topology.
I started going around my house using Smart Start and your app to re-include devices that are SS capable... Also swapping out some first gen plus switches in the process... Ultimately, I would like to have all of my z-wave devices cataloged in your app and available to more easily do a complete z-wave rebuild if forced to do so for the LR fix... I won't be able to fully do it as a I have a few devices like sirens and GE motion switches that just don't support it...
Anyway, just wanted to let you know another use case and how it is going... All of my wall switches are what I like to call gen 5 1/2. Although they were all plus devices I put in starting around 2017/2018, half of them were the original plus with no security or SS features... I know there has been some question about it, but the second gen 500 series devices for the most part all support security and SS... I'm not including them with security, but its there...
I know there has been talk that 500 didn't support it at all, but that's not the case...
If and when I move in the next year or so and we get into the new house, I will outfit that one with all 800 series stuff or whatever is new then... But for my main mesh in the current house, the 500 series stuff is working well alongside 700/800 sensors, etc... Anyway, just dropping this here for reference...
So I stuck my head in the sand for a couple of days ... and lo and behold, it seems the problem went away!!! The devices have been included (I hope)!!!
@jtp10181 Jeff ... (if you are available) could you give me your thoughts on my situation please?
So ... I have all of the sensors online!!! Yay!!! Some minor problems (later) ... but I thought that I would comment @jtp10181 and maybe it might even be feedback ...
Given that (I finally) got all of the water sensors are included:
My guess is that the sensor has gone to sleep, as opposed to failed. I think that I read that the Zooz ZSE42 800LR Water Leak XS Sensor reports status every hour ... but I don't know that for a fact.
Is there something I can set up to show “Sleeping” instead of failed (e.g., maybe a longer timeout) and still indicate failed when failure is more likely … highlighting the fact that “failed” is apparently not representative of the actual status?
SmartStart is only used to pair the device after that is does not do anything. You can either just uncheck them all so they are not on the hubs SS list or ignore the failed status.
I see that I misinterpreted the functionality of the SmartStart Manager. No problems are left to solve then!!! All of my 11 water sensors appear to be running in the HE/Devices window.
Not necessarily a problem, just trying to understand, how can a device be both mesh and LR? Just noticed this entry when verifying a different device. This device was added with Smartstart
EDIT
As I'm looking at this, I have no idea how it didn’t include as LR, but can I change it to LR with that toggle in Smartstart? Or is exclusion and re-including it the only way?
The left side is the SS boot mode (how SS will pair it at next pairing attempt), the right side is how the device is actually paired to the hub. So it is paired as LR, but since then you must have changed the boot mode to Mesh.
I need to add another heading to that table or some notes on there to explain the columns a little better. Working with those tables in the app code is a pain, brings me back to my high school days of creating web pages with hand typed HTML code in notepad.