Please login or register.

Login with username, password and session length

Author Topic: Updated to 3.316 from 3.199, many devices don't work now  (Read 5716 times)

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Updated to 3.316 from 3.199, many devices don't work now
« on: September 22, 2011, 07:20:53 AM »

I upgraded to 3.316 because I purchased one of the soft start modules (PWL01).
My older wall switch devices don't seem to work now and my chime screeches mercilessly.
Do I need to go in and recreate the devices over and delete the old ones using the older model list?
Is there any easy way to do this?
I did it for my new PLW01 (code G15) and the old device (at code G15) showed up greyed out; I had to edit all my macros to clean it up.
I'd go back to a previous version but then the PLW01 won't work correctly and I like to keep current.

Thanks!

Logged
ActiveHomePro 3.310
SmartMacros 3.310

Brian H

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 305
  • Posts: 13295
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #1 on: September 22, 2011, 07:54:23 AM »

I believe you can click on the module. Then edit it. Picking the type from the Old before Soft Start Tab.
Then saving the changes.
Logged

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #2 on: September 22, 2011, 01:13:59 PM »

Thanks, I'll try that.
I looked before but I had an older version of AHP, sounds like it's all there now, perfect! :).
Logged
ActiveHomePro 3.310
SmartMacros 3.310

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #3 on: September 23, 2011, 09:08:11 AM »

Wow,
This is driving me nuts, not sure if I can even describe what's going on :).

I have some issues I think I can resolve but the biggest one is the PLW01 lamp switch control.
I configured it properly but the dimming is just not right, I used absolute dimming.
When I turn it on, it actually dims sometimes!
I've manually maxed it out by pushing the button thinking it has some internal limits but that didn't work either.
I'm trying to remember the exact sequence but the worse thing is if the module is at full bright or dim and I keep sending commands, my chimes start screeching like banshees! Didn't even know that they could do that!

All my modules prior were not soft start and the program was working perfectly for a very long time.
I added the PLW01 and updated AHP and now it's all gone to heck.
I think I was running 3.199 but it ran on W7 64-bit for some reason without issues.

I'd like to make sure I have everything for AHP removed and install again because now when I try to go back to a 3.2xx version it says it's not compatible. Do all the .dll's reside in the activehomepro folder or are there more somewhere else?

I had to fire up the ole 1132cu smarthome module to get it working somewhat but it has issues with dimming.
I'd like to go back to AHP, this is driving me nuts!

Thanks
Logged
ActiveHomePro 3.310
SmartMacros 3.310

Brian H

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 305
  • Posts: 13295
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #4 on: September 23, 2011, 09:28:31 AM »

The screeching chime module have been seen before.
I am not sure if a fix has been found.
http://forums.x10.com/index.php?PHPSESSID=llep4jrrn8vptb32m9h5lcekd5&topic=9273.0

Hopefully someone with knowledge of AHP can give you some pointers.
I was also using a 1132CU at one time.
Now I have a Insteon and X10 mixture. Not sure if that was any improvement.  ???
Logged

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #5 on: September 24, 2011, 10:58:10 AM »

 :)% ;D :)% ;D :)% ;D :)%

Got it working!

I experimented with the 1132cu but it does have issues with dimming. I didn't want to waste any more time on it.
Back to the CM15a.
Long story short I put the PLW01 on a different house code, H16 (haven't verified that this was necessary).
No godawful chime screeches!

When I want to command the module I just used the Extended Command.
 
Code - H16
Command Byte - 0x31
Data Byte - 0x00 for off
Data Byte - 0x3E for on
Data Byte - 0x1C for dim (anywhere from 0x00 to 0x3E sets the dim level)

I'm a happy guy!!!

BTW I'm using 3.310
Logged
ActiveHomePro 3.310
SmartMacros 3.310

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #6 on: September 24, 2011, 11:38:22 AM »

Well, not perfect :).

I had a module sharing the same Unit as the PLW01, it responded to the Extended Commands also.

Not a big deal, I changed it's Unit.
Logged
ActiveHomePro 3.310
SmartMacros 3.310

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #7 on: September 24, 2011, 12:59:22 PM »

Well this is goofy, changing the unit did not work.
I have another different type module on the same settings and it works just fine.
Also it only errantly turns on after the dim setting (0x1C) not the on setting(0x3E) of the PLW01.
As a fix after issuing the Extended Command I just shut off the light again :), works for now.
Still happy.
Logged
ActiveHomePro 3.310
SmartMacros 3.310

Brian H

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 305
  • Posts: 13295
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #8 on: September 24, 2011, 01:35:56 PM »

I am glad you found the answers you needed and it is now functioning.
Logged

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #9 on: September 27, 2011, 07:44:08 AM »

Well I thought it was working completely but it wasn't.
Here's what I had.

Daytime?
    Light OFF
Else
    Light on 50%

Motion detected
    Light on 100%

Motion detected complete (4 minutes)
    Daytime?
        Light OFF
    Else
        Light 50%
           
During Daytime it worked exactly as programmed.
At Nighttime however the light would not go 100%, it would stay at 50%!

I "fixed" this by Unchecking the "Issue on in place of Bright 100%".


I just have to track down the Bedroom Light being turned on by the Extended Command bug.
I'm investigating if it's related to the Data code being sent, I'll keep ya posted.


BTW I went back to 3.306, it works, afraid to change it :).
Logged
ActiveHomePro 3.310
SmartMacros 3.310

Noam

  • Community Organizer
  • Hero Member
  • ***
  • Helpful Post Rating: 51
  • Posts: 2818
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #10 on: September 27, 2011, 03:06:17 PM »

Well I thought it was working completely but it wasn't.
Here's what I had.

Daytime?
    Light OFF
Else
    Light on 50%

Motion detected
    Light on 100%

Motion detected complete (4 minutes)
    Daytime?
        Light OFF
    Else
        Light 50%
           
During Daytime it worked exactly as programmed.
At Nighttime however the light would not go 100%, it would stay at 50%!

I "fixed" this by Unchecking the "Issue on in place of Bright 100%".


I just have to track down the Bedroom Light being turned on by the Extended Command bug.
I'm investigating if it's related to the Data code being sent, I'll keep ya posted.


BTW I went back to 3.306, it works, afraid to change it :).

Sounds like an "Absolute" vs. "relative" dim problem.
Make sure the dim setting is set to "absolute" in all your macros.
Logged

emil

  • Sr. Member
  • ****
  • Helpful Post Rating: 2
  • Posts: 100
Re: Updated to 3.316 from 3.199, many devices don't work now
« Reply #11 on: September 27, 2011, 04:22:42 PM »

It's set to absolute.
Like I said, it's all working now.
Thanks
Logged
ActiveHomePro 3.310
SmartMacros 3.310
 

X10.com | About X10 | X10 Security Systems | Cameras| Package Deals
© Copyright 2014-2016 X10.com All rights reserved.