ctviggen1

Thanks for the fast response. Hmm...it's in at least 3 programs: a going to bed one; a "normal" daily routine"; and a guest routine (to lowly light the hallway while guests are upstairs). I'm plugging it in again.

I went to install something neat a lamp that's in our upstairs hallway. The lamp was plugged into the outlet, but in the outlet also was an Insteon plug-in lamp module (lamp not plugged into the module). Using the address written on the lamp module, I found that the module is called "Lamp upstairs hallway". I assume I had it programmed at one time, and then someone unplugged the lamp from the module. Is there a way to use the address and/or name of this module to determine which program(s) it's in?

We got a new front door. The "old" (different model) zwave lock didn't align with the new strike. I had another ("new") zwave lock, which I tried on the front door. (Alas, also doesn't align with the strike. More work to do.) I'm keeping the "new" zwave lock, however, and I'll put the "old" zwave lock on a different door, some day.... Should I put the batteries in the old lock and "officially" remove it from my system? Or just wait to put it on the other door (could be a while)? Also, I have a "phantom" "entry control". I was trying to add my new lock and did it incorrectly. After adding, removing, adding correctly the new zwave lock, I still have this phantom entry control. Can I remove this?

Hi Geddy, Thank you. Were is the "My ISY"? I got both computers working without the error. I thought I had already removed the applications and reinstalled, but I guess not. Once I removed the applications and reinstalled with the latest start.jnlp, everything went back to normal. And zwave is back to normal too.

I found it. I guess I have to bookmark this: https://forum.universal-devices.com/topic/24381-iox-launcher/

One thing I don't understand: Where do I get the latest start.jnlp? Don't I need the latest version?

Thank you. It's on a different computer, but I'll try these this weekend.

I'm on IoX v5.8.0 (2024-01-01-10:29:02). Just upgraded to the latest software/firmware this morning by upgrading packages. Any idea what this message means and how I debug it? It came up a few times before the upgrade, then went away. By the way, I had upgraded a few days before, and then my Z-wave went completely offline. Did not realize this until none of my Z-wave worked, including my door locks. (I may have to change them to automatically lock by themselves. Not fun to have doors that don't lock.) A reboot did not fix, but removing the power and putting the power back in, along with the upgrade, seems to have worked. Not sure if this is related to the current error or not.

Yes, before your note (thank you for it though), I was able to click on the Network folder and then that brings up a "Network - Managed Scene" window. A view of this: I then clicked on "Address" and it arranged the addresses so all the Zwaves were together. I then turned on and off the device a few times until I found the device, which had a name like "ZY 005..." and then I renamed it (as foyer lamp) and used it in my programs, replacing the old "foyer lamp" (now called "foyer lamp (old)"). The problem is that I have ZW and ZY and the ZWs are actually "real", here's a portion of the table: Should I have all these ZWs? If not, how do I get rid of them? And I don't even know what a lot of these are, no idea what or where ZW 18, 19, ZY 2 even are. I THINK the ZW 16 and 17 are small on/off plug ins that I have turned on and do not control, and are there just because they are within a short distance from my front door lock, which was having issues due to poor zwave strength (I think, anyway). I will use the folder technique, because for what is now my "foyer lamp", I have five entries, of which only one does something I need it to do (turn on/off). For my "old" foyer lamp, it was dimmable instead of on/off, it also has five entries. And I'm only keeping it to make the network stronger, as it no longer dims correctly (it causes the light to flash). But this shows what's up: I'll move all the stuff I don't use to a folder.

Thanks, that is helpful. I realize that I have tons of ZW and ZY entries and have no idea what they are. ZW16 - ZW 19; ZY 2, 4, 5, 6, 7, 8, 12. I will have to work on those first, then maybe try to figure out what the reals ones are, one by one.

After the time change, all of my programs were disabled. I had to go in and re-enable all of them. Any idea why this would occur?

