oskrypuch

For anyone familiar with the ZEN17, I was unable to turn off the relay driving (p10 & p11), if I did that then there would be no sensing provided on the SW1 & SW2 labelled nodes, at least on the p2=10 & p3=10 settings. I don't need the relays triggered, but I guess the click will make no difference in the garage. * Orest

Well, that is what I did, I removed the device altogether, and then added it, and up came two more nodes. Named them SW1 & SW2. Is Z-Wave "exclude" not implemented yet on the Polisy? (so remove/install is the next best thing) * Orest

I am adding a ZOOZ ZEN17. Purpose is to capture the status of two garage doors, each has a magnetic contact. This will be replacing an IOLinc. I have it set to what I think I need (dry cell contact detection for door open/close sensors p2 & p3 = 7), and disabled the relay drive for the switch for good measure, so no more clicking on shorting the contacts. I can see activity on the event viewer when I short one contact, and then the other, which may be what I'm looking for, at least shows that I'm close ... But not sure how to pick this toggle up in a program. Despite the activity, I don't see any changes on the screen for any of the nodes. Here are the nodes that popped up: It says: ... you'll need to exclude and re-include the device so that a child device is created for the input of your choice. OK, that kind of makes sense, the missing link, the missing nodes -- but I am looking all over for an exclude/include toggle, can't find it. Does that just mean to remove the switch from the network, and re-add it? I know this is basic Z-Wave, but thanks to anyone for help. Unlike in the docs, there is no Remove/Exclude option in this menu. And nothing on the device context menu. Is it perhaps the Add/Refresh button nodes? I did try it without luck. * Orest

I am trying to add ZOOZ ZEN17. ... <moved to its own thread>

Oh gosh, didn't realize that a device identity in Z-Wave is so fragile, in contrast to the "nic" type hard ID on the Insteon side. That would be a real nuisance if you scrambled the IDs. I assume that a power loss won't cause this?? And the ISY relies only on that labile ID to address the devices. Hmm. is there a way to recover the original logical device ID, by manually reassigning it, if it gets scrambled? If not, that means editing all your programs in ISY?? That could be a royal headache. * Orest

In my setup, when I moved from X-10, twelve years ago, that was my very first Insteon switch, in the bathroom. Actually three of them. They are triggered by a motion, and will light bright or dim or intermediate, with varying time outs and ramp rates, depending on the time of day and the house state. * Orest

The other thing, folks talk about including/excluding. Is that a way to force a rejigging of the path to the controller? Presume that is a context option, when you have a device installed? So, that might be if you were rebuilding a full already (physically) installed network. Otherwise, you can just use the Update Neighbors option, assuming that only one device needs fixing. Does the "topology" map list the Z-Wave routing, so you can check the logic yourself? Fun to be a newbie again. * Orest

That would allow you to move the plisy to the installed location, but at the penalty of having to reboot the Polisy twice, each time, unless you have a very long extension cord! I have a lot of program initializations and such, so that would be a pain. * Orest

Yes, that is the first thing I added, the Aeotec 700 repeater. That is all I have so far, so not too concerned about Z-Wave backups thus far! For plug in units trivial to do, but for in box devices I guess you would just keep a 110v plug with a loose wire hookup to get it going? So, let's say I add a unit next to the Polisy (and repeater, it is only 10ft away), I then pull the power on the just added unit, and walk it out to its final location, plug it in/wire it up, and then just let it sit and it will "heal" itself in a a bit? And if putting in a bunch, you want to sequence from closest (first) to furthest away. * Orest

<disregard>

Oh, that is an issue. So if your system farkles, you have to recreate (learn) the whole net on the Z-Wave side, and then you'd have to fix all the references throughout your programming for your devices?? If so, ouch. (for now) Another question. I understand that Z-Wave devices are location sensitive and use something like an internal routing table for best access? But, it used to be (before Network-wide Search) that you had to have the device within range of the primary controller to add it. How do you square that peg? Did you move it to the final location after it is added, and then run optimization? Or, now, should you not power up the device to add it, until it is in its final location? Or, is that where self-healing comes in. I understand that manual heal is no longer available on 5.3 and later. (just read through the Tips & Tricks again) * Orest

Got my 700 dongle hooked up to my Polisy, ticked the option, rebooted. 700 is visible. ? Plugged in my Aeotec series 7 range extender, Z-Wave|Add Device and the Learn button on the extender, I'm connected! Bear with me, this is my first dip in the Z-Wave pool. ? On my way to future proof my mature Insteon setup, and, do have a few trial devices to hook up as well. But, my question is about backups. In the wiki it mentions that you need to create a Z-Wave backup first, then an [ISY] backup. I believe that relates only to the older ISY/500 Z-Wave board? There is no such option in the Z-Wave menu in the Polisy. So, is it correct that the Z-Wave setup is backed'up as well, with the one-step usual File Backup ISY option, if Z-Wave is active? * Orest

Lots of cool stuff coming is good. Thanks in any case. * Orest

I guess you could just SSH in, and watch it once, to be sure. * Orest

Just discovered the default settings page, for NULL, =0 and POSITIVE colors, wish I had noticed that earlier, would have saved me a bunch of time! But, a request, can you also add a custom default color for value is NEGATIVE. Why? I have defined the value -1 as $xc_True (0 as $xc_False), and use that for all my boolean variable states. -1 comes from the old days when boolean TRUE was always all bits set to 1, so with a signed integer it would be -1. Adding the above should be relatively easy. Perhaps you could also consider adding a custom default color for user defined values too -- although that would need a bit of a UI change. FWIW, I'm in the Beta channel on android. * Orest

... but that begs the question, what do you then do to power it back up. I guess, you just power cycle it? * Orest

I'm trying to remember, it was a while ago, but I don't think there was anything pointing a finger to anything. The ISY just became unaddessable by network at random intervals, so backup/restores would fail, program updates, and just being able to log in. I'd have to reboot the ISY. As a first measure I put the ISY on its own sub-lan, and mirrored the port to wireshark to snoop. I also had some old direct addressing cameras, and some open ports. I closed up the UDP gate, and the problems stopped. I subsequently closed up the ports altogether as I migrated to a different system. it is a wild world out there on the internet! * Orest

@kyderrDo you have the ISY open to an external port, or any device on the LAN open to the outside, for UDP packets? If so, close those ports if you can, or at least set them to TCP only. Probes on your router that leak UDP packets, can confuse the NIC in the ISY, even though you likely won't see anything much else going wrong. I discovered that as an issue some time ago. * Orest

Done, and worked. And, no issues with the programs using the "real" node. Thanks. * Orest

I was trying to input my station ID in the PG3 dialog, but I wasn't sure which number constituted the station ID. There is a number on the device, the hub, an ST number, and finally a number for reference on the website, the latter is the correct one, and I didn't hit it until the last. Using the other numbers, by trial and error, ended up with the additional random units defined in my grouping under WeatherFlow, on the admin page. So, how do you ungroup the sub-nodes in order to delete them? * Orest

There is a reset button in the admin applet, but not a power down button. If one needs to power down the Polisy, for example to move it, is just pulling the plug tolerated well? * Orest

I was kind of in the same situation. I finally opted to buy a Polisy, with the intention initially to just serve PolyGlot (and eventually migrate over). But, decided to go whole hog when my 994 coincidentally started developing some issues. Clearly this took a bit of a push, and it is a bit of work, but I'm delighted with my setup now, Polisy running IoP, the portal migrated and the UD app repointed with setup preserved. PolyGlot available through PG3, slick. Secured a couple of spare PLMs, but my first Z-Wave stuff is to arrive imminently, including the 700 dongle. Also set up my WeatherFlow Tempest at the same time. Cool beans! If you do make the move, be sure to first read up on the threads in the Polisy section, and read through the wiki as needed. Folks here were ready to help as well. Makes it real smooth. * Orest

If interested... ZW189 Aeotec ZW189 Zwave Plus Plug in Range Extender Repeater 7

I am just getting set up. Ordered a 700 series amplifier repeater, that was recommended here. Larger area, very minimal mesh yet (covered with Insteon now), so why not -- although I understand the newest series 7 devices perform better in this regard. * Orest

So an S2 capable device just falls back to S0? When S2 becomes supported, presume you have to reregister and use the token code. * Orest