stillwater

Thanks for this @lilyoyo1 With all the interest right now in moving from Insteon to Zwave (or adding Zwave devices to an Insteon system), It would be great to have a table that shows closest equivalents to the various Insteon devices -- I had the impression that Z-wave was mostly switches and outlets.. It looks there is more than I had assumed (for example. sensors). I have seen the Zen17 recommended as a replacement for the Insteon IO module. I was wondering are there Z-wave plus or (better) 700 series equivalents to the Insteon Micro On/Off, Micro Dimmer, and Micro Open/Close modules? Though they are not exact replacements I see the Zooz Z51 could work instead of the Micro On/Off and the Z52 instead of the Micro Open/Close. I looked at a few other brands but haven't yet found a Zwave 700 equivalent to the Insteon micro dim.

@Michel Kohanim Apparently yes a KPL button. First sentence of first post from @arshishk was "I have the following program that checks the status of a keypadlinc button, and if the status is On, waits 1.5 hours and then sets the switch to Off."

I don't think we on this forum should get too speculative about what UDI might or might not do if it succeeded in some way in licensing Insteon technology or buying some Smarlabs assets including IP. It does not help UDI if we talk up the value of the Smartlabs IP or assets! If resurrecting the existing product line were going to be a significant money maker the sale Smartlabs was negotiating would probably have gone through. If you look at modern equivalent products they have lots of features the existing insteon products lack -- like (for example in the Shelly pucks) Bluetooth Low Energy or wifi setup, software defined dimmer parameters (for example leading edge vs trailing edge, soft start, etc.). energy monitoring, etc. etc. Now the dexterity of the ISY or IoP makes up for some of that but not all of it. Making the insteon protocol a going proposition into the future would require very significant investment, in my opinion. It isn't impossible that it could work out, but it isn't a a sure thing either, even at a possibly very low purchase price.

By default a Mac will often unzip the firmware file you downloaded. You want to upload the stil-zipped file to the ISY994. Can't guarantee that this is your situation but that's often the problem.

3-4 Insteon devices failing each year out of 53 seems high, unless perhaps they are very old. Do you have a whole-house surge suppressor at the electric service entrance or main panel? If not this is a crucial investment to prolong the life of insteon and other electronic devices. It's been a long time since I made the jump to 5.x but my memory is that it isn't very difficulprocess if you only have insteon. You will need to check your scenes and the controller scene menus after the upgrade. A few programs may indeed need to be re-saved and possibly edited. The good news is there is no hurry to do the upgrade if everything is working for you now. You will definitely need to upgrade firmware and Z-wave interface before making use of Zwave --especially the new and better Zwave products (series 700) which you will want to use exclusively if you move to Zwave.. [I am not a Zwave user and others will have more info on that. I believe that there is an intro to Zwave somewhere either in this forum or in the UDI wiki that would be helpful to you --- maybe search for that.]

I don't use UD Mobile but if it's on an iPhone try disabling notifications for the UD Mobile App in Settings?

Thanks for this explanation. Very sad.

"ISY Serial Controller" I assumed @Michael805 meant a 2413s, or maybe a 2413s+ISY994i, not an ISY 994i

What is an Insteon server? I don't think I've ever used one. The insteon.com website is up.

Of course this means that for those of us that would never use the Shelly Cloud for access to devices have to pay a share of the cost for infrastructure we don't intend to use. Just saying... On the other hand since I am sure the Shelly Cloud is a big part of getting the multitudes to adopt initially, by amortizing the development cost over a bigger number it gets the hardware cost down for those of us who wouldn't use it so maybe it's not a bad bargain.

@simplextech Good thing you chose HTTP rather than COAP because the 2nd Gen Shellies (ESP32 based Plus and Pro) that are (I assume) mostly or completely replacing the ESP8266 1st Gen do not use COAP. On the other hand they allow MQTT and the Shelly Cloud to coexist on the same device (optionally). There are some subtle differences in the HTTP responses of Gen2 vs Gen1 that may require attention also, though it seems in recent firmware these differences have been narrowed somewhat. Obviously you have a connection to a better source of info than me.