Thanks, all. I tried finding the single zwave on/off module by turning it off and then on, and couldn't find it. The problem is that zwave modules aren't highlighted (relative to Insteon, which I have tons of). So, if I named something X, and don't remember that I named it that, I don't know that it's zwave. It's possible I could print out all of the devices and whether they are on or off, with the one zwave module being off, then do the same with the one zwave module being on and find it this way. I just am unsure how to do this. I have never named a Zwave module anything but a real name, like "main foyer lamp". So, if these have a name like ZW or ZY, I didn't add them. And I thought I reset the system when upgrading to prevent this. I guess I didn't.

I should say that I don't have much "real" zwave. Three ceiling fans, two door locks, one to control my main foyer lamp (and I could use Insteon to control the lamp, but this plug is close to the front door, so want to use zwave to make the network stronger). I could therefore reset the zwave network and re-add everything. I'd prefer not to do that, though, as then I have to find all the programs that use these and redo those too.

Yes, I am on the Zmatter dongle. How do I get rid of the ZW? Basically, I have a zwave on/off device connected to a lamp. How do I know which device that is? With Insteon, there's a network address you can use that's physically printed on the device. I don't see that for zwave devices. If you don't use that, when I installed them, I only added a single device at a time. I would then rename this, eg, "main foyer lamp". This would let me know where it is. The problem with these zwave devices is I added them for the sole reason of making my zwave network stronger around my front door, which has a zwave lock that wouldn't work .... sometimes. I was trying to strengthen the network, and just blanketed the area. I just plugged them in and that was it. I didn't care what their names were or where they were, and I didn't use them to control anything. Now, I want to control one of them that I moved from an outlet to the main foyer to control a lamp. But I have no idea which device this is. Does that make sense?

I upgraded a while back from ISY 994. I have both ZW and ZY devices. Should I have both? If so, what's the difference between them? I bought a bunch of plug-in Zwave devices to put near one of my doors with a Zwave lock. Normally, I name my devices so I can find them, but since I bought so many Zwave plug in devices, I didn't name them. So, I have ZW 016, 017, 018, 019, and ZY 002, 004, 005, 008, 012... One of these is a dimmer that is connected to a lamp but is causing it to flicker. I can find this one, because it's part of a program. I removed it and replaced it with an on/off plug in Zwave device that was not controlling anything, just there to help the Zwave network. How can I find that device?

OK, I'm trying to set up a program that will let me know when the front door is unlocked due to no status update. I have a program that is the following: If front door lock status is unlocked then wait 15 minutes and set front door lock to lock This is called "Front door normal". I'd like to set up a program like this (pseudocode): If "front door normal" program is not running AND every 30 minutes then query the front door lock if the front door lock status is unlocked, generate an error message The "If 'front door normal" program is not running" is there to prevent the program from accidentally querying when there is a status update and the program is running correctly. I can see how to do this part: "If program 'front door normal' is False" should work, I think. One problem is that I see no way to schedule a query every 30 minutes. The only thing under "schedule" is "time is" and then a time. There's no way I've found to schedule something to happen every so often. The second problem is that I don't know how to generate an error message. There's a "notify", but the only selection is "default", and I don't know where to set that or how to get that to notify me.

Have you manually tried querying the lock from the admin console? When I try this, I click "Query"...then nothing happens. That is, there's no indication that a query is doing anything. So, the idea is that you query the lock every so often (15/30 minutes), and then would lock if unlocked? My problem seems to be more intermittent. For instance, I can see the admin console on a computer from where my front door is. I went and unlocked the front door, and the status basically immediately updated. Then I locked the front door, and again the status immediately updated. But sometimes I walk past the door and the door is unlocked. The only time we go out the front door is to walk the dog, so someone took the dog for a walk, and the front door never locked. And I've blanketed the area around the front lock with Zwave devices that are mainly there just to communicate with the lock. And I bought the IoX and moved it closer to this lock. That definitely helped, but I don't think it's cured it. I did buy the other lock, but I could theoretically use it elsewhere if the current lock would work correctly.

Yes, and these are very hard to test, unless they fail all the time. My front lock fails only...sometimes. I realize when going to bed and walking past the front door, that it's unlocked. The auto-lock feature is okay, except that I have a program for our basement door that does not lock the door for something like 3 hours. This is because we're in and out of the door too much, say having people over, or doing work that involves tools (and the basement is where we keep tools). For a "normal" door, this works well.

I also have an issue with my front door lock, a Kwikset Smartcode 916. I have a 10 minute delay before locking, and this works...most times. Sometimes it doesn't. I had the same lock on my basement door. The front door is north-facing, but the basement door is south-facing. The Kwikset lock has an all-glass front. The rear door's glass started degrading over time. I replaced this with a ULTRALOQ U-Bolt Z-Wave, the cheaper model (not the Pro). This seems to work well. I'm thinking of replacing my Kwikset with another ULTRALOQ U-Bolt Z-Wave. Warning: They say that all you have to do is change out the lock, but the the lock did not align with the latch. Then when I used their latch, I mis-installed the plate they give for the latch, by a tiny bit. I then had to go out and buy a different latch plate, and install that. Took well over a day to do. Multiple days.

Thanks. I attached the EISY to a joist in my basement, which was near a preexisting outlet in the ceiling and also between the two Zwave door locks I have. The original location of the ISY 994i (which the EISY replaced) was too far from the front door, causing intermittent issues. This location (and probably different Zwave hardware) has resulted in many fewer issues. I was able to unplug the transformer using a ladder. Turns out this is also on the breaker for the fire alarms, which I found out when I changed out an alarm. I could do that too. Sorry -- I didn't realize that the ticket would be for them to troubleshoot. I just thought a shut down and reboot seemed reasonable.

Unplugging the EISY then plugging it back in did work. I found all the devices and was able to lock the front door using the admin console. I couldn't see a way to do a clean shutdown. There's only a "reboot" on the admin console, no "shutdown". And I figured there's not much difference between a reboot and unplug and and unplug without rebooting.

Thanks, I'll try that when I get home (I'm at work). For the power down, is this just a removal of the power plug? Or does the admin console have a shutdown? (My EISY is in a place that's a bit tough to get to.)

I upgraded to 5.6.4, and now nothing on Zwave works. I'm not sure it was the upgrade, as the front lock MIGHT not have been working before then. I have limited Zwave, only one light, ceiling fans, two locks. I cannot control or query these from the admin panel. I was getting various errors when I queried these. Current error for queries is "Request failed". How can I test whether the Zwave module/card works? Or whether it's the software?

This particular upgrade was weird, because my admin console did not go away. Often, the system reboots. This time, I got the same message that you did, that the system had to reboot, some minutes into it. Also, the "Upgrade packages" is a little strange, since it doesn't necessarily mean "install new firmware" (since there's also an "Upgrade BIOS" button -- aren't firmware and BIOS the same thing?

That's an interesting idea. I have never used variables. I'll have to look into these. I have not set up UD Mobile yet. Mainly because we run everything through Alexa, which my wife also has on her phone and she can control everything too. At some point, I'll get to installing that. I'm too far into Alexa to stop now. We can say things like "watching movie", and a bunch of lights go off and on for movie watching; my kids use it to turn on/off lights and their ceiling fans; we have a "dog lights", which turns on at least 4 different sets of lights to light up the area at night while the pup goes out. I resisted Alexa for a long time, but once you get used to it. it's hard not to have it. I also don't know what will happen when we sell the house. Most people wouldn't know how to program the EISY. I have an MSEE, so it comes relatively easy to me. For the program I'm using now, I realize I can also disable some things while we're away, like a towel warmer. Nice to have when you're here (and dries the towels during the summer), but a waste of energy when you're not.