-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Timeout exception occured function PowerSensorWrapper #51
Comments
Hi @ccorderod , |
Hi @albertogeniola, |
Hi @albertogeniola, When first installed all was well until I needed to restart HA to add a new sensor, after which I got these log errors. Toggling either switch does not operate the corresponding device but the Meross Android app still can see and operate both devices ok. 2020-02-21 22:25:22 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform meross_cloud is taking over 10 seconds. |
Hi, |
Hi, |
I am still trying to spot the problem, but I'm under the impression this is sort of related to some race condition with the MSS310 sensor implementation. Would you mind testing the same component you have installed but disabling the MSS310 Power Sensor entity? To do so, follow the instructions below: |
OK just disabled both sensors for power and rebooted, this is still using the latest component release. 2020-02-22 11:05:15 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for wiser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. The only way I have found to make both switch and sensor work ok is to follow this sequence. Install component using HACS. DO NOT REBOOT. Now go through the integration entering user and password from the UI. Can now add both sensors and switch to Lovelace and all is good until a reboot is performed when all the errors occur again! |
Installed: 20200222.2 2020-02-22 12:38:44 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. |
Let us know! |
Result of power sensors being enabled. Anything else I can do to help? 2020-02-22 12:54:40 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. |
This is now a repeatable pattern. Disable sensors and reboot HA, log is good as are the switch entities. |
Hi @Fulch , I've just released a new version (20200222.4), which might increase stability of power sensor+mss310. I am not 100% sure it will work, yet. Would you mind testing it and let us know how does it work on the NUC? Don't forget to re-enable the power sensors. |
@albertogeniola Hi Alberto Have just re-enabled the power sensors after installing this latest release and rebooted HA, No errors in log and sensors are showing real time data! I have written some simple automations based on power usage which I will test tomorrow and let you know how it goes. |
Good news, it looks like you have solved this issue. I have been running automations based on power sensor data all day without any problem. Have also rebooted HA in excess of 10 times throughout the day just to test and have not had a single error about switch platform meross_cloud in the log on startup. As far as I am concerned I would consider this issue closed but I will leave that up to you. |
Glad to hear that. The latest version 20200223 also introduced minor improvements. Before closing this issue, would you please update to this one and let me know if is it working? |
Hi Alberto Installed: 20200223.1 Installed, rebooted HA and life is good not an error in site! Well done and thank you once again. |
Hey, just got again the error:
Additionally I got the error: Meross cloud is working fine, all my devices do have a strong connection to the access point and my internet connection is also without downtime since 3am (daily reboot). |
Hi @maltemosler , |
mss425e is not controllable anymore over home assistant while the meross app works fine. The valve is not gaining data so it doesn't show the current state and I can't control it. Honestly all meross devices don't work. After rebooting everything works fine. My IP changes every day at 3am could this be the cause for that? The error occured after the reboot/IP change I investigate a bit more tomorrow and update you if I find something |
What do you mean your IP changes? Does the connection drop? If so, can you identify the a log like "connection dropped"? |
Yeah at 3am my connection drops for like 1 minute and the isp provides me a new public ip but after checking the logs this morning I am sure this is not the reason for the errors. At 00:00:25 where the first error occured I was still awake and programmed stuff so this can't be the fault of a connection drop. Again nothing was controllable (this morning 07:30) per HA and the valves doesn't show temps and their state hope this log helps you
|
Well, it seems the connection to the Meross Cloud MQTT broker dropped at 2020-02-25 02:17:48. Do you have any other logs about connection drop? |
Sorry, i didn't posted the whole log cause it is over 2000 lines. According to fritz.box I got at 3:07 the new ip and my other raspi had no connection drop until 3:04 and it was at 3:07 again online. here is the full log: |
@albertogeniola, rev 20200223.2 of the component has been running with no issues for 3 days now in my setup. Thank you very much for your hard work spooting the glitch :-). |
Are you running version 20200223.2? |
Yeah, I installed it manually with custom components and now I double checked it, its 1:1 the same code like in git |
Hi @albertogeniola All was going well with my 2 x mss310 unti I updated HA to 0.106.0 today, after reboot of HA these errors started again. The log below is with both plugs enabled. 2020-02-27 22:20:06 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform meross_cloud is taking over 10 seconds. The log below is from having the lounge_plug disabled (both switch and power sensor). 2020-02-27 22:55:38 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform meross_cloud is taking over 10 seconds. This results in the bedroom_plug switch and power sensor being created and working ok and no further errors appear in the log. It seems the errors occur when the entities for the second plug need to be created. The HA update also caused a "race condition" problem with the deCONZ integration, causing some sensors not to be created on HA startup on supposedly 'slower hardware'. I'm happy to test and report back if it helps? |
Have just removed integration, uninstalled component and rebooted HA. Re-installed component (20200223.2) , did the integration again followed by HA reboot and I now have NO errors in log with both plugs installed and reporting power values correctly! I did notice yesterday that the Meross Android app reported scheduled server maintenance was occurring, maybe this was the cause of my problem and not the HA update to 0.106.1? |
Hi @albertogeniola I am running latest rev of the component, but there is still something wrong with it: |
I found a bug that might be the cause of this behavior. Would you please update to the latest release of this component and test it again? |
After updating to the newest version I get other errors - and again I can't controll anything until I reboot home assistant:
|
Oh damn, my bad. I forgot to release the updates I've done on the low-level library. I apologize. Would you please try again with the version I've just released (20200308.1)? Your feedback would be very appreciated. |
I still get the error but today was the first night where it was still working after waking up! Appreciate your work! :) 👍 🥇 It seems to occure every ~30 minutes Logger: custom_components.meross_cloud.common A timeout exception occurred while executing function <function SwitchEntityWrapper.update at 0x6dcf5a98> |
Hi @maltemosler , |
@ccorderod , can you perform the same test to double check? |
I didn't reboot HA since 2 days and so far everything is still working! <3 👍 |
Tonight it died after 4 days of working :/ Needed to reboot |
Hello. Was using Meross fine until 4am last night (all my thermostats lost connection so the graph stopped from that time onwards). Have uninstalled, reboot, reinstalled etc. but no go. I saw in HACS it was updated today 9 hours ago (I installed this component manually) so went the route of uninstall reboot then reinstall via HACs but still same issue; any ideas? Happy to send logs and troubleshoot etc. Thanks for your work btw, been very happy with my meross thermostats and HA integration :) (this immediately appears when setting up integration - meross cloud hasn't started blocking this has it? gut feel is the authentication is failing (but my android app works OK)) 2020-04-08 18:39:08 ERROR (MainThread) [homeassistant.components.climate] Error while setting up meross_cloud platform for climate |
Hi all, I think the latest version of this plugin should finally mitigate this issue. Would you please give it a try and report back if that's working as expected? |
Hi @albertogeniola. Apologies. Had to disable the component again.
My log is full of those:
2020-02-18 09:55:05 ERROR (SyncWorker_14) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20> 2020-02-18 09:55:15 ERROR (SyncWorker_10) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20> 2020-02-18 09:55:47 ERROR (SyncWorker_18) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20> 2020-02-18 09:55:57 ERROR (SyncWorker_19) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20> 2020-02-18 09:56:07 ERROR (SyncWorker_1) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20> 2020-02-18 09:56:17 ERROR (SyncWorker_14) [custom_components.meross_cloud.common] A timeout exception occurred while executing function <function PowerSensorWrapper._fetch_power_status at 0x7ff0c6a48c20>
and power sensors show as not available. Side effects (not sure it is related to the component):
Netatmo component, alexa component, push notifications, ... fail
The text was updated successfully, but these errors were encountered: