-
Random 'Failed Communicating with <device>'
Update. Not sure what happened but after everything, the frustration, the panic and time spent, all seems to be working fine. Still not certain what failed and why the major issues in getting it up and running after a modem replacement. I somehow believe my old PLM is ok. Any thoughts on why is appreciated. John
-
Random 'Failed Communicating with <device>'
@Brian H Revision 2.6 1223 on the PLM. I replaced this one with a new one with the same revision and date code... what a nightmare.. more to follow! And nothing at all has been changed or added in the last year. The status quo remains on all of that stuff. I can think of nothing new, added or plugged in, but I am starting to think that maybe something is creating noise or it is coming in from the lines or I have a faulty eISY, like the USB chip or driver got flakey. Last night after physically replacing the modem, plugging it in and plugging in the eISY, it was doing a query. That query ended up with nothing being found of course. When complete, I did a File>Restore Modem (PLM), (which I have had to do in the far past), and nothing seemed to be found... a few nodes were found and updated, however the rest were Failed Communication. The dreaded red exclamation mark. Being frustrated beyond all belief and wanting to just chuck everything, I walked away. About 10PM, I started to click and query each device one at a time. About half of my devices or nodes responded with the green Write Update to Device icon and I was able to individually update each device. HOWEVER, there were a few that after showing up and working just lost communication and the red exclamation mark reappeared. Then I could not get a positive query of other devices for some time. I tried to note the HVAC fan motor or anything else that might be running but nothing was. After letting things sit again for a few minutes, I was able to continue my manual query and write updates. There were a few that I had to Restore Device but by the time I went to bed everything was found and seemed to be working. When the HVAC came on everything was still alive and I just have no idea what if anything is making noise. I have to admit, I am looking at something flakey with the the eISY and figure it might be to my advantage to put in a ticket and pay whatever to try and find a fault somewhere in the eISY or at least where to start looking. At the time of this writing, 1030 AM MST, everything still seems to be working. In hindsight, (I have two locations and two eISY's), this one that I am having problems with did give me an issue with Notifications running but not connected during the big upgrade, which reinstalling the plugin twice, fixed, but I have had other issues with this one in the past. Especially after updates. I am not pointing the finger to the recent updates as it has worked great since that time, but something weird was going on and I have no idea on where to start sniffing. Now, I am wondering if this latest "fix" will stick or what may happen next but I will report back. Thanks! John
-
Random 'Failed Communicating with <device>'
A couple weeks ago I upgraded my second location eISY to the latest firmware, 6.0/7.2 and things have been going along well. A few days ago, Alexa would not turn some of lights on or off. Then it would. Checking my UDMobile, I could turn some things off and on and others would not. The ones that didn't react now would and others would not. Going directly to the JAVA app, same thing. Doing a Query of all devices a lot of devices failed to communicate. Everytime I would do a full query things would change. I can manually query individual devices and 9 times out of 10 they will communicate. Some after several queries. What a PITA. All of my stuff is Insteon and I have the USB power line Modem. I have rebooted the eISY, unplugged and plugged back in the modem, have unplugged the eISY, unplugged the modem, waited a minute, plugged it back in the plugged the power back into the eISY. Same results. I feel that my issue is a failed/failing USB modem as all worked very well BUT with new firmware, I have some doubts and it could be 'something else' firmware related. Can I do a modem restore? might that help or hinder? How do I know for certain or better, how do I troubleshoot to truly know that and/or where my problem lies. The modems are spendy, and it seems no matter what they will only last a few years. The cost of home automation I suppose. My modem is almost as old as the eISY as I purchased mine maybe a year after they were introduced. Thanks again you guys for all the help now as well as the past. Been using UDI since the ISY 994 came out! Oh, and does anyone know where to get a 2413U PLM as Insteon is out of stock until December. John PS. Never know where to put possible helpful tidbits, but in the new 6.0 firmware, after three (3) "Failed Communicating with..." dialog boxes, the following ones always come up blank. White screen inside the box.
-
johnjces started following New Web/Browser Based Login 6.0/7.2 , Random 'Failed Communicating with <device>' , After Upgrade to 6.0/7.2, Notifications Disconnected and 2 others
-
New Web/Browser Based Login 6.0/7.2
@RKenny04 Someone replied with use port 8080. That is incorrect. To stay local login via your isy finder by adding: https://xxx.xxx.xxx.xxx:8443/desc Your eisy ip address of course. You're SOL to login to the new web ui using any other port and your local user name. John
-
After Upgrade to 6.0/7.2, Notifications Disconnected
@DennisC THANK-YOU!!!! It took two reinstalls and that did the trick. Reconnected!! It always stated that thigns were running, just not connected. I was panicked as I get a bunch of notifications via the UDM!! @paulbates, I did place a post where I thought you mentioned and shared it here as more people seem to respond and when one is not sure what to do and not getting notificaitons it is to worry! But reinstallation and a couple of tries at that and we are back up! THANK-YOU AGAIN!!!! John
-
After Upgrade to 6.0/7.2, Notifications Disconnected
I have two eisy's each in a different location. I upgraded one eisy a couple weeks back and had no issues whatsoever. In the last few days, I upgraded the other eisy when I got to it and all seemed good. However I noticed today that I was not receiving any UDMobile notifications via the notifications plug in. When I checked the plugin it stated it was disconnected. PG3x was running fine, just that notification was disconnected. I tried stopping and restarting the plugin. I rebooted the eisy. Nothing brought it back online. A weird thing is when I stopped the notifications plugin, the timer kept counting being online... not the PG3x but the notification plugin. When I started it again, the counter never zeroed out to start again the time online or connected. How do I reconnect after this upgrade so notifications is connected and works again after this major upgrade? Thank-you in advance for any advice. John
-
Program Error in Web Based UI when displaying code
@Geddy I received an email that you replied to this post but your reply is not appearing. I am doing nothing other than just displaying my code and just going through things. I did easily note that no edits could be done just actually reporting this error. I do know that it is not yet 100 percent but just trying to help! John
-
On Clearing Java Cache and Rerunning Start.jnlp
@Geddy , Thank-you. All matches this time right out of the box! And this was a local logon not using portal credentials. Thank-you for the advice and answer. John
-
Program Error in Web Based UI when displaying code
Solved an error in a previous post whereby I could not display my code in a program using the new web based UI. By adding a dummy integer variable, (had plenty of State variables), I can now view my code. Thanks to @bmercier for this bug work around. Now, in my notifications using my email server, the old way of notifications, I get the following red error:"*** Action Not Supported: Notify ***". The line that is in error is: Send Notifications to 'Default' content 'Someone Opened Garage' That code above, clearly seen and editable in the original Java UI, that is hidden by that red error, still works just great as I get an email or text sent through my email server on any program I have using the original notification method supplied in IoX. Using the Notification Controller works just as well too, but there are times when a text, (which I can still do), or email can be preferable. My question is why? Another bug I would guess. Is the original form of Notification to be deprecated in future updates/upgrades, which I truly hope does not happen? Thanks again! John
-
On Clearing Java Cache and Rerunning Start.jnlp
I recently upgraded my eisy to the latest 6.0/7.2 firmware. I did not clear my java cache nor did I renew it by rerunning the startup java script, start.jnlp, needed after every upgrade. I have had no errors or issues whatsoever. In these latest upgrades, and moving forward, is this still necessary? My Finder appears correct, I can login locally and via portal credentials without any issue, warning or error.. Thanks for the info! John
-
New Web/Browser Based Login 6.0/7.2
@bmercier THANK-YOU! That worked! Had plenty of State variables bit no Integer variables. Other odd things have shown up that I will post separately. @wmcneil Thank-you too! That's what I read and I should have figured it out by fully reading!!! John
-
New Web/Browser Based Login 6.0/7.2
@bmercier Thank-you! Again, just I "thought" I read something about it at port 8080 in a forum post here. I guess I got confused regarding port 8080 in the mulitpage Forum Post/Topic "Questions after update to IoX v.6.0.0" Regarding clearing the java cache and running the start.jnlp again, is that really still needed? I didn't do it, everything works fine, but should that still be done moving forward. Lastly, I probably should create a new post but I'll try it here; In the new web/browser based gui, when I try to load my programs, any program, I get Error Loading Variables (1). I realize that the new UI is not at 100 percent, but just checking. Is this my error or a not yet mature UI error?
-
johnjces changed their profile photo
-
New Web/Browser Based Login 6.0/7.2
There has been some confusion over logging in to our eisy units since the major upgrade to the 6.0/7.2 versions. I have figured all that out and can sign in to my eisy with my local eisy username and password using port 8443, or using my portal password by not specifying any port and of course using the IoX Finder. By the way, I did not clear my java cache nor did I renew by rerunning the startup java script needed after every upgrade. I have had no errors or issues. From the UDI team, must I still do this? It seems to me that I read somewhere in the forums, that I of course cannot find, that one can login to the new browser/web based UI using one's local username and password by specifying a port and I thought that was port 8080. I've tried multiple browsers and my browsers report nothing is there, i.e. "looks like nothing is there" or similar reply for each browser. Is there a way to login to the new web/browser based UI using one's local username and password or is this fully entrenched in the cloud via the portal. After updating to 7.2, I forgot to sync my UDI Mobile and before doing that I could not access any of my variables using the web/browser based UI. After the sync to UDI mobile, all my variables came through. Prior to that had an error loading variables (1), or similar language buyt there was a (1) at the end. Thanks for your information and insight. John
-
Upgrading from old upgradable version to 7.0/7.1
Thank-you!!!
-
Upgrading from old upgradable version to 7.0/7.1
Does the latest update to 7.0/7.1 require the 6.x upgrade first? Or will the update do the full upgrade from 5.9.1 to 7.1. Just wondering about the sequence of events for those units not getting upgraded yet. Sometimes you have to update then do update again to get caught up. I still have one eisy on 5.9.1 that I won't get to until mid November. I had great luck with my local eisy from 5.9.1 to 6.0. will move to 7.1 in the next week or so on my local unit. Thanks. John