Guy Lavoie
-
Posts
132 -
Joined
-
Last visited
Community Answers
-
Guy Lavoie's post in Upgraded to EISY and can't get into it with Launcher was marked as the answer
I had that happen to me 2 days ago. It had been running fine for weeks, then suddenly both my eisy and polisy wouldn't show up. Did the clear cache, full resintall of java, reinstall of launcher...no go. I ended up having to use the "add" button on the launcher to manually tell it where the devices were. Like this:
https://192.168.0.145:8443/desc
Just write in your own ip address. It worked for both devices. I then did a "save" to make it easier next time.
No idea why this suddenly happens.
-
Guy Lavoie's post in iOS shortcut support to trigger a program was marked as the answer
If you can construct multiline URLs, the better way is to encode the username and password as a base 64 value, and include it as a parameter. Browsers do this internally. It looks like this:
GET /rest/programs/0009/runThen HTTP/1.0
Host: 192.168.160.31:8080
Authorization: YWRtaW46YWRtaW4=
That authorization value is the result of encoding "admin:admin"
You can encode your own userid:password here
https://www.base64encode.net/
-
Guy Lavoie's post in Can't send X10, admin console not allowing some menu choices was marked as the answer
A fix has been issued. try the following procedure to install it:
Please reboot using the following method:
1. Press/hold power button -> red
2. Click again -> blue
Everything working again.
-
Guy Lavoie's post in No way to detect/trigger on scene events in IoX? was marked as the answer
This has a happy ending! From reading and searching, I discovered the plugin called "Virtual" which seems to be exactly there for this purpose. This forum reply will also help anyone looking for this functionality in the future. Virtual allows you to create virtual switches (and other devices) which can then be added as responders to scenes. Turn on a scene and the virtual switch turns on too, and same for off. Then you can use the virtual device in a IF statement just like an actual device. Because the device only exists as a responder for the scene, no need to "guess" the status of several devices as suggested earlier.
Having this capability helps maintain the optimum failure mode for an Insteon setup, since Insteon is peer to peer. So if the eisy/PLM/whatever ever fails, the generic scene will still function, and only the additional functionality provided by the eisy will be lost. This is different than relying on eisy to launch the scene just because you also want added functionality in a program.