Hello, thx for answering.
I followed this guide:
it asks me for the client id and refresh token but following the guide I don’t get them
Sorry but are this post and the one I linked are two different things?
I got the same error, and can’t make it work since april… i tried to restart, reinstall and no change hope someone can help us :s
Maybe this helps. After a while I found out that the stove wasn’t in the DHCP list of my router. I restarted the router and then the stove was visable. The strange thing is that I can’t ping the device for sone reason, but it’s working now.
i think you’ve right. in the mind i can’t configure wifi as it doesn’t recognize my wifi… so i can’t add it. Don’t know how to do, the mind is pure pain to make it works
If you mean the app, I agree. But if the integration in HA runs fine you don’t need it.
yep the app, so i managed to make it works again.
You’ve right my pellet wans’t recognize by the dhcp, i had to add it to the wifi with the app THE MIND. ( tooks me approx 35X try to do it). Once I can see it in the DHCP, i can control it again with HA. So for everyone with this type of error check if you’re stove is still on the network and good luck. 
Thanks a lot for your tips alexkoel.
Like GerAtDronten I’m controlling the Stove with scenes. I only got this in my automation trace.
I have an idea that it’s caused by the relax-mode setting. Off course I’m not sure. Is there a way to debug this? With debug logging on the integration I can’t see what’s going wrong. My stove, slide2 7 up, supports relax mode. If I’m controlling relax-mode direct from the automation it works. Any ideas?
Hi i have a pelkamin10 witj wifi routers.
Can you send me the link to integrates to my ha
?
I have found ha integration but it s for the mind app.
Here i use the wi fire.
Thanks gregory from belgium 
Hello Ger,
I’am new here and I use your integration for my new Nara II plus Up. Everything works fine exept one thing. There is only one fan showing up even after several new install’s and the stove is hot.
The first time after the install the fan was named fan 3 and fan 1 didn’t show up. After de-installation and re-installation the fan is named 2.
When I use the switch in HA the fan is switched off and on again. But only fan 2.
The strange thing is that the fan is named in HA Fan 2. But in The Mind app that fan is named Fan 3. Fan 1 is not showing. Fan 3 is the fan for the canalisation.
I’ve taken a look in your python code in the fan part but I don’t understand enough from Python to fix it.
Is it possible to help me out?
Regards,
Martin
Hi
lately, right after starting my Celia AirThight C+ I had to open the front door.
This, of course, triggered an alarm. The error code was 11, which means Door Opened.
Unfortunately, this error code was unknown in the Edilkamin integration which made my stove behaved erratically. I was able to start it but unable to get any status.
I finally solved this issue by changing the code in strings.py:
# TODO : find other alarm codes
ALARMSTATE = {
0: "None",
1: "Unknown code 1",
2: "Unknown code 2",
3: "Pellet End",
4: "Failed Ignition",
11: "Door Opened",
21: "Power Outage"
}
Problem solved. I guess this can be added to the integration.
Thanx
Hi Martin,
Sorry I missed your post, for some reason I do not get a popup or message.
Yes I know what you mean with fan 2 and 3, I experience some times the same issue
Check in the settings of Edilkamin with the remote if you have 2 fans setted.
Then, in home assistant you need to reload the integration also some now and then, today I found out an automation that does this automatically
Also bare in mind that fan 2 will only get visible when the stove has reached the setted temperature, you can also set that in the settings
If a fan starts when stove is still cold it is not convenient…
I had it sometimes as well but playing around in the settings, reload the integration, set the temperature low for the fans in order you can start them earlier if you want to, restart the stove with the switch 230v on the back, etcetera
Hope this helps
Hi,
First of all, thanks a lot for all the work, the custom integration has been working fine for months
@Nuick, I created a PR in your repo to add pellet reserve status and autonomy time. Also fixed some deprecation warnings we had in the logs. It’s working fine on my setup, feel free to test it and merge the code if it’s OK for you.
Autonomy timer defaults to 2100 seconds, and starts decreasing once the tank is in reserve (see screenshot below).
–
Bart
Hi,
Great work.
Can you share your design please?
Hi,
Sure, I’m using mushroom, generic thermostat and simple-thermostat cards for the layout. It’s the generic thermostat that controls the stove on/off, with a zigbee temperature sensor, since I didn’t find the edilkamin remote reliable enough.
Here’s the yaml code :
- theme: Backend-selected
title: Chauffage
path: chauffage
badges: []
cards:
- type: custom:mushroom-chips-card
chips:
- type: back
- type: thermostat
entity: climate.thermostat_poele
- type: custom:simple-thermostat
entity: climate.pellkamin
header:
name: Pellkamin
layout:
step: row
mode:
names: true
icons: true
headings: false
control:
- hvac
- preset
- fan
- type: horizontal-stack
cards:
- type: custom:mushroom-entity-card
entity: sensor.pellkamin_state
icon: mdi:state-machine
name: Status
- type: custom:mushroom-entity-card
entity: sensor.pellkamin_actual_power
icon: mdi:fire-circle
icon_color: red
name: Power
- type: horizontal-stack
cards:
- type: custom:mushroom-entity-card
entity: sensor.pellkamin_fan_actual_speed
name: Fan Speed
icon: mdi:wind-power
icon_color: light-blue
- type: custom:mushroom-fan-card
entity: fan.pellkamin_fan_2
name: Fan 2 Speed
- type: horizontal-stack
cards:
- type: custom:mushroom-template-card
primary: >-
{% if is_state('binary_sensor.pellkamin_pellet_in_reserve','off')
%}
OK
{% elif
is_state('binary_sensor.pellkamin_pellet_in_reserve','on')%}
Reserve
{% else %}
unknown
{% endif %}
secondary: ''
icon: >-
{% if is_state('binary_sensor.pellkamin_pellet_in_reserve','off')
%}
mdi:storage-tank
{% elif
is_state('binary_sensor.pellkamin_pellet_in_reserve','on')%}
mdi:storage-tank-outline
{% endif %}
entity: binary_sensor.pellkamin_pellet_in_reserve
icon_color: >-
{% if is_state('binary_sensor.pellkamin_pellet_in_reserve','off')
%}
green
{% elif
is_state('binary_sensor.pellkamin_pellet_in_reserve','on')%}
red
{% endif %}
- type: custom:mushroom-template-card
entity: sensor.pellkamin_autonomy_time
primary: Autonomie
secondary: '{{ states(''sensor.pellkamin_autonomy_time'') }}'
icon: mdi:timelapse
icon_color: |-
{% if is_state('sensor.pellkamin_autonomy_time','2100') %}
green
{% else %}
orange
{% endif %}
- type: horizontal-stack
cards:
- type: custom:mushroom-entity-card
entity: sensor.pellkamin_alarm_state
name: Active Alarm
icon: mdi:bell-alert
card_mod:
style: |
ha-state-icon {
{% if is_state('sensor.pellkamin_alarm_state','None') %}
color:green;
{% else %}
color:red;
{% endif %}
}
secondary_info: state
- type: custom:mushroom-entity-card
entity: sensor.pellkamin_last_alarm
name: Last Alarm
secondary_info: state
For the background, I use this: GitHub - basnijholt/lovelace-ios-dark-mode-theme: 🏠🤖 Theme by @basnijholt based on iOS Dark Mode for Lovelace Home Assistant
Thanks it’s great.
I miss some sensor.
sensor.pellkamin_state
sensor.pellkamin_actual_power
sensor.pellkamin_fan_actual_speed
fan.pellkamin_fan_2
And i think those are missing without your PR
binary_sensor.pellkamin_pellet_in_reserve
sensor.pellkamin_autonomy_time
I don’t know if it’s available on mine.
I would have thought that state, actual_power and fan_actual_speed would be available for all models.
For fan_2, your model needs to have this installed and activated (mine is a Pellkamin 10 EVO plus).
Same for the pellet reserve sensor, it needs to be installed on the stove, and then activated with the remote.
You can add the code manually in the custom_components folder (and then restart HA) to have the new sensors. My files are here : GitHub - bartelemby/ha-edilkamin at update_edilkamin_integration
Except for the reserve, i do not have sensor for fan speed, state and power.
They’re attribute from climate.pellets
Maybe i need to make a template for them
Yep you’re right, my bad, I set this up a while ago, I indeed created template sensor for those:
# Pellkamin current status
- name: pellkamin_state
state: >
{{ state_attr('climate.pellkamin', 'operational_phase') }}
# Pellkamin current power
- name: pellkamin_actual_power
state: >
{{ state_attr('climate.pellkamin', 'actual_power') }}
# Pellkamin current fan speed
- name: pellkamin_fan_actual_speed
state: >
{{ state_attr('climate.pellkamin', 'fan_actual_speed') }}
Reserve sensor will be there with the new code, if it’s activated on your device.
Do you know how to activate?
Technician credentials needed?
Yes if the pellet level sensor is installed on your device, it needs to be set to ‘on’ in the technician settings, then it will appear in the user settings, and you can turn it on (setting 14 on mine).
But if it’s set to ‘on’ and the level sensor is not connected, the stove will think it’s empty, and won’t start. That’s what happened to mine, it was set to ‘on’, but the sensor hadn’t been installed at first, they had to order it and came back to set it up and connect it to the motherboard.