We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2023.6.0
Kamstrup Omnipower (DK-8660) Pow-K+ (amsleser.no, 2.2.21) MQTT payload (HomeAssistant) Mosquitto broker (6.2.1) AmsHan addon (2023.6.0)
Current month peak 3 always "unknown" despite tariff peaks display correct values.
name: Current month peak 3 state_topic: amsleser/realtime unique_id: ams-xxxx_peaks3 object_id: ams-xxxx_peaks3 unit_of_measurement: kWh value_template: '{{ value_json.peaks[3] | is_defined }}' device: identifiers: - ams-xxxx name: AMS reader model: Pow-K+ sw_version: v2.2.21 manufacturer: amsleser.no configuration_url: http://ams-xxxx.local/ device_class: energy platform: mqtt
Received 15:43:32 QoS: 0 Payload: max: 3 peaks: - 3.57 - 2.45 - 3.06 threshold: 5 hour: use: 1.38 cost: 0 produced: 0 income: 0 day: use: 21.9 cost: 0 produced: 0 income: 0 month: use: 63.5 cost: 0 produced: 0 income:
The text was updated successfully, but these errors were encountered:
Looks like the index is wrong here value_json.peaks[3] It should be 2 for the third peak (0,1,2 not 1,2,3)
value_json.peaks[3]
Sorry, something went wrong.
No branches or pull requests
Version of the custom_component
2023.6.0
Configuration
Describe the bug
Current month peak 3 always "unknown" despite tariff peaks display correct values.
Debug log
The text was updated successfully, but these errors were encountered: