xlurkr

A couple of days ago my Polisy spontaneously restarted - I heard the chimes. It was probably due to a power glitch I observed at about the same time. After that, not only couldn't I access its ISY via the Finder, I couldn't add it back after deleting it. Another reboot seems to have fixed it. I also have a 994, and it was also unreachable, but after I rebooted the Polisy, I could reach them both. Weird. And like carealtor, I've always had to add the Polisy, though Finder can usually find the 994. Lesson: keep those URLs handy so you can manually add them to Finder whenever you need to, which might be often. There is a save button, but I've never used to recover the addresses. -Tom

As an outsider, let me just comment that this could serve as a textbook example of thread drift in the future. Pretty sure there's no connection between the 300 series dongle and COVID. -Tom

I don't know how I missed that Michel misspelled Insteon in fix #1. I guess the love affair is truly over. -Tom

Glad you tried! I would have been afraid to. Yet another option for moving forward. I have one of these sitting in a drawer. This plus Polisy on WiFi= one outlet (and it could be a noisy, signal-sucking one), no hardwired network port solution. Probably just what somebody needs. -Tom

I moved across country for an extended work assignment, left my ISY at home, and took my Polisy with me. I bought a USB PLM from Smarthome and the combo is my only means of automation in my rental here, controlling a couple of LampLincs and an ApplianceLinc. I'll be adding some Door/Window Sensors soon. It may be alpha, but it's stable enough to control my small environment here. When you connect via the Java Administrative console, you'd never know the difference. -Tom

Sorry, I've been away from home for a while, and will continue to be for a while. For anyone joining this thread, keep in mind that I'm still using the 300 series dongle (though I have the 500 series in a box) and am on 5.0.16C. It works well enough for my needs now, but someday I'll upgrade and see if I can enable more functionality. At this rate, it'll probably be with the upcoming 700 series dongle on the Polisy, though, and not the ISY. -Tom

Thanks for helping. My ISY is on the other side of the country. I just want to delete the nodeservers on my Polisy, not connect to an ISY. I deleted my ISY's address from the Polisy just now, and I get an error Invalid URI "http:///:null/rest/profiles/ns/1/connection remove/" when I try to delete the 1st nodeserver on the Polisy by clicking the Delete button. I assume that's the Polisy attempting to remove it from the ISY. But it doesn't actually delete the nodeserver from the Polisy, which is my problem. -Tom

I moved and took my Polisy with me, but left my ISY behind. My plan is to use it to control Insteon at my new location. It has two nodeservers on it. At the new location, they both show as "Connected." Not sure why. Anyway, I can't delete them. Are the two related? Is it finding my ISY through the portal? If that's what's going on, how can I delete the nodeservers from the ISY through the portal so I can delete them from the Polisy? -Tom

How are you having the Vera tell the ISY to turn on the load? There are several ways to do this, but a REST command should be possible to implement regardless of how you're doing it now. -Tom

You don't need to upgrade the dongle to run 5.0.16C. That's the last release that supports the original dongle. However, you may find that some of the nodes still won't work after showing up. This is device-dependent. I have a couple of ZooZ switches for which that is true, and plan to upgrade the dongle and firmware to deal with it. It will cost you nothing to try 5.0.16C first, and see if it solves your problem. -Tom

If the switches are linked by being part of an ISY-defined scene, you should be able to send a REST command to turn on the scene, rather than the one light, and it should work like you want it to. -Tom

Sorry if this is irrelevant, but are you sure you're not having a problem of too high of an RF signal to the MSs? With mine, I always need to move them to a location inside of a drawer or cabinet to write links successfully. They will trigger existing links correctly and I can almost always read their status correctly in situ, but for some reason writing updates to them doesn't work unless I attenuate the RF level to them somehow. Others have reported this, too. -Tom

I forgot to add: having an ON level of <100% is really nice built-in Insteon behavior. If the ISY is down, or you want to or need to remove it from the environment, you can still have a low lighting level set with the first press, and go to 100% with the second. I remember loving it when I was first starting out with Insteon and didn't have my ISY, 20 years ago. -Tom

Thanks for the clarification. I only have 6 button KPLs, but I can understand why an 8 button toggles the load on/off by default. There's no off button! I still don't see how variables can fix the following issue: a switch doesn't appear to generate either a control or status event if it is turned on when it is already at its ON level. Without a means to trigger the ISY to know this has happened, how can the ISY do anything to establish the desired state? If you suggest using variables along with not having an ON level of <100%, then I get it. -Tom

This may be true for the non-load-controlling keys on a KPL, but I believe that the KPL load acts like a dimmer or relay, so it will go to the ON level on first press, then 100%, then ON level, then 100%, etc. Looking at the Event Viewer, it looks like an ST event is triggered when the switch is turned on manually ONLY if the status is not the same as the ON level when it happens. If so, it goes to the ON level (whether that is higher or lower than the status; i.e, down or up) and there's an ST command. If it is at the ON level, it goes to 100%, with no ST command. So maybe the solution will involve setting the light programmatically to be 1% away from the ON level, so you will always get an ST command if it's manually manipulated. Also, turning the switch on, no matter what its current state, always generates a DON 0 event, so maybe just look for those somehow. Dimming doesn't generate a DON 0, but does always lead to an ST event, in my testing. -Tom

I think the problem is one I noticed a few months ago - that the ISY does not change the status of a switch when it is turned on a second time. The status remains at the pre-defined ON level of < 100%, if that's how it is defined. I just checked, and if the on level is defined as 100%, and you programmatically lower it, then when the light is turned on again, status correctly shows 100%. So maybe you need to set the light's ON level to 100%, and lower it to wherever you want it every time it is turned ON from OFF. -Tom

Thanks. BTW, "Fast On" is triggered in Insteon by a double click. Maybe that's why there's no double press. If you're willing, please test this. -Tom

@edentel: Sorry, but I missed your response to my Zen32 thread. I think you made it very clear. -Tom

@edentel: Can you detail what you did to get it to work, if anything? Did it just get discovered and create all of the right nodes automatically? I have a Zen32, and the scene controller functions are not working. I'm on 5.0.16C though, with the series 300 dongle. I just bought the series 500 dongle, and am looking for motivations to install it. This could be one. -Tom

OK, so I bought one. The picture shows the nodes that were created in 5.0.16C. The first one (Binary Switch) is the only one that changes under any circumstances. Pushing any of the 4 scene buttons does nothing, other than toggle the LED state for that button. I guess that's the bad news. The good news is that the Binary Switch status is updated instantly when actuated, and it can be controlled by the ISY. So once again, a ZooZ switch has met my minimum requirements. If you have been following my saga, you will know that I now have the 500 series dongle. Some day I'll install it - I'm still worried that my Schlage lock won't be reachable based on others' reports. But then maybe the scene buttons will do something. I'll probably start a new thread at that point, but I'm curious if anyone has been able to get ZooZ scene activations to do anything useful with 500 series/5.3.X or greater. -Tom

This thing looks like it would make a great fan timer controller if it is fully supported on the ISY. The big upper button controls a load. The smaller lower 4 scene buttons could probably be used to both turn on the load through the ISY, and start a timer, so you could get 4 pre-defined timer settings. I'm still unsure if the ISY currently supports scene controllers like this well, and specifically if it would support all 4 scene buttons as control triggers. Control of the LEDs on the scene buttons (e.g. turning off when the timer expires) would be great, but not necessary. Anyone with experience? -Tom

From this post: Scene with only Zooz ZEN23 switches - ISY994 Z-Wave - Universal Devices Forum (universal-devices.com) It looks like scenes and Control as a program trigger were reported as not working in 5.0.15, and I don't see anything in the release notes to suggest that this was fixed in 5.0.16. I have ordered the 500 series dongle and will upgrade to 5.3.3 (or later) when it arrives. Wish me luck on my Schlage lock when I do. -Tom

You might be right, but let's see if anyone else who is still on 5.0.16C can help me out. -Tom

Thanks, but I'm in that post at the end. @asbrilrecommended something, but it's only available in >5.2. Unless I'm wrong, there's nothing in that post that describes how to fix the problems I'm having on 5.0.16C and series 300 dongle. Did I miss something? -Tom

Short story: I recently installed a Zooz Zen30 dual switch. It has a dimmer on top and a relay below. It's only partly working. The relay reports its status when it is manually actuated. The dimmer does not. Both report status when controlled by the ISY, or when queried. Neither will generate a "Control is switched On" (or off) trigger in programs. As you might guess from the observation above, "Status is On" (or off) will trigger programs for the relay, but not for the dimmer. Please give me your advice for getting the dimmer to report status, and for both to generate Control triggers - if it's possible. Note: I'm on 5.0.16C with the 300 series dongle, so my Z-Wave menus will be somewhat different than yours if you are on 5.3.X. Thanks. -Tom