simplextech

Different stick. The $19 stick is the Official reference stick from Silicon Labs and it is a Z-Wave 700 series USB stick. It is cheap (costing) but it is the reference standard by which others must validate against. Oh and yeah I have 2 of those and they work great.

Oh please NOOOOOO.... that stick aka Nortek stick is horrible and oh BTW you can't backup the z-wave portion so.. umm... SOL if the stick fails... it's also NOT a 700 series stick so you'd want to be upgrading in a year or so and without being able to backup and restore... ooops too bad! Would Zigbee end devices be nice with ISY... sure! But... that's a whole different ball game and a new can of worms and up until just recently with Zigbee 3.0 there really wasn't a REAL standard to cling to and call something supported so it was always a hit or miss and MUCH leaning on community developed drivers for most devices.

No it wont cause a "problem". @blueman2 pointed out that the "update neighbors" is still available which will work for some/most mixed environments. I'm currently treading in somewhat of an unknown here as well as I no longer have a mixed environment to test with. However my concern which could be unfounded is that the explorer frames are not being responded to by the non plus devices. This may not cause any problems at all if doing the update neighbors sends that information back to the controller to update the routing table with. So what I'm getting at is... No you shouldn't be alarmed about this. But aware that the "heal" being removed is not some "new to ISY thing" I've seen it with other systems as well. How this will affect things in real world scenarios I can't tell you as I don't have a mixed environment. So far I've not heard from any systems that don't have a "heal" the screams of bloody murder and calling for heads to roll from any users... about this issue.. I think many more pains are involved from those trying to implement S2 security (across the board with all systems) at the moment and I'm curious when that will emerge from the depths to the ISY and how "SmartStart" will even be handled....

Like @lilyoyo1 said... send it back... return it.

Technically by the Z-Wave Plus specification a "Heal" is.... "Not necessary".... Now the details of that is because Z-Wave Plus introduced "Explorer Frames" which when a route to a device no longer works the controller will send out lots of explorer frames that essentially ping the neighbors and ask who their neighbors are and the controller will "self-heal" and rebuild the routing table. This normally actually works ok and the mesh will re-route within seconds. The spec and docs say something like "up to X seconds" if I remember is something like 5-6 seconds for max time to send/respond to explorer frames. In general this does seem to work well in a ALL Z-Wave Plus mesh.... Now the kicker hits if you are running in a mixed Z-Wave environment..... some Plus devices and some NON Plus devices... Non Plus don't understand explorer frames so they don't respond and this can leave a hole in the mesh or inability to communicate with devices that can only route through that one non plus device. Now this is an extreme example of a broken mesh of a single device being the single route to another device... BUT... it can happen and the more non plus devices in your network the higher the chances of this happening..... In a mixed environment like lots of z-wave networks TODAY I think (my opinion) that network heal/optimize should be left in the controller as an option and in my preference I like it when controllers allow doing a per-node optimize so instead of "healing" the whole network one device at a time I can choose the node I want to optimize and force a neighbor update on. Like when I add another node and I just want to ensure the neighbors get the message they have a new neighbor.... knock knock here's some cookies

I'll second this sentiment. Systems should be able to "function" through manual control as well as automations (programs). The programs add spice and "smarts" to the overall system but "things" happen and it defeats the idea of a smart home when a dumb switch doesn't work because the "system is down".

Setup the older Occupancy nodeserver in the portal. Go to Connectivity IFTTT setup to generate a token URL for that purpose Use the phone to send a HTTP GET to that URL associated with that "Geofence" user Setup program to do what you want when that "user" becomes present or away This way your portal credentials are not exposed and the access is limited to a single function of marking the person home/away.

This is simple. Pay someone to write the nodeserver or donate the GEM + CT's necessary to develop against. Easy... maybe... Sexy in the Admin Console? ?

Aren't we all already... except the MIA company part... You send money to SmartHome who's products are made in China... so... same thing. Except if you bought it directly from the manufacturer you'd probably get support. Only good thing I have to say about the MSII is the ability to use the "On-Only" feature and linked to a switch. That's it. Wrap that in program to make logic decisions on when to turn off and call it a day. Nothing else about the MSII worked correctly for me. Glad I got rid of them!

The drivers are there for Linux. I don't know about Mac. However you will still need a software controller to interface with it. If you're intending to do firmware updates then from the Mac you will need to run Parallels or Fusion to run a Windows VM and you can then use the free Silicon Labs PC Controller to flash the firmware. Same would apply from Linux you would need a Windows VM to run the SiLabs PC Controller software to flash firmware.

Not without a VPN or port forwarding (BAD!!!).

Your link is not working but I remember it from before and the info wasn't very "interesting" to begin with nor was this "ordeal" very disgusting... hear say from a anonymous user on a forum... hmm never happens.... sooooooo what's the good stuff or is that it? If so I'm disappointed

But... but.... now we're all waiting for the story....

I don't know for sure but the typical sources are "sold out". With the COVID-19 issues around manufacturing and shipping from China this really isn't a surprise.

This is something I can definitely give props to Inovelli for. They are very open to problem reports and have appeared active with finding the root of the problem and fixing it when it's their problem.

So as to quote other forums. Here's the favorite Hubitat and the Inovelli bulb that is Z-Wave Plus Certified Hub keeps locking up This particular thread is in regards to the Hubitat hub continuously locking up presumed to be caused by the Inovelli RGBW bulb. This bulb may or may not be the problem as the bulb is a certified device and the hub is not a certified gateway. The "driver" in question is the one developed by Inovelli for this bulb so in theory everything should work but there's a user having significant problems not with just one bulb but several on this hub.... who's the blame? In the end when it comes to these DIY forums the fan boys of the system are going to defend their hub of choice no matter if this was a ISY problem or a Hubitat problem the fans are going to blame some device as the cause and wash, rinse, repeat with every "bad" device that someone has issues with on their hub of choice. There's really a flaw in any gateway that uses "drivers" to function and work with a Z-Wave Certified device.

Happy to address both questions around "compliant" and around this one above. First the compliance item is around the Z-Wave Certification itself and the liberties that vendors take in the "optional" portions of the certification. I like to pick on Fibaro as my goto in this category of doing oddball things that are off the cuff but because they "meet the bare minimum" requirements for certification then they get the sticker. I've seen this with other vendors as well. This is why I also point to both ends of the stick and I do device verification with multiple platforms BEFORE I point the blame at the device or the gateway. Often it's a mixture of both where a device has "extra" things that are not part of the Z-Wave Certification specifications or sometimes not even part of the z-wave specification at all but those devices are generally designed to accompany and perform best with their own brand. Often times what I do with devices for ISY are not necessarily verification of "conformity to specification" but using the device and checking settings to provide recommended setup or notes. Such as (Fibaro again) those buttons are a real pain to include in any controller even their controller but it can be done but how they "show up" in the ISY versus another controller will make you scratch your head and wonder "what do I do with this?" Sometimes a dimmer is reporting back on basic report and the ISY is expecting "basic set" and that's just a flag in the options to toggle but if a user doesn't know then that leads to a "bad device" outcome. I post all results, good, bad, ugly to the Github listing (until there's something better) which lists the devices, vendor, info and notes if there's any setup challenges or issues. This github issue list is open to the public so please feel free to add your own testing information and results. Since you now have an ISY on hand for testing it's likely easier and faster for you to test than me.

That user post is a half-truth.... The ISY994i ZW Firmware 4.3.0 is a Z-Wave Certified gateway. https://products.z-wavealliance.org/products/1228?selectedFrequencyId=-1 The ISY994I ZW+ Firmware 5.x is still in BETA and knowing UDI will go through certification when they are ready and can fully pass certification. The other hub mentioned in the post is not Z-Wave or Z-Wave Plus certified at all however Inovelli has done a lot of work with them on custom "drivers" and firmware updates to make the products "work". The other software based system is the only one of the three in discussion that is Z-Wave Plus certified and that is dependent on the version 3 of the software as the new version 4 unless they use the old v3 z-wave plugin will also require going through the certification process again. As long as Inovelli sticks to standards of Z-Wave Plus then in time the ISY will be certified and things should work out of the box no fuss. However until both sides are fully compliant with standards it's all up in the air. At this point in time the ball is in the ISY corner waiting on them to release and certify. I've not received any product from Inovelli to perform any testing/validation with so I can't say for sure where any of the issues originate from. I have been doing testing with Zooz and ISY for a while and there have been issues found that are being addressed.

I can't find any fault or issue with this.... dang.... Although I will throw in that if it's new install depending on budget I would suggest you look at a Lutron RadioRa 2 system or if you have a really big budget a Lutron HomeWorks QS system. With QS you can do wired and RF mixed and the Lutron RF is a lower frequency and VERY reliable. I've never had an issue and I don't know anyone that has when things are installed correctly. You can't beat the versatility of the Pico Remotes either like the Insteon remotes but at $15 a pop they multiply like rabbits

Yes. But there are much cheaper options. I would go ahead and buy the newest SiLabs USB 700 series stick..... https://www.mouser.com/ProductDetail/Silicon-Labs/SLUSB001A?qs=sGAEpiMZZMve4%2FbfQkoj%2BNEfRvhA8yqctH3nhvzmHIE%3D At $19.00 for the latest/greatest you can't beat that with a stick!

Yes you can use other controllers. A common/simple method is with a USB Z-Wave stick and then download the PC Controller from Silicon Labs. It's a free download but you have to register on their site as it's part of the Z-Wave SDK. Here's a HOWTO article for updating Zooz devices. The process is the same though for all Z-Wave devices. The difference is getting the firmware file from the vendor. https://www.support.getzooz.com/kb/article/253-how-to-perform-an-ota-firmware-update-on-zooz-devices/

There are some known issues with some Inovelli devices and there are firmware updates available for most of their devices. Problem being ISY doesn't support firmware doing firmware updates.

Also if you can add it to the "Issue" list on the github. https://github.com/UniversalDevicesInc/ZWave-Devices I've been compiling a supported devices lists using the issue tracker and setting the tags as works or not. If you look at one of the existing and just copy the same format that would be great.

Amazon devices are cheap because they only work with Amazon.... the same with "most" Wifi devices. They are tied into and locked into that vendor's ecosystem and usually do not work with anything else. There are exceptions and some open devices. Otherwise don't go cheap and buy products that are going to actually work without having to find some work around. This is the biggest mistake most people make is going cheap and then having to learn that no it won't work and having to either return the device, toss it, make some kludge work around to get partial functionality and in the end ultimately buying the proper working device if they want something that actually works and is consistent.