oskrypuch

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

Yep, even the Portal migration went just fine, and the UD app favorites ported across 100% - that saves a lot of time! * Orest

Well, just to relate my positive experience. When PGC went down, I needed to get my Polyglot back up, so made the step I had been deferring for a bit, and bought a Polisy. I was initially just going to use it for Polyglot, but then when I started developing some issues with my current ISY994 and the need to include Z-Wave, decided to do the full migration. I have a large Insteon setup with a working serial PLM (and just started adding Z-Wave, 'cause I have to for the future), and was serving some weather services. I just bought a new Tempest, and wanted to get that up and running too. Did a lot of reading, and punched around the various setup screens, and here I am with my entire Insteon setup moved over, the weather services set up, Tempest feeding it, and I'm delighted. Still have to move my ISY Portal license to the Polisy (using the 1mo free one as per the directions), and then will need to repoint my UD app, it appears that should work without the need to set it up again, but we'll see. In any case, one happy customer. The Polisy certainly seems a lot more zippy. The ISY994 was no slouch, but you can't beat faster, more up to date hardware. And good timing, that my Z-Wave leap will now be solely hosted on the Polisy, no need for later migration. * Orest

And the Z-Wave Plus "plain" products, these are the older 500 series units. Z-Wave Plus v2 is only included in the 700. * Orest

Q: Do you ship to Canada? A: Unfortunately, we no longer ship to Canada. Most items we sell are available from Home Tech Solution, our partner located in Ottawa so you can purchase your Z-Wave devices locally, ~~~~~~~~~~ Yep, looks like they defer to a Canadian "partner", so won't ship to Canada. Will have a look there too. * Orest

Oddly, looks like Smartest ships all over, but not to Canada, or there is a bug in their shopping cart. Amazon will get it to me tomorrow, so easiest. Description has 700 all over it. Thanks for the adapter fit tip. * Orest

OK, headed into Z-wave to complement my extensive insteon install, for obvious reasons. I would just buy the Z-Wave USB stick from UD for the Polisy, but the shipping (to Canada) is twice the cost of the unit! I should have just added it to my recent Polisy order!, But, if I have to splurge on the shipping, I suppose I will ... But, wondering if I could just grab the same stick from a more local supplier. Here is one, appears to be the same hardware: https://www.amazon.ca/Z-Wave-Stick-Assistant-HomeSeer-Software/dp/B07GNZ56BK/ref=sr_1_7 Anyone? * Orest

Disregard, I just wasn't patient enough! * Orest

So, it is getting to PG3 ... Curiously the WeatherBit Weather is showing as a controller of some sort. What am I doing wrong? * Orest

Looks like it was two issues, kind of. The restore reset the password to default. Fixed that, expect it would have blocked PG3's access. Then I deleted the node in PG3, reinstalled, and then I did a Query in the Node Servers menu again to load the node. It's there now. Now just waiting for my Tempest! * Orest

Transitioning to Polisy from my ISY, and surprisingly everything is going pretty well! (the surprise more a comment on me than anything else). I read through the wiki and a number of critical posts here, which I suppose helped. BUT, one issue. To have a look at it, I bought and installed the Weatherflow node (PG3) on the yet "empty" Polisy. Installed fine, I could see it. and play with it. All good. I then restored my ISY994 programming setup, the kind of final step in the ISY migration, and the Weatherflow node server disappeared on the Polisy. Not surprising I guess. I tried to run a reinstall of WF/PG3 from the PG3 interface, but when getting to the choosing the slot step (slot 5 in my instance), that slot is no longer showing as an available target. So, the issue is a mis-coordination between PG3, by my wiping out the WF node with the restore. How do I force a fresh install of the WF/PG3 node in my Polisy? Do I need to delete the node in the PG3 interface, and do a "do over" install? * Orest

Here is my error log, includes a number of attempts to update, and a reboot or two. There are some disconnected modules with pop up no comm errors, that is expected. Thu 2022/03/31 07:23:02 PM System -110020 /TMP/19/insteon.img Thu 2022/03/31 07:26:30 PM System -50001 -6 Thu 2022/03/31 08:15:15 PM System -50001 -6 Thu 2022/03/31 08:41:44 PM System -50001 -11 Thu 2022/03/31 09:40:43 PM System -110020 /TMP/19/insteon.img Thu 2022/03/31 09:45:06 PM System -110020 /TMP/19/insteon.img Thu 2022/03/31 09:53:15 PM System -170001 [UDSockets] RSub:25 error:6 Thu 2022/03/31 09:53:32 PM System -5 Start Thu 2022/03/31 09:53:38 PM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2022/03/31 09:53:41 PM System -7066 ID 00A5 :err=0, tag='id', num=22, nest=6, offse Thu 2022/03/31 09:53:53 PM System -7123 ID 0037 :err=0, tag='control', num=6, nest=4, o Thu 2022/03/31 09:54:04 PM System -7066 ID 0171 :err=0, tag='id', num=22, nest=6, offse Thu 2022/03/31 09:54:04 PM System -7066 ID 0172 :err=0, tag='id', num=22, nest=6, offse Thu 2022/03/31 09:54:04 PM System -7066 ID 0173 :err=0, tag='id', num=22, nest=7, offse Thu 2022/03/31 09:54:04 PM System -7066 ID 0187 :err=0, tag='id', num=22, nest=6, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 00A1 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 0191 :err=0, tag='id', num=22, nest=6, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 00A3 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 01A4 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 01B6 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 01B7 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:05 PM System -7066 ID 01CF :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:06 PM System -7066 ID 01DA :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:06 PM System -7066 ID 01DF :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:06 PM System -7066 ID 020F :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:06 PM System -7066 ID 0235 :err=0, tag='id', num=22, nest=5, offse Thu 2022/03/31 09:54:15 PM System -110022 /CONF/UZWNDKEY.TXT Thu 2022/03/31 09:54:15 PM System -110012 /CONF/UZWNDKEY.TXT Thu 2022/03/31 09:54:16 PM System -170001 [Network] Established Thu 2022/03/31 09:54:16 PM System -60006 n/a Thu 2022/03/31 09:54:25 PM System -251001 RX-U 010B000A03000102 Thu 2022/03/31 09:57:50 PM System -140008 ISY:503 Thu 2022/03/31 09:57:51 PM System -140008 ISY:503 Thu 2022/03/31 09:57:52 PM System -140008 ISY:503 Thu 2022/03/31 09:57:53 PM System -140008 ISY:503 Thu 2022/03/31 09:57:54 PM System -140008 ISY:503 Thu 2022/03/31 09:57:54 PM System -140008 ISY:503 Thu 2022/03/31 09:57:55 PM System -140008 ISY:503 Thu 2022/03/31 09:57:56 PM System -140008 ISY:503 Thu 2022/03/31 09:57:57 PM System -140008 ISY:503 Thu 2022/03/31 09:57:58 PM System -140008 ISY:503 Thu 2022/03/31 09:57:58 PM System -140008 ISY:503 Thu 2022/03/31 09:57:59 PM System -140008 ISY:503 Thu 2022/03/31 09:58:00 PM System -140008 ISY:503 Thu 2022/03/31 09:58:01 PM System -140008 ISY:503 Thu 2022/03/31 09:58:02 PM System -140008 ISY:503 Thu 2022/03/31 09:58:02 PM System -140008 ISY:503 Thu 2022/03/31 09:58:03 PM System -140008 ISY:503 Thu 2022/03/31 09:58:52 PM System -50001 -11 Thu 2022/03/31 09:58:54 PM System -50001 -6 Thu 2022/03/31 09:58:58 PM System -50001 -11 Thu 2022/03/31 09:59:01 PM System -50001 -11 Thu 2022/03/31 09:59:03 PM System -50001 -11 Thu 2022/03/31 09:59:10 PM System -50001 -11 Thu 2022/03/31 09:59:15 PM System -50001 -6 Thu 2022/03/31 10:03:03 PM System -140008 ISY:503 Thu 2022/03/31 10:03:04 PM System -140008 ISY:503 Thu 2022/03/31 10:03:05 PM System -140008 ISY:503 Thu 2022/03/31 10:03:05 PM System -140008 ISY:503 Thu 2022/03/31 10:03:06 PM System -140008 ISY:503 Thu 2022/03/31 10:03:07 PM System -140008 ISY:503 Thu 2022/03/31 10:03:08 PM System -140008 ISY:503 Thu 2022/03/31 10:03:09 PM System -140008 ISY:503 Thu 2022/03/31 10:03:09 PM System -140008 ISY:503 Thu 2022/03/31 10:03:10 PM System -140008 ISY:503 Thu 2022/03/31 10:03:11 PM System -140008 ISY:503 Thu 2022/03/31 10:03:12 PM System -140008 ISY:503 Thu 2022/03/31 10:03:12 PM System -140008 ISY:503 Thu 2022/03/31 10:03:13 PM System -140008 ISY:503 Thu 2022/03/31 10:03:14 PM System -140008 ISY:503 Thu 2022/03/31 10:03:15 PM System -140008 ISY:503 Thu 2022/03/31 10:03:16 PM System -140008 ISY:503 Thu 2022/03/31 10:03:27 PM System -50001 -11 Thu 2022/03/31 10:04:13 PM System -110020 /TMP/19/insteon.img Thu 2022/03/31 10:39:35 PM System -50001 -11 Thu 2022/03/31 11:08:34 PM System -50001 -6 Thu 2022/03/31 11:18:34 PM System -50001 -6 Thu 2022/03/31 11:20:18 PM System -110020 /TMP/19/insteon.img Thu 2022/03/31 11:55:05 PM System -50001 -11 Thu 2022/03/31 11:55:07 PM System -50001 -11 Thu 2022/03/31 11:58:34 PM System -50001 -11 Fri 2022/04/01 12:05:55 AM System -110020 /TMP/19/insteon.img Fri 2022/04/01 12:08:34 AM System -50001 -11 Fri 2022/04/01 12:15:24 AM System -10011 n/a

OK, thanks, good thread, but still no joy for me. Added the -Xmx1024m, looks like that gets cleared on updates. Ensured I cleared the java cache (x3). Downloaded a fresh start.jnlp file, just to be sure. Downloaded another copy of 5.3.4. Identical hang, while trying to update insteon.img. Perhaps I should try to update to 5.3.2 instead? Any other thoughts? * Orest

Upgrading from 5.0.16C. Consistent error, upgrade stalls during the insteon.img file upload, and then shows socket errors as depicted in the second image. Tried rebooting the ISY, downloading a fresh firmware (left unzipped of course) for the correct version (with PLM). Also ran the procedure on a different computer, same issue. Did shut off all virus checking and firewall temporarily (never needed that before). At least the error is consistent. Any suggestions? * Orest

Well, I guess the 20% discount just about pays for that. ? Yes, I've been haunting this place for a long time, but only very intermittently when there is an issue, system just seems to purr along most of the time. * Orest

Thanks much @Geddy Ordered the Polisy, ouch on the shipping to Canada. Oh well. * Orest

<disregard>