Replies: 2 comments 23 replies
-
Yes, I was mistaken. All profiles are initialized on startup and loaded in memory to prevent constant unneccesary file I/O
Auto discovery should just work also for custom profiles.
The manufacturer and model list should be limited to only profiles which match possible device types for your selected entity.
I have found PR where the local loader was overhauled and this was implemented: |
Beta Was this translation helpful? Give feedback.
-
Let me ask you over there: Asking because during testing I found, that
the profile looks like this: {
"measure_description": "The measured device fw: 1.14.1-rc1, Eco Mode enabled, Wifi Client enabled, LED disabled. The result represents the average value of measurements collected from the measurement device API for the following scenarios: dumb device/baseline consumption (~4.9W), the the relay turned off, and the relay turned on.",
"measure_method": "manual",
"measure_device": "Shelly PM Mini gen3",
"measure_device_firmware": "20241011-114503/1.4.4-g6d2a586",
"measure_settings": {
"SAMPLE_COUNT": 120,
"SLEEP_TIME": 1
},
"name": "Shelly 1PM",
"aliases": [
"SHSW-PM"
],
"discovery_by": "entity",
"device_type": "smart_switch",
"only_self_usage": true,
"calculation_strategy": "fixed",
"standby_power": 0.739,
"standby_power_on": 1.0,
"sensor_config": {
"power_sensor_naming": "{} Device Power",
"energy_sensor_naming": "{} Device Energy"
},
"created_at": "2024-01-03T00:00:00 CET",
"author": "Michal Bartak <[email protected]>"
} |
Beta Was this translation helpful? Give feedback.
-
I updated Powercalc to v1.17.0 beta4.
I uploaded newly created profiles to
config/powercalc/profiles
location to test new shelly profiles (this path didn't exist before)with regards
Beta Was this translation helpful? Give feedback.
All reactions