johnnyt

almost forgot: double clicking (fast on / fast off). adds so many possibilities. I use it a lot.

+2 for 8-button keypadlincs. haven't found anything comparable out there insteon scenes work really well. zwave not even close. (only know about those two) dual band certainly helped with the above, among other things would love to see more speed if that's possible (to add to the talk of expanding capabilities)

I've created a lot of specialized log files using the ISY's web server module and "Dynamic/Custom Page Creation" functionality described here: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic.2FCustom_Page_Creation and every now and again I spend 20 minutes or more, downloading/archiving and resetting these custom log files. If I don't do this often enough, they do eventually drop old data to put in new data in so I lose some of the history. I would like to automate the download/reset task. Basically write a script to go through each web server file, download it, append the date to it, save it, then reset the log in ISY. For a few of them I have ISY reset programs that add a header showing when it was reset and, in some cases, putting links to other related log files for ease of navigation. I guess I'm looking for a way to run some sort of batch file able to download HTML and save the file with a name based on current YYMMDD then, in some cases, call an ISY program to do the reset, while in other cases, just delete the file from the ISY web server. Any suggestions?

So how does one factory reset IoP without clobbering or losing anything else, e.g. portal, other Polisy config, existing nodeservers, etc.? I want a fresh IoP that can be found by launcher, portal, etc. without having to restore backup. Just like it was when it was first installed and before I restored a i994 backup to it. I want to do a number of "dry runs", including testing things without doing a restore first, before I do the real thing.

a little while later all traces of i994 went away so I guess it just took a while to fully register