I originally looked at the Shelly devices when the Insteon Micro modules became unavailable (Dimmer, On/Off, Open/Close). Shelly had almost the same form factor (maybe a little smaller?) and functionality though of course via wifi rather than Insteon powerline/RF. They also could be separated from the Shelly Web application, which was a plus in my book compared to some alternatives. Ultimately I had enough Insteon modules for my needs at that time. Frankly coming from the ISY/Insteon world the Shelly world was something of an adjustment. @simplextechas far as a node server is concerned, the Shellies are so flexible I am not sure how you would go about configuring them as nodes except to some extent as substitutes for the earlier insteon modules... Looking forward to see what you do with them. I'd tend to use the MQTT mode of communication with them.

Nothing "just works." On the Shelly English Facebook support group right now there is someone who is trashing all his or her zigbee devices because they keep dropping off the network --and replacing them with wifi shellies.

FYI for Forum readers.... Google says Doug Roberson is the CTO of Allterco Robotics US, which I take to be the US arm of the manufacturer of the Shelly automation products.

@Doug Roberson Thanks for the explanation of the Shelly Plug US backlog and redesign. The inclusion of a heat sensor and automatic disconnection on high-temperature in many of the Shelly devices is an impressive safety feature.

@lilyoyo1 Here is the "Features" description from the Python Script in the Github link posted by @Doug Roberson This utility can be used to provision, maintain, update, and keep an inventory of IoT devices. There are many different operations available, described briefly here, and in more detail in the built-in help for the program. It can automatically locate new devices that are in the factory reset state, ready to configure. Each located device can be added to the local WiFi network, using the "provision" operation, or added to specific other WiFi networks, on a per-device basis, using the "provision-list" operation. The provision-list operation can also assign different static IP addresses to each device if required. With provision-list, one or two spare DD-WRT routers can be used as the client connection and WiFi access point, automatically configured at each step to match network SSID of the factory reset IoT device and the target SSID and credentials specified in a list of instructions given to the program. Note that with two DD-WRT devices, the process is much faster, able to provision 1 to 2 target devices per minute. When using the simple provision operation, your computer or laptop will change from one WiFi network to another (to connect to the target device's WiFi hotspot to configure it). Using the more sophisticated provision-list can mean no loss of WiFi connectivity on your computer, since instructions can be sent to a DD-WRT device to set the WiFi SSID instead. The provision-list operation in this mode is generally twice as fast as provision. There are commands to work with the set of instructions used by provision-list to import, view and clear the list: "import," "list," and "clear-list". The concept behind importing and managing the list of instructions is so that the program can easily resume where it left off. The set of "todo" items gets checked off as the program successfully provisions each device and this information persists even if you quit and then restart the program. The provision operation supports only DHCP, while provision-list can setup devices with either DHCP or static IP addresses. Either operation can additionally command each newly provisioned device to take an OTA firmware update to the LATEST or a specific version of software. With provision-list there are many additional features, including setting the name of the device as it shows up in the phone app and in the settings web UI, plus latitude/longitude and timezone on an individual device basis. The imported list of instructions can include a "Group" column, which then allows provision-list to work on a specific set of instructions instead of the entire queue. A mechanism for automatically printing labels, given a small program provided by the user, is available with both provision and provision-list, but additional attributes like "Label" (a free-form text string) can be added to the imported instructions for provision-list. There is a "factory-reset" operation which makes it easy to return a device to factory settings, given it is on the local WiFi network. The "flash" operation instructs local devices to take an OTA firmware update. A database is maintained with all of the newly provisioned devices. For an end-user provisioning devices for use on a local network, the database is tremendously useful for tracking the devices, managing settings and performing OTA updates. For existing devices on the local WiFi network that weren't provisioned using the tool, there is a "probe-list" command to discover their settings and status. For battery-powered devices that are only periodically available on the network, the option --access=Periodic lets probe-list run for an extended period of time looking frequently for the devices. A powerful "query" operation can report on any information recorded during provisioning or found using the probe operation. An "apply" operation allows programming the discovered devices with OTA firmware updates, as well as making arbitrary settings changes using the --settings and --url options. An "identify" operation is available to continually toggle on/off a light or relay, given an IP address, in order to aid in identifying a device. Useful, for instance, with multiple light bulbs in a lighting fixture. The settings from one device can be copied to a new replacement device using the "replace" operation. Having transfered the settings, it is then possible to use "apply" with --restore to reprovision the replacement device. Use the "list-versions" operation to check the available archived versions of prior firmware for a device. The "acceptance-test" operation checks that devices can be contacted in AP mode (factory reset) and toggles their relay, without provisioning them. For a more complete test, choose "config-test" which provisions each device, toggles their relay, and then returns them factory settings.

Conceivably a niche player could economically resurrect the previous product line by paying next to nothing for the rights and having better management. Seems like if a major player were interested they would have bought it by now.

@Idan I ordered a Shelly plug (US) in December and it hasn't arrived yet --though I did receive a Pro 1 -- so it's plausible the problem with your delayed replacement is lack of stock rather than poor organization. It's true that communication is not their strong suit -- I received a partial order and had to inquire by email to be sure that other items were still to come ---but they did respond by email after a couple of days. Their management actively participates in the Facebook Shelly English Support group -- Not as organized as UDI forums but a good place to get the pulse. The eu official support forum seems to have has less corporate response but seems to be more organized. Google translate is useful if you don't understand German...

I did not mean that the Shelly devices were ready for widespread US consumer adoption at this time -- in fact I raised several issues arguing in the opposite direction. Just that someone had done more or less what @lilyoyo1 mentioned. I specifically said I wasn't advocating them. Treat it as a proof of concept. They do it with the ESP32 platform which is widely available to developers. I doubt there are any intellectual property issues. In terms of predicting the wave of the future I suspect Wifi6 plus something like the ESP32 with more flash memory or RP2040 with wifi will win out over Zigbee or Zwave, though you have to worry about performance in urban areas with RF congestion. Or maybe LoRa or something else low power on 433 or 915 mhz will prevail eventually. The prevalence of wifi means that low-end of the market won't be available to fund the more exotic uses. Re Routers and Wifi Access Points -- I have had great success with Ubiquiti Unifi Edgerouter and Unifi access points. (I wish their branding was less confusing!) With several access points for 5G this leaves 2.4 GHZ open for IoT. The only glitch has been with a Roomba -- had to disable some advanced features on the APs that weren't doing me much good anyway. One of the new Wifi6 access points can handle 300 devices at a time. In fact the Shellies are a little more ready for adoption than my post suggests -- for people who don't need keypads and are retrofitting, their existing AC switches will work fine. From my reading of the various support forums it looks like there is abundant activity on Home Assistant to make using the devices more straightforward on that controller. (The changeover from Gen 1 to Gen 2 Shelly devices has put some bumps in the road). Re: No Shelly Switches Yes, I referred to the lack of keypads and meant switches too. As a Bulgarian company they have been more responsive to 230 v form factors and have just come out with their first switch (4 buttons per gang) but nothing yet for North American boxes. From what I have seen their plastics manufacturing is not the best anyway. If you like paddle switches there are high voltage switches that would work fine with no modification. For example the momentary SPDT Leviton 5657-2 (available in all the usual Leviton colors). This could control a single shelly input or 2 different Shelly inputs. And as mentioned the shelly inputs distinguish between singe and double taps and long pushes so you could in theory use it for 6 control inputs. (According to Shelly the i4 will later have additional input combinations with evolved firmware) [By input I mean either the switch input on a Shelly relay or dimmer or the input on a dedicated Shelly input device like the i4 or uni that communicates via wifi to other shelly devices or to a controller] My plan is to use dumb Kyle Touch Plate low voltage switches (either Mystique or Ultra). These are not cheap but they will never fail. I have not seen them close up yet but the pictures look nice (the Classic switches look clunky). You can get them engraved for $$$. And while it probably would be safe to use them with the non-isolated Shelly inputs, my plan is to connect them to the Shelly dimmers via opto-isolators so that there will be zero chance of shock. The Kyle switches are available in 1-8 momentary buttons per gang, with or without LED indicators (need to energize and control these separately). Update -- I received a sample Touch Plate Mystique 8 button switch in the Black color. My spouse said they are "beautiful." Not glossy like the Insteon or Lutron black (which always looks a little brown to me, btw). I haven't tried the engraving though on the Touch Plate site you can order either engraved button caps or engraved switch covers, or both. Touch Plate has been in business since 1946 so there is some likelihood that they will continue -- though this is only relevant for expansion or new houses -- there is no reason to think that these switches will ever break switching low voltage at minimal current (in my case 3 volts at maybe 20-35 ma.). https://www.touchplate.com/product/mystique-series-wall-switch/ (I actually ordered from Kyle Switch Plate in CA before I located the actual manufacturer).

@larryllix Re "Somebody just needs to develop grouping commands (Scenes) in WiFi based devices for less pop-corn effect." The following is just informational -- I am not advocating adoption of these but I am going to try some. I haven't tested this feature but the Shelly switches/dimmers/input devices have "webhooks" and scripting and some scheduling so you can set them up hubless. I vaguely remember the Gen 2 (ESP32-based ) devices have at least 5 webhooks -- so they can send http commands direct to 5 devices. I don't know how much of a lag between commands there might be but probably short if no authentication/encryption is used. There are drawbacks in that most of the devices are not (yet?) UL listed (though they are certified some other places), and there are no keypads (the input devices are designed to hide behind dumb switches) and most of the devices expose line voltage to the switches used to trigger them. A 50 cent photo coupler solves the last problem if you have a DC source -- (an AAA battery or a coin cell would have a very long life because it's only a momentary contact for something like 20 ma) and the input devices code separately for short, long, and double taps. And the Shelly Dimmer 2 can do a lot of tailoring in software (in addition to choosing between leading and trailing edge). But with no heatsinks it's limited to something like 200 watts -- and it's still a Gen 1 (ESP8266) device -- Gen 2 probably will be released by end 2022... The Shelly devices can also post/subscribe to an MQTT broker which would get around the small number of webhooks in the devices but still result in near simultaneous turn on of lights. There is a Shelly cloud but the devices can be set up to operate separately from it (and a router can enforce this gap if you don't trust the Shelly software to turn it off). There are also Shelly LED bulbs but I am finicky about light quality and don't plan on trying them. Also I'd stay away from the "PM" devices that have built-in "power measurement" as they seem to rely on resistors for measurement rather than Hall effect sensors and so generate more heat than they should. On the other hand the company seems to have rapid development cycles with frequent firmware releases and a hardware cycle that seems faster than most competitors so maybe they will manage to survive.

Right, but it could get you through selling the house.

@MarkJames My understanding is the 8 button and 6 button KPLs are the same under the plastic keys, so you just need 2 KPLs of either kind, of any color. May be able to find on (e.g.) Ebay.

@apostolakisl Future WiFi will have features to make it more friendly to numerous low power/low data rate IoT devices.... https://www.electronicdesign.com/technologies/iot/article/21182189/nordic-semiconductor-why-wifi-6-will-be-a-key-component-of-tomorrows-iot Whether this tips the balance to WiFi for HA I can't say. Unfortunately I notice that the new WiFi 6 Unifi Access Points only have WiFi6 on the 5 GHZ band. For my current project (new construction and retrofit with access to stud bays) I am going with maximum ethernet and wired low voltage stuff and some wifi devices (mostly dimmers in light fixtures). Sensors all wired. Switches/keypads will be dumb low voltage so completely agnostic to future technology. This is painful but the alternative was completely dumb with no comms.

One data point re Zigbee vs Zwave -- Nabu Casa, the business arm of Home Assistant, integrated Zigbee but not Zwave into their Home Assistant Yellow box. https://www.crowdsupply.com/nabu-casa/home-assistant-yellow Clarification -- the logic behind this choice is partly that Zigbee is the same worldwide whereas Z-wave operates on different frequencies and so makes more sense to add a USB stick as needed.

Interesting. I would have wanted the ability to separate the load from button A on a KPL. Theoretically if the LEDs became programmable and if one wanted to hack the FanLinc one could substitute a suitable opto-coupler for the LEDs and gain two more ISY controllable outputs from the Fanlinc. Also theoretically, could one write a Node server that would communicate appropriately with the PLM to provide functionality such as these elements that UDI has not included in the Insteon code in the ISY?