steve cougar Posted March 5, 2011 Share Posted March 5, 2011 PLM WRITE FAILS Hi, I just replaced my old PLM with a new 2413S, Dual Band. The changeover went smoothly, no issues. However the icon for my PLM now constantly shows a green (1011) and every time I right click on the PLM and choose "Write Updates to the Device" I get an error that says: "Failed writing device link" PLM [-200000/-51] Everything seems to be working fine though. Any ideas? Thanks Link to comment
LeeG Posted March 5, 2011 Share Posted March 5, 2011 The PLM used by the ISY as the powerline interface is not a defined device and should not be in the My Lighting tree. Link to comment
steve cougar Posted March 5, 2011 Author Share Posted March 5, 2011 Okay. It is where it is and I can't seem to be able to move it anywhere else. Under the "Main" tab I have "Network" and under that I have "My Estate". Each device program and scene is located under that along with the PLM. Link to comment
LeeG Posted March 5, 2011 Share Posted March 5, 2011 The PLM is automatically identified when the ISY boots up with the PLM connected to the Serial port. Delete the PLM definition in the My Lighting tree. Be sure to have a current Backup before deleting the PLM device entry. Link to comment
steve cougar Posted March 5, 2011 Author Share Posted March 5, 2011 Okay, bit scary... thinking I'm going to delete the PLM from my system and make an appointment for a hair transplant but I did it and everything is still working and no PLM under my lighting anymore. Thanks Leo! Link to comment
Brian H Posted March 5, 2011 Share Posted March 5, 2011 After the PLM swap. In the files menu area. Did you use the "Restore PLM" choice to update the ISY99i system to the new PLM? That is how I swapped my 2412S for the newer 2413S. Restore PLM was needed to do it. Link to comment
steve cougar Posted March 5, 2011 Author Share Posted March 5, 2011 I do not see what you are referring to. I followed the instructions given the post about swapping PLMs. When the new PLM was installed I selected "Restore Modem PLM" from the choices on the "file" menu and that was it. Did I miss something? One problem I'm having is that the "Status" is not being updated under HomeSeer but that might be a fault of the plug-in so I didn't post that problem here. Link to comment
Brian H Posted March 5, 2011 Share Posted March 5, 2011 No there was a type on my post. Restore Modem PLM was what I wanted to say. Not replace plm. Link to comment
LeeG Posted March 5, 2011 Share Posted March 5, 2011 I was holding my breath as well. The backup would have you got you back in case bad things happened. The PLM should not have been defined as a device so what the ISY would do when deleting it was a question. As Brian has inquired, did you Restore PLM after booting up with the new PLM. Either the Wiki or the User Guide has the steps to follow in replacing a PLM. It is not the same as replacing a device. If a Restore PLM was not done then the Admin Console will not reflect the correct device status because the devices still have the old PLM address. Also Programs will not trigger for the same reason. Link to comment
steve cougar Posted March 5, 2011 Author Share Posted March 5, 2011 Hi Leo, Like I said all went well and was totally painless, with the exception of seeing and deleting the PLM that was listed as a device for some reason. Programs and status changes are working and showing up like they should but, again, I'm using HomeSeer as a front end for my whole house automation system and the status is NOT changing there, yet I can control all of my lighting through HomeSeer with no problem. Thanks for your speedy reply, great advice and a successful resolution! Steve Link to comment
bpwwer Posted March 6, 2011 Share Posted March 6, 2011 Hi Leo,Programs and status changes are working and showing up like they should but, again, I'm using HomeSeer as a front end for my whole house automation system and the status is NOT changing there, yet I can control all of my lighting through HomeSeer with no problem. Thanks for your speedy reply, great advice and a successful resolution! Steve Steve, Did you restart the HomeSeer or the plug-in after the swap? If not, I'd recommend at least doing a re-sync of the plug-in from the plug-in's status page. Restarting HomeSeer would be better to make sure it syncs properly with the ISY. Also, what version of the plug-in and what version of the ISY firmware? If at some point in this your ISY got upgraded to the latest firmware but you're still using an older version of the plug-in, you'll need to update the plug-in to the latest release candidate available on the HomeSeer Forums. http://board.homeseer.com/forumdisplay.php?f=919 Link to comment
steve cougar Posted March 6, 2011 Author Share Posted March 6, 2011 Hi Bob, I left a message on the HS forum as I didn't want to muddy the waters here but I forgot about your dedicated investment to both HS and the ISY. Thx. Okay, ISY 2.8.16 ISY Plugin 1.0.2.22 HS Pro 2.4.0.1 I in fact do now have a problem here. I installed the new 2413S in accordance with the instructions I found on the forum and Leos and Bruces help and comments confirmed that I did it correctly but something is def wrong here. I'm not getting any error messages in the HS log and I can control my lighting from HS. I have not messed with the debugging mode on the plugin yet. I did a "Restore Modem PLM" again just now and still have no status in HS. Also some of my programs and scenes are not working. I did make a backup of the ISY before changing the PLM. Should I restore the ISY from my backup? Should I change the debug mode and capture it for analysis? Steve Link to comment
LeeG Posted March 6, 2011 Share Posted March 6, 2011 No. Do not go to a backup before the PLM was changed. That backup has the old PLM address. Are the Scenes working from an ISY perspective? That is, if the Scene is turned On or Off through the Admin Console does it work correctly? Was not sure if the Scene problem is through the ISY Admin Console or HS only. Link to comment
steve cougar Posted March 6, 2011 Author Share Posted March 6, 2011 No the Scenes are not working. The only way to get a current status update is to manually query the entire site. I do also have a Venstar T-stat with the 2441V V2.8. I wasn't able to get the status on that T-stat before I changed the PLM but that's another issue. Link to comment
LeeG Posted March 6, 2011 Share Posted March 6, 2011 Under Tools | Diagnostics | PLM Info/Status, does this show the new or old PLM address. If the new PLM address, pick a device that is not responding to a Scene = run Tools | Diagnostics | Show Device Links Table. The link records that have a PLM address, is it the new or old PLM address. If the new PLM address, run Tools | Diagnostics | Show PLM Links Table. The device that is not responding to the Scene, does that device address appear in a link record that starts with an E2, has the Scene Group number, and has the device address. Link to comment
Sub-Routine Posted March 6, 2011 Share Posted March 6, 2011 Hi Steve, Unplug the thermostat adapter. Unplug your Access Points for a few seconds each. Sometimes the adapters seem to create noise. Rand I do also have a Venstar T-stat with the 2441V V2.8. I wasn't able to get the status on that T-stat before I changed the PLM but that's another issue. Link to comment
steve cougar Posted March 6, 2011 Author Share Posted March 6, 2011 Hi Lee, It seems that the new PLM is being used but there is something else listed but not a plm. When I do a Device Links Table for my Exterior:Front Railing Lights I get the following after doing a compare: [identical] OFF8 : A2 00 18.CF.BE FF 1F 00 [ignore] OFF0 : 00 18.00.00.00. B7 1F 00 Query; Since I changed to the new dual band plm should I remove my older access points? I also installed two switchlink dual bands in my system. Link to comment
LeeG Posted March 6, 2011 Share Posted March 6, 2011 Steve The link record at 0FF8 is created when the device was added to the ISY. The entry at 0FF0 that starts with 00 is the end of list marker (remainder of data is irrelevant). There are no Scene link records in this device. The new PLM is being used as it is connected to the Serial port of the ISY. The question is whether the ISY is aware of the PLM change. The Tools | Diagnostics | PLM Info/Status display should show the new PLM address. Lee Link to comment
steve cougar Posted March 6, 2011 Author Share Posted March 6, 2011 Hi Lee, Sorry I forgot to state that the new PLM does show up under PLM/Info Status. I had a hell of a time trying to add three motion sensors to the system and only one is added and working now. I also had an occurance where my main kitchen light was dimming, i have a scene that dims it afer midnight, going off and dimming again, repeatedly. Again, I am using HomeSeer to control some of the lighting via programs set up in HS. All of these were working perfectly with the other PLM. I have disabled them in HS but there are still problems. My Biggest issue is that there is no status updates within HomeSeer. I'm getting to the point of either putting the old PLM back in place, don't really want to though, and resetting absolutly everything back to zero and rebuilding my system. Link to comment
LeeG Posted March 6, 2011 Share Posted March 6, 2011 Do you know the technique the HS plugin uses to keep track of device status. A few days ago a user was having problems adding a TriggerLinc because the I2 Extended commands were not working correctly. Motion Sensors are dependent on the same commands. The problem was resolved by unplugging the tstat adaptor. It looks like the tstat adaptor problem is also interfering with Extended command communication in some way. Might not be your motion sensor problem but worth a try unplugging the tstat adapter and see if motion sensors can be added. Link to comment
steve cougar Posted March 6, 2011 Author Share Posted March 6, 2011 Well, Bob, aka bpwwer, has given birth to and developed an outstanding HS-ISY plugin when HS dropped all development on it's native one and he's looking into and helping me with the HS-no status change issue. I'm a bit pissed, not the first time, in the way that Smarthome develops and releases Insteon products... sometimes before they are ready for prime time. I wish they followed a firmware upgrade path like the ISY does or develop their products fully before selling them. I'm tired of being nickle and dimed to death and forced to buy an entirely new, upgraded product when they "fix" it. It's like we pay for the privilege of being their beta testers! I have the 'older' version of the t-stat adaptor which for some reason doesn't support "status" at all and to buy a new one is another 100 bucks. I may just go back to my extremely reliable RCS/Z-wave T-stat. It's a much better interface and complete control through HS. Then I wouldn't have to get soaked again buying another Smarthome adapter that maybe/maybe not be 'possibly' causing problems with my other RF devices. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.