Probably quite a niche integration, however, if you have an Evonic Fire in your home, then you’ll know that they have an E-Smart App that either uses their cloud API, or local connection to the fire.
I did some digging around, and found that the app simply loads in HTML pages from the webserver running on the device, which then communicates locally using WebSockets.
I’ve created a Custom Integration for Home Assistant, which creates a wrapper around the WebSocket connection to get your device control into HA.
I only have an Evonic Linnea, so that’s the only device I have been able to test this on, so if you have an Evonic Fire, please leave me some feedback on what works or doesn’t so we can investigate.
Right now it supports the following features:
Supports the following features:
It’s worth mentioning that this is my first Home Assistant Integration, as well as my first Python project, so if my code is a bit ropey, please bear with me. I only started learning Python a couple of weeks ago. I used WLED as a base line for this, so you may notice some similarities in the code
I’m pretty sure this happens when it cant send the request to the fire. I might need to figure out how to change this to polling instead. If you keep the WS open for too long, it just seems to die, but i dont know if thats the fire or my code
Hey, new to home assistant so sorry if this is a silly question, however getting an error " Repository greghesp/hacs-evonic not found" when trying to install?
Are you able to consistently replicate this, and are you on the latest firmware for the fireplace?
I’ve not had this issue recently, so wondering if they fixed something in the fires firmware.
Essentially, I think what is happening is that the websocket connection stops responding. I’ve tried logging everything out, but it never seems to actually kill the connection to the fireplace from what I can tell, so I can only assume it’s the fireplace firmware
this is working well with my fire (unsure of the model), thank you. I have two questions after setting it up:
To turn on the heater in the fire I first have to turn on the lights. Is this a limitation of how Evonics fireplaces are set up, or can it be overcome (my automations have failed so far!) Edit: This is an Evonics limit, but the heater entity can be programmatically enabled and disabled with Spook: https://spook.frenck.dev/ - setting up an automation to couple it with the fires lights means the enabled/disabled state in HA matches the state in the fire itself.
The light card for the fire allows me to select the effect/colors used. Is it possible to expose this element to the rest of the system? (context: HomeKit Bridge only sees an/off toggle)
Due to the way HA works, you can’t do something else before executing an action. Since the fire needs to be on before you can set the temperature, you will always need to ensure that it’s on first.
There also isn’t really an on/off for the fire themselves, as it’s actually just the lighting, hence why lighting is what you would consider the on/off switch.
As for the effects, I suspect there’s a way to handle this in Homekit. HA exposes effects as a toggle like it’s currently implemented, I’m not sure how this should work in Homekit
Not sure if you got this to work, but my e1030 works fine using an automation.
This one does a bunch of things when I have cheap electricty, but the 1st thing is to turn the fire lighting on, it then does some other (unrelated) stuff then toggles fire HVAC mode to heat.
Had no problems with this working (FrontRoom is my fire’s name BTW…!);
