| Author |
|
damutha
Newbie
Joined: January 17 2007
Online Status: Offline
Posts: 13
|
| Posted: February 28 2007 at 22:19 | IP Logged
|
|
|
I installed the new version last night, and since that time I am noticing new entries in my event log that were not present before. Here is an example:
Feb 28 2007 23:15:42 Incoming X-10 Incoming X-10 received on Insteon DM controller POWERLINC. Byte Values: 01 FD Decode: J{Status On}
Feb 28 2007 23:11:57 Incoming X-10 Incoming X-10 received on Insteon DM controller POWERLINC. Byte Values: 01 FF Decode: J{Status Request}
Feb 28 2007 23:09:14 Incoming X-10 Incoming X-10 received on Insteon DM controller POWERLINC. Byte Values: 01 BF Decode: L{Status Request}
Feb 28 2007 23:07:02 Incoming X-10 Incoming X-10 received on Insteon DM controller POWERLINC. Byte Values: 00 00 Decode: M13
Thoughts on what this is and what is causing it? My system is 100% Insteon, other than my ControLinc (which I don't even really use).
|
| Back to Top |
|
| |
damutha
Newbie
Joined: January 17 2007
Online Status: Offline
Posts: 13
|
| Posted: March 01 2007 at 11:49 | IP Logged
|
|
|
Another new glitch--my timed event that reinitializes PowerHome every day has stopped working. I got the following message yesterday and today:
Mar 01 2007 11:53:53 Macro Macro executed.
Mar 01 2007 11:53:52 System Message SmartHome Device Manager ISRESPONDING command failed for Insteon PLC POWERLINC. Commands will not be sent.
Mar 01 2007 11:53:36 Execute Timed Event Timed Event processed for timestamp 2007-03-01 11:53:35, type 2, action ph_reinitialize ()
Even though it says "Macro executed", it did not reinitialize. Another one of my timed events DID work last night, and I can control devices directly through PowerHome, so there is communication going on. Help?
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 01 2007 at 21:10 | IP Logged
|
|
|
Damutha,
One of the things that changed between .9 and .10 was that I went back to an older version of SDM (235). The data that you've posted for the eventlog is caused by commands coming directly from the SDM. It's possible that this version of the SDM is doing something wrong, but it's more likely that some kind of noise on the line is being recognized as X10 (It's not too hard for noise to get interpreted wrongly as X10 signals).
If you're not using Powerline X10 at all (or don't want the SDM to signal PowerHome with X10), you can get rid of this by unchecking the X10 Receive Commands boxes in the Setup window of the Insteon controller (PowerHome Explorer PowerHome|Setup|Controllers). Save and restart or reinitialize and these messages should be gone.
Concerning the ph_reinitialize event. I checked this out on my system all seems to be working. I got the same messages you got as well. Based on your messages, PowerHome should have reinitialized. The Timed Event fires, PowerHome reinitializes, about 20 seconds later the System message saying that PowerHome could not connect to the SDM, followed by the Reinitialize macro being executed (you don't have one so it appears blank).
Now the problem with the SDM seems to be tied to the new (old) SDM version in this release of PowerHome. It appears that when PowerHome is reinitialized, the SDM is shutdown and the timing is such that sometimes (most likely) the SDM is not able to be properly reinitialized and you get the error message. I found that I was able to fix it by reinitializing a second time. You could do this with a second timed event (this is what I tried) and it seems be working consistently (I couldnt get it fail in the 6 times I tested). This is a pain though and may not be ideal for you. You may want to change your SDM back to a later version if this one seems to be causing problems.
HTH,
Dave.
Edited by dhoward - March 01 2007 at 21:14
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: Additions to Event Log with New Version
