apostolakisl

Open weather also stopped working on one of my two ISY's. No idea why. It is not blank, it is a bunch of zero's. PG is saying there is an authentication error despite me confirming my api key is correct and active. But I don't think this has anything to do with this thread topic.

I have several of your node servers, but sadly, I can't confirm which ones didn't connect. Some of the node servers are on LAN only so they weren't affected. If memory serves, you did Elk and I have that one, but it is lan only. And when I click on the node server store right now, it isn't working. Nothing shows up so I can't see who wrote which nodes.

Spectrum failed me yesterday for about 3 hours or so. When service was restored, none of my PG3 or PG2 nodes came back online. It has been about 18 hours and none of the nodes reconnected to their online data source (ie Tesla, Husqvarna, etc). I restarted both PG2 and 3 and the nodes reconnected. This was not node specific, it was all nodes. Anyway, this really shouldn't happen. They should be able to restore connections after losing internet on their own. I believe that my public IP address did not change when Spectrum restored serviced based on my DDNS server logs indicating that I have had the same IP for a long time. EDIT: Running on Polisy

I totally agree with how fickle and buggy the Java console is and I do not like it at all. The one good thing I can say is that for many tasks you can now use the phone app. You can't write programs, but many of the other admin console tasks can be done from the phone.

Have you tried accessing the admin console from a different computer? I have had issue with the Java applet on one computer and simultaneously not on a different one. Though not this particular issue. The other thing to try is a reboot of ISY. For my rant of the day. The Java thing has always been a PITA but UD really doesn't want to change it. In the old days, Ctrl-Alt-Del/end task was something you had to do for almost any application periodically as they would hang. Well, MS seems to have fixed that maybe a decade ago, except for this Java console. I still find that it hangs and needs an "end task" maybe once a month or something. Clearly, something is not coded right. Not sure if it is Java itself or the UD applet. To the best of my knowledge, UD is the only Java applet I have need of use.

I have a 6 button kpl controlling the fans. I created a single scene, the kpl as well as the fanlinc are in the scene. The 3 KPL buttons for low/med/high are set to non-toggle on. The scenes when controlled by each of the KPL buttons will turn on the fan to its respective speed and turn off the kpl button for the other. The 4 kpl buttons, A is off, B is low, C is med, and D is high. All 4 of those buttons are controllers of the scene. If you turn on the scene from one button, the scene response is to turn off the other buttons and turn on the fanlinc to the corresponding speed. Since the buttons are toggle on only, pushing a button that is already on doesn't do anything. Pushing say medium button when it is already on low, will turn the backlight off on the low speed button as it changes the fan to medium speed. I actually have multiple fans and multiple fanlincs as well as some additional switches that will only turn the fans on/off but not control speed complicating this screen shot. But this is the screen shot of setting the fans to high.

If you want any of those devices to respond to conditions or actions of any of the other devices, then you need a common platform. PG3 is that common platform, of course it also integrates zwave and insteon devices.

Michel says it probably has something to do with a browser cache. I don't why my browser would be involved, I cleared the cache over and over for Java and rebooted computer and still same thing. I didn't try clearing browser cahce, not sure which one I would clear. Finally I just loaded the admin.jnlp off of the ISY itself and that works fine. Since I am only accessing this one ISY from that computer it works fine.

Posted here because IoX launcher thread is locked. I have been using IoX launcher since it came out on one particular PC. Yesterday, I could no longer get it to work on that PC. The java applet opens, finds ISY, I click on ISY, and I get nothing, no drop down menu. I ran windows update (and windows had an update to install), ran the java update (and java installed an update), deleted everything from Java including the applet, downloaded and installed fresh applet from forum, and still, same thing. Restarted ISY also. Also tried loading the portal access to the launcher but same problem if I click on that, no drop down menu to click on. I am able to open the admin console from a different computer using IoX launcher. I changed nothing on this computer, it worked 2 days ago and yesterday it didn't, nothing changed, not even a computer reboot (until I started trying to fix the situation). The computer is behaving perfectly. Ideas?

@Panda88 I wasn't able to find any beta version. Also, installing a beta version means it will not have any of the programs and stuff I use with it to test unless I want to redo all of them. I saw the beta version in my previous purchases section, but clicking on that didn't work.

@Panda88 Sorry, just noticed this today. Hard to test since Tesla server needs to go down and who knows when that will happen. Perhaps never? Anyway, I'll load it up and let you know if there are any issues.

As far as I can tell, this has only happened twice, and both times I know that Tesla server was down because my phone app wouldn't talk to the car. So the pathway to failure would seem to have something to do with the Tesla server not responding.

It isn't the node that fails per se, it is the Tesla server that goes offline, then the node isn't resetting when the server comes back online. I knew that Tesla was offline because my Tesla phone app stopped working too.

I have seen this twice now. Tesla server seems to have gone down for a period of time, the node says "failed", but when the Tesla server comes back online, the node still says "failed". Restarting the node does the trick, but it seems like it should have a mechanism to fix itself in this situation.

Yes, I guess I wasn't clear about the at home car is with sentry off. Sentry definitely uses some battery. Waking the car up once per day doesn't use much battery.

I have been running the tesla node server for about 6 months, basically since it was a thing. The short poll just queries the Tesla server and does not affect the car. The long poll will wake the car up and you will lose quite a bit, maybe 5 percent or more per day if you have your long poll short enough that the car never sleeps. I made this mistake when on a 2 week vacation and checked my car about 1 week in and saw that I lost like 40% of my battery. I turned off the node server and then it lost barely anything for the second week. I did not have sentry mode on at all for this trip. I currently have the long poll set to 24hours and the short poll to 15 seconds. When my car is at home and not plugged in, the battery hardly loses anything, less than 1 percent per day. At the airport, with sentry mode on and long poll at 24hours, the car loses a couple percent per day.

Turns out deleting the java applet and reinstalling fixed the clock. So I guess it was just the time displayed on the admin console and not the time running on the machine.

My Polisy also did not adjust for DST (still on Standard time). I believe that my programs still ran correctly, but probably wrong by an hour. I was out for the evening both Sat and Sunday night so didn't notice. Time zone is set within the admin console to the correct location and the DST box is checked (but greyed out). In PG3, I see no time settings. In PG2 I have the location set, but there is no DST setting available. I don't know anywhere else you might set the time zone. Do I need to change my location to get the time correct until a fix comes out for this? Of course changing my location will screw up sunrise/sunset.

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 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.