matapan

http://10.0.xx.xx/rest/zwave/node/ZW023_1/query/

Second method is over my head.

I get a 404 error when using the first method.

I had the occasion to turn some circuit breakers on and off several times while working on installing some new outlets in my house. The circuits power cycled have some Z-Wave devices on it. Apparently, power cycling these Z-Wave devices didn't do them any good, as I am getting strange communication errors now for these devices. According to the wiki page article on communication errors, there should be an option in the Z-Wave menu in the Admin UI for healing the Z-Wave network. I cannot find this menu pick or its parent called Tools. Is the Wiki page outdated? I am on firmware version 5.3.4 on an ISY994i with the Z-Wave plus board.

I have the occasion to update device properties on two Aeotec Trisensors I acquired recently. There appears to be a means to set a device's properties by specifying a parameter to be updated along with its value in the Admin UI. There doesn't appear to be a means to view the device property values directly. I think I found another post in this forum which describes in general detail how to pull the parameter values in a script and assign it to a variable to email or text it out. Seems like a kludge if all you want to do is to see the current device property value is set to. Is there an easy way to see the parameter values set for a device? If the script route is prescribed, can someone describe in detailed terms how this is done? Thanks.

I have a six button Keypadlinc I added to my ISY setup a while ago. Recently, I wanted to assign one of the buttons as a controller for a scene, only to discover two of the nodes for the buttons were missing. What is the best way to restore the nodes in the Admin Console. I have no idea how they went away.

What if you deleted and recreated one of the scenes that is failing? Does this change anything?

I'm kind of curious if an extra layer of control causes noticable latency.

I second the recommendation you should just test the bulb with your specific configuration directly. There are many Insteon dimmer revisions, all addressing different issues. Some of them I recall related to specific flickering conditions. You may or may not have the revision that addresses the flickering issues. Bulbs themselves have specific characteristics that cause them to flicker on one circuit but not another. It's beyond my pay grade. I can just share with you my personal experience. I'd just go out and get the bulbs and see if they do the trick or not. If not, hopefully you've purchased them from a retailer that has a good return policy for situations like this.

Not really sure how this thread became a discussion about the Nokia Hub; the title of the thread specifically refers to the Insteon hub. If UDI attempted to purchase the unused inventory from the new owners of Insteon and they weren't interested in selling the Nokia hubs for a reasonable cost to repurpose them as hubs, and they require rework of code on the ISY or Polisy, is there any worthwhile value proposition to be considered for the Nokia hub? As mentioned previously, there is a post from another user which asserts he/she was able to take a stock 2nd generation Insteon hub, connect some wires from it to a serial card and use it as a PLM. If the poster is to be believed, no code changes required. Isn't that a worthwhile avenue to explore if PLMs are not going to be available for a long time or ever from the new owners of Insteon?

I Googled MAX232 breakout boards. eBay has them for less than $5. Some for $1.29. You still have to convert from a DB9 connector to what the ISY uses in the form of a different cable. To me, once this is replicated, it is a solution some enterprising individual like the recap service eBay seller can easily do at an affordable price.

Fixing your old PLM is an option. I've recapped mine. However, there are products other than the ISY that also use a PLM like the EZIOSA8 which require a PLM. PLM's are hard to come by. If you look at the prevailing prices paid on eBay for them, they are like gold unless you get really lucky. There is also no guarantee that replacing the caps which typically fail will resurrect a PLM. I have one PLM which still had issues after replacing the caps. The original poster of the thread I am referring to on this forum reported they modded the Hub and was able to use it as a PLM. No code change on the ISY required. The original poster posted the information about their discovery over a year ago. I attempted to PM them but have not received any reply. I have a number of hubs and would be very interested in giving it a try. We're literally talking about four wires soldered to the hub PCB connected to a generic serial breakout board if the OP is to be believed.

According to the original poster on this forum in a different thread: "It is easy to figure out where to connect the serial just by looking at the 18f25j10 datasheet for the tx/rx pins." "But all I did was connect tx,rx,3.3v,gnd and held the pic32 in reset." For the serial card used: "a max3232 chip breakout board would be good enough." I believe you actually responded to this posting when it was posted a year ago. The proposed mods are above my pay grade in terms of understanding it - I am not someone with an EE degree. Maybe it is very simple for someone who does as the OP alludes in his post.

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.