Michel Kohanim

Hi BrianH, So am I: the problem is that those groups are linked to iMeter and we had a hell of time getting it to report directly to the PLM. Also, since this is a battery operated device, doing a query may kill the battery. I think they had an option for an external power supply but ours doesn't have it. So, extensive querying may just drain the battery. We'll take another look. With kind regards, Michel

Hi LeeG, Thanks so very much for the detailed explanation. We shall take a look and figure out what's causing the glitch. With kind regards, Michel

Hi KHLUDI, 994i Series (including PRO and IR) have an expansion slot that can be use with our ZWave dongle (not out yet). 994iZ Series already use that slot for Zigbee. So, it's either Zigbee OR ZWave. With kind regards, Michel

Hi LeeG, Is this with the beta version you have? With kind regards, Michel

Hello jmed999, Just responded to your ticket. LeeG, thanks so very much for all the help. With kind regards, Michel

Yes, I think so. With kind regards, Michel

Hi Teken, Thank you. We will take another look ... but, just to be clear, this device does not report temperature so you will have to query it explicitly. And, if you have many of them with high query frequency, then the performance of everything else in your system will be impacted. With kind regards, Michel

Hello kjbbasic, I am so very sorry ... the current 3.2.6 firmware for 994 didn't have SDHC support turned on and thus you cannot go above and beyond 1GB. This said, this bug is already fixed and shall be included in the next drop. Again, sincere apologies. With kind regards, Michel

Hi Teken, We tried implementing it and ran into some anomalies especially with respect to linking to iMeter solo. I am not sure if simply supporting the temp monitoring will be enough for everyone. With kind regards, Michel

Hi KHLUDI, Comments below. With kind regards, Michel Unfortunately not since it uses a proprietary version of Zigbee made by Control 4 and for which we do not have access to the APIs The best option would be to use our soon to be alpha version of 994 with ZWave (NOT Zigbee). This will allow you to communicate with Schlage door locks and a limited set of ZWave devices (in addition to INSTEON).

Teken, I do hope so. We are not going to support Energy Monitors (they simply display whatever you can already get from iMeter) ... are you planning to use them for temperature sensors? With kind regards, Michel

Hi inline, Currently working on our security pack/enhancements for 994 and supporting up to TLS 1.2 and additional ciphers/hashes. We might be able to do something with this as well but I cannot guarantee. With kind regards, Michel

Hi Clarence, I had no idea that the dashboard worked on Droid tablets! Thanks so very much for the information. With kind regards, Michel

Hi Xpendable, We are using Java 7.4 without any issues (except for WeatherBug screen hanging which has been fixed). Can you tell me which URL you were using? With kind regards, Michel

Hello automateit, Thank you. Please keep an eye on Program Summary: 1. Last Runtime 2. Last Finish time We need to figure out whether or not the program actually ran vs. it ran but could not communicate with devices. With kind regards, Michel

Hi Tim, What is the Java version? The problem seems to be security related ... it seems as if Java does not have enough security permissions to access the network. Are you using ISY's URL or are you using the application (http://www.universal-devices.com/99i/admin.jnlp)? With kind regards, Michel

Hi Nuttycomputer, Yes, hopefully in the next release. With kind regards, Michel

sloop, As per your posts above, the Admin Console is working. So, I do not understand the question. The main point is NOT to start adding devices/scenes with the old PLM because you HAVE TO replace it and all you have done might be lost (especially in your case). So, what else can you do with the Admin Console without any INSTEON devices? With kind regards, Michel

LeeG, as always, you're 100% correct! matapan, sorry but 26 does not have enough code space to support I2CS devices. With kind regards, Michel

sloop, If you are selling the house, I think it would be a waste of your time going through everything again. The fact that your system never worked properly and that it's so old (2.7.15 is about 3 years old) tells me that you are going to have a hell of a time getting everything back to functional. If you so choose to go ahead with ISY anyway, then: 1. Don't do anything till you get the new PLM (you also need a power supply) 2. Factory reset ISY 3. Upgrade the firmware 4. Add your devices/scenes Do not go overboard with scenes as the PLM still has the 1000 limit. With kind regards, Michel

Hi sloop, What you need to do is this: 1. Make sure you factory reset ISY 2. Upgrade the firmware 3. Change the PLM to 2413S With kind regards, Michel

Hi sloop, Did you use the link above to try and gain access? With kind regards, Michel

Hello wrj0, We have been going through a lot of discussions as far as the accuracy of the irrigation module. Thanks to IM and Nuttycomputer, we'll be making some minor changes and hopefully we'll include this feature if it does not break anything else. With kind regards, Michel

Hi Xathros, Thanks so very much for the information. I really had no idea that it might take routers so long to reboot. Yes, in that case, you are right on: static IP address is the way to go. In either case, our next drop should address this issue: this was a regression bug introduced in 3.1.x branch. Nuttycomputer, we do recommend to all our customers to do manual port forwarding and thus UPnP would only be a problem if one used File | Enable Internet Access. With kind regards, Michel

Hi Tim, I am so very glad you got the system back up and running. Since we do NOT do anything with JavaFX, I still suspect some type of virus (especially the .ru extension is quite odd). So, please do keep an eye. With kind regards, Michel