apostolakisl

FYI, hubs also die from bad caps. I fixed one just for fun. I use a couple hubs to help with long range Insteon radio. It seems that the radio in the hub is much stronger than the radios in all other devices. Could be just other random issues, but I use Insteon thermostats at my church. They are radio only of course. I tried using multiple dual band plug in modules first and had dismal com. I tried a hub, and it is flawless. The radio covers a distance of maybe 100 feet through metal stud walls.

Well, just the devices made by Universal Devices (UDI), the company whose forum you are writing on. The trouble is you need a plm to interface the UDI device with Insteon and the PLM's are only made by Insteon. Pretty much that means ebay for a used/new old stock. I would suggest getting a polisy because it supports all PLM's (USB and Serial). The Polisy is a newer product and is, I believe now in beta, but I think you will be fine with it. You could get an ISY 994i but then you will be limited to the serial plm (unless you want to hack a usb/serial adapter for it). But Polisy is the future for UDI so I would go that route. I imagine the 994i will stop being supported in maybe 5 to 10 years. Of course ISY/Polisy can control and interface a myriad of other products, the most widely adopted one being z-wave, but there are tons of other things. Polisy is the name of the hardware device that the controllers run on. The base controller is ISY, which natively handles Insteon and Zwave. I believe z-wave radio comes standard with polisy with the option to purchase a stronger radio. Of course the Insteon "radio" (PLM) is as discussed. 994i base model does not have a zwave radio. In addition to ISY running on polisy, polyglot (PG) is a separate piece of software running side by side with ISY on Polisy. Polyglot serves as the middle man between all sorts of things and ISY, pretty much anything with an API. Things like weather stations, Tesla, Roomba, camera software, pool control systems, alarm systems (DSC and Elk) and on and on. UDI also hosts a cloud service at a minimal cost. This is optional but allows for access to your ISY from outside your LAN without port forwarding your router. It also manages synchronizing ISY with Alexa and Google.

One of the many reasons I hate cloud based services. Whenever I consider buying a cloud based device, I ask myself if I would be OK tossing it in the trash in a few months. If the answer is no, I don't buy it.

Not sure how relevant the patents are. Without the source code, the patents might not do much for you. I don't know. A big part of the profitability question is how expensive is it to make these devices? Seems like to make money you would need to have manufacturing costs at no more than $10 for a 2477d. Somewhere, I assume there is a pallet full of the proprietary Insteon chips. I kind of doubt that running out of those chips was the end-of-Insteon production point. Seeing as those chips are custom they would have run them in batches and no one else can use them.

@stillwater Could just be the asking price.

I wonder if there are creditors. This may have been venture capital and is just lost money. If there are creditors, this will likely all go to auction. I am a bit at a loss as to what the strategy is. Someone is gong to offer at least some amount of money for the Insteon technology. And any money is more money than no money, so why would it not sell? It would be a real shame. The Insteon protocol is so versatile and most complete of any I have seen. The myriad ways to set up scenes and whatnot is pretty much unmatched. Combined with ISY, it just works. And dual band com, in my experience, is nearly flawless. And of late, the quality seems to be great. It seems like they finally got it figured out, but a day late and dollar short.

I can't see how anyone even remotely serious about HA could go with wifi. You would have to have enterprise grade wifi to support all those devices. Wifi is just fine for a few toys around the house, but not HA.

It sounds like someone is bankrolling them, losing money, and just wanting to cut their losses. So no bankruptcy auction of the patents etc. But I can't imagine why they wouldn't agree to license the plm chip to you. How would that be anything but money in their pocket minus some attorney fees for drawing up the contract??? It may be a small negative to someone wanting to buy the whole lot of their product technology, but some simple time/quantity limits would take care of that. We appreciate your interest in making the plms and supporting your customers.

Are they in bankruptcy or are they solvent but just shut down? Are they selling their patents and secret code? If they are in bankruptcy then these things would be for sale by court order.

Website works, but as far as I can tell, everything is either sold out or sends you to amazon. We shall see who comes away with the technology. I assume someone will. In the meantime, I have plenty of spares. Wonder where Nokia comes out in this? Nokia website for the switches looks to be taken down.

The router wouldn't have any issues. I have set it to allow com between polisy and roomba bridging the two vlans. The only question is if the node server will try to re-discover roomba when (if) it senses that its subnet has changed after I return it to the more secure vlan.

Would it keep the ip address if I moved polisy to the Roomba subnet and then back again?

I would install a proper security system based smoke detector which can then easily be bridged for "informational purposes only" to your ISY via lots of methods. DSC alarm panels are quite inexpensive and UL listed and all. The smoke detectors themselves will likely cost far more than the alarm panel depending on the quantity. Linking DSC to ISY can be done with polyglot and an IP adapter for the DSC panel. If you already have a standard smoke alarm system that is just a local, interconnected, siren only type system, often they do have models with relays that can bridge to an Insteon, Zwave, or other IP based contact closure device that will link to ISY.

@bpwwer I have an i7. I keep all of my iot stuff on a different subnet that is firewalled from my important stuff. When needed, I open a path between two devices, which I have done between polyisy and roomba. I had the pg2 roomba node working, except it really doesn't work on the i7 very well at all. I also have polyisy talking to my blue iris server using the same firewall hole technique . . . so I am confident there is no firewall problem. I was hoping to use your pg3 node which appears to be expressly made for i7, amongst others. But the autodiscover does not seem to be looking across subnets, the node server log lists it as giving up after several tries and not discovering. Anyway I can tell it where to look or set the ip address manually? Thanks.

