matapan

I'm not talking about Nokia Hubs, or having UDI support this. Truth of the matter is that someone reported on this forum it was possible to make a 2245 hub, which is very commonly available, more so than the esoteric PLM's. If there is a way to use them as drop in replacements to the PLMs, UDI would not require supporting this by code changes or modifications. Insteon may be effectively dead, but there are people who have invested a lot of money in Insteon equipment who want to keep their investment going for as long as possible. If no one on this forum thinks this is a good idea who actually can verify the claim made by one poster by replicating the mod, so be it. I personally think there's value in this. If not, I guess there's always Home Assistant.

It does not have to involve UDI at all. There was one poster on this forum who took a stock 2245 Hub, soldered two or three wires on the hub PCB, ran those wires out to a RS232 breakout board and connected it to the ISY without any issues. Does UDI have to support this configuration? No. But there have been discussions about how Nokia hubs can be reworked to support ISY's. It's in the same flavor. If it operates just like a PLM, why does it matter? Especially in light of the situation with PLM's essentially no longer being available.

That’s correct. If you are an installer there is little money in this. You’d be selling them an upgrade to something new and rip out all the Insteon stuff. My comment is for users who cannot find a PLM and need one for their ISY or other PLM depedent module (like an EZIO8SA module) to function.

There is a post here and elsewhere where someone has added a connection between a 2245 hub and a serial breakout board to make a PLM out of it. Unfortunately, the details supplied aren't enough for the layperson to do the same. If PLM's aren't going to be available near or long term and people have perfectly good ISY setups, isn't this compelling enough to repurpose an existing product which seems to be way more readily available? We have information on how to resurrect PLM's and hubs by replacing specific capacitors on the boards. Why is making a hub useful as a PLM any different?

It seems like the likelihood of a PLM Pro release or the return of new PLM stock grows dimmer with each passing day. From reading other posts here and elsewhere on the Internet, it's possible to repurpose a Insteon Hub as a PLM. Why are there no details available in the form of step by step instructions on how to do this? Insteon hubs are more available than PLMs. Sounds like Insteon isn't interested in selling more PLMs. For those who aren't EE majors, it would be nice to make these hubs useful. Anyone willing to share how to do the mod?

Thanks to everyone for their replies. I could not tell from the official documentation what the proper behavior is supposed to be. This gives me a baseline from which to work from to better understand the device's behavior and how to use it.

There seem to be two versions of the Leak Sensor: For the first version: When the leak sensor is in the WET state, the ISY shows the WET status as ON and the DRY status as off. When the leak sensor reverts to a DRY state, the ISY shows the WET status as OFF and the DRY status as on. For the second version: When the leak sensor is in the WET state, the ISY shows the WET status as ON and the DRY status as off. When the leak sensor reverts to a DRY state, the ISY does not change any of existing states set until one presses the SET button on the sensor to clear the WET condition. Is it possible to configure these sensors to all operate and behave the same way?

I recently acquired a set of Leak Sensors. Never having played with any of these devices before, I added two of these leak sensors for testing. For each leak sensor added, three nodes are created, a wet node, a dry node, and a heartbeat node. The initial state of these nodes is undefined after the device is added. When the terminals on the bottom of the sensor are shorted, the Wet node state is set to On and the Dry node state is set to Off for both test sensors. However, when the terminals on the bottom of the sensors are no longer shorted, one of the devices sets the Wet node state to Off and Dry node state to On. The other sensor remains set to the states set when the terminals were shorted. In searching through the forum for posts on the Leak Sensor, one poster said that the Leak sensor needs to be reset after it registers a wet condition in order for it to detect a dry condition for certain revision devices. Other devices toggle the node states as they change. There was also a very complicated post with 3 or 4 programs for using these sensors I could not understand at all with the intent or the logic. Could someone on the forum who uses these leak sensors help me understand if I have some bad sensors or sensors of different revisions that behave differently by version? How are these sensors supposed to work when there is a wet condition and then the condition changes from wet to dry? Is there someone who can explain the logic of the post with the 3 or 4 programs?

With Smarthome done and given the current situation with respect to PLMs, would someone with the appropriate skill set be interested in sharing how one can repurpose a hub for use with an ISY or Polisy. I imagine some sort of IP to serial converter would be required to connect with the ISY currently. Or perhaps the ISY could be modified for use with a hub directly to handle Insteon network communications. There is another post elsewhere on this forum which mentions how Homeseer already uses the hub as a PLM.

Just a thought….. Since part of a hub’s function is to act as a bridge between a LAN and the Insteon network, what are the chances a hub could be repurposed as a PLM? Perhaps by modifying the hub’s firmware? I’m just looking at this from a broad functional perspective. Since most of those inconvenienced already own a hub that presumably works, what are the chances of connecting an ISY or a Polisy to a hub?

Just so you know, the actual company that invested in Smarthome is one that Rob Lilleness himself created, Richmond Capita Partners LLC. I believe it is different from the company you found online based in Richmond VA. The LLC is based in Seattle WA.

