bradshawkyle
Members-
Posts
31 -
Joined
-
Last visited
bradshawkyle's Achievements
-
I tried that first and ran into sone strange behavior. I couldn't access via Admin Console, PG3 disconnected, no UD Mobile, BUT I could see and control devices via ISY Portal. I looked around for a post explaining how to configure Ethernet and could only find instructions to "plug it in and wireless is disabled". And ideas how to resolve? If not, I guess I could back-up, factory reset, and configure eISY with Ethernet instead of Wifi. Seems kinda of extreme, though..... That said, I'm willing to go that route if I can get things working properly.
-
Like the title says, I can't seem to get the Node Server to discover my devices. It's worth noting they're running the S1 app (not the newer S2) as some of my devices are 1st Gen Sonos. I have some ZP100's and ZP80's that still work perfectly at 15+ years. The devices are on wifi (not currently using the Bridge) and eISY is on the same 2.4GhZ network. I've tried reinstalling the Node Server and restarting eISY, along with clicking Discover in PG3 and in Admin console, and the Node Server shows connected in both places as well. Any troubleshooting tips would be greatly appreciated.
-
It seems that moving eISY to the 2.4Ghz band and restarting several times did the trick. This is a GREAT Node Server! Just converted my trial to a purchase - thank @Jimbo.Automates for all your help!
-
Thanks again, PM sent.
-
Goo d point on how Honeywell is configured, you point the Node Server to an API you have to create on the Honeywell side. I forgot about that. IP address for one Kasa device is 10.0.5.87. Log file is attached. Also, thank you very much for your help! Kasa_1-31-2023_84102-AM.zip
-
The smart bulbs are on a 2.4gHz network, eISY was wireless on 5gHz. I've read about people having problems accessing devices on the same network, but different bands. Just to be safe, I moved eISY to 2.4, reinstalled the node server, but no luck. I'm currently running the Honeywell Home node server to access two wireless thermostats with no problems.
-
-
Overkill is a relative term. 😎 Ho-ly cow, that looks awesome. My wife would be....nonplussed if I bought that, but I may add it to my Wish List just for laughs.
-
I just installed the trial and cannot s=seem to discover any devices. Node server is connected, showing 1 node on PG3 and eISY, and I've tried Discover on both. Any suggestions to get my devices discovered?
-
I had to go with the submersible pump + motion detection instead of the motion-activated sprinkler approach because things are freezing overnight. I'm hoping the short hose and lack of connected hose bib will prevent freezing.
-
We just moved to a house on a lake with a dock. Beautiful view, plenty of nature, all the good things that come with it. Yesterday we encountered one of the not-so-good things when a flock of 20 Canadian Geese had a poopapalooza party on the dock. It's covered in massive, slimy goose turds, preventing anyone from safely walking on the dock or even in the yard. So I hatched a plan to prevent the geese from returning and set to work: Created IFTTT web hook from the Ring cam on my dock. Action is to signal eISY to turn on 2634 On/Off Outdoor Module when motion is detected. Create program to wait 15 minutes after module is turned on, then turn off. Connected submersible water pump to On/Off Module and garden hose, then suspended pump below the dock. I chose submersible pump because all hoses bibs are currently winterized. Connected other end of garden hose to noisiest sprinkler I own. I'm thinking 15 minutes will rinse off most of the turds while making the dock an inhospitable place to roost. Sit back and wait for those noisy, honking [censored] to return. And the bonus is I'll have video of them getting run off, which I expect will be mildly satisfying. 😎 This is my first time experimenting with IFTTT triggering an Insteon device - does anyone have suggestions on how to improve v1 of the Goose Poop Preventer or any other clever applications of IFTTT for mundane household tasks?
-
Wait.....there's a Ramp Rate BUTTON?! Son of a biscuit.... I tend to have a "short bus" moment every month or so....apparently you fine folks got to witness mine for January. 😂 Thank you......
-
@briansI'm running eISY, here are the steps that aren't working: 1) Set ramp date to 2.0 seconds, click "Write Changes" 2) Move away from device, return and ramp is back at 0.5. Wash, rinse repeat every conceivable combination of Write Changes, Query, airgap switch etc. and I can't seem to set a default ramp rate for single device. What on earth am I missing? The only think I haven't tried is removing and re-adding, which I didn't both trying because the new devices behave the same as used ones.
-
Yup....that's me. I followed the majority of advice on this thread (and my own personal bias towards what I know) and set up a starter system with my backup PLM (from the old house) and some switches I snagged used from OfferUp. Last week, my first "new Insteon" order arrived - a 6 button keypad and the 50 button set - and just like that we're up and running. To be honest, my biggest problem right now stems from my own ignorance: Scenes and dimmer default values (ramp rates, on level etc.) seem to work differently than my old 994Pro. I can't program any ramp scene or default rates - the devices won't retain them. I found an article saying you have to airgap a dimmer after setting default values, but either I'm doing it wrong or it's not working, either.
-
One thing I've observed with the three node servers I've used so far it they are noticeably slower than Insteon-based programs/scenes/commands. It seems to me that an Insteon + Lutron Hybrid approach would result in Insteon devices responding almost instantaneously and Lutron devices delayed a bit as they travel from the trigger/command to ISY, then to Node Server, then via API/whatever to Lutron, THEN down to your Lutron hub and finally commanding the devices. That would drive me bananas, so between that (unproved) hypothesis and the fantastic advice received above, I decided to go all-in on Insteon once again. In fact, I installed 10th Instron device today and am in the middle of programming my new scenes. Even with the opportunity for a completely fresh start, far Insteon still seems like the best path forward for me.