jkmcfadden

Hi @tmorse305 I ran across this post because I also am trying to integrate my Droplet into eISY. I have it sort of showing up as a device under MQTT, but only as a switch. I know it is my specific config parameters. Can you show me what you are using? I know I am missing something. Specifically: Your integration settings in the Droplet app? Your Node configuration settings in the Polyglot configuration screen? Your entry in the .yaml file? And anything else you found useful. Thanks!

Very common item to buy. I have several for my testing. Amazon.com: EP 2 Pack 3 ft 14/3C SJTW Appliance and Power Tool Cord, 14 Gauge 3 Prong Heavy Duty Replacement Power Supply Cord Cable, 110V 115V 120V AC Pigtail, 15A, 1875w : Tools & Home Improvement

I mix the two often, though over the years I have relegated the older switches to out of the way places like closets and the garage. Primarily since the ones I have are toggle and everything else is generally decora. Just make sure a dual band is somewhere in the vicinity and you should be OK. In the same box (like Guy mentioned) is ideal but probably anywhere nearby will help. I have one older switch, that consistently does not get the signal, that I plan to replace in an upcoming remodel. In the meantime, I have a dual band keypad in a tabletop encloser (that I use for testing and other things) and I plug it in near the "offending" switch. Problem solved. For Z-wave, I like the Zooz line. Lots of options for switches and keypads. I have a few dozen installed of different types. Only issue with Z-wave is that they will respond to, but not control, a scene. So programs are required. Good Luck!

While Insteon is my first choice, they just don't offer the variety that Z-wave does. I love the Zooz Z-wave motion detector switches - I use them in closets, pantry and my attic. A Z-wave fan controller for a fan that is 18 foot up and just not an easy install with the Insteon fanlinc. The Z-wave water detectors are much better as well. I use the UD Z-wave dongle. Z-wave does not always play well with scenes (it can respond, just not control) so that is the only real drawback.

I have been hesitant to upgrade given all the posts mentioning issues. So, this gives me hope. However, some recent posts mentioned issues with their Z-wave devices after their upgrade. And as I have a significant number of Z-wave devices, I continue to hold off. Do you have any Z-wave in your configuration?

I wonder if it is now automatically included in the normal backup with the newer version. It is annoying to have to remember to do it because it apparently becomes embedded in the normal backup anyway. UD Support should be able to answer.

You are saying that you don't have this? I am on 5.8.4. If not you might need to open a ticket unless someone else has an idea.

You might investigate using a program as the Alexa interface instead of the device directly. The program can set the actual on level. I use a ZooZ Z-wave dimmer switch in this manner and programmatically set the on dimming value when turned on. I like Z-wave devices, but you (like many of us) have discovered that there are some limitations where Eisy is concerned. Programs seem to be the best/only solution.

I currently use a program or programs to activate a scene. But occasionally, in my more complex scenes that also have multiple zwave devices as responders, I end up in what I can only describe as a feedback loop where the scene turns off and on repeatedly. That is why I am trying to find a less complex solution.

For those of you who use Z-wave, has anyone found a solution where the Z-wave device will control a scene? I can only get it to work as a responder. There is a setting under the Z-wave main menu called "Detect Button Presses" that is defaulted to "Off". Setting it to "On" displays a worrying warning box, so I hit cancel. The Help Wiki has no specific info on the setting that I could find. Is there more substantial Eisy/Z-wave documentation anywhere? Or is anyone aware of a solution to the problem?

Nothing is obvious where Z-wave is concerned when implementing with Eisy 😉 but I have figured out quite a lot though trial and error. I still have not figured out how to get Z-wave to control a scene though (my Holy Grail). It will respond but not control based on my experience and anecdotal reports of others. There is a setting under the Zwave menu called "Detect Press" that is off by default. But I can't find any specific info on it in the Help Wiki. And when trying to turn it on a warning box pops up with all sorts of worrying statements, so I hit cancel. When I have time, I might turn it on to see what happens, but that scares me a little that I might break a perfectly working Eisy environment. 😬

I use the Zen32 as fan controllers in my secondary bedrooms. The smaller buttons control the speed via an Insteon Fanlinc. Here is what I do to change the parameters of the small buttons when one is pressed. When one is pressed, it lights up and turns off the led on the others. I have a separate program for low, med, high and off. Scene Button 1 is parameter 2, the rest are the other small buttons.

