tmorse305

I also use Geofency on my phone. On rare occasions I'll get a message that a webhook failed. I switched from Locative years ago because it was unreliable for me. Geofency has worked even when the UD geofence did not. Hopefully a larger radius will solve the problem. I'd like to retire Geofency in favor of the UD solution. One less thing to manage.

Hi @Javi, I increased the radius from 200 to 500. I'm 3 for 3 so far so maybe that was the issue. I'll keep you posted if that changes. Thanks all for the heads up on 16.4.1, I'm going to wait until the dust settles before updating iOS.

I'm going to hold off doing the update to 16.4.1. Yesterday I left 3 times. It worked 2 out of 3. All the re-entries were ok.

I'm on 16.3.1

I am setting a variable on exit and return. I am using Testflight

Thanks for the reply. The geofence is less than 1/8 mile. I don’t have vehicle WiFi so the switchover for my phone is to cell service.

Hi @Javi, I've noticed intermittent operation for me with the geofence functionality. It seems to happen more when I exit then when I return. When I leave the geofence I can see the departure acknowledged. but the variable does not change. There is an error in the log, attached. What is causing this? Thank you.

Thank you, that did the trick!

I was trying to create a web hook for a KASA plug. I got error 400, see attached screen shot. When I changed the device to an Insteon switch, it accepted it without a problem, see screen shots. Is there a restriction about what devices can be used? Or maybe this is related to the another thread is saw where error 400 was generated when trying to add a spoken? Thank you.

If you pull the jumper you will lose the AC. The jumper is used to turn the compressor on (yellow wire)when the thermostat calls for cool via Y1. The reversing valve will be energized by the orange wire but the compressor won't run. If you turn on the heat without the jumper the heat will operate normally. I know this is the opposite of what Mirgo said above but I think he has it backwards based on the wiring diagram you show above. If you want to restore the Fan On functionality you could do this: 1. Remove Jumper (W1-G) 2. Add a switch between W1 and Y1 Switch Open = Heat Only Switch Closed = Cooling only If you try to cool with the switch open just the Fan will run, no cooling If you try to heat with the switch closed the cooling will run forever as the heat setpoint will never be satisfied.

It is set up as "o". To make it "b": 1. Remove jumper 2. Swap Orange and Yellow wires 3. Jumper "G" to "Y1" Note: Never set the Fan to "On" or the compressor will run as long as the fan is on regardless of the set point.

@Mirgo Maybe the color coding is different, but on my HP system the yellow wire is the compressor. With the jumper that was added it seems that if the Fan is switched from Auto to On on the thermostat, the compressor would run (heating) regardless of the temperature setting. That seems like a downside.

Thank you for the quick response, all is well with 3.2.1

Hi @glarsen, I just started up the RainMachine NS for the season today. I'm running 3.2.0. The NS is up and running but the AC indicates that the RainMachine status is Offline. I looked in the log and I saw this error: 2023-04-14 21:27:10,908 Thread-58 udi_interface ERROR rmfuncs:rmHeartBeat: Ping Error - No Heartbeat 2023-04-14 21:32:10,920 Thread-76 udi_interface ERROR rmfuncs:rmHeartBeat: Ping Error - No Heartbeat The odd part is that it is working, I can turn zones on from the AC. I noticed in your change log that there is a version 3.2.1 but it doesn't seem to be available in the NS store even after a refresh. Any suggestions? Thank you for your help.

I switched the Camect host to the IP instead of camect.local and that fixed it. Weird that it worked the first time I installed it. Thank you!

Hi @Jimbo.Automates, I tried to add another camera but I couldn't get it to show up in the AC. I have 6 cameras currently active in Camect. I deleted the NS and started over thinking it would pick up the new camera. Now it doesn't find any cameras. The controller node shows up in the AC but that's it. I tried the DIscover button in both the NS and the AC but no luck. Log attached, it looks like the user and PW are not set but they are saved in the configuration. Thank you.

@Jimbo.Automates, Camect's built in connectivity to Telegram has been enough so I couldn't really see a need for the NS in my automation. That just changed! I built a bird/squirrel deterrent a while back that uses compressed air to scare unwanted birds and squirrels out of my feeder, see photos of setup. I use the guts from a cheap wifi plug and a time delay relay to create a nice short pulse of air pointed at the feeder. I used Alexa to trigger the air blast. This week I added a camera and your NS. With the Camect set to detect squirrels the blast is now automatic when there is a squirrel. I attached a video of it in action. The response is a little slow because the wifi plug does not connect directly to an NS so I have to send the command to Alexa first. Now if I could just get the Camect AI to distinguish kinds of birds. https://www.dropbox.com/s/40lt83xrevbauoq/Video Apr 03 2023%2C 5 23 00 PM.mp4?dl=0

I actually just got in. I recalled a screen within the app. I found the admin user, I guess I set it up sometime ago. All good, thank you!

Hi @Jimbo.Automates, I just installed the Camect NS. I use 'Sign in with Google' to access my Camect. Those credentials don't seem to work. Is there a preferred method to access Camect? I tried using my regular email (not gmail) but the log in process sends a link to my in box, no password required. Thanks.

My "Good Night" routine works without an issue. Maybe something changed (again) since you last tried it. I say "Good Night" from bed so the order is not important. I do use a program as you suggested, that way I can include a check to make sure all the doors are locked. If one is left unlocked Alexa will let me know.

As it should. If you said "Alexa turn Good Night on" then you should see your lights go off. To shorten the phrase to "Good Night" create a routine in Alex with a spoken trigger of "Good Night" and an action that turns on your scene.

The virtual switch added to a scene is the only way to trigger a program based on a scene activating. Individual items in the scene can be triggered independently of the scene being activated. Actually you can set the delay to 0, so either a contact or motion will work the same way. I use both depending on what makes more sense for the action that's happening.

@bwade913, You can eliminate the first 2 programs by adding the virtual button 01 to the scene. When the scene fires the button will be pressed. You still need a 2nd button however to shut it off. There is another NS call Virtual that allows you to add as many switches as you want. These can also be added to scenes but act as a toggle not a push button. When the scene is on the switch is on, when off the switch is off. The status of this single virtual switch can be passed to Alexa via a variable configured as a motion sensor which can toggle the 2 Alexa routines to control the lamp. One downside to this approach is that Alexa throttles the change to once every 30 seconds. No monthly fees.

To confirm the noise problem you could connect the 2476D you just removed from the wall to a power cord. Black>Black White> White Ground > Ground Red - no connection but cover it with a wirenut so it can't touch anything Plug it in near the PM then try to add it.

@waffles, I still think the root of your issue is communication problems. Take one or both of the worst offending sensors and place them next to the PLM for a few days and see what happens then.