Closed iFac3 closed 4 years ago
I've played a bit with this recently, and found something.
Since I wrote you I've done reset device, reinstall app, readd device multiple times, but run into the same failure at some point. Everything goes well for a while, but once when issue comes, it has one visible thing every time:
Writes "Error on filter" at Product section.
Connecting result is that automated reporting stops, update on status happens only when I set anything on the device. (I can check it under "Latest update date") It's weird, becuase all started with lost control over the device, but now ability of control remains, however updating is missing.
Great info, let me check it again. mostly a failure should not block the next run 2 minutes later.
also can you try if it has something to do with the wifi connection and using 2.4ghz
WiFi is definitely not an issue here, spectrum is clear, I have UniFi ac system, what works very good indeed.
Rgds,
Gergely. On 2020. Apr 10. 16:19 +0200, Edwin Biemond notifications@github.com, wrote:
also can you try if it has something to do with the wifi connection and using 2.4ghz — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
oh wow , I have the same issue. error on filter and last update from 2 days ago. plus control does not work.
restart app from the homey app works for me , nice I also got this issue
It worked for me too now, I’m gonna check time by time and report you.
Rgds,
Gergely. On 2020. Apr 10. 22:16 +0200, Edwin Biemond notifications@github.com, wrote:
restart app from the homey app works for me , nice I also got this issue — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I see the errors in debug mode, status goes well , filter and firmware is failing.
found an error where there is a restart/ re-init of the app, 1st step went well but the old shared key was used on the 2 minute crontask .now I will always use the new key instead.
can you test it again https://homey.app/a/com.athom.philipsair/test/
also I had to restart the philips device after too many retries , I was getting connection resets
Is something changed in the Philips Air device behaviour, or Homey behavier differs?
Üdv,
G. On 2020. Apr 10. 23:48 +0200, Edwin Biemond notifications@github.com, wrote:
also I had to restart the philips device after too many retries , I was getting connection resets — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I think in homey
I guessed... since the updated Homey FW...
Üdv,
G. On 2020. Apr 11. 0:13 +0200, Edwin Biemond notifications@github.com, wrote:
I think in homey — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I hope philips auto updates its firmware, they changed protocol on late 2019 devices and I don't have 1 or I don't know how I can upgrade the firmware.
got it again after 4 hours, Status is now 6 hours behind, cron is still working. I see error on product. will try to find out why the key is not valid anymore and do some re-init when we got some failure
added a fix so secret is renewed after a communication error , plus store secret on device https://homey.app/a/com.athom.philipsair/test/
Nice, thanks for update!
Test of 0.0.19 has just started...
...I’ll get back to you with feedback.
Rgds,
Gergely. On 2020. Apr 11. 13:04 +0200, Edwin Biemond notifications@github.com, wrote:
added a fix so secret is renewed after a communication error , plus store secret on device https://homey.app/a/com.athom.philipsair/test/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
for me it is stable for the last 24 hours. I don't know what is changed on homey or philips but it is good. I will retrieve/refresh its secret key on error at least so next time should be good again. I saw somehow the key was not valid anymore. maybe we got some silence philips update.
Hi Edvin,
Worked fine till now. The device has just became unreachable by Homey.
(IP exists, it has been fixed, device is reachable through the AirMatters app.
Rgds,
Gergely. On 2020. Apr 12. 11:32 +0200, Edwin Biemond notifications@github.com, wrote:
for me it is stable for the last 24 hours. I don't know what is changed on homey or philips but it is good. I will retrieve/refresh its secret key on error at least so next time should be good again. I saw somehow the key was not valid anymore. maybe we got some silence philips update. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
A restart solved this, I'm testing continuously
Allright! App is perfect again!
Hi biemond,
First of all I’d like to thank you so much this Homey app!
What I experienced is regards to Humidity. The device shows target humidity instead of measured humidity. I can not access the integrated humidity sensor data even from insights, however would be awesome to set up automations based on this.
Other thing is connected to HomeKit Experiment. Philips device appears as a switch instead of purifier/humidifier and shows in the details target instead of current humidity.
My device is 3000i 2 in 1 Purifier and Humidifier (AC3829/10)