| Author |
|
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 24 2011 at 18:19 | IP Logged
|
|
|
BeachBum wrote:
| Just a quick thought… Is this a similar scenario we have with the motion sensors cured by “trigdisable”? |
|
|
You know I tried doing something like that when I got my EZIO and the disable happened after they were queued. I just created the “trigdisable”and Added it to the Boolean on a few trigger(s) and that stops the double fire of the triggers. I like that, Less talk more work :) So, Thanks for that.
However that doesn't solve my problem... This all worked before the upgrade. It seems PH just quits talking to the SDM. I reinitialize and it works once or twice then stops working. I then go into Insteon Explorer and PH can't control any device ON/OFF. I reinitialize and it works again. The devices are not flagged failed.
I'm going to do more testing and find the simplest scenario to create the problem I guess.
Edited by Lenny - January 24 2011 at 18:20
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 24 2011 at 23:13 | IP Logged
|
|
|
I’ll see what I can do. I’ve got the Beta on my PLC system and will activate the controller tomorrow.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 26 2011 at 09:08 | IP Logged
|
|
|
I setup my house with all lights and motion sensors running on the PLC with Beta 213. The IR control and a few appliance devices were under control of the PLM and V2.1B. I had no glitches with the setup. The Beta side went through many iterations of sequencing the lights on and off triggered by a motion sensor light sensitivity. I monitored SDM throughout the whole time and saw no glitches. I initially did have problems with SDM until I installed 213 Correctly. My bad. The Beta install was done taking all the defaults on a I7-930 SSD Win 7 Pro 64x system. The SDM is 235 as I have always had good luck with that version. The other system (PLM) is on a Vista laptop.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 26 2011 at 10:34 | IP Logged
|
|
|
It must be something with my setup then. I'm just having a hard time trying to figure out what... Seems to go all bad when power home controls my "ALL Lights" PLC Group #254. Is there something different with group PLC Group 254 now with the new version?
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 26 2011 at 11:14 | IP Logged
|
|
|
I ran test against group 254 using 2 lights and then did a group fast on. No problems. I’m sensing you have multiple problems. You reported that SDM sometimes stops talking and that some lights come and go at will. Also there is the Ezio problem. Correct me if I’ve got it wrong. If the SDM appears to give you a problem then switch to the other version and try that. I’ll hold on to my setup until we find some kind of solution.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 26 2011 at 12:01 | IP Logged
|
|
|
Here is an example of when PH is in P/O'd State. I can't make it any more simple than turning on 1 light...
I just went into Device Status and selected a lamp module 0D.59.E3 and Selected "ON" and the module didn't turn on and PH still shows it off.
This is the logs.
Insteon Raw Log
1-01-26 11:38:40.395 TX &nbs p; !sendinsteonraw=00 00 00 00 00 1E CF 11 00
2011-01-26 11:38:40.520 RX &nbs p; SENTINSTEON=00 00 00 00 00 1E CF 11 00
2011-01-26 11:38:41.114 RX &nbs p; SENDINSTEONRAW=TRUE
2011-01-26 11:38:41.348 RX &nbs p; EVENTRAW=03
SDM General Log
ui:!sendinsteonraw=00 00 00 00 00 1E CF 11 00
uifinished:!sendinsteonraw=00 00 00 00 00 1E CF 11 00
si:00 00 00 00 00 1E CF 11 00
PLC:sendinsteonraw=True
PLC:eventraw=03
Event Log
1/26/2011 11:38:40.52 31 ; INSTEON DM Controller POWERLINCUSB transmission of Address:[00.00.1E] Flags:[207] Cmd1:[17] Cmd2:[0]. Decode: Group Broadcast. Group: 30, On &nbs p;923 Insteon Out 0 &n bsp;#000000 16776960 ; #00ffff
Now Group 30 is my Overhead Door Status PLC Group. Button 7 on 5 Keypads.... I have no Idea why it would send that!?
Now, If I reinitialize and do the same thing. Works as expected.....
Insteon Raw Log
2011-01-26 11:52:18.072 TX &nbs p; sendinsteonraw=00 00 00 0D 59 E3 0F 11 FF
2011-01-26 11:52:18.181 RX &nbs p; SENTINSTEON=00 00 00 0D 59 E3 0F 11 FF
2011-01-26 11:52:18.415 RX &nbs p; SENDINSTEONRAW=TRUE
2011-01-26 11:52:18.712 RX &nbs p; EVENTRAW=03
2011-01-26 11:52:18.915 RX &nbs p; EVENTRAW=04
2011-01-26 11:52:18.962 RX &nbs p; RECEIVEINSTEONRAW=04 0D 59 E3 0A A1 D6 2F 11 FF
2011-01-26 11:52:19.228 RX &nbs p; EVENTRAW=03
2011-01-26 11:52:19.228 RX &nbs p; EVENTRAW=03
2011-01-26 11:52:19.228 RX &nbs p; EVENTRAW=03
Event Log
1/26/2011 11:52:18.962 30 &nbs p; Incoming Insteon received on INSTEON DM controller POWERLINCUSB. From Address:[0D.59.E3] To Address:[0A.A1.D6] Flags:[47] Cmd1:[17] Cmd2:[255]. Decode: Direct ACK. From: LV_LAMP_LEFT To: POWERLINC1, On &nbs p;942 Insteon In 0 &nb sp;#000000 65280 &nb sp; #00ff00
1/26/2011 11:52:18.181 31 &nbs p; INSTEON DM Controller POWERLINCUSB transmission of Address:[0D.59.E3] Flags:[15] Cmd1:[17] Cmd2:[255]. Decode: Direct. ID: LV_LAMP_LEFT, On &nbs p;941 Insteon Out 0 &n bsp;#000000 16776960 ; #00ffff
SDM General Log
ui:sendinsteonraw=00 00 00 0D 59 E3 0F 11 FF
uifinished:sendinsteonraw=00 00 00 0D 59 E3 0F 11 FF
si:00 00 00 0D 59 E3 0F 11 FF
PLC:sendinsteonraw=True
PLC:eventraw=03
PLC:eventraw=04
PLC:receiveinsteonraw=04 0D 59 E3 0A A1 D6 2F 11 FF
1/26/2011 11:52:18 AM:ackmsg=0D.59.E3:ON at ON
PLC:eventraw=03
PLC:eventraw=03
PLC:eventraw=03
BeachBum wrote:
| If the SDM appears to give you a problem then switch to the other version and try that. |
|
|
I am using SDM 1.1.138.308. That is the same version I used with PH2.1B. So I guess what version should I try, and where can I get it?
Should I just bite the bullet and get a PLM and dump the SDM or should I not change 2 things at once? If so what model?
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 26 2011 at 12:18 | IP Logged
|
|
|
The Insteon Raw Log is showing a Group command rather than an individual device command. If the command was generated as a result of the individual device On this is a bug in Powerhome. Changing back to the earlier SDM3 will not fix this. It looks like some indicator is being left on from a PLC Group activity that is affecting subsequent individual device commands.
Try sending a PLC Group command and then go back to the individual device control you attempted. My guess is that either PLC Group activity in general or perhaps some error condition associated with a specific Group left some indicator around that is causing Powerhome to process individual device commands incorrectly as Group requests.
Dave should be able to fix this with the data you just posted. Good job of documenting the problem.
__________________
Lee G
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 26 2011 at 12:19 | IP Logged
|
|
|
What I would do is rebuild the DB (phupg.exe). Although now to me it doesn’t look like a SDM problem because the Insteon raw log matches the SDM. If you want to try the other version go to C:\powerhome\smarthome\device manager\ and run the bat file 235. I would also check all your devices and groups to make sure the controller is correct.
Lee you type too fast.....
Edited by BeachBum - January 26 2011 at 12:20
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 26 2011 at 12:30 | IP Logged
|
|
|
Pete
Maybe someone is just slowing down in their old age!!
Some bad weather down there. Everything Ok where you are?
__________________
Lee G
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 26 2011 at 12:37 | IP Logged
|
|
|
We had it yesterday meaning coming your way soon….
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 26 2011 at 13:38 | IP Logged
|
|
|
Lenny
I ran a test using a PLM, turning a PLC Group On and Off, followed by a device On and Off through Device Status, all worked as expected. This does not mean a PLM would work in your situation, only a simple test of Group and Device activity works on a PLM.
Eventually you will want to move to a PLM. The PLC does not support Extended commands which are required for Powerhome to manage the link records in Motion Sensors and TriggerLincs. Extended commands are also being used more and more in device configuration. Smartlabs is implementing a set of Extended commands to set various device configurations independent of the device firmware level. Once device configuration has moved to Extended commands all the issues with configuration being firmware level dependent goes away.
__________________
Lee G
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 26 2011 at 13:44 | IP Logged
|
|
|
The same test ran with the PLC also. I would definitely echo what Lee said and go with Serial PLM NOT the USB. The speed and reliability is incomparable. Beware though your problem may have nothing to do with the PLC.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 27 2011 at 16:53 | IP Logged
|
|
|
grif091 wrote:
Try sending a PLC Group command and then go back to the individual device control you attempted.
|
|
|
Sorry took so long to get back to you... with a clean start of PH and sending PLC Group command and then individual command works fine. I can't seem to make it mess up from within PH. I did this testing remotely... Now that I'm home I'll try pressing physical buttons to cause triggers to fire and see if I can nail down when PH goes out to lunch.
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 29 2011 at 08:37 | IP Logged
|
|
|
I have not given up yet... I created new plc group and did testing and am unable so far to reliably recreate the problem. It seems to not happen when I want it too and does when I'm on my way out the door and I need it too. So far it only happens when a trigger is fired from an Insteon Device Change and a group is controlled. I think Lee is right, and something is getting queued up not flushed.
|
| Back to Top |
|
| |
kemporama
Senior Member
Joined: November 21 2008
Online Status: Offline
Posts: 102
|
| Posted: January 29 2011 at 17:12 | IP Logged
|
|
|
Here's something strange that has been happening to me since the upgrade, wondering if anyone else is experiencing the same.
I just received various new switches and devices that I'm adding as I have time. Whenever I go to link a new device using the auto discovery, it creates 2 new devices for a single device with the correct device address spread between the 2 new devices. It's done this for about 4 devices so far. For example, if I have a device with the true address of say 11.22.33 and I try to add it with auto discovery, PH will create a New Device 1 with the address of 99,11.22 (comma is correct) and New Device 2 with the address of 33.77.88. I have to go into devices afterwards and delete one of them and correct the address, and also choose the proper device type because that doesn't populate properly either.
I know I can create the device manually, and it's not the end of the world to have to do that or correct things because it's not like I'm normally adding devices very frequently. Just was wondering if this is happening to others or if it's being corrected.
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 31 2011 at 07:36 | IP Logged
|
|
|
Ok, here is an example. Clean start of PH with a couple lights on. I press RemoteLink1 Button 6, it fires my goodbye scenario "ALL_OFF_REMOTELINC1" Trigger. Turns off PLC Group 254 (My All Lights Group) and exits Pandora "PANDORA_EXIT" The "MIDNIGHT_SNACK_OFF" trigger fires because the KPL Button for "Midnight_Snack" is part of the "All Lights" plc group 254.
After this happens I try to turn on "OFFICE_LAMPS" several times. It does eventually turn on, but if you look it takes a couple times before PH actually sends it. It seems to come on after it empties out a buffer… Just so you know I'm not crazy, here is a screen recording. It's low quality and slower because of the screen recording software but the results are just the same. The longer PH is running and the worse this gets. If I switch back to 2.1B it works fine, I'd like to stay on the new version and switch to a PLM since PLC doesn't support newer devices, but I am at my limit of what I can take...
Since I maintain my local rc site I dumped the flash video out there...
Also Attached are the logs
http://www.team1raceway.com/temp/ph.swf
2011-01-31_073610_Logs.txt
Edited by Lenny - January 31 2011 at 07:38
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 31 2011 at 08:59 | IP Logged
|
|
|
GREAT Documentation… I’m curious. What is in Pandora besides setting a global? If there is more add a 1 second wait to break it up and see if that breaks the hold. And you might add a user msg at its exit. This in the interest of debug. Don’t know if it will point to the real problem though.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
Lenny
Senior Member
Joined: January 06 2008
Online Status: Offline
Posts: 102
|
| Posted: January 31 2011 at 18:14 | IP Logged
|
|
|
BeachBum wrote:
| What is in Pandora besides setting a global? |
|
|
The "ALL_OFF_REMOTELINC1" uses raw formula to turn off 2 plc groups "ALL_LIGHTS" and "WINAMP_PLAY-STOP" using ph_insteongroup. (I used to use winamp now use pandora, I never renamed the plc group) The "WINAMP_PLAY-STOP" group off causes the The "Pandora_Exit" trigger and Macro. The only thing in that macro is "ph_closewindow(ph_findwindow("Pandora",1))" then the set of the Global Variable.
I can try doing it differently to see if it makes any difference... Is it better to have the trigger call a macro or just use the raw formula in the trigger? I guess I just used formulas in the trigger to avoid creating so many macros and macros when I'd use the same event more than once.
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 31 2011 at 18:28 | IP Logged
|
|
|
I have found recently I have been hanging waiting on things to complete. Not a PH problem other than it delays the following lines to execute. So I have added waits to those macros that are not time dependent thus allowing others to execute in the queue. Don’t know what that has to do with 213 other than exposing some bottleneck. In a trigger I believe it is better to call a macro. Although I do use the Boolean field for some triggers.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: February 01 2011 at 08:31 | IP Logged
|
|
|
I think I created your same scenario. It appears if there is stuff in the execution queue you cannot queue up a direct command. The difference is I don’t see anything in the Execution Queue in the video and that may be due to the recording software. This problem may be attributed to a slow responding “ph_closewindow(ph_findwindow("Pandora",1))". One way to prove that would be to execute it manually in the formula builder.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome Beta 2.1.2
