apostolakisl

I have been pulling my hair out with geofencing. I am on Android. I take it that UD Mobile on IOS has native geofencing . . .yes? Will this be on Android soon? I have been using the antiquated UDI Mobile with a frustrating level of works almost all the time, which is just good enough for me to keep using it but get super annoyed when it fails.

Looking at maybe doing some yolink stuff. But I want the node server to access locally, no cloud. Can't figure out from the description here is the node server is locally accessing the hub or it is accessing Yolink's server. Thanks

I can't say if this is your problem, but really the only point of ISY failure I have ever seen is the SD card going bad. You might try replacing the SD card and then restoring.

Does it make any difference which flirc? I've never used flirc and I see they have a couple models. Currently, I took my old isy99ir out of retirement and have it accepting the 40 IR codes and then relaying to my polisy. It was fun trying to dig up the admin console software to do that. My needs are not complex. I am using about 20 of the 40 IR codes and doubt I will ever need any more.

Polisy has usb ports, so I could plug a flirc in, but would it work? Also, is it possible to have flirc/your node server automatically load the standard 40 ISY IR codes?

I can understand that, but I have an S22, pretty much the latest and greatest. Other geo apps like life 360 seem to always work. And UDI mobile is always correct, but for some reason it just doesn't automatically send when I cross in/out. But it always knows where I am. My Tesla always knows where it is and all the geo-fences on it work great (like opening my garage door and raising the suspension), but there is no way to have the car post a url. I did figure out why the wifi/tasker didn't work, I have multiple ssid's and it was logging into the wrong one. I "forgot" the incorrect ssid so it only logs into the correct one.

Tasker I am using logging into wifi. Right now, I am logged into the wifi that is supposed to send the url, but it did not. I will look at the other way to use Tasker, but I want to say I tried that years ago and had issues, but let me look again. It seems like however, that there should just be an simple app that upon entering a geofence posts a url.

There has got to be a reliable geofence app out there. I have tried UDI mobile, Tasker, and Alexa. None of them work reliably. Sometimes they work, sometimes they don't. If I open UDI mobile and hit it to refresh location, it gets it right, but half of the time it just pays no attention to your location until you click on it, which of course defeats the purpose. Alexa doesn't really work much at all. Tasker is set to report when I log into my wifi, that just sometimes pays no attention either. There has got to be an app for Android that you can set a geofence and have it reliably post to the ISY URL.

It was my impression that they are the same software running on different hardware. It has always (or almost always) been my impression that bugs were largely hardware independent assuming the hardware isn't massively different. For example, bugs in an iphone app usually exist the same across many generations of iphone. Perhaps I am wrong and eisy is running different software than polisy or maybe there is a hardware dependent issue, but for something like doing an automatic update, that really seems like it would be strictly a software issue.

Just updated Tesla from .18 to .19 using the button. Did you try power cycling first? Curiously, it still is asking me to restart to update to .19, even though it is running .19. I "x'd" out of the message, restarted, and it seems to still be gone. @bpwwer

No, I have polisy and restart of nodes or even the entire polisy with a power cycle or otherwise does not update my nodes. Using the store to get to the "reinstall here" does work.

Thank you, I am quite familiar with the bug. It has nothing to do with using the reinstall button. Only restart.

Clicking the reinstall button should work. I have done it on lots of nodes, including the tesla one. Maybe try a hard power cycle and then use that button.

@vandy what mr bill said. In the old days you could hit a single button "copy scene to all devices" or something like that, but when ISY started supporting things besides Insteon, I guess that tool conflicted and they got rid of it. So now you have to go through and set your device on level and ramp rate for each of the controlling devices. Understand that the primary scene is when ISY/PLM is the controller. ISY/PLM as controller isn't really any different than any of the other controllers, but the way it is displayed in ISY it seems different. Keep in mind, you don't have to set the settings the same, you could have the same scene turn on differently depending on which of the controlling devices you used to turn it on. As Mr. Bill said, this is something you might want. For example, you might have a scene in your bedroom, when you turn it on from a switch next to your bed, you might want the devices to come on dim, but when you turn it on from the door you might want it bright.

This happens sometimes, I don't know how. The PLM can lose links, and somehow those links also get lost from ISY, since restore PLM should fix it but doesn't always. At that point, the only solution is to delete it and start over from scratch. Glad you got it done. The bummer is if your device is in a bunch of scenes and programs.

You have missing links. You will need to delete the device from ISY, factory reset the device, then add it back. You will need to of course rebuild all the scenes and programs that the switch is part of. I find it easiest to do screen shots of this stuff to be certain I get it all back correct. EDIT: Outside chance if you do a "restore plm" it might fix it too.

Using Insteon has been a roller coaster ride. I could not be happier with my current iteration of Insteon. The dual band stuff (aside from PLM) has all been rock solid going on maybe 10 years now without a failure. I actually thought I had a failure, and then realized it was an old single band straggler I had forgotten to replace. I see two flaws with Insteon. 1) it is not secure. While it would require a physical presence on my property to hack, it is still easily hacked by someone who might know what to do. Therefore, it is limited to non-secure functions. However, to the best of my knowledge, there is no way to hack anything except an Insteon device, in other words, it can not be a backdoor to my network. 2) It is nearly, but not 100% reliable. This is, of course, an issue with almost all protocols aside from hard wired ones. Therefore, you can't use it to control anything critical, where a failed command would mean damage and destruction. So for both of the above, I use other protocols (mostly hard wired). If I were to do it again, I would still go with Insteon. The speed of response and amazing ways you can configure them is unmatched (except perhaps in hard wired Creston and such). Coupled to ISY there are just an endless number of possibilities.

I asked openai to write a program for isy that turns on the lights every night at sunset until 10pm, and it gave this answer: import datetime from pyisy import ISY # Connect to your ISY device isy = ISY.Isy("http://your-isy-ip-address", "your-username", "your-password") while True: # Get the current time now = datetime.datetime.now() sunset = isy.sunset() # Check if it's after sunset but before 10pm if now.time() > sunset.time() and now.time() < datetime.time(22, 0): # Turn the lights on isy.on("your-light-node-address") else: # Turn the lights off isy.off("your-light-node-address") # Sleep for a minute before checking again time.sleep(60)

I have tested it and it appears to work now. I connected elkrp2 to the system, disconnected, and ISY still had access to the system. Thanks. @Jimbo.Automates

Wouldn't any processes be reset with a soft reboot? Anyway, I'll test it out tonight.

No. I just did the update a few minutes ago so haven't tried. It is now running .8 But since you had never seen this issue, I'm assuming you didn't do anything that might fix it between the .7 and .8 versions. Unless you accidentally fixed it because it was something in common with another issue you did know about. Just seems very odd to me that an entire power cycle of polisy is needed. What issue could persist through a restart of the node or a soft restart of polisy?

It was reproducible. Both time I connected to ElkRP2 I had to power cycle polisy. Soft restarts of the node and PG3 did nothing either time. The first time I also tried power cycling the Elk ethernet module.

@Jimbo.Automates what about the problem with having to power cycle polisy after connecting to elkrp to get it to connect again?

@Jimbo.Automates This has happened again. I needed to use ElkRP, logged in, did what I needed to, logged out. The node server was now not connected. Restart the node, nothing, restart polisy from the PG3 console, nothing. Had to hard power cycle polisy to reconnect. In addition, I am on 3.5.7 while the current is 3.5.8. None of any of these restarts updated to the latest version. My Tesla node server also is not updating even though it is an old version. Something is not right with this.

@arf1410 That works fine, but can be very tedious if there are a lot of dates.