Thanks @bpwwer. Did the delete and no problem in i994. @Michel Kohanim did the add but IoP not getting added. here are screenshot showing IoP in launcher, followed by the add screen to show the data, followed by the About screen in IoP from Launcher (i.e. it's there and userid/password I used is correct), followed by PG3 dashboard, which shows no ISYs but does show "ISY version 5.3.4".

Using SSH did all the upgrades so now have PG3 installed and it's seeing my i994 but not my IoP. Before adding IoP I want to "delete current ISY" as I have no PG3 nodeservers, I'm not ready to migrate my PG2 NS to PG3 until PG3 is at least beta and it's polluting my i994 error log with 100's (maybe 1000 a day?) of "System -170001 [Auth:-10103] 192.168.200.249:22130->80, Num=3" error messages Problem is I get a message that deleting the ISY will "delete all the existing nodeservers from ISY" and I don't want that to happen. Is it speaking only to PG3 NS's or will it delete my PG2 installed NS's? I only want PG3 seeing the IoP.

so I made a typo in reporting my version of FreeBSD. I was at 13.0 RELEASE p3. I mixed things up with my FreeNAS version, which is 11.3. Oops So by connecting on the same switch (same VLAN 200) as my Polisy I did the upgrade and am now at 13-p6 and can see my polisy and login to IoP from ISY Launcher Also, when I SSH from my main LAN (aka VLAN 1), I get the message in the attached screenshot before the connection is closed. So I think this is what was closing the connection but without saying so. Anyway, I've opened a support ticket with UDI so am getting the great service they provide and expect to get to the bottom of this soon.

yes, I noticed that. will do manual update. I tried pushing the reset button on front of my polisy but I guess I bought one too early because that did nothing. sigh I'm still trying to get SSH to work from my PC so I can do the update from comfort of my big chair instead hacking my laptop into switch with ISY/Polisy on it. I did a packet capture on SSH port 22 and can see that traffic is being forwarded from my PC to polisy and a response is coming back (nothing is "dropped") but I still get' 'connection refused' from polisy. I think I need to log a support ticket, unless someone detects something from the screenshot and packet capture attached. packet-c.pcap

Yes, I went through the guide and tried adding all the following to the ISY Launcher (from same subnet/VLAN) with no luck: http://192.168.200.249:8080/desc http://192.168.200.249/desc http://192.168.200.249 https://192.168.200.249:8443/desc https://192.168.200.249/desc https://192.168.200.249 uname -a shows my Polisy is running FreeBSD 11.3. Before I SSH'ed into it, I did "check for polisy updates" and it reported having 88 updates so I did "update polisy". Is that all I need to do, or is there stuff that can only be updated using SSH/command line?

So the way to do this securely - which is why I'm using VLANs - is for the more secure devices on my LAN to be able to make a call out to my separate VLAN for IOT devices - better known as Internet of Insecure Things - but not allowing my 8 year-old-no-longer-being-updated-smart-TV and other IOT devices with notoriously weak security like cameras from reaching (and perhaps infecting) PC's on my main LAN. Usually a call out, such as HTTP, FTP, SSH, etc. provides a return channel to the caller. This is why you don't need (or want) to have WAN firewall rules that allow traffic in the "opposite direction", i.e. being initiated FROM the internet. From a firewall rule perspective I treat my IOIT VLAN like I do the WAN.

I was able to connect and do stuff by plugging a laptop into same switch/VLAN subnet so it appears my fw rule isn't working as expected. I don't understand because SSH is explicitly allowed, plus I have a rule to allow "Any" traffic from LAN to the VLAN - AND I can get to the polisy, e.g. ping and https work and I do get login prompt when I ssh. Anyway, looking like it's probably not a polisy issue. Interestingly on a die note, I also can't get Polisy to come up in ISY Finder, even when I try to add it from the same subnet... but that's for another thread (and maybe a UDI support ticket)...

Windows firewall is off for private network and router/fw is configured to allow all traffic from my main subnet to that VLAN. I did try putty (before command line, actually) and, similar to command line, it connects but then rejects the connection after I enter userid. See screenshot.

Trying to SSH into my Polisy at 192.168.200.249 but keep getting "Connection closed by 192.168.200.249" ssh admin@192.168.200.249 The authenticity of host '192.168.200.249 (192.168.200.249)' can't be established. RSA key fingerprint is SHA256:7zYnlSpxx6z0t884lR5vNYfelxewzWwu8N1X6v+wsZA. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.200.249' (RSA) to the list of known hosts. Connection closed by 192.168.200.249 port 22 ssh admin@192.168.200.249 Connection closed by 192.168.200.249 port 22 ssh admin@192.168.200.249 Connection closed by 192.168.200.249 port 22 I will say that my ISY and Polisy are on their own VLAN but I have a rule that allows the PC I'm using to have full access to that VLAN and am not having any problems accessing either via browser, although I did have to manually add ISY to ISY Finder. As well, based on the initial message, it does look like SSH is getting to the Polisy. It's just that once there it's getting the door shut in its face... Any help would be appreciated

As we can all see, a ton of assumptions are made! Would like to bump this back to the original question. is there a very simple set of instructions on how to get ISY on Policy? (If so, I can't find them either.) I'm okay to wait until there's also a migration tool from ISY994i 5.x (coming soon, I just read) since that is very important too but please it needs to be "for Dummies". I only just found out now about the update button on newer polisy, and didn't initially (a few months back) know about the much needed putty and ssh and the various low level updates before you can hope to have success with ISY on polisy. Thanks for considering it, whoever out there knows...

In the overnight automatic virus scan, MS Defender quarantined Nodelink, calling it a "severe" threat. See attached screenshot, and below is what I got when I clicked "Learn more" https://go.microsoft.com/fwlink/?linkid=142185&name=Trojan:Win32/Wacatac.B!ml&threatid=2147735505 I don't actually use nodelink anymore but thought I would mention it here.

I'd like to know this too before I take the leap. Either remove/uninstall or disable such that it doesn't restart at next reboot. In case it causes more grief than its worth and I need to wait until all the kinks are worked out.

the problem started before the upgrade command. I wasn't able to restart ISY but was focusing on the commands given for this post. below a more complete sequence of errors, and attached is the stuff before that, which seemed to work ok other than issue with /dev/speaker. sudo service isy restart isy does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@polisy ~]$ sudo service isy restart isy does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable [admin@polisy ~]$ [admin@polisy ~]$ sudo pkg upgrade isy Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: isy is not installed, therefore upgrade is impossible Checking integrity... done (0 conflicting) Your packages are up to date. ISY-update.txt

so to be clear I've done the following: - sudo pkg update- sudo pkg upgrade (this should upgrade your ISY to 5.0.1)_ sudo service udx restart- sudo service isy restart sudo pkg updatesudo pkg upgrade isy (-> 5.0.2_2) and posted the messages related to the last command above

I'm talking about the steps at the top of *this* post: sudo pkg updatesudo pkg upgrade isy (-> 5.0.2_2)sudo service udx restartsudo service isy restart I was just saying I did the steps from linked post BEFORE in case it was key to being able to do these steps

Am getting message that "isy is not installed..." [admin@polisy ~]$ sudo pkg upgrade isy Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: isy is not installed, therefore upgrade is impossible is did follow the steps outlined here first. what am I missing?

Ok so am thinking probably manageable second PLM scenario Now what about the steps I propose to follow to get it done (and the outstanding question):

I learned from Aartech that Smarthome will be providing a PLM to replace my still warrantied defective one. I also found one on Ebay yesterday from a reseller that converts USB version to serial. I went back this morning to post link here but it was no longer available. When I found it, it said there were 10 left (102 sold, with 100% positive feedback) Just to bring this thread back to what I'm asking about, below is the context I provided earlier in response to "How many devices do you have in your system? Even with 200 devices that 5 programs for each and every one. I would recommend looking at your programs and cleaning them up..." ...and further down/attached is a screenshot of my ISY Inventory. Bottom line, if my secondary insteon network only has 3 infrequently used keypadlincs (24 nodes) with programming that factors in risk of collisions, how likely am I to have a lot of problems?

I reached out to Eaton about their RFWC5 and they replied that: I've since found a number places that sell them for far less than amazon.ca but between only being 5 buttons (I'm looking to replace 8-button Keypadlincs) and having reached EOL, I don't think I'll go for this. Inovelli has only 3 buttons that can light up to act as an indicator that something is ON so I would need 3 to replace 1 KPL. I may have to give up on zwave for what I'm looking to do.

I've done some program cleaning up and will certainly continue to look for opportunities but, after spending weeks/months doing countless things to finally get things to the point where I wasn't also exceeding the ISY event queue (mostly at startup, which was leaving system inconsistent and causing program misbehavior), I want to get back to spending time adding to my automation rather than trying to code around technical limitations, which means that program cleanup would only buy me time, not solve my issue (a more powerful ISY). To provide a bit of context, I guesstimate that 70% of my programs are related to HVAC and react in multiple ways to multiple conditions and multiple sensors. For example I have about 40 programs running just my HRV (one device for high and one device for low) based on time of year, time of day, temp inside, temp outside, humidity, air air quality sensors (CO2, VOCs, Radon). That's 20 programs per device right there. Probably that many programs also running furnace fan (two devices: stat and dry contact for fan high) based on similar set of factors. I completely redid the HRV series of programs looking for efficiencies, including fewer programs and more "waits" to allow time for things to run (HVAC is not as time sensitive as a motion sensor to turn a light on). While I'm happy to program new HRV usage conditions, I'm tired of spending time just looking to do the same thing more efficiently, which has returned little value for the money. In addition, carving off the HVAC would also allow me to leave that but remove all the lighting if I sell the house (with time to figure that all out before we're ready to sell) On the HVAC front I would only have 2-3 keypadlincs. That would be the only insteon on my 2nd network, and none of those would interact with lights. If I could find similar keypad offering in zwave I would get some but I can't find anything suitable. They're only to enable/disable HVAC events, and to act as reminders to change filters and reset those reminders. That's 16-24 infrequently used insteon devices and I could probably add some redundant actions to account for potential collisions. Yes, I could have email reminders to reduce that down by a keypad but the convenience of being able to press a button to reset a reminder vs going into ISY to reset it along with the variables that track usage is worth quite a bit to me (and helps with the WAF). My biggest concern with this second network was making sure the insteon signal reached the devices / ISY because of distance to ISY. Is that a valid concern, and given what I just explained, should I really still be worried about other issues? Thanks.