-
Notifications
You must be signed in to change notification settings - Fork 1
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
Stale temperature when heating (python module) #26
Comments
Hi @montgomeryb, As you found out, there is an issue opened on the home assistant integration, and I still don't know where the issue does come from. If possible, could you please provide logs, as I asked Geoff-Hz to ? I am working on it, and the info you already provided are very useful. To circumvent the issue, you can automate a 'power on' every few minutes and it might refresh the temperature. Regards |
Hi, |
Thanks @montgomeryb This clearly leads to a bug in the spa firmware. However, the logs confuse me about 2 things:
Last thing:
I know am I asking for elaborated tests, but I see you made a great first answer 👍 |
I am not using Home Assistant (yet) or anything similar. I am using the api in a simple script that is run through cron
Previously I was using the Intex App to schedule the heating from 00:00 - 08:00, it is still active and this time actually worked and turned off the heater.
I agree that it is more a firmware issue, than this library. I think any command that changes something will force the updated temperature. Turning the power on doesn't do anything as it's already on but turning it off resulted in an update. As I'm sure you noticed, I ran the intex_spa_get_status_double but they both came back with 101 instead of 103. I was able to try another experiment. I let the tub cool to 102 and turned on the heat. Once the control panel was reading 103 I again rand the status commands. I then went to the app that still had the temperature as 102. I changed the app from Fahrenheit to Celsius. Ran the status and then changed it back to Fahrenheit and the status came back with a current temp of 103. After a short period, I saw the Intext app change from 102 to 103. I'm not sure how easy it is to capture the traffic to the spa for the unit change and determine the command to send?
P.S. Thanks again for your efforts, and your English is excellent. I had previously tried some hardware attempts at controlling the spa that were not very successful - this is much better even with the Intex quirks. |
I think I have found another work-around. Setting the preset-temp to 106 (which is above the maximum) seems to trigger an updated current temperature, and also leaves the preset temp at the existing value. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@montgomeryb, big thanks for the lead! My spa is disconnected for a while now, and I have currently now way to test the python module by myself. So, could you investigate on these 2 points?
|
Hello, you are welcome. Yeah, in Ne York my spa is disconnected for another three months or so :) If there's no answers before then I'll be honoured to help out and get answers for those two questions. |
Hello! I'm assembling my SPA this Sunday, and I'd like to help testing it. Have a nice day! :) |
I tried looking to see if this is documented elsewhere, but didn't find it.
With no heating, it seems the current temperature is correctly reported with the status message, at least it changes over time.
However, when the heater is on it doesn't report updated temperatures. I noticed this on the intex app and had to force refresh it to give me an updated temperature. Today after leaving it heating overnight it still had the same temperature. The one way I found to force it to update was by changing the preset_temperature. It seemed that I had to set a different temperature for it to actually update the current temperature.
Am I missing something? I tried the three example get status scripts and info. before trying to change the temperature. Maybe it's my model (SC-WF10)? Anyway, it seems to be working now with making the call to change the preset temperature.
The text was updated successfully, but these errors were encountered: