Measure tool: Time-out not honoured for stand-by measurement ?
See original GitHub issueHi !
I am trying to use a Fibargroup, FGWP102 to measure an LTA004, but get a Power measurement is outdated
error.
I’ve tried decreasing the time between reports on the FGWP102 and increasing the SLEEP_TIMER
in the .env
file to 30 seconds, but looking at the debug-log this time-out does not appear to be honoured for the wait-time between samples when performing the stand-by measurement.
Or am I misinterpreting the purpose of the SLEEP_TIMER
?
2022-01-22 10:30:03,314 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:03,334 [DEBUG] http://homeassistant.local:8123 "GET /api/states/light.hobbykamer_lamp_1 HTTP/1.1" 200 300
2022-01-22 10:30:03,337 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:03,500 [DEBUG] http://homeassistant.local:8123 "POST /api/services/light/turn_off HTTP/1.1" 200 10
2022-01-22 10:30:03,501 [INFO] Measuring standby power. Waiting for 20 seconds...
2022-01-22 10:30:23,522 [DEBUG] Taking sample 0
2022-01-22 10:30:23,533 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:23,580 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
2022-01-22 10:30:24,586 [DEBUG] Taking sample 0
2022-01-22 10:30:24,594 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:24,628 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
2022-01-22 10:30:25,631 [DEBUG] Taking sample 0
2022-01-22 10:30:25,637 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:25,681 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
2022-01-22 10:30:26,684 [DEBUG] Taking sample 0
2022-01-22 10:30:26,689 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:26,722 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
2022-01-22 10:30:27,726 [DEBUG] Taking sample 0
2022-01-22 10:30:27,736 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:27,781 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
2022-01-22 10:30:28,788 [DEBUG] Taking sample 0
2022-01-22 10:30:28,800 [DEBUG] Starting new HTTP connection (1): homeassistant.local:8123
2022-01-22 10:30:28,829 [DEBUG] http://homeassistant.local:8123 "GET /api/states/sensor.metered_wall_plug_switch_power HTTP/1.1" 200 257
Traceback (most recent call last):
File "measure.py", line 517, in <module>
main()
File "measure.py", line 514, in main
measure.start()
File "measure.py", line 144, in start
standby_power = self.measure_standby_power()
File "measure.py", line 287, in measure_standby_power
return self.take_power_measurement(start_time)
File "measure.py", line 268, in take_power_measurement
self.take_power_measurement(start_timestamp, retry_count)
File "measure.py", line 268, in take_power_measurement
self.take_power_measurement(start_timestamp, retry_count)
File "measure.py", line 268, in take_power_measurement
self.take_power_measurement(start_timestamp, retry_count)
[Previous line repeated 2 more times]
File "measure.py", line 260, in take_power_measurement
raise OutdatedMeasurementError(
powermeter.errors.OutdatedMeasurementError: Power measurement is outdated. Aborting after 5 retries
To the extent relevant, I’m running the tool in a docker container on Windows, the image id is 6f3a84da8137
HomeAssistant OS v7.1
core-2021.12.10
supervisor-2021.12.2
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Modern standby SleepStudy - Microsoft Learn
SleepStudy can measure modern standby performance with minimal impact. Details on the report's contents can be found below.
Read more >TV Standby | Android Open Source Project
In Android 11, inattentive sleep is a power-saving feature that allows a user inactivity timeout to be set after which the screen turns...
Read more >(RX610)How to stop BCLK output during sleep mode & all ...
Answer: When BCLK output has been set, although it will automatically stop in software standby mode and deep software standby mode and go...
Read more >pt-online-schema-change — Percona Toolkit Documentation
The tool supports a variety of other measures to prevent unwanted load or other problems, including automatically detecting replicas, connecting to them, and ......
Read more >Measuring Availability Group synchronization lag - SQLShack
If no error is detected, then a failover may occur if the health-check timeout is reached or the lease between the resource DLL...
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 FreeTop 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
Top GitHub Comments
Nice. Make a pull request is no rocket science. Just Google it. “Github create pull request”. Than you will also be marked as contributor, learn some new skill and it takes me less time.
Yes I have added a feature some time ago that you can resume the measurements later on. The wizard will ask you if you want to do that. What setting do you have your
SLEEP_TIME
now? If you still have that at 30 you can set it at 5 now.If you still have it on 30 the measurements will take ages.
This is also a good point to inspect the CSV by eyeballing for correctness. Do you see slowly increasing wattages? And no 0 values?