Stopped sending sensor data to Telldus Live after running for about 2 weeks,about erijo/tellive-py

Comments (20)

erijo commented on June 21, 2024

You didn't happen to restart telldusd (perhaps due to a upgrade) around
that time?
On 18 Mar 2014 20:23, "pkempe" [email protected] wrote:

tellive_core_connector was launched correctly on system boot February 28
and has correctly reported sensor data and been able to remote control
switches as expected. On March 17 at about 18:30 CET (i.e about 17 days
later) it stopped reporting sensor data and Telldus Live now reports the
location as offline.

I have looked for error messages in the system logs, but haven't found
anything. The python process is still running, nothing appears out of the
ordinary.

System is Mac OS X 10.9.2.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

from tellive-py.

pkempe commented on June 21, 2024

No, I didn't do anything knowingly on that system. TelldusService (I suppose that's what you mean) is still running. By the way, I still haven't restarted neither TelldusService nor tellive_core_connector if you wan't me to try something.

from tellive-py.

pkempe commented on June 21, 2024

FWIW, simply stopping and restarting tellive_core_connector solved the
problem, nothing else was needed.

18 mar 2014 kl. 20:26 skrev Erik Johansson [email protected]:

You didn't happen to restart telldusd (perhaps due to a upgrade) around
that time?
On 18 Mar 2014 20:23, "pkempe" [email protected] wrote:

tellive_core_connector was launched correctly on system boot February 28
and has correctly reported sensor data and been able to remote control
switches as expected. On March 17 at about 18:30 CET (i.e about 17 days
later) it stopped reporting sensor data and Telldus Live now reports the
location as offline.

I have looked for error messages in the system logs, but haven't found
anything. The python process is still running, nothing appears out of the
ordinary.

System is Mac OS X 10.9.2.

Reply to this email directly or view it on GitHub<
https://github.com/erijo/tellive-py/issues/2>
.

Reply to this email directly or view it on
GitHubhttps://github.com//issues/2#issuecomment-37976888
.

from tellive-py.

erijo commented on June 21, 2024

Which version of tellive are you using?

from tellive-py.

pkempe commented on June 21, 2024

tellcore-py 1.0.3
tellive-py 0.4.2

19 mar 2014 kl. 19:54 skrev Erik Johansson [email protected]:

Which version of tellive are you using?

—
Reply to this email directly or view it on GitHub.

from tellive-py.

erijo commented on June 21, 2024

Which version of Telldus Core are you using?

from tellive-py.

pkempe commented on June 21, 2024

TelldusCenter 2.1.2, if that's what you mean. I believe that's what provides TelldusCore to the mac. It's the only telldus application I have installed besides tellcore-py and tellive-py.

from tellive-py.

erijo commented on June 21, 2024

Yes, exactly. Since you're using 2.1.2 it isn't the problem I suspected...

The only thing I can think of now is to run with debug (-d or set debug option in config), reproduce and see if that gives any clue.

from tellive-py.

pkempe commented on June 21, 2024

OK, done. Will report back with any findings.

19 mar 2014 kl. 06:43 skrev Patrik Kempe [email protected]:

FWIW, simply stopping and restarting tellive_core_connector solved the problem, nothing else was needed.

18 mar 2014 kl. 20:26 skrev Erik Johansson [email protected]:

You didn't happen to restart telldusd (perhaps due to a upgrade) around
that time?
On 18 Mar 2014 20:23, "pkempe" [email protected] wrote:

tellive_core_connector was launched correctly on system boot February 28
and has correctly reported sensor data and been able to remote control
switches as expected. On March 17 at about 18:30 CET (i.e about 17 days
later) it stopped reporting sensor data and Telldus Live now reports the
location as offline.

I have looked for error messages in the system logs, but haven't found
anything. The python process is still running, nothing appears out of the
ordinary.

System is Mac OS X 10.9.2.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

—
Reply to this email directly or view it on GitHub.

from tellive-py.

