-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/radiant controls zone occupancy #1571
Merged
Merged
Changes from 8 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
f13d38c
added arg for using zone occupancy and rearrange existing arg
carlosduarteroa 04022e2
use zone occupancy objs use for radiant control
carlosduarteroa e7f40aa
fixed bugs with naming EMS programs
carlosduarteroa f9f7842
reference specific zone occupancy in EMS programs if selected for con…
carlosduarteroa 4d98523
remove extra occupancy schedules/rulesets that are not needed
carlosduarteroa dfc1c26
added errors to users for zone occupancy control
carlosduarteroa 99a08b9
add Carlos to gemspec author list
mdahlhausen 409d1f3
Merge branch 'master' into feature/radiant_controls_zone_occupancy
mdahlhausen ba2dd5b
Merge branch 'master' into feature/radiant_controls_zone_occupancy
mdahlhausen 9080899
add methods to testing helper
mdahlhausen 54dd618
implmented a schedule with occupied hours to determine when to calcul…
carlosduarteroa b471c4a
added occupancy arguments into method to create low temp radiant
carlosduarteroa 0fd35ed
add radiant occupancy tests
mdahlhausen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend implementing this with EnergyManagementSystemSensor on the Schedule value, like you have for the temperature setpoint schedules.
Use the schedule value to determine the control, rather than
IF ((CurrentTime >= #{zone_occ_hr_start_name}) && (CurrentTime <= #{zone_occ_hr_end_name})),
That would mean changing it so if occupancy control isn't defined, and instead you get starting/stopping hours, making a ruleset schedule that has those hours and then following that schedule value for control.
To summarize:
IF ((CurrentTime >= #{zone_occ_hr_start_name}) && (CurrentTime <= #{zone_occ_hr_end_name})),
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thermal_zone_get_occupancy_schedule(zone, sch_name, occupied_percentage_threshold)
to make an on/off schedule"#{zone.name} Radiant System Control Schedule"
occupied_percentage_threshold
argument to radiant controls method, and pass intothermal_zone_get_occupancy_schedule
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example to create new ScheduleRuleset
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made the changes you suggested with commit 54dd618 and b471c4a