oskrypuch

<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

I tried deleting the errant nodes in PG3, but I get an error message:

You mean this delete: Only ONE of these station IDs is mine. The rest are what turned out to be just random IDs, matching my attempts to guess what number it was looking for in PG3. If I delete WeatherFlow altogether, won't I lose/scramble all the references in my programming? And, if those other false nodes are still a thing in PG3, won't they just recreate themselves again, anyway? * Orest

I poked around a bit until I discovered the "number" that was needed to identify my Weatherflow Tempest. As a result I ended up with a bunch of (mainly NULL) nodes listed. How do I get rid of the ones I don't want? * Orest

Security is always good, but is S0 really a big issue for a home setting? IOW, should that restrict the devices we pick? Also, does a mixed S0/S2 environment make the S2 devices downgrade to S0? After all, we've been running Insteon for years, which is pretty hackable. Isn't even S0 better than that? * Orest

With Insteon, when a newer device came along it took a bit of time to get included in ISY. Let's assume you are set up with the Polisy/700 dongle, and we are talking 700 series devices ... Is there the same kind of restriction with Z-Wave devices? Or, because they create their own sub-nodes, and you manipulate those directly, does it just work even with brand new devices? * Orest

Hmm, odd (to me) that it doesn't include a PS. * Orest

I am an Insteon old-timer , but brand new to Z-Wave. [disregard] Found the user manual for it. Looks good. * Orest

Yes, that works. The delay is not too bad, but noticeable. I have a large mature setup with hundreds of nodes and programs, it would much more efficient if there were an (items on this) page only download button. Just a thought. * Orest

So I have a few pages defined that logically groups some variable queries and program instances. But these remain uninitiated until I tap on them. For example I have one item that shows the state of the Family room curtain, and it shows as nil for the indication until I tap on it. Then I get the swirly on the next page, and the value is loaded, and shown on the main page. Then that item works or displays as it should. Is this normal? If so, can you add 'force' initiation button on a page? * Orest