CommandTimeoutException in 0.3.X.X version
See original GitHub issueVersion 3 of your api does not work for me. When I am trying to use version 3 of your api , The following error occurs when trying to command or get the status of any device I own. The devices I own are mss110 and the dimmer switch (MSS560).
Unknown event!
Unknown event!
Unknown event!
Device online status changed: Family Lights went online
Device online status changed: Living Lights went online
Device online status changed: V2 Extra 2 went online
Device online status changed: V1 Extra 1 went online
Device online status changed: Bedroom Lamp went online
Device online status changed: UV Light went online
Traceback (most recent call last):
File "./test.py", line 54, in <module>
bed.get_status()
File "~/git/MerossIot/meross_iot/cloud/devices/power_plugs.py", line 117, in get_status
self._state = self._get_status_impl()
File "~/git/MerossIot/meross_iot/cloud/devices/power_plugs.py", line 78, in _get_status_impl
data = self.get_sys_data()['all']
File "~/git/MerossIot/meross_iot/cloud/device.py", line 129, in get_sys_data
return self.execute_command("GET", ALL, {})
File "~/git/MerossIot/meross_iot/cloud/device.py", line 126, in execute_command
return self.__cloud_client.execute_cmd(self.uuid, command, namespace, payload, callback=callback, timeout=timeout)
File "~/git/MerossIot/meross_iot/cloud/client.py", line 300, in execute_cmd
raise CommandTimeoutException("A timeout occurred while waiting fot the ACK: %d" % timeout)
meross_iot.cloud.exceptions.CommandTimeoutException.CommandTimeoutException: A timeout occurred while waiting fot the ACK: 10
I’m not sure why this is happening as version 2 seems to be working fine (Although for me, version 2 stops working after a day of running which is why I want to test version 3)
The test script is essentially doing this:
# Initiates the Meross Cloud Manager. This is in charge of handling the communication with the remote endpoint
manager = MerossManager(meross_email=username, meross_password=password)
# Register event handlers for the manager...
manager.register_event_handler(event_handler)
# Starts the manager
manager.start()
# You can retrieve the device you are looking for in various ways:
# By kind
devs = manager.get_supported_devices()
devs[0].get_status()
It happens on the .get_status(), .turn_on(), .turn_off() commands.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
How to properly catch SQL command timeout expiry exceptions?
I am using ADO.Net SQL Client to connect to a SQL Server 2005. Due to some concurrency issues, I get SqlExceptions indicating "Timeout ......
Read more >CommandTimeout does not cause exception when exceeded
If I set a command timeout on a Query action, the command is able to exceed the timeout set until it completes.
Read more >How to troubleshoot timeout problems and gather additional ...
This article provides information on how to troubleshoot timeout problems and gather additional information to resolve those.
Read more >Download 0.3 - NSClient++
The updated version has a few minor quick bug-fixes. A few new things but mainly a bug fix: - Fixed a crash when...
Read more >How to catch SQLServer timeout exceptions - Stack Overflow
-2 is the error code for timeout, returned from DBNETLIB, the MDAC driver for SQL Server. This can be seen by downloading Reflector,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s been tested already on my own local source for a while now. I just decided to create a pull request now since I would like it to be up on pip. Thanks for the merge! One thing to make sure would be that @vincenzosuraci can also use the api still I cannot confirm if it works in EU the same way.
Figured it out. For anyone experiencing this issue, it is due to the domain being set to “eu-iot.meross.com” instead of “iot.meross.com” I assume only people in the US will have issue with this.