larryllix

IIRC just factory reset, set your DHCP, time zone, and location lat/long, and restore a good backup. Done. But if you loaded up your caches before, you need to disable those caching functions or it will just happen again. I have many older MSes and apparently they don't support the "open linking window period" after sending events.

I haven't really needed any of those tools lately so I haven't bothered yet. I used it on my RPi but my desk behind the couch got tossed when listing the house for sale last year. Now the RPis are being used for other purposes and a fast laptop has taken it's place. At the suggestion of @io_guy I started using NotePad+ and it works very well for a lot of different file types. Over fancy text docs and spreadsheets have become mostly obsolete in my world, lately. They are so 90's.

No idea. I don't use these features anymore. It locked up my ISY until I did a factory reset to clear the caches, before I figured what was causing it.

There are icon options at the top of the admin console software in Windows machine java screens with two different options concerning this. Then you write programs that trigger on event from the battery devices, wait a few seconds to avoid signal collisions and the write the updates via an ISY program line. Caution: If your battery devices do not support this option, you may flood ISY caches with data that can bog your ISY down to a very slow grind. Every time a trigger is detected, ISY will attempt to write the whole cache out and you will constantly see "Busy" on your admin console. This can become hard to find and hard to correct.

...and your Admin Console themes, including font sizes will have to be redefined again every time. PITA! If you continue to accept updates to Windows 7 it will cease two work for almost all apps. MS will make sure you are forced to upgrade. If you have the original installation CD Win 7 will become very fast again and everything will start to function again. I still run MS Office 1997 despite all their attempts to stop it and ruin it.

Yeah. You just need to re-associate java files with java so that launching them automatically uses java instead of your browser. Sounds like you done that already!

If you run multiple browsers you will soon find out that most webpages, if they support IE 11, are missing half the internet features. Webpage writing has become much more advanced and IE just hasn't progressed. This is why many webpages block it now. I have never found any webpages that require IE 11, in the last 5 years. I should mention that IE 11 does not have the bug I mentioned, that Chrome and Edge suffer from. I can detect it on all webpages at random. When you click on a link, at random they don't send a proper URL terminator and you have to click it again. Then the server will respond by returning the webpage twice. Most people will think they mis-keyed or mis-fingered the link. The OP asked about browsers for admin console, but ISY admin console does not use any browser, and never did, AFAIK.

I was a strong supporter of IE 11. Now after doing some HTML5/CSS code writing I have found IE 11 is deprecated, way out of date. I have also found problems with Chrome and Edge that FireFox doesn't have. OTOH, FireFox presents it's own problems. However Admin Console doesn't run in any browser. It runs under java and is not browser related.

You missed the other part of the retriggerable timer. That same timer is used to time the off cycle of the MSII also. That means until you stop all motion the timer will never expire and the MSII will never send another On signal to turn on the lights. IOW: It's algorithm is just plain defective. I have walked around in the dark, middle of the night too many times with this MSII, now. I didn't want to stay with a SH Hub, or be a slave to Insteon's simple timer HA logic. Now that ISY has features to interfere with Insteon scenes, there may be more avenues yet. This may have something to do with the "block sending off commands" and I forget my results, when I tested that aspect. I may not even have tested that aspect. I like ISY to control as much as I can and avoid scenes whenever possible. Getting the speed of light response from a MS is one place I cannot avoid scenes though and one of the best parts of Insteon devices. If Zwave were not so slow, I may have switched to that system when the MS1 first died. I have a stock of MS1s now, though. I have one in my laundry room also due to USB power and saving a battery there. Again there are times when you stand in the dark until you manually override the MSII. Usually it is good if you only enter every 5-10 minutes or longer, each time.

Especially since a current Insteon company officer, formerly posting here, worked for the UDI that Insteon isn't aware of. ...and Insteon pulled the rug out from under UDI with their own PLM development. After years of interactions they just didn't remember they made any arrangements with UDI, and co-incidentally just as Insteon thought Apple was going to get into bed with them and make them industry giants? "You can fool some of the people....

MSIIs are not good for light operations due to not supporting retriggerable signals. They appear to support a retriggerable timer internally, but they do not inform external devices of the retrigger. This doesn;t work for ISY994 and other HA central control systems. Insteon appears to have created this to support the Insteon system devices and defy HA systems. MSIIs have another problem. The internal reset timer is the same internal timer used for the time-on timer (mentioned above). What this means is that once the internal timer expires from lack of motion detected, the MSII cannot send another On signal as long as it detects motion. Whether you require the external retriggered MS signal for HA, or not, you are going to have a period of dark time (no lights on) as long as the same lights on timer is set to. If you continue to move around the room, the lights will never come back on until you stop all motion for the timer time. Complete design fail. ISY is not the only system that will not work nicely with these units. I suspect Insteon doesn't want UDI to survive, and this is just one more clue.

I have not experienced that "insane mode" that I know of but I have seen random garbage come out of one MSII for temperature. The scary part is they are inconsistent between different units and even from one time to the next. Hopefully, MSIIs work with Insteon Hubs, giving hope that UDI will get it figured out one day and we can have at least one Insteon MS we can trust.

What is a "monitor" port?. I only know of two ports on ISY, Ethernet port, and a serial port for the PLM.

I don't use the luminance but I just may use it on one unit now. I am thinking of an algorithm to keep the lighting in my Gathering Room constant. We have some overcast days where the luminance varies greatly in the room and I was going to use outside Tags for that. I have an MS II in that room that is only used for occupancy detection, and not lighting, so it may work well. Now I must try it. Thanks.

I don't think ISY has changed any hardware or bus size. I believe if the old sectoring format would support larger SD card sizes they wouldn't make an SD card that small either. You may note you are not likely to buy anything smaller than a 32GB card now. They stopped making them. Once they got up to the maximum sector size using 2^16bit addressing size sectors, FAT formatting became overloaded and obsolete. Then EXFAT and some other formats were introduced with 32 bits of addressing, so that sector size could back to 256++ bytes, and save HDD space with small files etc. If you format an SSD/HDD using the new formats they seem to work and then the FAT overflows unexpectedly and nobody ever knows why because it worked for the last X years. I think there are some co-ordination problems between the drive size and the FAT table. eg. Y2K = Just need two digits for a year date. Everybody knows it always has "19" in front of it. Now "19" is a bad word. . FAT = file allocation table

Also. I don't think an SD card larger than 32GB can be used in older hardware. The EXFAT and other formats must be used and I doubt ISY would be compatible with it. IIRC 32GB is the largest SD card to still support plain old FAT format without low-level partitioning the SD.

IIRC I think the MS II goes into rapid Insteon packet flooding after a query. I am not sure I have experienced that but found ISY acting very strangely after MS II query. Can't rember the symptoms now. The parameters received were always garbage anyway.

Not likely an actual memory problem inside ISY. I would try turning off you anti-virus software, and/or enlarging your java memory, and reloading your programs again into a new trial of admin console. Check your UI and firmware. They must match. ISY hardware can only support a 2GB SD card. The rest will never be used.

I don't think ISY has the bus size to support more than 2^16 sectors = 2GB of storage. What usually happens in other applications is the O/s overruns the 2GB limitations and then the O/S begins to act crazy. Nothing less than 16GB SD cards are manufactured anymore so......?

You would have to search the forum, just like I would. Look for a Michel Kohanim or my post about the MS II about 6 months ago. Maybe "remove", "discontinue", or "mistake" words.

I have three of them and after testing in key locations, am slowly moving them to non-lighting locations. They seem to work well for just occupancy, and security applications. IMHO they are more reliable for those applications, more compact, and work without batteries. Getting real tired of hearing Insteon is going to launch "we-can't tell-you magic things, please stand-by, because we have a new CEO" every year since 2014, every year when the only thing we have seen is the MS II flop.

The MS II interface was a hack by UDI, as Insteon would not come forth and supply one after years of requesting, and Insteon users had no other source of MSes. Meanwhile, UDI has become frustrated and wanted to remove all support for the messy unit. They didn't after users not having anything else. We were also advised not to rely on any of the side parameters due to lack of accuracy that fluctuates with different usages. My temperatures jump all over the scale with different operations. Do not be surprised if querying the MS II causes your ISY to hang. It does mine at times. Known problem with the ISY/MS II hack. I am thinking of just sending money to China instead of a MIA company. Maybe they will have all the new Insteox products in waiting.

OK. You know the backup has to match the major version revision of the firmware, right? IOW: v4 and v5 backups are not compatible. IIRC UDI changed the style of storage and the internal ISY processing engine in v5 to make it faster and more efficient. Something not quite right what happened to you. If you get even another glitch I would open a ticket with UDI. You may have something overlooked or even a hardware problem, and UDI is better at those things, and more forgiving with hardware problems.

At that point I would factory reset my ISY, reformat the SD card and install ISY v5.0.16C, then restore your v5 backup. This will start your whole thing fresh and forgive all the accumulated junk inside ISY from experimenting. The whole process takes about half an hour or less. You will need to be able to telnet into (PuTTY works) your ISY to format your SD card inside ISY. The reloading of the O/S is built in from a chopped down admin console.