EnergyPlus v8.6.0 - Daylighting Control

Hello everyone,

As most of you probably know, E+ v8.6.0 is out and it brings a few interesting improvements over previous versions. One that caught my eye and would like to start a discussion on how it can be implemented in Honeybee (if not already there with additionalParams). I would love the feedback of the more experienced users here.

The change refers to the the Daylighting:Controls object (https://github.com/NREL/EnergyPlus/pull/5725). As most of you know until now this allowed for ‘only’ 2 reference points per zone, something that led most of us to manually split zones when we wanted a more detailed design of daylight zones and assessment of the impact of daylight control strategies. This is now changing with two new objects replacing the previous one:

  • Daylighting:DELight:Controls

  • Daylighting:DeLight:ReferencePoint

The extension of the single object to two now allows for as many reference points as the user wants! I was wondering if this will work out of the box with Honeybee. Does it make any sense to now include this capability in an input of a component, for example using the output of the HB grid points component to quickly define control points on a surface/zone?

Thanks in advance.

Kind regards,

Theodore.

Theodore,

I am glad to hear about this new change. I have implemented a basic version of E+ daylighting control objects on the “Honeybee_Set Zone Thresholds” component but this is even more basic than the 2-sensor model in that it just takes one sensor point and illuminance threshold per zone:

It will take a bit of time for me to update this component to the new capabilities but, if you go with the additionalStrings route, it should work right out of the box with HB.

-Chris

Hi Chris,

Thanks for the reply. It’s good to know this will be usefull and implemented (:)) There’s no rush ofc, I can start testing this out with the additional parameters. It’s good to know where to look for this.

Do you think this might also change something on the downstream, i.e. visualization/result assessment components or is it not that big of an impact? I am thinking something like visualizing scenarios of different daylight zones and energy consumption. I am guessing all this can be done with the re-color mesh just wondering if this merits some special treatment.

Kind regards,

Theodore.

Theodore,

As far as I can tell, the lighting energy use results still come out on a thermal zone-by-zone basis. This was at least the case for the two sensor daylighting control. If you find that the results with these new objects come out differently, we can consider some other ways of visualizing them.

-Chris

Hi Theodore and Chris, This is very good potential and much faster for early prediction daylight analysis like for large buildings during in design. I’m trying to test this method in honeybee with addstrings but i’ve problem to run. Is it possible to share an example for this method in honeybee to help me?

Thanks in advance.

best,

M

Hi Mohammad,

Unfortunately I am currently tied up to completely different studies.

I will hopefully be going over E+ again this week, revamping base on Chris’s new components. I’ll let you know when I try this out.

Kind regards,

Theodore.

Many thanks for the prompt reply Theodoros,

Very nice!!

I am looking forward to your good news :slight_smile:

Best Regards,

M

Dear @chris
Sorry for bringing back this topic,

Is there any way to overwrite the default name that OS writes the daylight control name? I also could not find a proper OS Measure to implement this, there is one but again do not accept a name for daylight control…

Also, when I use the additional string to overwrite the whole settings here for daylight control and referencing points, it gives me an error that I could not solve it through HB.

Many thanks
Amir