Following as I am also on 5.8.4 with a LOT of Z-Wave devices. Can you add any new Z-Wave devices? If you can, that might indicate just an issue with the upgrade. Can you remove and re-add one of the existing devices? Maybe one not in a bunch of scenes or programs to minimize inconvenience. Just make sure to use the Z-Wave remove and not just the normal delete. Again, this would indicate an issue with the upgrade and not your Z-Wave implementation. Please let us know what you find out.

I have done something similar using just scenes, but it is pretty convoluted in my opinion. You have to set a key "on" status to "off" and the like. So, I generally use programs to do this. I find them easier to understand and maintain. Create a scene for each key and assign just the one key as a controller for the scene. The create a program for each key that, when triggered, executes whatever you want to do but also turns the other key scenes off. I use this procedure for my ceiling fan buttons. When I press the 'low" button, it sets the fan to low and turns the other buttons off. Similar programs for med, high and off. I group all my key programs in a folder for readability. You have to create a scene for each key because, while you can recognize a key press in an if statement, you can't control a specific key in the resulting then/else. So, you control via the scene.

I love the Zen32 but as you have discovered (which I did as well) there is no obvious small button "off". I was fine with that since I use them primarily as fan controllers, so each of the buttons triggers a program to set a fan setting. And it "turns off" the other button by just turning off the led. In my setup (details attached) the big button controls the fan light and the small buttons control the speed via an Insteon fan controller. zen32-bed fan-howto.rtf

In my yard utility room, I ran power to the low voltage transformer through a smart on/off wall switch. I am currently using z-wave, but an Insteon switch (or any other controllable by eISY) would work just as well. With my setup, I can control manually at the switch or programmatically using my eISY. It is currently part of my sunrise/sunset program. My setup is just on or off only. Nothing beyond that.

It is likely tmobile doing this. Verizon started disallowing this as well several years ago. Though I was too lazy to completely remove my text notifications and still occasionally I get one hours or days later. I now just depend on email notifications. Those seem solid. Try googling tmobile email to text notifications and see what might come up.

Major Kudos to bpwwer - Amazon delivered my Bond Bridge an hour ago. I fired it up and got it talking to my gas fireplace. Then I added the BOND plugin to my eISY (best $11 ever) and, after a restart of the admin console, it just magically showed up in my devices list. I added on and off as a responder to my Fireplace scene and now I can control my fireplace from button "F" (what else would I choose ) on my 8 button keypad. Thanks again!

Eisy:User Guide - Universal Devices, Inc. Wiki Yep - I had to do this once before. It restores it to its original setting and then you can install your most recent good backup. Good Luck!

Add me to the list of failed upgrades. I was on 5.8 something. I waited over an hour and nothing, so I rebooted. Still nothing. I had a backup so I could do a hard reset and reinstall, but I figured what the heck. So, I connected up my monitor and executed the command listed above by cutthroat and that worked for me. I love my eISY but I cringe and hold my breath every time I do an upgrade. It is the only time I ever have issues. I agree, some type of status should be available other than "it should take about 30 minutes".

Thanks again. I will have a local temp sensor as part of the integration as well. My Bond Bridge is scheduled for delivery today. My plan is to get it working and then install and start playing with the Plugin. I have not used plugins before, so this will be a learning experience for me. I'll update this post with my results.

Thank You! I will absolutely take a look. I was looking at the PlugIn list, but nothing jumped out. My plan is to trigger it when our hvac heating kicks on/off (an Insteon thermostat) to use as supplemental heat. So triggering on and off is all I really need.

Personally, I just don't trust any battery status indicator. I have a yearly reminder in my calendar to replace any battery for my remote sensors. Water leaks are too critical to worry about a battery. That is just the way I have decided to deal with it.

I have hunted around and am not finding anything that seems applicable. I have a new gas fireplace with a Radio Frequency remote to turn it on and off. I would love to be able to interface it to the eISY so that I can automate on and off. I know there are plugins that interface with other RF devices (ROKU, SONOS, etc) but what about a generic RF? Maybe a device that can learn my RF signal? I am considering trying to retrofit a Zooz Zen16 800lr relay. I installed one in a different gas fireplace but that fireplace was older and more compatible with the relay. I thought I would check here before I go down that path. Any thoughts? Has anyone else faced or solved this problem?

I also could see this being useful. But I don't see '$Timer' anywhere in my dropdown choices. Can you show a more detailed screenshot?