pkempe commented on June 21, 2024

Now it has happened again. At approximately midnight last night Telldus Live stopped receiving updates (their website has the last report timed to 00:06). Since I've run tellive-py in debug mode, here's the log from just after midnight to now (before that there's nothing suspicious from what I can tell):

2014-04-06 00:05:43,514 DEBUG: Sending: b'28:e4ee8c829816145aada193dd37a5240344b88be178:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E37sss'
2014-04-06 00:06:02,853 DEBUG: Sending: b'28:017dea3ac20d8e728ad225a26dee4f744bf2ae6e7A:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:21.84:typei1s6:lastUpi53407E4Asss'
2014-04-06 00:06:02,855 DEBUG: Sending: b'28:affe1df4ecd58af58a2fa7725a5f71cc7e8730ce78:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E4Asss'
2014-04-06 00:06:06,916 DEBUG: Sending: b'28:598f685fa194aa221baaf1a59e0a8a7e344805eb69:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E4Esss'
2014-04-06 00:06:06,917 DEBUG: Sending: b'28:c624def3ea48e01ece5809c2355b0fedb4885fe367:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E4Esss'
2014-04-06 00:06:07,124 DEBUG: Sending: b'28:f0613bcce70de7abe3661b13e2aee66ab6ab743869:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E4Fsss'
2014-04-06 00:06:07,125 DEBUG: Sending: b'28:fc0bbbc0974ddb7d75c0101c02b8547cb2cadf3567:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E4Fsss'
2014-04-06 00:06:08,505 DEBUG: Received: b'28:59fc427083682822da64c0e2cd2e879d1483d2566:4:pong'
2014-04-06 00:06:36,686 DEBUG: Sending: b'28:ee4e2207e0cdedb3fb5b34379800f0db00665a0979:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value3:4.54:typei1s6:lastUpi53407E6Csss'
2014-04-06 00:06:36,687 DEBUG: Sending: b'28:422ee4e382cc07910f9790ab172e6eaafd23502f78:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:754:typei2s6:lastUpi53407E6Csss'
2014-04-06 00:06:43,213 DEBUG: Sending: b'28:77eedc3c4a21d757816b44d0e161ec8ba44c3bf77A:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:22.84:typei1s6:lastUpi53407E73sss'
2014-04-06 00:06:43,214 DEBUG: Sending: b'28:91dc4da2d3056f43073bad8da8207dfb0740020978:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E73sss'
2014-04-06 00:06:43,357 DEBUG: Sending: b'28:77eedc3c4a21d757816b44d0e161ec8ba44c3bf77A:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:22.84:typei1s6:lastUpi53407E73sss'
2014-04-06 00:06:43,358 DEBUG: Sending: b'28:91dc4da2d3056f43073bad8da8207dfb0740020978:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E73sss'
2014-04-06 00:06:45,916 DEBUG: Sending: b'28:e839c55cf52966bca7e5cdceea0c6bcf5df0fdcc69:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E75sss'
2014-04-06 00:06:45,917 DEBUG: Sending: b'28:47a261fa02312e1b774cc08001f8906a9554823e67:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E75sss'
2014-04-06 00:06:46,123 DEBUG: Sending: b'28:70e315fd1c4772363474078b8a5f87216fa1727d69:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E76sss'
2014-04-06 00:06:46,124 DEBUG: Sending: b'28:ec26abea79c36d0791ac5e36e84da408d44f0d3767:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E76sss'
2014-04-06 00:07:02,856 DEBUG: Sending: b'28:d1a6b62b1c3856ea3e3f31b1ddc468600a40f6767A:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:21.84:typei1s6:lastUpi53407E86sss'
2014-04-06 00:07:02,857 DEBUG: Sending: b'28:0989e674ace49ce906e1b161b61ab46473dc97aa78:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E86sss'
2014-04-06 00:07:03,144 DEBUG: Sending: b'28:d8f2e044bfbed154d9300d2a737885f0adee5fa27A:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:21.84:typei1s6:lastUpi53407E87sss'
2014-04-06 00:07:03,145 DEBUG: Sending: b'28:170d40acd5ec6cb59a62bc1aefd38bf4c69b5ab078:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407E87sss'
2014-04-06 00:07:10,279 DEBUG: Sending: b'28:ba3cf6ceecbe4ff68b2738142cf12f70d7d596cb79:B:SensorEventh9:sensor_idiDs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value3:7.64:typei1s6:lastUpi53407E8Esss'
2014-04-06 00:07:10,280 DEBUG: Sending: b'28:86d00aaa093785074d0841edb72838bad830545b78:B:SensorEventh9:sensor_idiDs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:704:typei2s6:lastUpi53407E8Esss'
2014-04-06 00:07:24,915 DEBUG: Sending: b'28:54d828c4d4c5b620b2672b5c9a575029e677fb4c69:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E9Csss'
2014-04-06 00:07:24,916 DEBUG: Sending: b'28:754413f3293a50760feb5d31c3153675116edafd67:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E9Csss'
2014-04-06 00:07:25,123 DEBUG: Sending: b'28:f0ce511f70b7474b49ed12644f597bf6bb74956469:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407E9Dsss'
2014-04-06 00:07:25,125 DEBUG: Sending: b'28:4289f12d6c032144d29ad130cade8ff6e687f6ea67:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407E9Dsss'
2014-04-06 00:07:36,545 DEBUG: Sending: b'28:b1f50e349bcebe108aa87aec0857371d2b4decbc79:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value3:4.54:typei1s6:lastUpi53407EA8sss'
2014-04-06 00:07:36,546 DEBUG: Sending: b'28:15259d4aad2de942b09de565131b2a19d0459cab78:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:754:typei2s6:lastUpi53407EA8sss'
2014-04-06 00:07:36,673 DEBUG: Sending: b'28:b1f50e349bcebe108aa87aec0857371d2b4decbc79:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value3:4.54:typei1s6:lastUpi53407EA8sss'
2014-04-06 00:07:36,674 DEBUG: Sending: b'28:15259d4aad2de942b09de565131b2a19d0459cab78:B:SensorEventh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:754:typei2s6:lastUpi53407EA8sss'
2014-04-06 00:07:43,392 DEBUG: Sending: b'28:99d984173425682110b711ba2820ae258e5de9e07A:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:22.84:typei1s6:lastUpi53407EAFsss'
2014-04-06 00:07:43,394 DEBUG: Sending: b'28:dabb8d53931eda8515614d3917ec020401c40c2478:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407EAFsss'
2014-04-06 00:07:43,504 DEBUG: Sending: b'28:99d984173425682110b711ba2820ae258e5de9e07A:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:22.84:typei1s6:lastUpi53407EAFsss'
2014-04-06 00:07:43,505 DEBUG: Sending: b'28:dabb8d53931eda8515614d3917ec020401c40c2478:B:SensorEventh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407EAFsss'
2014-04-06 00:08:03,004 DEBUG: Sending: b'28:74a8f2fe3e58f7460be0aa52c5f69e3e2e84b5e57A:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value4:21.84:typei1s6:lastUpi53407EC3sss'
2014-04-06 00:08:03,006 DEBUG: Sending: b'28:d5e2476221ac16642e4165fba9a254016d48709578:B:SensorEventh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolynslh5:value2:254:typei2s6:lastUpi53407EC3sss'
2014-04-06 00:08:03,916 DEBUG: Sending: b'28:be428ffc0963f57191810971fbc449af6f6b063969:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407EC3sss'
2014-04-06 00:08:03,917 DEBUG: Sending: b'28:a5fdb09b500c095d447ce4751c70f4eb16d9aa7a67:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407EC3sss'
2014-04-06 00:08:04,124 DEBUG: Sending: b'28:6aa6bb0d3f96be06873d6c50e88b1735078448af69:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value4:20.34:typei1s6:lastUpi53407EC4sss'
2014-04-06 00:08:04,125 DEBUG: Sending: b'28:d7c7f7659302e6a315fbf476b3737744d1e8f85c67:B:SensorEventh9:sensor_idi35s5:model4:1A2D8:protocol6:oregonslh5:value2:324:typei2s6:lastUpi53407EC4sss'
2014-04-06 00:08:08,792 DEBUG: Received: b'28:59fc427083682822da64c0e2cd2e879d1483d2566:4:pong'
2014-04-06 03:31:42,530 ERROR: Communication error: No pong received from server
Traceback (most recent call last):
  File "/usr/local/bin/tellive_core_connector", line 286, in <module>
    main(config[section])
  File "/usr/local/bin/tellive_core_connector", line 244, in main
    raise RuntimeError("No pong received from server")
RuntimeError: No pong received from server
2014-04-06 03:31:42,530 INFO: Reconnecting in 92 seconds
2014-04-06 07:07:47,172 DEBUG: Fetching server list from api.telldus.com:443
2014-04-06 07:07:48,321 DEBUG: Found 11 available servers
2014-04-06 07:07:48,321 DEBUG: Connecting to alice.telldus.com:45000
2014-04-06 07:07:48,392 INFO: Connected to alice.telldus.com:45000
2014-04-06 07:07:48,394 DEBUG: Sending: b'28:4f34ae508a7cdb2494f1a8d0487f867ce59a16bfAC:8:Registerh4:hash4:sha13:key20:THETECHET2STUSWAGACRUWEFU5EWUW5W4:uuid24:d4607341-2e15-4e35-8e00-89342da0582ash7:version5:0.4.22:os6:macosx8:protocoli2sA:os-version6:10.9.2s'
2014-04-06 07:07:48,541 DEBUG: Received: b'28:92eec3e51dd81147f5ffe28734f1696f912f08cf26:A:Registeredh10:supportedMethodsi3D7ss'
2014-04-06 07:07:48,541 DEBUG: Client is registered, supported methods: 0x3d7 -> 0x3d7
2014-04-06 07:07:48,547 DEBUG: Sending: b'28:48e3935bf056964dadc9684c5045e152861cec638F:D:DevicesReportlh5:statei2s2:idi3s7:methodsi3sA:stateValue1:04:name9:Brytare 1sh5:statei2s2:idi2s7:methodsi3sA:stateValue1:04:name9:Brytare 2ss'
2014-04-06 07:07:48,553 DEBUG: Sending: b'28:6556847dc40e93a51819d42009e62c91996d8be1341:D:SensorsReportllh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolyn4:name5:Altanslh5:value2:754:typei2s6:lastUpi53407EA8ssh5:value3:4.54:typei1s6:lastUpi53407EA8sssslh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolyn4:nameA:Vardagsrumslh5:value2:254:typei2s6:lastUpi53407EAFssh5:value4:22.84:typei1s6:lastUpi53407EAFsssslh9:sensor_idiDs5:model13:temperaturehumidity8:protocol8:mandolyn4:name9:Krypgrundslh5:value2:704:typei2s6:lastUpi53407E8Essh5:value3:7.64:typei1s6:lastUpi53407E8Esssslh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolyn4:name6:Sovrumslh5:value2:254:typei2s6:lastUpi53407EC3ssh5:value4:21.84:typei1s6:lastUpi53407EC3sssslh9:sensor_idi35s5:model4:1A2D8:protocol6:oregon4:nameA:Ovanvaningslh5:value2:324:typei2s6:lastUpi53407EC4ssh5:value4:20.34:typei1s6:lastUpi53407EC4sssss'
2014-04-06 10:44:21,024 ERROR: Communication error: No pong received from server
Traceback (most recent call last):
  File "/usr/local/bin/tellive_core_connector", line 286, in <module>
    main(config[section])
  File "/usr/local/bin/tellive_core_connector", line 244, in main
    raise RuntimeError("No pong received from server")
RuntimeError: No pong received from server
2014-04-06 10:44:21,025 INFO: Reconnecting in 89 seconds
2014-04-06 14:09:21,140 DEBUG: Fetching server list from api.telldus.com:443
2014-04-06 14:09:21,814 DEBUG: Found 11 available servers
2014-04-06 14:09:21,815 DEBUG: Connecting to zaida.telldus.com:45000
2014-04-06 14:09:21,884 INFO: Connected to zaida.telldus.com:45000
2014-04-06 14:09:21,886 DEBUG: Sending: b'28:4f34ae508a7cdb2494f1a8d0487f867ce59a16bfAC:8:Registerh4:hash4:sha13:key20:THETECHET2STUSWAGACRUWEFU5EWUW5W4:uuid24:d4607341-2e15-4e35-8e00-89342da0582ash7:version5:0.4.22:os6:macosx8:protocoli2sA:os-version6:10.9.2s'
2014-04-06 14:09:22,051 DEBUG: Received: b'28:92eec3e51dd81147f5ffe28734f1696f912f08cf26:A:Registeredh10:supportedMethodsi3D7ss'
2014-04-06 14:09:22,051 DEBUG: Client is registered, supported methods: 0x3d7 -> 0x3d7
2014-04-06 14:09:22,055 DEBUG: Sending: b'28:48e3935bf056964dadc9684c5045e152861cec638F:D:DevicesReportlh5:statei2s2:idi3s7:methodsi3sA:stateValue1:04:name9:Brytare 1sh5:statei2s2:idi2s7:methodsi3sA:stateValue1:04:name9:Brytare 2ss'
2014-04-06 14:09:22,061 DEBUG: Sending: b'28:6556847dc40e93a51819d42009e62c91996d8be1341:D:SensorsReportllh9:sensor_idiEs5:model13:temperaturehumidity8:protocol8:mandolyn4:name5:Altanslh5:value2:754:typei2s6:lastUpi53407EA8ssh5:value3:4.54:typei1s6:lastUpi53407EA8sssslh9:sensor_idiCs5:model13:temperaturehumidity8:protocol8:mandolyn4:nameA:Vardagsrumslh5:value2:254:typei2s6:lastUpi53407EAFssh5:value4:22.84:typei1s6:lastUpi53407EAFsssslh9:sensor_idiDs5:model13:temperaturehumidity8:protocol8:mandolyn4:name9:Krypgrundslh5:value2:704:typei2s6:lastUpi53407E8Essh5:value3:7.64:typei1s6:lastUpi53407E8Esssslh9:sensor_idiBs5:model13:temperaturehumidity8:protocol8:mandolyn4:name6:Sovrumslh5:value2:254:typei2s6:lastUpi53407EC3ssh5:value4:21.84:typei1s6:lastUpi53407EC3sssslh9:sensor_idi35s5:model4:1A2D8:protocol6:oregon4:nameA:Ovanvaningslh5:value2:324:typei2s6:lastUpi53407EC4ssh5:value4:20.34:typei1s6:lastUpi53407EC4sssss'
2014-04-06 14:11:22,117 DEBUG: Sending: b'28:6129697c4bb6179e8696877d36297326634db7ef6:4:Ping'
2014-04-06 14:11:31,062 DEBUG: Received: b'28:59fc427083682822da64c0e2cd2e879d1483d2566:4:pong'
2014-04-06 14:13:22,188 DEBUG: Sending: b'28:6129697c4bb6179e8696877d36297326634db7ef6:4:Ping'
2014-04-06 14:13:31,665 DEBUG: Received: b'28:59fc427083682822da64c0e2cd2e879d1483d2566:4:pong'

After that it's just ping/pong every two minutes until right now.

Other than timeouts with the server, I should mention that I changed ISP Friday, meaning that no values could be reported during a few hours before noon, and also that my previous ISP was a bit flaky w/r/t stability from time to time (implicating it might have affected the previous crash as well).

Please also note:

it takes almost 3.5 hours to conclude that we have lost the connection, and after that, even though the app says that it will reconnect in 92 seconds, it takes an additional 3.5 hours before actually fetching the server list.
there seems to have been another error at 7 AM, there are no log entries between 7 and 10, and the reconnect to the server waits until 2 PM (3.5+3.5 hours).

from tellive-py.

erijo commented on June 21, 2024

This is very strange.

Something should be sent to the server at least once every two minutes (ping). And if nothing is received within six minutes (pong), the client should disconnect and connect again. But after midnight it takes almost 3.5 hours before the client times out. Then, as you mentioned, it takes another 3.5 hours before reconnecting.

After searching the web a bit it might be caused by the App Nap feature in OS X 10.9. Please see ipython/ipython#4431 for ideas on how to check for app nap and how to disable it.

from tellive-py.

erijo commented on June 21, 2024

This might also help:

http://www.reddit.com/r/Python/comments/1peys3/pythonistas_stay_away_from_mavericks_for_now_or/

https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/man8/caffeinate.8.html

from tellive-py.

erijo commented on June 21, 2024

Can you try installing https://pypi.python.org/pypi/appnope and then run with the latest version of tellive-py?

from tellive-py.

pkempe commented on June 21, 2024

Can I upgrade to the new version through pip install --upgrade or do I need to checkout from github?

25 mar 2014 kl. 08:59 skrev Patrik Kempe [email protected]:

OK, done. Will report back with any findings.

19 mar 2014 kl. 06:43 skrev Patrik Kempe [email protected]:

FWIW, simply stopping and restarting tellive_core_connector solved the problem, nothing else was needed.

18 mar 2014 kl. 20:26 skrev Erik Johansson [email protected]:

You didn't happen to restart telldusd (perhaps due to a upgrade) around
that time?
On 18 Mar 2014 20:23, "pkempe" [email protected] wrote:

tellive_core_connector was launched correctly on system boot February 28
and has correctly reported sensor data and been able to remote control
switches as expected. On March 17 at about 18:30 CET (i.e about 17 days
later) it stopped reporting sensor data and Telldus Live now reports the
location as offline.

I have looked for error messages in the system logs, but haven't found
anything. The python process is still running, nothing appears out of the
ordinary.

System is Mac OS X 10.9.2.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

—
Reply to this email directly or view it on GitHub.

from tellive-py.

erijo commented on June 21, 2024

You need to get it from github.

from tellive-py.

pkempe commented on June 21, 2024

Updated and checked that your latest change exists, rebooted now. Now we wait two weeks…

8 apr 2014 kl. 20:37 skrev Erik Johansson [email protected]:

You need to get it from github.

—
Reply to this email directly or view it on GitHub.

from tellive-py.

erijo commented on June 21, 2024

Can you check the activity monitor and verify that app nap is off for the process?

from tellive-py.

pkempe commented on June 21, 2024

I was trying to do that before, but unfortunately since I launch it as a
service (through launchd) it does not show up in Activity monitor. I tried
to find another way of telling, but have so far not found anything.

I do still keep the debug logging, so at least I'll see if the Ping/pongs
work as they are expected to.

8 apr 2014 kl. 21:19 skrev Erik Johansson [email protected]:

Can you check the activity monitor and verify that app nap is off for the
process?

Reply to this email directly or view it on
GitHubhttps://github.com//issues/2#issuecomment-39890019
.

from tellive-py.

pkempe commented on June 21, 2024

Now that the app has been running some time, I checked the logs. There are occasional disconnects, but this time the app reconnects after the advertised delay (a number of seconds). I think I would've seen the error by now if it still was an issue.

from tellive-py.

erijo commented on June 21, 2024

Great. Thanks for confirming the fix.

from tellive-py.

Stopped sending sensor data to Telldus Live after running for about 2 weeks about tellive-py HOT 20 CLOSED

Comments (20)

Related Issues (7)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent