Jump to content

The PLM Saga Continues


smokegrub

Recommended Posts

I have an ISY that is located more then 300 miles from my primary residence. A few day ago I stated getting erroneous multiple email messages from a hidden door sensor that the door had been opened. After that happened a couple of times, a program failed to run that reports temperature. I also had a SyncroLinc erroneously twice report that a well pump had run. Today,  I accessed that ISY and saw that all the programs in the program tree had disappeared. It is evident that the PLM has died. This is no longer just a nuisance. It is for me a critical failure. I will not return to that location for 4 months! The fact that I have numerous battery powered devices makes replacement of the PLM something that my elderly handyman could not manage for me. Fortunately, I can, at this time, still access the device tree and manually execute important actions but whether or not any programs will continue to run is doubtful given that one did not run this morning. Of course, I am also concerned that the PLM will completely fail. Smarthome needs to address this issue now!!! We need a dependable PLM! I, for one, am sick and tired of reading over and over again about failing PLMs and experiencing my own failures. In situations such as mine where great distances are involved I can foresee where such failures could have consequences that result in more than mere nuisances. I know that UDI once wanted to produce a reliable PLM but Smarthome blocked that path. I encourage UDI to make that request once again.

 

Teken, et al, I long ago endorsed the request for such a PLM but I have seen nothing that even suggests that Smarthome is doing anything to address that request. 

 

Link to comment

H

 

I have an ISY that is located more then 300 miles from my primary residence. A few day ago I stated getting erroneous multiple email messages from a hidden door sensor that the door had been opened. After that happened a couple of times, a program failed to run that reports temperature. I also had a SyncroLinc erroneously twice report that a well pump had run. Today,  I accessed that ISY and saw that all the programs in the program tree had disappeared. It is evident that the PLM has died. This is no longer just a nuisance. It is for me a critical failure. I will not return to that location for 4 months! The fact that I have numerous battery powered devices makes replacement of the PLM something that my elderly handyman could not manage for me. Fortunately, I can, at this time, still access the device tree and manually execute important actions but whether or not any programs will continue to run is doubtful given that one did not run this morning. Of course, I am also concerned that the PLM will completely fail. Smarthome needs to address this issue now!!! We need a dependable PLM! I, for one, am sick and tired of reading over and over again about failing PLMs and experiencing my own failures. In situations such as mine where great distances are involved I can foresee where such failures could have consequences that result in more than mere nuisances. I know that UDI once wanted to produce a reliable PLM but Smarthome blocked that path. I encourage UDI to make that request once again.

 

Teken, et al, I long ago endorsed the request for such a PLM but I have seen nothing that even suggests that Smarthome is doing anything to address that request. 

Have you thought about switching to Zwave ?

Link to comment

I have an ISY that is located more then 300 miles from my primary residence. A few day ago I stated getting erroneous multiple email messages from a hidden door sensor that the door had been opened. After that happened a couple of times, a program failed to run that reports temperature. I also had a SyncroLinc erroneously twice report that a well pump had run. Today, I accessed that ISY and saw that all the programs in the program tree had disappeared. It is evident that the PLM has died. This is no longer just a nuisance. It is for me a critical failure. I will not return to that location for 4 months! The fact that I have numerous battery powered devices makes replacement of the PLM something that my elderly handyman could not manage for me. Fortunately, I can, at this time, still access the device tree and manually execute important actions but whether or not any programs will continue to run is doubtful given that one did not run this morning. Of course, I am also concerned that the PLM will completely fail. Smarthome needs to address this issue now!!! We need a dependable PLM! I, for one, am sick and tired of reading over and over again about failing PLMs and experiencing my own failures. In situations such as mine where great distances are involved I can foresee where such failures could have consequences that result in more than mere nuisances. I know that UDI once wanted to produce a reliable PLM but Smarthome blocked that path. I encourage UDI to make that request once again.

 

Teken, et al, I long ago endorsed the request for such a PLM but I have seen nothing that even suggests that Smarthome is doing anything to address that request.