OK, getting them now. Sent a note to support.

"long time". Not sure what that means. But I am now at 3 hours.

I don't know. Not getting any email. Checked spam and all. my login name is my email address. Searched my email for that ircodes@. .. email and I see they sent me one 5 years ago. So I must have been playing with it back then. but not working now.

Not that I need any right now since I already manually learned them all on my own, but how does the website work? I already had a user/pass with them. I click to get it, it says "sent" . . . sent where? I didn't get anything in my email, no download, where? And as it turns out, the primary device I use GC for is not in the database. So I'm copying them from where I figured them out into the format GC wants. I am seeing that you did it this way because I assume it is how they come formatted from GC.

Deleted ISY from PG3 and re-added. This was my very first installation of PG3, so I had no nodes installed to screw up by doing that.

First off, very happy to have the node server. Not complaining, trying to be constructive. So many different situations with node servers because of the vast differences in node specific needs, so my comments are more to the general construct of PG, not to this node. I get it, PG is this generic template. The whole concept of the manually entered key is just not a user friendly situation. It isn't the end of the world, but it isn't really a GUI and everyone wants GUI's. Lots of directions to read and then you must manually type in "keys" precisely as expected and wondering "was the colon part of the key?" type stuff. The general format for these sorts of things are that all the "keys" are already there. Makes it obvious what info needs to be entered for values. With this particular node server, the value has the potential to get out of hand. For example, lets say you have 25 ir codes for a device, trying to input that into the format of "key" / "value", well that "value" line will be insane. You'd have to do it in a text editor and copy/paste it over. Lots of opportunity for screw ups, getting all your commas, quotes, and spaces right. Which is where I am now as I am adding my 5th "button" to the same device and plan to add about 15 to that device, with others to follow. Within PG, a system where you have radio buttons to push "add device", then "add code" would be more typical GUI stuff. Obviously, with iTach, you have these crazy *** codes that are generated for each and every ir message in the world. And unlike every other universal remote, which keeps all that code internal, itach keeps none of it onboard, instead requiring that you send the crazy code with each request. So, yeah, tough. Now I don't know anything about "control tower", I have actually been using my itach for a good 7 or 8 years as is without need to change anything, so maybe this is something new they added to simplify the ir code retrieval. All my codes I had to generate myself, which was a PITA since often times they didn't work. A lot of trial and error. What I have done here is just copy/paste the codes over from where I saved them on ISY network resources. I totally didn't need to install this node server, but I prefer using nodes to network resources, and I am also a glutton for punishment . . . screwing with things that work perfectly fine and breaking the golden rule of "if it ain't broke, don't fix it". Oh well.

The screen shot was the most helpful, but you can't put that into the Node server display, I'm sure. Where things get unclear is whether things like "" symbols, or , symbols, or spaces are part of the language of explanation or part of the actual parameters. Often times people use the <> symbols to make that clear or if you could change text color or similar to make it clear what actually goes there. Finally, just a general polyglot comment. For this thing to really go mainstream, need to get rid of all this manual configuration of "key' and "value". Needs to have custom menus for each node server with pre-labeled slots, drop down's when appropriate, and then once configured, have it displayed in a more user friendly format. Basically, something like the polyglot ISY config page where it has pre-labeled slots for all the parameters like user, password, ip, port, etc.

Just spent some time with some trial and error. Anyone setting it up might find my experience helpful. The basic theme is that each device/ virtual remote occupies a single custom parameter. So if your TV has 20 buttons to control, it is just a single line with the "key" being the name of the remote (ie TV) and the "value" part being a very long single line of 20 commands one after the next. The format allows for 2 codes per button. If you put nothing for the second code, it just does the same as the first code. You can not eliminate code 2 from the drop down menu by not including "code2, hexcode2" in the preamble part of the "value" section. Here is an example of 2 buttons I installed for a single remote. Note the double space between the two buttons. The precursor part of <function, code1, hexcode1, code2, hexcode2> is just entered once at the very start of the "value" section of the custom parameter, from there on, a double space between each button setup. function, code1, hexcode1, code2, hexcode2 "whole house on","sendir,1:1,1,38580,1,1,19,177,19,177,19,177,19,178,19,178,19,178,19,274,19,178,19,178,19,178,19,274,19,3858" "whole house off","sendir,1:1,1,38343,1,1,15,180,14,181,19,176,19,176,19,176,19,272,19,272,19,176,19,176,19,177,19,272,19,4907"

Never mind. I deleted it and re-added and now it shows the nodes.

I did put the isy info, ip, username, password, and it says "connected", since I don't know what else it would connect to, I assume this means ISY. It also lists ISY as 5.3.3 which is correct along with the correct UUID, neither of which were entered by me but rather discovered.

I just installed and ran PG3 on polisy. It appears to have connected to my ISY, it says "connected" and it lists the uuid of my ISY in the settings. However, on the dashboard, it lists no nodes, unmanaged or otherwise. When I try to add a node , it asks me what slot and the drop down makes any number I want available. Should it not see that I already have nodes (from PG3 and IoGuy) occupying many of those slots?