Active TopicsActive Topics  Display List of Forum MembersMemberlist  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin
PowerHome General
 PowerHome Messageboard : PowerHome General
Subject Topic: Insteon and the SDM. Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: May 18 2006 at 19:25 | IP Logged Quote dhoward

Hello all,

In an effort to help SmartHome iron out SDM problems, please post all errors and crashes to this thread or email them to me. If you are able to cause a crash in a reproducible way, please let me know what steps you took. Also, if you get the SDM Debug window, please take a screenshot as well as the debug log and forward it to me. If possible, provide as much info concerning the crash and what may have proceeded it. I realize that most of the time this is entirely random but if we can narrow it down even a little bit, it will be a huge help.

Good luck and looking forward to some crash information and hopefully a stable SDM.

Dave.


Edited by dhoward - May 18 2006 at 22:27
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
mustangcoupe
Super User
Super User
Avatar

Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
Posted: May 20 2006 at 08:47 | IP Logged Quote mustangcoupe

OK, dave my original problems have gone away

ex.
PLC:srq:ERROR=012:MapNotLoaded-PLC not connected or no valid map. Try using isResponding first.
PLC:srq:SRIR=send failed
ui:srq:srir=00 00 00 04 49 D6 0F 19 00
si:01 2C 06 04 49 D6 0F 19 00

I actually beleive this was caused by Opeating System. It went away with a load of XP (was running win2000 server)


USB PLC still locks up now and agian (hours to days) not sure why yet.... background PH stuff off...

ui:srq:srir=00 00 00 04 49 D6 0F 19 00
ui:srq:srir=00 00 00 00 C2 AC 0F 19 00
ui:srq:srir=00 00 00 04 42 43 0F 19 00
ui:srq:srir=00 00 04 41 6D 0F 19 00
ui:srq:srir=00 00 00 04 49 D6 0F 19 00
ui:srq:srir=00 00 00 00 C2 AC 0F 19 00
ui:srq:srir=00 00 00 04 42 43 0F 19 00
ui:srq:srir=00 00 00 04 41 6D 0F 19 00
ui:srq:srir=00 00 00 04 49 D6 0F 19 00
ui:srq:srir=00 00 00 00 C2 AC 0F 19 00
ui:srq:srir=00 00 00 04 42 43 0F 19 00
ui:srq:srir=00 00 00 04 41 6D 0F 19 00
ui:srq:srir=00 00 00 04 49 D6 0F 19 00
ui:srq:srir=00 00 00 00 C2 AC 0F 19 00


__________________
Todd Hannemann

HA newbie

   PowerHome - UPB - ELK    
Back to Top View mustangcoupe's Profile Search for other posts by mustangcoupe Visit mustangcoupe's Homepage
 
mustangcoupe
Super User
Super User
Avatar

Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
Posted: May 29 2006 at 00:00 | IP Logged Quote mustangcoupe

Dave came home and after about 2 days 5 hrs...uptime
the sdm puled agian. is there any way to detect numerious ui:srq requests and automatically reload the sdm?

ui:srq:srir=00 00 00 04 42 43 0F 19 00
ui:srq:srir=00 00 00 00 C2 AC 0F 19 00

__________________
Todd Hannemann

HA newbie

   PowerHome - UPB - ELK    
Back to Top View mustangcoupe's Profile Search for other posts by mustangcoupe Visit mustangcoupe's Homepage
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: May 30 2006 at 10:25 | IP Logged Quote dhoward

Todd,

Since it seems to hang in a consistent manner for you, can you test a couple of ways to see if it comes back?

The first thing I would try is just disconnecting the controller from the File menu. Wait a few seconds and then reconnect. I doubt this will fix it, but it's best to try the lowest things first.

If that doesnt fix it, try a reinitialize.

Last, try a PowerHome restart.

Let me know at what level the problem gets fixed and I'll try to code for it for the next beta.

Thanks,

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
WayneW
Groupie
Groupie


Joined: March 29 2005
Location: United States
Online Status: Offline
Posts: 50
Posted: May 30 2006 at 11:28 | IP Logged Quote WayneW

dhoward wrote:
The first thing I would try is just disconnecting the controller from the File menu. Wait a few seconds and then reconnect. I doubt this will fix it, but it's best to try the lowest things first.

If that doesnt fix it, try a reinitialize.

Last, try a PowerHome restart.


I happened to run into this today.
The disconnect for 10 seconds did not help.
The re-initialize appeared to fix it.

FYI, I am using the 2414S serial interface.

Edited by WayneW - May 30 2006 at 11:30
Back to Top View WayneW's Profile Search for other posts by WayneW
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: May 30 2006 at 11:34 | IP Logged Quote dhoward

Wayne,

Thanks for the feedback. It helps alot. I didnt think of it earlier, but if it should happen again, one other test may help me pinpoint exactly how to recover without having to do a reinitialize.

If it happens again, Todd or Wayne or anybody, try manually closing the SDM. Leave PowerHome up and just open the SDM and exit it. You'll likely get a window saying that a client is still connected, are you sure you want to close. Go ahead and say "Yes" and close the SDM. PowerHome should automatically restart the SDM the next time it tries to send an Insteon command (within 15 seconds if background processing is turned on), otherwise, you need to send an Insteon command so PowerHome will restart the SDM.

