
walkman9999
Members-
Posts
128 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
walkman9999's Achievements

Experienced (4/6)
9
Reputation
-
Just getting started with this, and following instructions found in the link below. The goal is to have both the EISY and the included z-wave remote control the blinds. I added the blinds to EISY and can control them as expected. I then followed the instructions to pair the Bali premium remote control to the EISY and this succeeded as well. Following the instructions, I then paired the remote control to the blinds which is successful. The remote works as expected until I use EISY to control the shade, at that point the remote stops being able to control the blinds while the EISY still can. [minor edit to describe things better] It is as if the blinds can only be paired to a single controller, although the link (and Bali's support folks) say otherwise. I'm looking for any insight into what I should be looking for, any tests that may show what is happening, or really a better understanding of the process (e.g., why does remote have to be paired to EISY?) Haven't found much in the forum, hoping someone has worked through this and can help. Attached is a screenshot of the EISY console. TY
-
Ideas needed: Audio alert for triggered event
walkman9999 replied to walkman9999's topic in Coffee Shop
@dbwarner5: Got it! For some reason there was a delay in My Alexa "seeing" the new device under Smarthome. But, it works perfectly at this point. TY for the help. -
Ideas needed: Audio alert for triggered event
walkman9999 replied to walkman9999's topic in Coffee Shop
@dbwarner5: I have the variable created and the program to change it from 0 to 1 when event occurs. I have the mapping created in the ISY portal as a device/motion detector and added a spoken. But...when I go into the Alexa app to create a routine, I do not have "Motion Detector" as an option under "Select an Event". I have a bunch of categories, but none of them include motion detector. Couple screen shots attached. Wonder if you have any pointers? -
Ideas needed: Audio alert for triggered event
walkman9999 replied to walkman9999's topic in Coffee Shop
Seems obvious, got it. I have gotten the info I asked for, to keep the thread on point I'll mark solved. Thank you for the suggestions. -
Ideas needed: Audio alert for triggered event
walkman9999 replied to walkman9999's topic in Coffee Shop
Working through all the suggestions, thank you. I have EISY, cannot seem to figure out how to find and install plugins. Sounds basic, but I cannot find the option. Can some one point me>? -
Ideas needed: Audio alert for triggered event
walkman9999 replied to walkman9999's topic in Coffee Shop
Appreciate the quick responses, few follow-ups: @paulbates: This is most appealing of the options, nothing else to buy. I've looked through the forum and at Alexa app and cannot find a Event for any of the Insteon devices even though they are recognized devices within Alexa. Any idea where I can find additional info? @JTsao: I have the z-wave module on my EISY, but haven't added any devices yet. I assume the EISY programs (If...then...else) controls this device once added? Thanks to both of you. -
Hello - I am looking for suggestions to create an audio alert when a open/close sensor is triggered. I have a visual alert (a nightlight plugged into an Insteon outlet), but would also like some sort of sound. I've used the "Beep" function for this, but I'm finding that it is too subtle. Any suggestions? TY
-
Older, single-band devices and some noise on the wire contributed to this. The devices have been replaced and comms are as expected. TY @IndyMike for the decoding help, I've found the explanations useful in other troubleshooting of I1 vs I2 devices. Marking solved.
-
As suggested by replies, combination of bad programming, older devices, and a questionable PLM contributed to this problem. I can't say specifically which of the changes solved the problem, but it no longer exists. A smoking gun would have been nice, but marking solved as the troubleshooting was helpful. Thanks all.
-
Not sure if it is implemented, but it would be possible to use the MAC/Insteon ID to get a FW update to the devices. Wouldn't work over a WAN, but within the local network the capability is there. (I rarely get to offer any expertise, but network guy by trade.)
-
That is a great answer, thank you. I think what you've said, along with @lilyoyo1's point about the upgradability of the new platform makes the decision for me. Appreciate the feedback. And, removing ALL ON from the command suite is ultimately a good marketing move. That uncommanded command was responsible for giving home automation a bad rep in my fam.
-
Thanks, all for the opinions and info. Does anyone know if the powerline protocol has been updated, similar to the way it was updated between I1 and I2? I'm not an expert on this category, but I2 devices perform noticeably better in my somewhat noisy environment and any additional improvement would be a consideration for me. Thanks again for the input so far.
-
@IndyMike, all good info. Making suggested changes to simplify programs. I was wondering about the "Link for responder XX.XX.XX not found" as well. I tracked down the MAC/Insteon ID and restored both the device and the PLM, but still they persist. I believe all of the devices listed are KPLs if that sheds any light. Looking at any logs of what happens "on the wire" always yields a few mysteries (I'm a network guy). Found that all mysteries do not need to be solved so taking that approach. Appreciate the insight as always, will post back if anything interesting happens. Otherwise, I'll close the thread in a week or so.
-
Should have specified, I have EISY.
-
Hello - I'm replacing some non-dual-link switchlinks in my network and ran across two choices, wondering if anyone has any insight on differences? Possible shortcutting the assignment, I'm interested in the best comms for the devices (I2 was a huge improvement over I1 in my environment), but I'd like to match the style of the 2477D if comms are not significantly improved in the PS01. I read reviews on Insteon website, but I didn't find mention of any new protocols. Maybe I missed something. Is there a compelling reason to go with PS01 over 2477D? All opinions welcomed. TY!@