apostolakisl

If they look the same you will capture most of the current Insteon users as they expand and/or replace units. If they look different, all bets are off. Most people don't want to have a hodge podge of looks, and if they are willing to have a hodge podge, there is no reason to stick with the Insteon protocol (Nokia) anyway. A descent number of people will gut their system and switch brands, flooding ebay with Insteon devices, suppressing sales of Nokia devices amongst those wanting to keep the Insteon protocol and preferring to keep the look. In short, I think current users will be very loyal customers through the transition if you make the effort to acknowledge them. I'm not sure about this Nokia name either. A royalty will go to Nokia in some way or another. All just to put the word Nokia on the box. Is "Nokia" even going to be written on the switch where someone could see it after install? If it were, it would have to be very subtle and thus what is the point. Is the Nokia name going to pay off? Hard to know. But the devices will cost more for it.

Can always change the name to UDI or something. Of course if it looks exactly the same. . . but you would still want to make them look the same so current installs can add/replace units.

A node server that supports keyboard input through a polisy usb port would totally do the trick. You could use those 40 insteon ir codes or you could program the lirc to recognize, I assume, just about any ir signal. I assume you program lirc then, upon detecting the ir signal of your choice, to produce a key stroke equivalent. If ISY had a node server that recognized keyboard input, then a simple program "if keystroke A" then set lights to x.

You mean to get the 40 IR codes ISY has built in? I have done that if that is what you mean. Though I only use a few of them. I basically have on, off, and 15% for the room light. Nothing else Insteon enabled in there.

@Athlon @xlurkr I have a routine setup in my Harmony 900. I push one button and it does everything. Turns on projector, turns on receiver, turns on (whatever input device I selected), it pauses for 15 seconds, then dims the lights. The only thing I need ISY for is the lights. I am all over having the buttons to watch TV or change the volume. I will often start watching a football game or whatever an hour or so after it starts and zoom through the commercials. Pretty much only a button thing. Changing the volume is also not very voice command oriented. You have to do it in stepwise fashion with voice unless your receiver is capable of going direct to a volume level by some API (mine is not). And I get to leave my hand wherever since it is all rf. And at the end, 1 button and it shuts everything down and brightens the lights. I can push a button way faster than I can say a word and it never mis-understands me or does that swirly thing for 5 seconds before responding. Plus, the remote just has a comfortable feel in my hand.

Yes, that looks like it would work. But, I think I already have everything I need in my old 99i. I only need this for my theater room to let the handheld IR from my Harmony 900 control the lights in the room. Like 3 commands at most. The GC-IRE looks like it would be overkill. Good to know it exists, though. What I don't understand is all the people going to these touch screen devices (phones). What a terrible way to control things. You have to look at the screen, you usually have to push a button to turn on the screen first, and if you accidentally brush your finger on the wrong spot it starts doing the wrong thing. Regular remotes are so nice, especially the ones that use rf to a base station so you can hold the thing in your hand under a blanket or pointed completely the wrong way or whatever. No look, you can feel the button once you get to know the remote.

maybe I can use my old 99i as an ir receiver. Have the ir trigger a network command to ISYoP. Knew I kept it for a reason.

The node server has no instructions for anything but output.

My understanding of ITach IP2IR is that the IR receiver on the unit only functions as a mechanism to learn IR signals, not to generate a specific action based on a specific IR input.

@JTsao Opposite direction. I actually have that and am using it, but that is for ISY to send IR (via Itach transmitter), I need ISY to receive IR. I have a Harmony Elite but also have a Harmony 900. The 900 does not have a network connection so the Harmony node doesn't work as with the Elite. And now Logitech doesn't make them anymore. I could probably get another Elite used, but man, so much work. It would be so much easier if there were an IR receiver for IoP.

I am considering moving ISY to Polisy, but I am using the IR receiver on the 994i unit and don't see that Polisy has any option to receive IR. Ideas?

You can buy the new Polisy and run ISY on it. This supports both USB and serial PLM. ISY running on Polisy is new and, I believe still in beta, but very stable from what I see here on the forum. I am likely going to migrate my ISY to Polisy soon and retire my 994i. Polisy also runs Polyglot which dramatically increases integration between ISY and damn near everything else that has a published API, and some things that aren't published but people have reverse engineered. I have installed over 20 node servers on my ISY now so things like my roomba, flume water meter, sense energy meter, weather stations, etc are all nodes on ISY, the same as an Insteon device is a node.

That is what they are. Look at the label on a 2477d for example. Though I am reading from others that because the rf was in a freq not allowed in Europe they didn't sell there. I don't know, I thought I saw some stuff about them selling products there, but maybe not. Obviously the stuff would work in Europe, but their FCC wouldn't allow you to sell it there if indeed the freq is wrong. I suppose you might be in violation to even use it if you brought it over in a suitcase, but who would know.