Programs not visible in the Admin Console would point to an issue with the ISY Series Controller. I would suggest a remote reboot and circle back as to what is seen afterwards.

 

Please keep in mind when you're accessing remotely the terminal you're on and using should have the same UI / Firmware. Otherwise strange issue can and will be present.

 

Also clear and delete the Java Cache if you do find a mismatch when selecting Help -> About.

 

Is the 2413S PLM at the two year mark? I ask because sometime last year you had similar issues of things happening and never heard back what you did to resolve those past issues?

 

 

Sent from my iPhone using Tapatalk

Link to comment

Programs not visible in the Admin Console would point to an issue with the ISY Series Controller. I would suggest a remote reboot and circle back as to what is seen afterwards.

 

Please keep in mind when you're accessing remotely the terminal you're on and using should have the same UI / Firmware. Otherwise strange issue can and will be present.

 

Also clear and delete the Java Cache if you do find a mismatch when selecting Help -> About.

 

Is the 2413S PLM at the two year mark? I ask because sometime last year you had similar issues of things happening and never heard back what you did to resolve those past issues?

 

 

Sent from my iPhone using Tapatalk

 

The firmware and ui are both 4.6.2

The PLM is itself a replacement which supposedly was more durable than its predecessor. The PLM is 26 months old.

How do I remotely reboot the ISY????

Link to comment

That makes sense, but consider getting Zwave when you need to add or replace devices.

 

If the new company, Smarthome, does not aggressively address this and other issues, I will do that as the need arises and the Zwave device is the more superior of the two. There are some devices I love, e.g., the KPLs, that have no Zwave equivalent. Plus, as I go down that path I am aware that device communications will be an issue. As I see it, the home automation game is significantly changing and competition is going to become more prevalent. The PLM is, to me, a no brainer and why Insteon has not addressed it astounds me. It is almost as if they were inviting erosion of a significant portion of their customer base. 

Link to comment

The firmware and ui are both 4.6.2

The PLM is itself a replacement which supposedly was more durable than its predecessor. The PLM is 26 months old.

How do I remotely reboot the ISY????

 

At 26 months its probably time to replace that 2413S PLM. If you accessed the ISY Series Controller from home where you are you need only select the *Reboot* in the general tab on the Admin Console. 

 

This of course assumes you set up port forwarding on the router where the remote system resides. 

Link to comment

At 26 months its probably time to replace that 2413S PLM. If you accessed the ISY Series Controller from home where you are you need only select the *Reboot* in the general tab on the Admin Console. 

 

This of course assumes you set up port forwarding on the router where the remote system resides. 

 

I will change the PLM as soon as I get there in 4 months.

 

There is a "Restore ISY" option available under the File menu. Will executing that option affect the battery devices?

Link to comment

I would reboot the controller first and report what you can see. If you select restore ISY that will leave any battery operated device in a unknown state.

 

 

Sent from my iPhone using Tapatalk

 

Pardon me for missing something: Under the File menu in the Admin Console the only options I have are:

Backup ISY

Restore ISY

Restore Devices

Restore Modem

Delete Modem

 

There is no option to reboot the ISY remotely that I can find.

 

I continued poking around and saw a Reboot button under the Configuration tab. Is that it?

Link to comment

I rebooted the ISY from the Configuration Tab in the Admin Console. I then loaded the system from the Admin Console and the programs did not reappear. I waited a couple minutes, reloaded from the Admin console again and the programs were there! Thanks for the help. Now, if the PLM will survive for the next 4 months I will be able to change it.

 

You guys are the best.

Link to comment

I rebooted the ISY from the Configuration Tab in the Admin Console. I then loaded the system from the Admin Console and the programs did not reappear. I waited a couple minutes, reloaded from the Admin console again and the programs were there! Thanks for the help. Now, if the PLM will survive for the next 4 months I will be able to change it.

 

You guys are the best.

 

That's great to hear one last tip for you in case this hasn't been done or known to you. There are two versions of ISY firmware that anyone can use on the system. One assumes you have and use Insteon and requires the 2413S PLM. Should the 2413S PLM ever fail and not be seen by the ISY Series Controller it will declare a fault and more often than not you will not be able to access the Admin Console (AC).

 

The other firmware supports Insteon, Z-Wave, and ZigBee.

 

If you install that firmware should the 2413S PLM fail it will still allow you to access and use the controller. Even though the Insteon network is not fully operational or at all at least this isn't one extra thing to worry about.

 

Please do consider updating your ISY Series Controller to this firmware version.

 

Happy New Years . . .

Link to comment

That's great to hear one last tip for you in case this hasn't been done or known to you. There are two versions of ISY firmware that anyone can use on the system. One assumes you have and use Insteon and requires the 2413S PLM. Should the 2413S PLM ever fail and not be seen by the ISY Series Controller it will declare a fault and more often than not you will not be able to access the Admin Console (AC).

 

The other firmware supports Insteon, Z-Wave, and ZigBee.

 

If you install that firmware should the 2413S PLM fail it will still allow you to access and use the controller. Even though the Insteon network is not fully operational or at all at least this isn't one extra thing to worry about.

 

Please do consider updating your ISY Series Controller to this firmware version.

 

Happy New Years . . .

 

That is something I did not know. I will download and install that firmware and delete the JAVA cache.

Link to comment

That is something I did not know. I will download and install that firmware and delete the JAVA cache.

 

Bare in mind this should be done when you're able to do so while on site. As doing so will leave any battery operated devices with a unknown state icon or not reflect its last state until it changes.

Link to comment

Oops! I did this while away. Darn!

 

Oh, well.

Not a big deal just something to keep in mind. Also if your battery only hardware is newer and has the heartbeat node.

 

You can create a program to update those devices when the heart beat comes in. The update works on some pretty good while others are hit and miss. Playing with a wait time seems to help in this aspect.

 

Since the update can you see all of the programs?

 

 

Sent from my iPhone using Tapatalk

Link to comment

Not a big deal just something to keep in mind. Also if your battery only hardware is newer and has the heartbeat node.

 

You can create a program to update those devices when the heart beat comes in. The update works on some pretty good while others are hit and miss. Playing with a wait time seems to help in this aspect.

 

Since the update can you see all of the programs?

 

 

Sent from my iPhone using Tapatalk

 

Yes, I can still see all the programs plus all the battery devices show their correct status in the device tree. What would a program look like to update these devices during heartbeat?

 

I will wait to see if the battery devices report before doing anything else.

Link to comment

Yes, I can still see all the programs plus all the battery devices show their correct status in the device tree. What would a program look like to update these devices during heartbeat?

 

I will wait to see if the battery devices report before doing anything else.

 

I checked and none of the battery devices now show their status.  :  (

 

I would appreciate you guiding me in developing the program to try addressing these issues during heartbeat.

Link to comment

Yes, I can still see all the programs plus all the battery devices show their correct status in the device tree. What would a program look like to update these devices during heartbeat?

 

I will wait to see if the battery devices report before doing anything else.

 

I appended an image capture for you as a picture tells a thousand words better. Let me know if you need more insight or guidance in this endeavor. You will notice there are two programs one is to address the older style motion sensors. Once that sensor see's movement it will remain on to auto update.

 

The other is an example of ANY device which has a heart beat node. As you can see I selected a random device and choose the appropriate node for both conditions. Once seen it will remain on and update and than go back to sleep. As I stated early on you may find a *Wait* statement is required for the most consistent response and completion.

 

I've found a wait from 0~3 seconds is the window that works.

 

NOTE: For the benefit of others or new users the heart beat node of On vs Off is not a mistake. As some versions of firmware shockingly sent a off signal instead of a expected ON signal. Thus the reason to monitor both states which will allow you to auto update the device with pending writes.

 

Of course you need to wait the customary 24 hour period before this will happen. Which of course relies upon you having a strong Insteon RF mesh in the home where ever the devices reside. The Hidden Door Sensor which has adjustable heart beat interval will of course update based on that defined report in.

post-1970-0-51322200-1514909742_thumb.png

post-1970-0-88787500-1514909898_thumb.png

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...