The easiest solution is simply to find an Insteon motion sensor. They're available on eBay and other places online even if they're not on the Smarthome site. No repeater necessary, no protocol conversion. The other alternative might be to used a wired motion sensor attached to an IOLinc.

You can find Insteon motion sensors on eBay still. if your setup is primarily Insteon based still, using an Insteon motion sensor has its advantages. The timeout period can be set to different values. The latency of the sensor is relatively minimal. ZWave sensors are also an option, but the sensor may be affected by the number of devices on your ZWave network and where the sensor is located in relation to the ISY. I personally have on Schlage sensor which has a fixed timeout period. That can be a potential issue for certain applications. I don’t know about sensors from other companies. X10 sensors might be a low cost alternative too. The X10 signal is wireless and would require a tranceiver near the ISY.

Yes, that is the menu pick. I am not the only user who noticed nothing happens when activating this pick. Not sure why.

Selecting the menu pick does nothing, as others have pointed out. If the new way to access ISY externally is via the portal, why keep this at all?

So thank you to all who have responded.I have a portal subscription already and accessing the ISY this way is fine. One has to ask why the menu pick for managing certificates hasn't been removed from the Admin Console. It seems to serve no purpose based on the lack of functionality and rationale described here, only serving to be a potential unnecessary call or support request generator. Why not clean up the UI?

First, let me say that I have very little knowledge or understanding of web security. As a user, all I really care about is being able to access the application in question. That said, I have followed the advice regarding the use of ISY Launcher to start the Admin Console on my local area network. I wish to access the Admin Console when I am outside of my local area network.To that end, I have set up the port forwarding necessary to access the ISY externally. I obtained the IP address my home connection uses, then set up an entry in the ISY launcher to access the Admin Console externally. After successfully launching the Admin Console, I get an error saying that my security certificate is expired and I need to update it. In the AC Help dropdown, there is a menu pick for managing certificates, but it brings up nothing when invoked. Found a post from another user on this forum about the same issue with certificate management, but the ensuing discussion is over my head. What is required to access the Admin Console externally without certificate errors? Thanks.

I use a tiny screwdriver used to remove or install small screws in things like eyeglasses. This seems to work best for me.

FWIW, I wrote a test program to try email to text notifications using my T-Mobile number. It worked. I used the default SMTP settings. I did not try testing the message length, just a short text alert. If one were to try Pushover, what would the Network Resources setup look like?

Several users on this forum have suggested trying out some of the node servers which provide specific support for functionality I'd like to add to my existing setup. They suggested running Raspberry Pi as a means to try this out. The way forward for those people who have Raspberry Pi setups wasn't clear to me. I assumed eventually there would be no Raspberry Pi fork when the Polisy replaces the ISY994i. There have been other users on this forum who have tried and use Home Assistant. I was curious about this as well, since it uses essentially the same hardware. Is there a specific setup for a fanless configuration of Raspberry Pi 4B someone can recommend here?

I'm thinking about trying out Polyglot and wanted to know the best place to purchase a Raspberry Pi 4 for this purpose. Any recommendations? Thanks.

Magnitude Lighting makes a line of transformers which I found works reasonably well with Insteon dimmers.

When you see this behavior, was the Admin Console idle for a while? Sometimes the Admin Console loses its connection, even if it does a refresh when you relog in. I find it best to close the Admin Console and restart it. Usually the queries will refresh correctly after that.

I've been playing with ZWave devices of late. Here are some tips: 1. If you have the means to relocate your ISY to the very center of your home, I would do this. You'll generally have more uniform coverage this way over the long run. Having the ISY located in a place with an outlet nearby that's easily accessible makes it easier to add a ZWave device. 2. It's best to add any new devices close to the ISY for the best results. You can always move the device where you want, provided it's within the range of the ISY or a repeater device. 3. Plug In devices seem to have the best range compared to devices installed in wall. 4. If the device you are attempting to manage is located in a place where the ISY cannot communicate with it, either directly or with repeater devices, add some plug in devices between the target device and the ISY to create the mesh between them. The plug in devices don't necessarily have to do anything, other than to act as repeaters. Best to make sure no one unplugs these devices any time so as not to compromise the link. 5. 500 level devices are faster in responding than the 300 level devices. If you have a latency issue where a light doesn't turn on as quickly as you want and it's a 300 level device, swap it out with a 500 or 700 level device. The latency drop is noticable.

I have a few ideas to put forward that I haven't fully qualified. That said, I can't think of any negatives at the moment: 1. Use a X10 motion sensor. They're wireless, battery operated and low cost. Install a tranceiver to convert the signal to powerline X10 near your PLM and I think this might be an easy way to achieve your objectives. Some of the motion sensors have seals to make them usable outdoors. Both the sensor and tranceivers are pretty readily available. 2. Use an older Insteon motion sensor. They have programmable countdown timers. I think the default is 30 seconds but you can adjust the ON time to be longer. 3. Use a ZWave motion sensor if you have the add on Zwave board in your ISY. If you go this route, I would make sure the countdown timer for the ON duration is adjustable to your requirements. I know that with the one ZWave motion sensor I've tried so far, the countdown duration is a fixed 4 minutes and it cannot be adjusted.