Quick update for you, I loaded your updated jar file, it looked good, properly created the things and channels and no errors from anything. However when I try to switch either of these two pumps on or off they do not do anything. The item changes as it usually does with the 3 usual logs:
Item received command ON
Item predicted to change from OFF to ON
Item changed from OFF to ON
(something like that, that’s from memory, I’m not at my computer). However, There is not an xml request logged to the Hayward server as with actuations for the other devices. So, I’m wondering if there may still be an error in the binding code for these types of pumps. I’ve triple checked the channel code on each item in the items file and they are correct. (I copied them straight from the UI things/channels pages)
Thank you! Let me know what I can send to help you.
Ok. We are getting close. I found one more omission that should solve the command issue. Let me know if you find anything else, or if this all works so I can publish the changes. Thanks!
I just installed it and there is no change yet. I re-initialized the Omnilogic bridge after re-installing. Here are some more specifics: when I turn on the working pool Filter pump Switch item that I have it does this (as an example):
14:27:52.950 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'PoolFilterPower' received command OFF
14:27:52.965 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'PoolFilterPower' predicted to become OFF
14:27:52.978 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'PoolFilterPower' changed from ON to OFF
14:27:53.070 [TRACE] [internal.handler.HaywardBridgeHandler] - Hayward Connection thing: handleCommand Hayward http command: <?xml version="1.0" encoding="utf-8"?><Request><Name>SetUIEquipmentCmd</Name><Parameters><Parameter name="Token" dataType="String">1c75e9b5893f424d96cadf526cd0a939</Parameter><Parameter name="MspSystemID" dataType="int">116587</Parameter><Parameter name="PoolID" dataType="int">1</Parameter><Parameter name="EquipmentID" dataType="int">3</Parameter><Parameter name="IsOn" dataType="int">0</Parameter><Parameter name="IsCountDownTimer" dataType="bool">false</Parameter><Parameter name="StartTimeHours" dataType="int">0</Parameter><Parameter name="StartTimeMinutes" dataType="int">0</Parameter><Parameter name="EndTimeHours" dataType="int">0</Parameter><Parameter name="EndTimeMinutes" dataType="int">0</Parameter><Parameter name="DaysActive" dataType="int">0</Parameter><Parameter name="Recurring" dataType="bool">false</Parameter></Parameters></Request>
14:27:53.104 [TRACE] [internal.handler.HaywardBridgeHandler] - Hayward Connection thing: handleCommand Hayward http response: Successfully <Response><Name>SetUIEquipmentCmd</Name><Parameters><Parameter dataType="int" name="Status">0</Parameter><Parameter dataType="int" name="StatusMessage">Successfully</Parameter></Parameters></Response>
However when I turn on or off one of the two pump things linked items it does nothing, other than this:
14:27:37.319 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'FountainPower' received command ON
14:27:37.430 [INFO ] [openhab.event.ItemStatePredictedEvent] - Item 'FountainPower' predicted to become ON
14:27:37.446 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'FountainPower' changed from OFF to ON
(the two pump devices we’ve been troubleshooting) Also, one more piece of info, none of the items linked to the channels of either of these pumps (spa jets and pool fountains) populate with any data, ie the pumpSpeed, pumpState, pumpLastSpeed and pumpEnable (they don’t seem to be getting any of the info from the getTelemetry call).
Edit: I also rebooted and restarted openhab and it still didn’t change (I just wanted to be sure that the new jar was installed)
Wow, I found yet another omission. Try this one. This is difficult developing code that I cannot test myself. I guess I need to install a water feature in my pool.
I loaded it up and there is progress! One of the pumps can be turned on and off (the single speed pump, pump 16) using the “pumpEnable” channel. The other pump can only be turned off using the “pumpEnable” channel (the variable speed pump, pump 9). Here is the command and response from the logs. I’m not sure why it isn’t working.
The other problem I see is that neither the “pumpState” nor “pumpLastSpeed” channels for either pump update their items. The getTelemetery call, while the pumps are on, have the correct data for those values, but for some reason it’s not parsing it into the channels and on to the items. Here is the getTelemetery return when the pumps are both on:
“pumpSpeed” does get updated properly, though I have not checked yet if I can turn the pump on by setting a speed yet, instead of by using “pumpEnable”. The other functions I haven’t checked yet are seeing if I can control the heater.
@matchews, I have now verified that sending commands via “pumpSpeed” channels works great. I can control the speed of all of my pumps, and turn them off through this channel, with no issues. The only component I haven’t got incorporated on my sitemap yet is the heater, which I will test soon.
The issue from my previous message remains, I am unable to turn on my fountain (variable speed pump) using the “pumpEnable” channel. It turns on momentarily, sends the request, gets a successful response (also above) and then as soon as the next “getTelemetery” returns, it turns the linked item back off. The pump never actually turns on. Also, neither pump gets the “pumpState” or “pumpLastSpeed” channels updated, when the data is indeed in the “getTelemetery” return.
One suggestion I have, and I can write this up on github if you’d like… Would it make sense to request a “getTelemetry” a short time after any other command? I don’t really want to increase the normal polling speed of “getTelemetry” (currently 10 sec), but it would be nice to have items update close to immediately after you set them (somewhere between .5 and 2 sec would probably be good, you know better than I do how the system responds to commands though).
The “pump on” command was sending a 100% speed request, which exceeded the max speed on your Fountain Pump 09 and was therefore being ignored. I am now consuming the min and max speeds for each filter/pump as thing properties, and commanding the max speed when powering on the filter/pump. I still need to investigate how to dynamically set the pump/filter speed sliders to represent the min and max speeds of the filter/pump.
The state and speed channel updates should be fixed as well. As for the polling, the hayward API server has limits on the frequency of hits. Once the commands are fully functional, you shouldn’t notice any toggling.
This update will require you to remove and recreate all Hayward things. Copy the UID from your existing connection/bridge, delete all of the things first, then delete the connection/bridge last, then recreate the connection/bridge using the same UID, then scan/discover and add all items. If you use the same UID, all of your linked channels will survive.
Ok, I followed your instructions and reloaded, it’s working nicely. All of the fields populate with data now. I have a few questions:
How does the binding do it’s “mapping”? When I look at the raw data in the logs a pump’s state might be 0, or 1 or 7, but in the sitemap default element it will actually say “Running” or “Off”, etc. How can I access these “maps” so that I can use them too in my own custom sitemap elements (like a selection element)
I’m still having the issue where If I Turn a pump on just after a getTelemetery call, it could take 9 seconds for the other data fields to populate or update, I don’t see any immediate updating going on.
As far as the Fountain Pumps are concerned:
What I’ve found (though it’s really hard to be consistent with testing because there are so many variables) is that if I’ve got a value in a “Selection” item on the sitemap that is greater than the pump maximum (in my case I had 100 as “max” on my fountains), then it wouldn’t “enable” the pump. But this wasn’t consistent. I’ve gone through and changed my Sitemap to reflect the settings in the thing properties for each pump, but I wonder if it would be possible to just have the binding check for the maximum (or minimum non-off setting) and then just apply that instead. Ie if the user said “I want 100%” but the max is 75%, and the binding has collected this data, then just change the command to be 75%. It seems like one of my pumps actually did this when I set 48% as the min, but it changed to 50% automatically. Maybe that is your intention and there’s still something amiss with the pump thing specifically.
The mapped states are hard coded into the binding. OpenHab’s UI’s will utilize the textual states when the channel is displayed (rather than the raw integer). In other words, it’s handled for you. Speaking of UI’s, I recommend you use the new OH3 model which automatically builds your pages rather then the old OH3 sitemaps. Regarding the pump min/max, that will all be fixed once I implement the dynamic implementation of the min/max properties of each pump/filter. This will prevent the user from commanding anything outside of these limits.
Not sure how much you have to adjust your chlorinator, but this is the front end of an algorithm I wrote to automatically adjust the salt output based on water temperature and UV exposure. It really helps if you have a cover and can detect if its open/closed.
If you switch over to the OH3 pages, you can setup so nice graphs as well…
Oh wow, I haven’t even seen the OH3 models yet. Still using the same old OH2 site maps. I will have to read up on that.
Sounds great about your dynamic pump/filter values in work. I’ll be looking forward to that.
I’ve made a rule that fires on changes to BOW temp changes and filter pump states (and will eventually fire on heater on/off) so that I can update a String item with the overall state of the pool system ie: “Pool Heating in Spa Mode, 86° F”, I also use this rule to update additional spa and pool temp items so that I can always see the current (or last known) temp of the pool and spa, rather than -1 (if it is not in that BOW mode currently).
I just added the pool temp to my overall temp chart, so I’ll have a look at how OH3 models do charts as well.
Yes, the -1 temperature is anoying. Here are some rules I made to handle that and a few other things to clean up the trends.
rule "Pool: Flow Delay"
when
Item HaywardPool_FlowSensor changed
then
if (HaywardPool_FlowSensor.state.toString=="ON"){
FlowTimer = createTimer(now.plusSeconds(600)) [|
PoolBOWFlowDelayed.sendCommand(ON)
]
} else {
PoolBOWFlowDelayed.sendCommand(OFF)
if(FlowTimer!==null) {
FlowTimer.cancel
FlowTimer = null
}
}
end
rule "Pool: Autocover Status"
when
Item AlarmPoolCover changed
then
if (AlarmPoolCover.state == "CLOSED") {
AutocoverStatus.sendCommand(OFF)
}else{
AutocoverStatus.sendCommand(ON)
}
end
//Avoid null water temp value when pool isn't running and erratic when it first starts
//Memorize last know good water temp
//Ignore when pump first starts up
rule "Pool: Update Temp"
when
Item HaywardPool_WaterTemp changed
or
Item HaywardPump_FilterState changed
or
Item PoolBOWFlowDelayed changed
then
var filterState = HaywardPump_FilterState.stateDescription.options.filter[stateOption | stateOption.value == HaywardPump_FilterState.state.toString].get(0).getLabel()
//logInfo("Pool", "Filter state: " + filterState)
//logInfo("Pool", "Flow Delay Switch: " + PoolBOWFlowDelayed.state)
if ((PoolBOWFlowDelayed.state==ON) && (HaywardPool_WaterTemp.state > 0|°F) && (filterState != "Priming")) {
PoolLastBOWWaterTemp.sendCommand(HaywardPool_WaterTemp.state as QuantityType<Temperature>)
}
end
//Running Average of Water Temp
rule "Pool: Average Water Temp"
when
Time cron "0 0/5 * ? * * *" //Every 5 minutes
then
if (PoolBOWFlowDelayed.state.toString=="ON"){
PoolLastBOWWaterTempAvg.sendCommand(Math::round((PoolLastBOWWaterTemp.averageSince(now.minusMinutes(120), "rrd4j") * 10).floatValue) / 10)
}
end
//Only chart heater setpoint when the heater is enabled
rule "Pool: Update Heater On Setpoint Temp"
when
Item HaywardVirtualHeater_CurrentSetpoint changed
or
Item HaywardVirtualHeater_Power changed
or
Item HaywardPump_FilterState changed
then
if ((HaywardVirtualHeater_Power.state==ON) && (HaywardPump_FilterState.state != "0")) {
HeaterOnSetpoint.sendCommand(HaywardVirtualHeater_CurrentSetpoint.state as Number)
} else {
HeaterOnSetpoint.postUpdate(40)
}
end
//Only chart chlor setpoint when the chlor is enabled
rule "Pool: Update Chlor Setpoint"
when
Item HaywardChlorinator_Power changed
or
Item HaywardChlorinator_scMode changed
or
Item HaywardChlorinator_SaltOutput changed
or
Item HaywardPump_Power changed
then
if ((HaywardChlorinator_Power.state.toString=="ON") && (HaywardPump_Power.state.toString=="ON") && (HaywardChlorinator_scMode.state.toString=="0")) {
PoolChlorTimedPercentFiltered.sendCommand(HaywardChlorinator_SaltOutput.state as Number)
} else if ((HaywardChlorinator_Power.state.toString=="ON") && (HaywardPump_Power.state.toString=="ON") && (HaywardChlorinator_scMode.state.toString=="1")) {
PoolChlorTimedPercentFiltered.postUpdate(100)
} else {
PoolChlorTimedPercentFiltered.postUpdate(0)
}
end
I do have a question/small problem. I have an OpenHab3 running and I have put in the binding. It works very well, with the exception of not finding my relay on my Omnilogic. Sadly it is one relay that I would really like to control through my automation. I cannot figure out why. I was reading your documentation and it indicates that relays are part of the binding, and it seems to discover all else. I am wondering if you have any ideas. As I am a new user to this form, I cannot upload files. I would like to share my MSP configuration file, but without being able to upload files I am not sure how to share this. Any ideas on how to share it?
Thanks for the feedback. You can paste the getMSP and getTelemetry responses right into your reply and I’ll check it out. I have a couple valve actuators that are working. Shouldn’t be a major issue.
I don’t know if I have done this right or not… as I am not fully familiar with OpenHab. I went into the terminal and entered log:set TRACE org.openhab.binding.haywardomnilogic. I then did a scan on the binding and here is what I got. (not sure how to format it correctly). Please let me know if I have done this right or I am missing something…
Hey @matchews I have a question about solar heating. I just added a solar setup to my controller and it uses an additional temperature sensor. I removed everything, installed the latest version of your binding and recreated all of my Things. It discovered two additional sensors, ID 13 (SENSOR_SOLAR_TEMP) and ID 4. But they’re both coming up NULL.
This is what I see in the UI. I’m not sure what that “virtual heater” is because it doesn’t exist. The only heater I have configured is the solar. But really I’m looking for the value of the rooftop temperature sensor (60 in the image).
I looked in the telemetry response and it doesn’t seem to be here:
Obviously you can’t do anything with a value that Hayward isn’t giving you. So my question is: why isn’t it returning this value? Do you know if maybe a different query is needed? Here’s my full MSP for reference:
You are right. It doesn’t look like they expose the solar temp reading anywhere in the API. The info you are providing is helping me fill in the blanks on how they handle sensors. While they do assign a system ID, BOW, etc., each sensor is associated with a backyard air temp, BOW water temp or BOW flow sensor. In other words, this information comes back in the getTelemetry with the parent object (Backyard or BOW), and not on it’s own. Sorry, but I can’t help with the solar temps. I’m going to remove the sensor handler from the binding as I have yet to see a standalone sensor that reports back in the telemetry.
Ok thanks, that’s frustrating that they don’t give you a way to query it. I also have an actuator on the solar loop and was hoping the actuator state would be captured in the filterValvePosition channel on the pump, but that never seems to update either.
@matchews I hope you’re doing well. After a while not looking at things I have started to get into linking items to my heater channels. It turns out that the binding only finds the virtual heaters when I do a scan, and does not generate any things for the actual heaters (which would give me a heaterState and enable channel I think). The heaterState would be useful for determining whether the Heater was actually on or if there was some discrepancy between heater status and the heater being turned on/off. Here is my getTelemetry response. You’ll see that systemId 4/12 are the virtual heaters (which do have things/channels) and systemId 5/13 are the heaters that do not get populated:
Do you think this may be due to my system having 2 bodies of water, similar to some of the other issues I saw months ago?
Lastly, do you know what the “Enable” channel of the actual heaters (5/13) represents? You can see that both of those channels say “YES” currently while the heater is actually not heating, and neither BOW (pool/spa) have the heater turned on. (BTW, there is only 1 physical heater in my system)
The VirtualHeater that you control is capable of utilizing multiple physical heaters (i.e. solar and gas), with each heater given a priority. I suspect the enable allows you to disable one or the other. As for the heaters not being discovered, which version of the code are you running? Here is a link to the latest version:
