UPB lighting

gwww · February 3, 2020, 3:45am

Invalid config fixed with 0.0.6-alpha build.

gwww · February 3, 2020, 3:00pm

Do you want to open this as an issue and tag it as “investigate”?

123 · February 3, 2020, 3:42pm

Not at the moment. Maybe later.

I’m currently having difficulty testing UPB events.

I’m using 0.0.6-alpha
I added upb.scene_activated to Developer tools > Events > Listen to events
Clicked Start listening
Pressed a button that activates link 2.
I see no response in the UI

I changed it to upb.scene_activate but got the same result.

What is your recommended test procedure for evaluating events? Also, where in the source code does it generate events?

EDIT

FWIW, this automation wasn’t triggered when I pressed a button that activates link 2:

- alias: 'UPB event'
  trigger:
  - platform: event
    event_type: upb.scene_activated
  action:
  - service: persistent_notification.create
    data_template:
      message: 'entity_id: {{trigger.event.data.entity_id}}'
      title: 'UPB Scene Activated'

What am I missing here?

gwww · February 3, 2020, 7:57pm

Here is what is working for me:

  - id: scene-activated
    alias: "Scene activated"
    trigger:
      platform: event
      event_type: upb.scene_activated
      event_data:
        entity_id: scene.family_room_half
    action:
      service: system_log.write
      data_template:
        message: "Activated '{{trigger.event.data.entity_id}}' Data '{{trigger}}'"

And the log that is generated on a button push:

2020-02-02 22:51:50 ERROR (MainThread) [homeassistant.components.system_log.external] 
Activated 'scene.family_room_half' Data 
'{'platform': 'event', 'event': <Event upb.scene_activated[L]: entity_id=scene.family_room_half>}'

I’m sure I don’t need the event_data on the trigger, but no time to try right now.

The code is in scene.py. Look for fire.

123 · February 3, 2020, 8:19pm

Comment moved to GitHub: https://github.com/gwww/hass-upb/issues/1#issuecomment-581622868

gwww · February 4, 2020, 4:50am

New version 0.0.7-alpha release up. Moving fast, so surely some bugs, but heading in a good direction. THANK YOU for all the testing everyone is doing!

bbrendon · February 4, 2020, 5:18am

@gwww I got everything switched over and I found that bug. Thanks for the wicked-fast turn around. Good timing for all this being the wife wasn’t home tonight.

We’re live!

123 · February 4, 2020, 12:05pm

FYI
Posted new issue: Light entity’s state is unchanged after using upb_light_fade_start service.

123 · February 4, 2020, 2:52pm

In the light.turn_on service, how is the value of transition mapped to UPB’s fade_rate values?

UPB fade_rate values

0 = Snap
1 = 0.8 sec
2 = 1.6 sec
3 = 3.3 sec
4 = 5.0 sec
5 = 6.6 sec
6 = 10 sec
7 = 20 sec
8 = 30 sec
9 = 1 min
10 = 2 min
11 = 5 min
12 = 10 min
13 = 15 min
14 = 30 min
15 = 1 hr

@gwww

UPB supports the sixteen discrete time-periods (shown above) whereas Home Assistant’s transition option is expressed in seconds.

If I set a light’s transition to 45 (seconds) how is that converted to one of UPB’s sixteen fade_rate values? Is 45 rounded up to the closest matching fade_rate level? In other words, for this example, it would be 9?

Catman · February 5, 2020, 6:24am

I have a pretty basic setup with 10 devices. So far it’s working pretty great. I have not tried scene entities yet. I’ll try to do that tomorrow.

123 · February 6, 2020, 9:44pm

@webmtn

How does one go about acquiring the following information from a device?

If the device is programmed to report its state when operated manually.
The device’s default fade-rate.

The Get Register Values command can request a Register Values Report from a device but I don’t know which registers store the default fade-rate and status reporting.

The documentation (from PCS) simply says this:

If I understand it correctly, the first 64 bytes of the Setup Register are collectively known as the UPBID and are consistent for all brands of UPB devices. The remaining bytes are called Configuration Registers and their contents depend on the manufacturer. So is it possible that the two properties I’m requesting are not located in the same Configuration Registers for PCS, Web Mountain, and Simply Automated?

gwww · February 7, 2020, 12:58am

Latest build is up 0.0.11-alpha.

All open issues have been have been coded and uploaded! Yipee!!

Time to open some more Add enhancements of what you would like done next.

I will be out of country, and hence not coding or responding to emails from Feb 14-24. Maybe get lots of testing done then!

123 · February 7, 2020, 1:17am

Before you leave, can you explain how transition is being handled? Or direct me to where it’s being done in the code?

If I set transition to 45 (seconds) how is that converted to UPB fade-rate? Rate #8 is 30 seconds and rate #9 is 1 minute. Is the transition value rounded up to the nearest fade-rate?

gwww · February 7, 2020, 1:35am

Not leaving for another week

The value entered for a transition is passed on directly to the end device. So if you enter a 6 you’ll get 10 seconds (the table you posted is the translation I’m using in my description here). So, you can’t enter 45 seconds as a transition value. You could pick a value of 8 to get a 30 second transition or a value of 9 to get a 1 minute transition.

I can point you to the code but it is super boring. As I say above it just takes the number you give and shoves that out onto the wire.

The reason I pass it on directly is I don’t know how a device will respond to the transition value.

Better ideas most gladly accepted!

123 · February 7, 2020, 1:47am

Thanks, I didn’t know it uses the supplied value verbatim (i.e. uses it as UPB fade-rate).

I think that may need to change in the future in order to comply with how Home Assistant defines transition. The value represents time in seconds. That’s why I had asked if it was being rounded to match the nearest discrete UPB fade-rate.

gwww · February 7, 2020, 1:54am

I use rate for Scenes for that reason. You’re right, need to do something about transition for lights. I just don’t know what that is.

I could map it to the closest value, at least for the values we know. The problem is what do all the devices do? And, if we did map it for lights then should probably use the same mapping for links.

123 · February 7, 2020, 2:48am

I suggest mapping it to the nearest discrete fade-rate value.

The documentation for the UPB integration can explain that transition values are mapped to UPB fade-rates and the maximum duration is 1 hour.

I don’t understand the question. Won’t the devices simply change their brightness at the specified fade-rate?

gwww · February 7, 2020, 3:05am

There’s no documentation on the transition rates. If we map them we may not get the desired effect on devices that don’t use the same rates as the devices we know about.

123 · February 7, 2020, 3:08am

Look in the UPB Command Wizard, at the step where you would specify fade-rate, it lists the fade-rate values and the durations they represent. That’s where I got the list I posted above.

EDIT
Used transition when I meant fade-rate. Duh.

webmtn · February 7, 2020, 3:16am

Sorry, 123 Taras. I’m out of town right now and not back until next Monday and just now saw this. On the first question - “If the device is programmed to report its state when operated manually” - I’m assuming you want to know if the device is programmed like that - and you already know how the device responds when the switch is operated manually.

Your assumption at the end is correct. Once you get into the Configuration Registers, all bets are off between manufacturers. It’s possible that there will be some commonality between manufacturers, but it’s not guaranteed. And, the SA / WMT devices are very different from the PCS devices. When I get back, I can try to find my register maps and see where that information is located on our dimmers and then try to determine if that’s where the same information is located on the PCS or SA devices. I might be able to find this information for the PCS devices, but doubtful for the SA devices.