Hi, I'm back. I've spent some time trying to figure out a way to have some interaction between this spa controller, the remote that came with it and Homeseer. They just don't like each other enough. So while messing around, I managed to wipe out my network a couple of times, but here's where I am today:
I put the pe953 (the remote control that came with the spa controller) as the primary controller on my network. Homeseer is the secondary controller. This way at least, I can still use the remote to have full control over all the spa functions and use Homeseer's api calls to monitor the spa temperature and trigger relay 1 on and off. Still borderline useless, but best I can get.
I tried to use the homeseer thermostat plugin api to try and set the setpoint on the pe653 with no luck. As mentioned above, the plugin has issues with this thermostat, so I used the api. I was able to get further - I changed the mode to heat (from off) and was able to set the heat setpoint to whatever temperature I want. Homeseer UI's confirm these new settings. All good, right? Wrong! For some odd reason, the pe953 handheld does not reflect the new setpoint temperature and still displays the old setpoint. Changing the setpoint on the pe953 remote changes the spa controller, but does not get reflected in Homesee. So either homeseer does not actually change the setpoint on pe653 or it is not the heat setpoint value that I"m supposed to be setting on pe653 but some other variable that might not be available through the thermostat api.
This is probably as far as I can get on my own. I'll be happy to try other stuff if somebody has ideas.
I put the pe953 (the remote control that came with the spa controller) as the primary controller on my network. Homeseer is the secondary controller. This way at least, I can still use the remote to have full control over all the spa functions and use Homeseer's api calls to monitor the spa temperature and trigger relay 1 on and off. Still borderline useless, but best I can get.
I tried to use the homeseer thermostat plugin api to try and set the setpoint on the pe653 with no luck. As mentioned above, the plugin has issues with this thermostat, so I used the api. I was able to get further - I changed the mode to heat (from off) and was able to set the heat setpoint to whatever temperature I want. Homeseer UI's confirm these new settings. All good, right? Wrong! For some odd reason, the pe953 handheld does not reflect the new setpoint temperature and still displays the old setpoint. Changing the setpoint on the pe953 remote changes the spa controller, but does not get reflected in Homesee. So either homeseer does not actually change the setpoint on pe653 or it is not the heat setpoint value that I"m supposed to be setting on pe653 but some other variable that might not be available through the thermostat api.
This is probably as far as I can get on my own. I'll be happy to try other stuff if somebody has ideas.
Comment