What were they taking pre-orders on? The Nokia stuff?

Pretty much always happens like this. There will be rumors (or not). They don't come out and say we are closing in 90 days or whatever. The chaos of the last 90 days (or whatever) would be worse than just "boom" done. There is no graceful way to go out of business. There are many examples where people show up to work on a Monday to find the doors are locked and the furniture is gone. The only graceful exits happen when a company closes a division while otherwise staying in business. Here the shut down is financed by the part of the company that is still in business. Though they should have made an announcement on that last day rather than just shutting down the server.

I'm pretty sure Insteon stuff sold in Europe. For quite a few years now ~everything they sold was 100-270vac 50-60hz.

Hopefully you have the old ones. Replace the capacitors for perhaps $10 total (mostly shipping) and you'll have $500/ea items to sell on ebay. 99% of the time they fail because of the capacitors and it just isn't very hard to replace them.

Success. I moved polisy to the other vlan, it found Roomba, I moved Polisy back to the secure vlan and it was able to maintain connection. Thanks.

With ISY, you don't need to know the Insteon address. It has a discover mode. You just click on the auto discover button on the ISY menu, and then press and hold the discover button on each device. You can do a whole bunch at once. I would start by going through every insteon device in your house and pull the tab out, then press in and hold until the long beep quits. This factory resets. After that, put ISY in discover mode and press the little button on each device and in a second or two ISY will discover it. Label the device in the ISY app. Before you start, I would create a plan for how you will name things and create a folder tree. Life is much easier later on. I like to add an "L" to the end of the name of every device that manages the actual load. Once all of your devices are part of Insteon, then start creating your scenes. You will find that ISY allows the creation of extremely complex scenes, if you like. It can get confusing because there are so many options. But in the end, you will appreciate it. Understand that each scene has one or more controller devices. A device can control only one scene, but respond to as many as you like. Each device will also have local settings. Meaning that when you push that device's switch paddle, the local settings are what happens, any scene to which it is a responder or controller is irrelevant, the local settings is what that device does when you control it directly (locally). Then there are the settings when the device is the responder to a scene. They can be the same or different as the local settings. Lets take an example, you have a 3 way. Each device is set as a controller to the scene. You want all 3 switches to do the same thing. Within the scene, you set each device to respond as you like (all the same). You then need to set each device independently to do the same thing when locally controlled. The beauty of this is that it doesn't have to be that way. You could instead make something different happen when you touch each of the three switches. A single scene with three controllers could do different things when using each of the 3 switches, if you like. Anyway, in short, factory reset, add devices to ISY, and have a clear plan of organizing them before you start.

Hubs work as really powerful access points. Much better than actual access points. I use a couple for that purpose, I do not use the hub as a hub at all.

Life is a lot easier if you do it my way. 1) tape off the back of the unit with some painters tape except the region of the repair. 2) Melt the solder with your iron from the back 3) Blast it away with an air compressor 4) Repeat on other terminal 5) The old will slide right out 6) Slide the new without trimming the leads, the air blast method leaves the hole virtually 100% free of solder so it goes in easy. 7) Solder it in using a spec of flux Spin the extra wire around and back forth for a few seconds and it will snap off at the solder 9) remove tape, check for solder splatter and clean if needed, also clean with q tip and alcohol any flux residue.

Well if it can be figured out that would be great. My father in law has an insteon thermostat which he needs the hub to control remotely. He had some insteon cameras as well but I'm not sure if any of those work anymore. But I know the thermostat does. If the hub can not be hacked to work as a remote interface anymore, I'll dig out one of my old ISY's and set it up at his house. Trouble is, I'd have to let him use one of my spare PLM's. . . which gives me pause.

All the power to him if he can hack the access point, er I mean hub, and make it work as a hub again.

Would be curious to know just how many active hub users there are. Seems like it would be many thousands, not hundreds.

You need to stop thinking of it as a hub. It is an access point. The best access point, better than the access point that is called an access point. I just stumbled across it because I needed some lamplincs and someone was selling a brand new kit of 2 lamplincs and a hub for less than the two lamplincs cost by themselves. So then I had the hub, just for the heck of it tried using it as an access point and was pleasantly surprised. Been running now for maybe 5 years, maybe more as the only plc/radio interface at my church activities building. The ISY and PLM are in a different building and the plc runs to building number two by what basically amounts to a 150 foot extension cord where it plugs into the hub. Without the hub, there is zero com at building 2. Neither plc or radio is detectable in building 2 without it.