| Author |
|
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 20 2006 at 00:53 | IP Logged
|
|
|
"Goshhh...Im an idiot", I say in my best Napoleon Dynamite voice  .
Anyways...here is the latest patch to PowerHome that corrects a serious problem that was introduced with patch 1.03.4.7-3. In the last patch, when trying to create groups with the PLC as a responder or controller, background processing would hang. I don't know how I missed this, but it's fixed now.
As with Patch 1.03.4.7-3, just unzip the two files and overwrite the existing ones in the PowerHome directory (default located at c:\program files\powerhome).
Get the patch here: http://www.power-home.com/download/phpatch10347-4.zip.
Other than this one glaring mistake, nothing else has changed since patch 3.
Let me know if you encounter any other problems.
PS...Thank you Jmvanden for catching this and sending me your database.
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 20 2006 at 09:19 | IP Logged
|
|
|
Ever since I have upgraded, my communication to Insteon devices has benn horrible. Macros and timers don't work at all. They look as if they were executed in the PowerHome Status window, but the commands aren't reaching the switches.
I have changed a LOT of things since upgrading (not an ideal situation for bug hunting) but mainly I upgraded to .7-3, turned on all the background checking in the settings of the Insteon PLC.
Here is a partial bit of the log wqhere I am noticing quite a few 'send failed' entries. Any ideas?
Quote:
PLC:receiveinsteonraw=04 04 3E 98 00 D4 33 2B 00 00
3/20/2006 9:11:00 AM:ackmsg=04 3E 98 00 D4 33 2B 00 00
PLC:srq:SRIR=04,04 3E 98 00 D4 33 2B 00 00
PLC:eventraw=03
ui:srq:srir=00 00 00 03 C5 ED 0F 19 00
si:00 D4 33 03 C5 ED 0F 19 00
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:srq:SRIR=send failed
PLC:eventraw=03
ui:srq:srir=00 00 00 03 07 05 0F 19 00
si:00 D4 33 03 07 05 0F 19 00
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=04
PLC:receiveinsteonraw=04 03 07 05 02 45 03 02 4F 03
PLC:srq:SRIR=send failed
ui:srq:srir=00 00 00 03 11 B1 0F 19 00
si:00 D4 33 03 11 B1 0F 19 00
PLC:eventraw=03
PLC:eventraw=04
PLC:receiveinsteonraw=04 03 11 B1 00 D4 33 2B 00 00
3/20/2006 9:11:45 AM:ackmsg=03 11 B1 00 D4 33 2B 00 00
PLC:srq:SRIR=04,03 11 B1 00 D4 33 2B 00 00
ui:srq:srir=00 00 00 06 03 C4 0F 19 00
si:00 D4 33 06 03 C4 0F 19 00
PLC:eventraw=03
PLC:srq:SRIR=send failed
PLC:receiveinsteonraw=04 06 03 C4 00 D4 33 2B 06 00
|
|
|
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 20 2006 at 21:17 | IP Logged
|
|
|
Carl,
If you upgraded from 1.03.4.7 to 1.03.4.7 patch 3 and saw the communications go bad, I would tend to think that it's one of the other factors. Im not trying to point the finger somewhere else, it just doesnt make sense. The SDM is the same, so that would not be a factor and the only thing that really changed is the validation routine for retrieving Insteon database links.
Based upon the SDM log you've posted above, you can see a successful status request to device 04.3E.98. This is followed by a status request to device 03.C5.ED that fails. When the commands get to the SDM at this point, PowerHome is really out of the loop and the ball is in the SDM or primarily the PLC and the Insteon networks court.
If we continue on, we see a status request to device 03.07.05 which ultimately fails. We do receive a response from device 03.07.05 but it is a direct ACK response to device 02.45.03. It's possible that the status request command was issued to 03.07.05 at exactly the same time that another command was issued to the same device and the status request was lost.
We then have a successful status request to device 03.11.B1. We then send a status request to device 06.03.C4 and we get the send failed. However, after the SDM has already failed the command, we do get a proper response from 06.03.C4. In this case, it appears that the response was either returned late (traffic or bad communication...most likely bad communication since we dont see any traffic) or the intial response was garbled (bad communication).
So out of 5 status request commands, 3 of them failed (however 1 failure may have been unavoidable). It would definately appear that at least two of the commands were lost due to something on the Insteon network.
Can you give me some clues what some of the other things were that you changed?
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 21 2006 at 09:02 | IP Logged
|
|
|
Dave, things went bad when I changed from 04.6 to 04.7-3. I didn't run the SW at all on just plain .7.
It appears as if PowerHome is doing a good job of keeping up with the status of devices, but it isn't sending commands to Insteon devices at all from macros and triggers. It sends commands to Insteon devices from the device status screen just fine.
I will be out most of the daytime today, but would be happy to do any kind of diagnostics that you suggest.
I could downgrade to 04.6 to see what is up, my guess is that it would work fine, but I have added a few swtiches since then.
Suggest away, I'm a willing accomplice. 
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 21 2006 at 21:57 | IP Logged
|
|
|
Carl,
Gotcha. Part of the problem may be that the patch was only for 1.03.4.7. Im actually surprised that it would even work.
What I would try is doing a full install of version 1.03.4.7. Follow the instructions as if you were upgrading (rename existing PowerHome directory, install, copy over database and ini files, etc). After you've got 1.03.4.7 up and running successfully, then go ahead and use the latest patch 1.03.4.7-4.
Once we've got a good, clear installation, lets see what the log looks like and take it from there.
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 10:09 | IP Logged
|
|
|
Actually, the way that I communicated what happened may not be clear.
Everything was working pretty well under 1.03.4.6. I upgraded to 1.03.4.7 following the instructions. I didn't runthe software as version 1.03.4.7 at all, I patched it with the zip file to take it to version 1.02.4.7-3. Things haven't worked right since then.
I do have my original version 1.03.4.6 directlry saved so I could revert if necessary.
Since I have already done an upgrade from .6 to .7 (basically doing a full install of the .7 version, I'm not sure how you would like me to proceed.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 22 2006 at 10:29 | IP Logged
|
|
|
Carl,
Ok, that makes more sense. I was going through the code last night trying to figure out how patching 1.03.4.6 with 1.03.4.7 code would even work  .
Since you say youve got a complete saved version of 1.03.4.6, lets go ahead and give it a try. Just rename your 1.03.4.7 PowerHome directory to something like powerhome_10347 and rename your 1.03.4.6 directory back to PowerHome (you don't necessarily have to do this, its just easier so you don't have to edit the pwrhome.ini file and update the database location).
Give this a whirl and lets see what it does for us.
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 10:57 | IP Logged
|
|
|
Dave,
Downgraded (renamed current version to 10347-3, renamed old version to powerhome). Put in a timed event to turn the Kitchen light on fully (01.78.c5) and it didn't work.  The SDM log (verison 1.01.20.157) is included. I don't have background checking enabled.
Quote:
downloadTimer started
timerActivate enabled
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=2.12
id=00.D4.33
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
SDM:DM=active,1.01.20.157,3/22/2006 10:36:13 AM,responded,00.D4.33,2.12
ui:srir=00 00 00 01 78 C5 0F 11 FF
si:00 D4 33 01 78 C5 0F 11 FF
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=05
3/22/2006 10:41:59 AM:nakmsg
PLC:SRIR=05 |
|
|
I then used the device manager screen to try to turn on the same light and it didn't work. I did a factory reset on the PLC, and tried again, still didn't turn on the light.
Here is the SDM log
Quote:
ui:getplcstatus
PLC:getPLCstatus=beginlist
port=USB4
connected=True
firmware=2.12
id=00.D4.33
devicetype=InsteonPLC-USB
lastErrorMsg=#0:
endlist
downloadTimer started
timerActivate enabled
SDM:DM=active,1.01.20.157,3/22/2006 10:54:09 AM,responded,00.D4.33,2.12
ui:srir=00 00 00 01 78 C5 0F 11 FF
si:00 D4 33 01 78 C5 0F 11 FF
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=05
3/22/2006 10:54:55 AM:nakmsg
PLC:SRIR=05
|
|
|
Not sure what to do now, was thinking of redownloading the core application to the PLC, but waiting for your input.
-Carl
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 22 2006 at 12:03 | IP Logged
|
|
|
Carl,
This is what I suspected. You shouldnt have seen any real change between version .6 and .7. You can see the command going out (the timed event and the Device Status screen both send the same command) and then it never comes back except for a NAK message and the SRIR command fails.
It definately wouldnt hurt to try re-downloading the core application. I would first "Clear PLC Database", "Download Core Application", and then "Add ID's to PLC". This should totally refresh the PLC side of things.
It's certainly possible that this will fix it, but it's more than likely that something about adding the new switches has changed the reliability of your Insteon network. If the cleanup of the PLC doesnt do the trick, the next thing I would try is repositioning your SignaLincs.
Let me know,
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 13:49 | IP Logged
|
|
|
Should I do that in the newest version or in the older version?
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 15:32 | IP Logged
|
|
|
Dave,
I re-upgraded to .7-4, then ran the core app, clear, and load IDs into the PLC...
Now at least, manual control works, goona try a macro is a minute...
The Powerhome Status event log says it executed the macro, but it didn't send any commands to the insteon devices.
The Macro is Kitchen Dusk On
line 10 has under commnad "Insteon"; under data null (nothing enterable here); under Id "from the drop down I choose "KIT ROPE LIGHTS (SINK)"; and under value "ON".
line 20 is similar for another set of lights.
I just noticed something...At first, the Item ID was not updated when I had changed the unit names to make them easier to read, they were showing the old name KITROPELIGHTS(SINK)... I refreshed them by rechoosing them from the drop down.
Then wehn I ran the macro again, I go at least Insteon out commnads showing up in the PH Status event log. BUT still now commands reached the devices.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 22 2006 at 15:38 | IP Logged
|
|
|
Carl,
If you're using the Insteon macro command "ON" then be sure that you put the on value in the "Send Keys/TTS/Formula" field. For Insteon, this value should be from 0 to 255 with 255 being full on. If you don't want to fool with this, then use the "Fast On" command.
Let me know,
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 15:39 | IP Logged
|
|
|
OK, so in looking at the event log more closely, I am seeing that the comd being sent is CMD1 17, and CM2 0... so I'm guseeing that the send keys data field at the end has to be set with 255 to be all the way bright, or 803 to be 33% bright... so I changed the commnad to Fast ON (they are appliancelincs anyway)and it worked fine.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 22 2006 at 15:41 | IP Logged
|
|
|
Carl,
Might have been a typo but 33% bright would be a value of 85.
(Looks like we were posting at the same time ).
HTH,
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 15:53 | IP Logged
|
|
|
Hey Dave, that is too funny, we must have been typing at the same time.
So quick ?... I'm no seeing how the Insteon Raw Group command works...
I have the PLC as a choice under DATA, but I want to choose a group that is in my DEN KPL... I don't see how to make that work.
Edited by QuickCarl - March 22 2006 at 15:58
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 22 2006 at 15:55 | IP Logged
|
|
|
I was just about to edit it so that it said 83...LOL. and you are right, 85 is exactly 33%
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: March 22 2006 at 17:36 | IP Logged
|
|
|
Carl,
Heh, you are discovering the big misunderstanding in the Insteon ointment.
Basically, there is no way to trigger another devices groups. If a KPL button 3 controls 5 lights, then only the KPL button 3 can trigger that group. You can create a group with the PLC as the controller and have it control the same 5 lights, but neither the PLC or any other device can trigger another device's groups. This is where the "Clone" option comes in handy in the Create/Edit/Clone Insteon link window.
HTH,
Dave.
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 23 2006 at 11:44 | IP Logged
|
|
|
Dave, I understan what you are saying about not being able to set up a buttoon on the PLC to control another controllers groups (a short sighted limitation I think, but addressable with mcaros and triggers I think) but that isn't what I'm talking about here.
I have a number of lights assigned to the button 1 on my Den KPL. That makes the Den KPL have a group # 1, which has three lights linked to it, and they show up in the Devices by controller section just fine.
BUT, when I want to creat a macro from within PH, and I choose Insteon Raw Group, the only choice is the PLC. So does that mean that the only groups that are addressable from PH are the PLC groups? That seems sort of weird that it couldn't send a message to the group that it knows about and has registered...
So if I have to clone the group that is controlled by the button one of the KPL to the PLC, how do you go about doing that?
|
| Back to Top |
|
| |
UpstateMike
Senior Member
Joined: February 18 2006
Location: United States
Online Status: Offline
Posts: 142
|
| Posted: March 23 2006 at 16:15 | IP Logged
|
|
|
Carl-
It sounds like you are asking for a way for PowerHome to send goup command as a broadcast referencing the members of another existing group that it knows about. I think the problem is that Insteon group commands do not work that way. The command does not contain any information about who is supposed to do what in reponse to the group message, that information is determined during the linking process and is held by the responder.
Example: A keypad has button 1 linked to light 1 and light 2. When you press keypad button 1, all Insteon devices in your house hear a message that keypad button 1 was pressed. They DO NOT hear anything about light 1 or light 2 in the message. Light 1 and light 2 know they are supposed to do something when they get that message because of data put into their tables during the linking process. Keypad button 1 DOES NOT know what light 1 and light 2 are supposed to do when they get the message, it only knows that it is supposed to get an acknowledgement from those 2 addresses.
Even though PowerHome knows what light 1 and light 2 are supposed to do when keypad button 1 is pressed it cannot duplicate the message because Insteon messages do not include any device data. The message just says keypad button 1 was pressed and the devices are supposed to know what to do based on tables built during the linking process NOT on data in the trigger message.
PowerHome cannot mimic another device because messages include the address of the originating module which would always be the PLC in the case of PowerHome. So the only way for PowerHome to mimic an existing group is to clone that group into a slot in the PLC. (Not really a problem since the PLC has 254 slots or groups or buttons, however you want to look at it.)
|
| Back to Top |
|
| |
QuickCarl
Groupie
Joined: February 13 2006
Location: United States
Online Status: Offline
Posts: 60
|
| Posted: March 23 2006 at 16:45 | IP Logged
|
|
|
OK, I got it now. Cloned the group that I wanted, then added the KPL button one to the PLC group (so I can control the load on the KPL)... BUT when I use the Insteon Raw Group commnad in the macro area of PH Explorer, there isn't any way to put in params for the CMD2 area [becuase the "senkeys/TTS/formula" field isn't activated, so I am limited to the Fast ON for Fast off commands, otherwise it will send a CMD2 of "0", which won't do what I want.... 
Edited by QuickCarl - March 23 2006 at 16:55
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome Patch 1.03.4.7-4
