simplextech

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.

Their whole product is the garadget thingy which is wifi and is only control no status and I don't like it. The Security+ unit is just an inline bypass to provide control to any other contact controller. Use an IOLinc and open close sensor and done. Or any other controller just like any old dumb GDO. Or deal with the MyQ BS hassles. They aren't the only supplier of the inline device they are just the cheapest I've found. There' another one out there and it's closer to $50 which is just stupid.

In essence... Yes.

It's not a controller. It's a pass through around the Security+ system so you can use normal contact closures like the IOLinc or their remote opener device.

If you're dealing with a Chamberlain MyQ or any of the Security+ 2.0 garage doors I recommend not wasting time trying to hack around their cloud services and buy one of these and then use whatever you want to control it. https://www.garadget.com/product/security-2-0-dry-contact-adapter/

There's actually two versions of the integration for HASS. The version from HACS updated and has more features. The developer @shbatm visits here as well.

The integration using the PyISY module which is an IP connection and uses the REST interface of the ISY. It does not do anything directly with the PLM. I'm not aware of anything exposed via the REST interface that could be causing any PLM issues either.

This answers my question. You're pulling the snapshot and not the video feed. I was wondering how you managed to convert a RTSP feed without 3rd party interaction like Blue Iris or something but you didn't.

I'm very curious how you got the Unifi Video stream to display in a browser. Are you running Unifi Video or Unifi Protect?

My StelPro's have a "lock" feature that prevents manual changes. The NuHeat is programmed so if it's changed within a matter of seconds it's changed back. No thought, no worry and no noise. However if someone was messing with my T-Stat I think I would enjoy their noises of frustration trying to screw with my stuff!

No. He has it setup so that if the set point is changed then it announces the new set point. So if someone changes the thermostat he wants to know and wants to know right now!

I've seen you mention this in a lot of places and it always makes me do a double take. Why do you do this? And more importantly why are people touching your thermostat's? Also, why not program them so people can't change them. If they get manually changed they get reset back to whatever you have programmed. This ends all problems right?