tmorse305

Hi @Jimbo.Automates, I'm running 3.4.6. I had some issues regarding the PGx upgrade but Michel was able to resolve it. My user name for Telegram is now missing from the configuration and there's no way to add it. See screen shot I cannot physically type it in anywhere. What am I missing? Also I'm on the latest version of PGx that came out today. Do I need to update Notifications to the latest too? I held off because you had said there were some issues going to the latest. Thanks!

Does you system operate normally despite the error? I had this problem yesterday but my system would not get past the error. I opened a ticket and by the end of the day they had fixed something on their end and the update then happened successfully. I also had this problem yesterday and it was resolved by what ever Michel did on their end of things. Did you try it again today? Try it today and see if you are successful Note, I had a new problem today and had to open another ticket. There is a bug in .32 that causes trouble if your internet connection gets flaky. There is a .33 fix that is due out later today. BTW, thanks to Michel for the amazing customer support!!

It looks like there was a change made in the ISY integration earlier this year. Follow these links: https://community.home-assistant.io/t/new-isy-variable-method/529753 https://www.home-assistant.io/integrations/isy994/ I have no experience with the new method but hopefully you can make sense out of it.

You do need a Node Server to do this. If you can't find someone to create the NS then you could use HA as the interface since it is already integrated with HA. Add the ISY interface to HA and then use the HA to pass the data to ISY. I did this a while back when there was no NS for Blink. I retired it as soon as a Blink NS came out, but it worked great.

It looks like there is a program turning it off. Use the Find/Replace function on all programs and look for occurrences of that Appliance Linc.

Did you find the IP address for the ISY connected to the eero?

You also might try to disable the ISY skill from Alexa then re-link it. I have fixed a few problems doing that.

If you tap on the entry for your isy it will display the IP address. Here is mine for my eisy but it's the same for your ISY.

Since you didn't provide a lot of details about your program or the motion sensor here is some general guidance. I'm assuming you already have a program that turns on the light to 35% at sunset, I going to call that the "Sunset Program". Add a 2nd program that does this: If Motion is detected and time window for the "sunset program" is true (ex. > sunset and < 11PM) Then Turn lights on to 100% Wait 5 Minutes Run "Sunset Program" (if path) Depending on how your if path in the "sunset program" is written, this might not work. If the condition is "after sunset and before 11PM" for example, it will work.

If you can control devices from the Portal and Mobilinc then your ISY definitely has an IP address. I wonder if you might have a failing SD card.

How far away is the pump from the house? Another solution would be to fix the ground wire. You could add a second ground wire at the pump and shallow bury it back to the house. If it's near your electric meter you might be able to ground it on the outside of your house, there is often a ground strip for use with phone and cable utilities. Otherwise you would have to come up with a way to get it back inside. Just a thought.

Use the Event Viewer set to Level 3 and capture trying to turn it on and off. Post the results here

Thanks Jim

Hi @Jimbo.Automates, I had an unexpected response today using the NS. I have a program: Squirrel Detect - [ID 0154][Parent 0001] If 'Camect / Deck / Deck animal' Squirrel is True Or 'Camect / Deck / Deck human' Person is True Then Set 'Squirrel Blast / Virtual Buttons Controller / Virtual Button 01' Push Button Today I enabled "unknown animal" on the Camect app for this camera. Shortly there after Camect detected an unknown animal and the above program triggered. The screen shot of the node is attached. Here is the log file entry: 2023-05-04 10:05:53,665 Thread-14 udi_interface DEBUG Host:callback: {'type': 'alert', 'desc': 'Deck just saw an unknown animal I'll PM you the log file Thank you.

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.