paulbates
-
Posts
5608 -
Joined
-
Last visited
Everything posted by paulbates
-
Use Wait, as dbuss suggests. You can also combine that with a repeat statement to keep the reminder coming at regular intervals. It will stop once the door is closed if door is on then wait 5 minutes repeat every 5 minutes send notification 'xxxxx"
-
Put java and the AC on a minimalist vm, or AWS or azure vm and spin it up when you need it. Is the attack surface of a "recompiled" java app any smaller than regular java? Paul
-
@Michel Kohanim Do you know what to do in this case? Paul
-
ok.. this helps. The problem is with Java itself. Browse to here to download a fresh java install. Remove any previous versions when it prompts you to do so. Paul
-
We use ISY portal services daily via echo and have had no misses in quite some time...outside of published maintenance windows, or a recent ISP outage due to downed lines.
-
You'll need to click save instead of open... IE (and chrome) no longer support launching java applets. Save start.jnlp to your desktop. Double click that icon with the java coffee cup on it. Paul
-
Hi Some virus scanners can block java apps, try temporarily disabling your endpoint protection.. Norton, McAfee, etc. Can you provide the message / window you are getting? There is a new way to launch the ISY finder, see this post and try it out. Paul
-
It would help if you posted screen shots of the keypads' configurations. You can use something like the snipping tool in windows to grab the area of the screen for each keypad and paste right into a reply window here. Type in a line in the reply window before pasting indicating which is which. Paul
-
I don't, but he ultimately contacted ISY via the support form
-
There are suggestions in jgcharlotte's thread about debugging / refreshing the portal connection on each side.
-
You have automatic checked for DHCP. When you plugged it into the ISP Modem, it got your houses internet IP from your ISP. You can follow the train of suggestions from jgcharlotte's thread, or go to the end and follow the last step. That's what worked. Hopefully you have a recent ISY backup. Paul
-
Disabling the keypad only makes the ISY ignore it. When the ISY creates scenes, it programs the insteon links into the switches pushes the work to the switches and its all insteon at that point. While its bad for this case, its good in that scene based lighting controls will continue to work if the ISY and/or the PLM die All you can do is use programs for the keypad functions only, and not scenes as oberkc recommended.. It will be slower, but controllable. You can put those programs in a folder and have a way.. manual or another switch that they can't reach, and set the logic of that folder to be false when the grandkids come over. Paul
-
Hi The ISY launching world has just changed a little, for the better. Read this ISY Launcher post from Michel There is a new icon associated with it, but the launching process is more managed and streamlined Paul
- 1 reply
-
- 1
-
-
Have your program use "If control <device> is switched on" instead of If status. It will only trigger when the message is sent Paul
-
RF is half science and engineering, and half unknowns of field use. While metal can be a blocking factor, it can also a reflecting factor in a positive way. There's no hard and fast rule to say that it will not work. Placing a battery sensor, leak or open/close, under there and wait for the 24 hour heartbeat would be the definitive test. You can write a simple program, if the sensor heartbeat is turned on, send you a text or email. if you get an email a day for 2 or 3 days straight, I'd say it works. Paul
-
The ISY is not designed such that a second ISY will automatically 'sync' devices with the first one, even with the portal. Devices from the second ISY will not appear in on the first ISY While it is possible to control devices on a second ISY, there will be additional manual integration work to do, device by device; writing ISY programs, variables and network resources to get devices on the second ISY to respond to the first. Its more straightforward to try an solve this at the insteon protocol level. Paul
-
The insteon white paper says rf range is 150'. Given that specs are usually conservative, its a worthy experiment. Do you have a couple dualband lamplincs to "borrow" and try it? Put a lamplinc in an outlet in the house as close / high as possible to the outbuilding, put another one in the outbuilding on an extension cord. Plug in a lamp and try it. move it around in the outbuilding to see areas that are better. If it works at all, try different outlets to plug the lamplinc in the outbuilding. Metal will be the thing to avoid.. metal siding, doors, walls, jboxes.. or foil backed insulation. Paul
-
I updated a 5 year old Lenovo all-in-one to SSD. It had an old HDD that was humming, getting slow and very noisy. I replaced it with a SAN disk SSD. Based on how the lenovo was designed, it took less than 15 minutes to swap the memory DIMM for more memory, and replace the HDD with an SSD. Before the swap, I used acronis, which is free when using a san disk ssd, to copy the HDD image to the SSD and make it bootable. Did the HW swap and turned it back on. It was one of the most painless upgrades, runs great and relatively cheap (compared to replacing an all-in-one)
-
Starts on page 6
-
Bill I had to put a range extender in my garage to get my garage door iolinc to work. Actually its the old school Access Point, which works with the older iolinc I have. Picked an outlet that was close to line-of-sight with dualband devices in the house.. Paul
-
I have odd behavior on one of mine from time to time. Factory reset it, then try a restore device
-
The feature is called "replace with" Backup your ISY Add the new keypad.. don't worry what to call it and leave it in the root of the device tree.. eg don't put it in a folder right click on the existing keypad and pick "remove from folder" Are any wireless devices involved... eg a motion sensor that turns a key on? You'll need to be ready to deal with wireless updates If you have the ISY pro you can click the little +battery- icon on the icon bar so it's grey, that will save wireless updates till later right click on the existing keypad and pick "replace with" and then pick the new keypad let it run, deal with wireless devices as they come up Paul
-
I didn't know if you had tried refresh.. I'm not sure how extensive that is and what assumption the ISY makes about connections once it "dials out" to the portal. Try the refresh on both sides, portal and ISY a few times if you haven't. If that doesn't fix it, I would go with opening a ticket. I know this has been a difficult one, and I think UDI on the phone with their end-to-end view will get this resolved for you.
-
If you log in to my.isy.io, there is ISY Portal Troubleshooting under Information when you select tool. What does that say? Paul
-
Somtimes scene info gets corrupted in the switches. Right click on each switch and do a restore device. One other thought. Not sure what is meant by slave for the switch. Make them both controllers and I think you'll be fine. If one is a responder only, delete it from the same (save a screen shot of the scene settings if you need to) and add it back in.. check the box for making it a controller Paul