See if just restarting the SDM alone without having to reinitialize PowerHome will take care of the problem. My suspicions are it will and I can save having to do a reinitialize.

Thanks,

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
mustangcoupe
Super User
Super User
Avatar

Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
Posted: May 30 2006 at 12:12 | IP Logged Quote mustangcoupe

Actually Dave that is how I get it back now... I just close the sdm manually and let PH reopen it...

__________________
Todd Hannemann

HA newbie

   PowerHome - UPB - ELK    
Back to Top View mustangcoupe's Profile Search for other posts by mustangcoupe Visit mustangcoupe's Homepage
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: May 31 2006 at 12:59 | IP Logged Quote dhoward

Todd,

Excellent! Appreciate the post. This puts the problem squarely with the SDM and minimizes the amount of "resetting" that must be done to recover. I'll try to detect and program for this situation in the next beta.

Thanks,

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 
fasttimes
Groupie
Groupie


Joined: March 12 2006
Online Status: Offline
Posts: 63
Posted: June 01 2006 at 19:00 | IP Logged Quote fasttimes

dhoward wrote:
Wayne,

try manually closing the SDM. Leave PowerHome up and just open the SDM and exit it. You'll likely get a window saying that a client is still connected, are you sure you want to close. Go ahead and say "Yes" and close the SDM. PowerHome should automatically restart the SDM the next time it tries to send an Insteon command (within 15 seconds if background processing is turned on), otherwise, you need to send an Insteon command so PowerHome will restart the SDM.

See if just restarting the SDM alone without having to reinitialize PowerHome will take care of the problem. My suspicions are it will and I can save having to do a reinitialize.

Thanks,

Dave.


Dave, I'm still having the problem with PH, not sure if it is the SDM or not.

Recently I noticed that PH was running for 11 days without me doing any "manual" trigger events, like pressing a keypadlinc linc button which fires a macro, or using the web interface. I went ahead and used the web interface to turn on a light, and it did turn on, five minutes after I pressed the button!

Eventually nothing would respond, and I would close the SDM, PH would restart it and say it could not find a connection. The only way to get it working again was to disconnect the PLC from the wall and reboot my machine and start PH again.

I don't know if this is related, but I have plugged into the wall one of those X10 receivers with an antenna that responds to the remote control. It is the only X10 unit I have in the house. I ocasionally hear it click every now and then, even though I thought I disabled all X10 functionality in PH.
Back to Top View fasttimes's Profile Search for other posts by fasttimes
 
mustangcoupe
Super User
Super User
Avatar

Joined: August 08 2003
Location: United States
Online Status: Offline
Posts: 308
Posted: June 01 2006 at 20:07 | IP Logged Quote mustangcoupe

fasttimes wrote:

Eventually nothing would respond, and I would close the SDM, PH would restart it and say it could not find a connection. The only way to get it working again was to disconnect the PLC from the wall and reboot my machine and start PH again.


When you went into the SDM did you happen to save any log files? What was in the SDM window? Do you automaticaly run macros or anything, or was PH idle for 11 days totaly?

__________________
Todd Hannemann

HA newbie

   PowerHome - UPB - ELK    
Back to Top View mustangcoupe's Profile Search for other posts by mustangcoupe Visit mustangcoupe's Homepage
 
dhoward
Admin Group
Admin Group
Avatar

Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
Posted: June 02 2006 at 21:20 | IP Logged Quote dhoward

Fasttimes,

When you say "disable" X10 functionality in PowerHome, IM assuming you mean you unchecked all of the X10 boxes in the Controller setup screen. If so, then this just means that the controller wont respond to incoming X10 commands. But, if you aren't having PowerHome send any X10 commands, then the controller shouldn't be sending any. Since you say it's an RF transceiver and it "clicks", then that would mean that you have a TM751. The relay in a TM751 ONLY responds to RF commands. An X10 powerline transmission could not turn on the relay even if you wanted it to so this would rule out the PLC and PowerHome. If it's occasionally clicking, then it is responding to incoming RF commands that it's receiving. It could be a device that you have or could even be something of your neighbors.

It sounds as if the SDM was hung. If PowerHome eventually go the command sent, then the execution queue wouldnt have been hung. If the only way to recover was to unplug the PLC from the wall, then that would seem to indicate a hang within the PLC. I wouldnt think that you would need to reboot however.

If it happens again, I would shut the SDM down and then unplug the PLC for about 5 seconds and then plug back in again. If PowerHome happens to restart the SDM before you get the PLC plugged back in, go ahead and shut the SDM down again. See if operation resumes as normal. If so, then PowerHome was ok and the problem is definately in the PLC/SDM.

Some good news though is that I hear SmartHome is hard at work on fixing SDM bugs and will probably have a new SDM available shortly. As soon as I get it, I'll post it for all to test.

Dave.
Back to Top View dhoward's Profile Search for other posts by dhoward Visit dhoward's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum