For the end of summer demo, I created an example PumpJob that got the job done - it would send a message to the Rhizome that toggled the pump state. With the recent status message additions ( #29 #30 #31 ), we now have near duplicates of that job that need to be refactored because:
The Rhizome takes in updates differently vs what we had at the end of summer
38 provides objects that encapsulate all the information necessary for identifying where to send the job information
So, the task at hand is:
Refactor those existing jobs so that they take their associated Equipment object as a parameter
Add jobs for Thermostat and RIMS
If Thermostat and RIMS send status updates (based on what we know so far), then implement those status updates (make a new Issue for that)
For the end of summer demo, I created an example PumpJob that got the job done - it would send a message to the Rhizome that toggled the pump state. With the recent status message additions ( #29 #30 #31 ), we now have near duplicates of that job that need to be refactored because:
38 provides objects that encapsulate all the information necessary for identifying where to send the job information
So, the task at hand is: