TSinclair

When you set up your condition in HA, try selecting "numeric state" instead of "state". You should be able to trigger on that. If your thermostat is in HA, I would likely use the HA app to trigger location. I have found it very reliable. I think you will find the "climate" call service in HA to easy enough to set up to change the thermostat to what I want.

I haven't tinkered with external antennas, so I can't say. Logically it seems it might be worth a try.

I've used a ZEN17 to control the garage door(s) in my detached garage for the last couple months. It has been 98% reliable. The 2% failures are from not opening or closing upon a z-wave button push from the house. I haven't had any random opens. With that said, I would not trust Z-wave at your 100' distance. I have a switch in a shed at about that distance and the success rate is ~80%.

I would add that after my migration to eisy I began using Telegram within the notification node server. It's been a couple months now and has worked very well. Not sure if you use iOS, but a bonus feature that I now probably couldn't live without is how well it integrates with carplay, it's nice to have the notification present and then siri read it to me.

Just for fun, I tried to create a new program as well as program folder using UDMobile. Now I've never used UD Mobile to do that before, so I don't even know if it should work, but received the error "Could not get programs data".

I am getting the same thing, "bad request" when saving a program on Eisy this morning. Other than clearing java cache, I have not tried to diagnose yet, but certainly odd.

I'm not familiar with the Jasco switches. You would assign the scene node generated during the z-wave pairing/interview to your program. Here is a simple example I am using: Garage Door Right - [ID 0206][Parent 0204] If 'Z-Wave Extra Nodes / ZY 043 Scene Button 2' is switched Fast On Then Set 'Garage / GA ZEN17 / ZY 093.2 Binary Switch' On Else - No Actions - (To add one, press 'Action')

I understand now. It is annoying that these switches do not function as elegant as insteon! A couple ideas would be to assign another variable that captures if the switch was activated by a motion sensor/program or check if the switch has any scene nodes. My zooz swiches do have scene nodes so I am at least able to use those for fast on's to operate programs (versus just status).

My workaround in this situation is to change the program to monitor status instead of control of the switch.

To keep it simple, I would use a second program for the reason stated above. Program Front Door Lights if from sunset to sunrise (next day) and 'front door motion-sensor' status is on then set front porch lights on run program front door lights off (THEN) else (blank) ________________________________________________________ Program Front Door Lights Off if (blank) then Wait 5 minutes set front porch lights off else (blank)

I'm surprised noone has responded to your question yet, so I'll take a stab. If I understand correctly you want alexa to announce if someone presses the doorbell, and you want to use the yolink app. If you have an existing doorbell, I see two possibilities. If you want to keep the chime, an automotive relay could be wired in with the chime/doorbell transformer and used to trigger a hacked yolink contact sensor, or if you don't want the chime you could simply wire the hacked yolink contact sensor with the doorbell wires. With that said, for the price of a yolink contact sensor and a relay, you could come pretty close to the cost of a ~$35 video doorbell that "works with Alexa".

As an Orchestrated MobiLinc user for MANY years I will concede the learning curve of UD Mobile was pretty steep. However after using it exclusively for 2+ months, I find its power and flexibility wonderful. Yeah remembering the hex colors and minimal icons was/is annoying, but the flexibility and ability to configure what works for my situation(s) is invaluable. The WAF is also high.

I only had only one of those messages overnight. I looked at my router log at the time of the offline/online notice and see the following: dnsmasq[7479]: Maximum number of concurrent DNS queries reached I'm not at all sure what that means or what is causing it, but it's the only occurrence of that message in my log.

I have experienced all Z-Wave devices going unresponsive. No doubt it was more frequent prior to 5.5.9, but has occurred once a few weeks ago (since 5.5.9). At least for me, a reboot doesn't solve, I have to go to each device and perform a Z-Wave>Synchronize>Update.

Please see screenshot. The description is not helpful so I poked around a bit to see if I could get identifiable information about the device but couldn't figure it out. Is there some way that I am missing, or should I send test messages to figure out which device is which? Thank you.