brockp

This started a while ago on my isy and carried over to the polisy. Pretty simple, every time the device reboots or loses power when it powers on after a few minutes it will shut off all devices so all lights, fans etc all shut off. Any idea what I should be looking for and what is causing that? I don't have an obvious program but I'm probably wrong.

The Schlage Connect locks didn't work even if I put the Polisy right next to them. I ended up excluding them and re-including them. This works perfectly and luckily my user codes do not appear to have been lost at all. I just need to update all the programs now that used them. Same with the repeaters never worked, just exclude include worked just fine. Weird, zwave continues to disappointment compared to Insteon with just being flaky, just too bad it doesn't have the legs and all the accessories available. Thanks, everyone for your suggestions.

Sure I followed the instructions from the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy I restored from backup to the Polisy and then did ZWave restore to the ZMatter board, insteon works without issue as I just moved the PLM. All the other ZWave devices returned from placeholder, outlets, some lights etc. The only ones that did not were the locks (I don't know the real process to 'wake up' And the repeaters. Again nothing in the aeotech docs says about waking up. The only thing I could think of is excluding and re-adding. Not a big deal for repeaters, more of a pain for locks because they are in programs etc. As for trying to add them I use as in the instructions zwave -> Synchronize -> update with interview. And it times out without any progress. Doesn't mater if I push buttons on the door, or run the door lock out (which would normally update it's status). One funny thing I noticed was that if I do run the deadbolt in and out the timeout on the interview increases. Still never resolves.

I'm upgrading to Polisy off ISY. All instion went fine, but Zwave is giving me issues. The primary issues are getting devices off placeholder: 2 Aeotek repeaters (I can probably remove and read) The main pain is 3 schlage locks. I'm not sure how to wake them up. I operate the bolt etc and get no progress when doing Update with Interview. Any thoughts how I can get them back in without doing factory resets? Prefer to not redo all the user codes and walk through all programs an update them.

Sorry if wasn't clear, I didn't get to the migration at all becaues the polisy is so borked. Polyisy isn't running at all anymore thus the errors about IoX (assuming that's the new name for the ISY software on IOX or Polisy). So I can't open the launcher for the version running on the polyisy if I wanted to to update it. I figured might have to reach out to UD as the current Polisy page says to update to open a ticket or RMA the device. I wanted to avoid that if possible, I have 2 days only to do this without causing disruption to anyone else in my home. I'll open the ticket.

I started my process of migrating off my ISY994i/zw pro today. I have the following devices: isy994 w/ZWave 6.82.01 v5.3.4 (I had upgraded the zwave module as required long ago) Serial PLM (Just found RJ45-> DB9 cable polisy, the origonal pre-order version. It was upgrading using the SSH method that did start pg3 and polisy zwave/Matter module for polisy (not yet installed) I want to complete the migration so my understanding is: * backup everything * install Zwave Matter module * move PLM to Polisy * follow instructions on wiki. So I setout to do that and to start ofcourse I try to update my Poilsy using the UI, but I noticed also in the IoX launcher that Polisy is missing. I also noticed that my two node servers are not running, Logs say things like: no module named polyinterface I also notice that my UI says: Version 2.2.13 Status: Connected Frontend Version: 2.2.9-5 ISY Version: 5.3.4 Uptime: 24 Minute(s) 55 Second(s) (c) 2023 UDI Running on Polisy Documentation Clicking on polisy settings never loads anything. I find this odd and ssh in and I see both PG3 and PG2 running: I reboot and now pg3 wont' start at all: ps aux | grep polyglot polyglot 846 0.0 0.1 12832 2304 - Is 18:18 0:00.00 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[847] (daemon) polyglot 847 0.0 2.7 346212 112876 - S 18:18 0:12.94 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot (polyglot-v2-freebsd) polyglot 1371 0.0 0.1 12832 2312 - Ss 18:18 0:00.08 daemon: /usr/local/bin/node[5458] (daemon) root 5492 0.0 0.1 12824 2436 0 S+ 18:44 0:00.01 grep polyglot Looking in pg3 logs in /var/polyglot/pg3/log/ 6/10/2023, 18:45:22 [pg3] error: Getting IoP UUID failed: Error: connect ECONNREFUSED 127.0.0.1:8080 6/10/2023, 18:45:22 [pg3] error: Is the IoX service enabled? The IoX service must be enabaled for PG3 to start. 6/10/2023, 18:45:22 [pg3] info: PG3 shutdown complete with code: 0 So what's hosed? I assume IoX is the new service name for polyisy? What did I do that hosed my setup so bad? I cant start with my migration because nothing is running that is needed and how did I get both pg versions installed at once? Lukly I had only 2 node servers weather and solaredge, and my ISY is fine and I have current backups. Factory reset press and hold the button didn't appear to actually do anything, LED's never changed as in the documentation but I'm happy to just re-image my polisy and start fresh then import my backups and re-create the nodeserveres.

Ok I restarted everything again, now my icetea install on Ubuntu is broken not sure what I did there. Just never loads, BUT it worked this time from the Mac. Which is great because now I'm current and I can migrate to IoP once my dongle arrives. Also I _think_ I have my db9->rj45 cable from my PLM in the magic box of cables, I'll have to see. Hopfully I don't need to find one of those. Sorry for the noise, been leading with this for months. My first download of the firmware on my system was from last year.

I have fought this problem the entire 5 series when I left version 4. Now I am revisiting bcause I just ordered my PoliSY Mater module and seeing the easy ZWave transfer I'm prepping for that which requires upgrading to 5.3.4 What I have tried Local UI (Same version as firmware) from a MAC (wifi) or Linux(ubuntu 22 wired to same switch as ISY) workstation both give same behavior. I have tried multiple downloads of the firmware file, I have rebooted the ISY before uploading, all give the same behavior. I have upped the memory available to the UI: brockp 85727 2.3 3.1 40607200 1029712 ?? S 12:04PM 3:08.13 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Djnlp.application.href=https://isy.universal-devices.com/launcher/isy.jnlp -Xmx1024m <snip> I will say the UI has been very slow/chunky to do about anything in and has been that way for a long time. I am mostly Insteon with some ZWave. I upgraded the ZWave as required for an earlier upgrade, ZWave has generally been unreliable/slow to some devices even with repeaters. All are probably unrelated but sharing because it has never 'felt right'. So looking forward to getting over to the Polisy which currently only run polyglot, but instructions say this is the supported version to upgrade from. Zwave and ISY backups take just fine.

Can confirm Fade Stop appears to work as the my button. Thanks!

We just had Graber blinds put in from a costco deal. We went with Somfy with the Z-Wave Bridge ZRTSI, everything works well on ISY 994i/ZW Pro, Question though is there a way select the favorite or 'my' position from the ISY rather than just all the way up or all the way down? Each RTS channel in ZWave creates 2 nodes, Binary Switch Controller which does all up or all down, and a Class A Motor Ctl, which has a lot of settings but at most just does all up or all down, with the combos I tried. So if it's possible I have not found it and it would be really nice in the morning. Thanks! BTW if your installer uses the new RU30 Jr motors you may run into issues that it can only listen for 4 channels, which is easy to hit if you have more than one RTS remote, maybe a group, and pair it with the ZRTSI. You will get a dreaded confusing up up up down down down jog.

I'm on 5.2 with an PML and updated ZWave module (Thanks!) It fails uploading Upgrade Failed: Failed Uploading File (reported written size is invalid). Re downloaded the insteon firmware etc. no change. Thoughts? I'm upgrading from a mac on 10.15.7

I have for a number of months now had issues where my ISY becomes very laggy, slow to respond, get java IO exceptions in the console and ZWave devices are most impacted. If I try to querry them they often fail, but the common thread is console is very laggy, slow to respond a lot of beach ball of death (Mac). I'm running the latest 4.7.x One thing I did notice in the console log when this happens I get hundreds of errors opening files that don't exist. See the attached image. If I reboot things mostly clear up. But I don't see other comments about this sort of behavior on the forum so I'm assuming this windows 95 behavior is not common? Thoughts?

Am I misunderstanding what Program Lock under options are? First time using it, I added my first insteion on/off outlets. 2663-222 v.44 Brand new from Smarthomes last sale. These have big buttons for manual control and whit little hands around I didn't want them putting devices into link mode. In my isy994i/zw running 4.7.3 If I set program lock under options I'm still able to put the outlet into link mode by pressing and holding buttons and getting a beep. I also verified by putting the ISY into linking mode, and doing the press and hold set on the outlet and the ISY responds but notes that it's already linked. Thoughts? Am I misunderstanding what Program Lock means? Is there another way to get my desired outcome? Thanks

I replaced my PLM with a new dual band PLM and I have not had a problem sense receiving heartbeats.

So given I put in brand new batteries, and I'm still missing heartbeats do you think the newer/faster PLM would help? Or should I just change my timeout to miss two heartbeats before raising an issue? I just worry not just the false positives about issues, but while I have not missed any 'wet' messages when I test, that those messages will be lost also and defeat the point of having the sensors.

Actually on top of that, I should have kept those batteries, Insteaon claims those batteries should be good for 10 years, https://www.insteon.com/leak-sensor

No the leak sensors all use AA's 1.5V,

Brian, The PLM links Table queried from the ISY is 263 entries, PLM info /status says v85 The PLM label is: 2412S Rev 3.1 0852 As for batteries, they were brand new amazon basics, so no lithium like the original batteries, didn't expect them to last as long (though these sensors are new, but some of them are refurbish so who knows how old the batteries were). I still find it strange how the some of the old sensors have no issues, it's only the newer ones I added. I guess I could compare revision/models Looking in the ISY only a leak sensor with no issues is: 2852-222 v00 One that is having issues shows up the same: 2852-222 v.00 So no luck there. BTW these two sensors are within 10' of each other.

So I swapped new batteries in, and I'm still getting unreliable heartbeats from some of the sensors. I might just increase the timeout to see the heartbeat from 25 hours to 50 so they have a chance to send two heartbeats. Still finding as I add more devices that 4.x with a 994pro is getting less reliable. Eg. I have some programs (that I only use when it's warm so only recently found) look for control signals to then take action. They are not 100% reliable, I do have an old PLM, the one that still provides power over cat5 to the ISY. I see lots of reports of these failing, but mine has not 'failed' Do you think I should replace it if I'm missing signals to my ISY994?

I have 15 leak sensors. I use the programs described here: They were installed in two batches. The first half worked perfectly. The second batch, about 4 of them have very unreliable heartbeats. It's very inconsistent. I have moved them to other locations (many have a dual band device within feet) adding access points close by, and the they still have their heartbeats missed. Generally at least 1 sometimes 2 devices are missed in any given day. The first batch still has no issues. Any thoughts? Can low batteries make the heartbeat weak? Am I running out of hoops? Did I overload my 994pro? Thanks

Ok so starting two days ago the symptoms of not being able to communicate with the 2441th returned, some data would appear, random failures. I went to try today (after three days of waking up to a cold house after weeks of working fine (no changes to network) I deleted the device from the ISY tried re adding this failed several times. Did factory reset twice, still fail. I actually have an older 2441TH that was a referb and different revision that I never used. Connected it, same behavior, I restarted my ISY, my PLM, as well as the two dual band dimmers less than 10 feet from the thermostat all with no change in behavior. I had a few acesspoints and moved them around, to try and make a stronger network in the area of the thermostat, it appears to just stop communicating. My non-referb device is less than a year old, so I'm going to call SH support and provide feedback and try to get it returned.

I should stress after I did my factory reset they have been working much more reliably now, enough that I don't worry. Will see how it works long term.

Yeah DTE Energy and Consumers Energy accepted it though their docs say wifi, I think they just saw 'control it form your phone' and it met the spirit of their intent.

Yeah I got mine on sale and then after a rebate for a 'wifi smart thermostat' from both my gas and power company (AC) I actually paid less than nothing for it. Still though now will seriously look at replacing it with a zWave model. I did try pulling power a few time, deleting re-link, it actually kinda made it worse. Then I found in the manual a factory reset. Given I don't use the schedule in the thermostat at all and use the ISY for all of that it didn't bother me at all do that. This appears to made a world of difference, at least back to how it worked when I first got it. I'll see if this is a recurring behavior or not. I'll go leave a review at SH hopefully people read the reviews first.

Ok so a 'node' doesn't always mean an entry in the ISY like the Main, Head Ctl and Cool Ctl?