The maintainer is very overworked and doesn’t always have time 
1 Like
But the simple answer is to see if you can get to the IFT website. It’s in the docs I think. Lemme know what doesn’t work vs that website
Hi!
Ok, I have some additional details for you – I’m going to err on the side of providing too much information, rather than accidentally leaving out a detail that I don’t realize is important (is there a more sensible way to do this than a very long post in a public forum?)
-
When I originally set up the integration, it did not show up with an “entities” at all. After poking around a bit in error messages, I noticed that the core.config_entries file didn’t include an IP address for the fireplace (that field was blank). I found the IP address using my wireless router, and added that in there, and that was how I was able to get some things working. I’m not sure this is relevant to the current issue (it’s more in the nature of a solved problem, I guess), but I’m including it here in case it does matter.
-
I also noticed immediately that some of the entities that were then present were clearly not relevant for an electric fireplace – such as a pilot light. I disabled both the pilot light control and the associated sensor just to clean up the dashboard card. I can’t imagine that this is relevant to my current problem either – but I include the information just in case.
-
I have successfully navigated to the website I think you must mean (titled “HHT Fireplace Server/Wifi Module Interface”). It’s also fairly obvious from here that the functioning assumes a different type of device than what I have, and not everything quite maps correctly.
-
It seems like toggling the “burner” turns on/off both the heater and the “fake fire” (an animation of a fire displayed on a screen). Toggling “cold climate” to 1 will turn off the heat without changing the display, and will prevent you from changing the flame height. Once you toggle it back to 0, that doesn’t restore the heat immediately but allows you to turn it back on via the flame height control. The flame height control works, but only 0 and 1 work as expected, which I think is because my device doesn’t allow for fine control of heat (only “on” and “off”). The light control seems to work as expected (though the HA integration doesn’t let me do anything more than on or off here, and the website lets me change the brightness).
-
I didn’t experiment with either the “soft reset” or the “factory reset”, but did note that the firmware version listed was 0.3.2. Check update didn’t do anything, perhaps because there is no available update. Neither “beep” nor “ping” appeared to do anything, though I’m not sure where I should be looking for the “ping” to show up (I checked the HA logs as well as the activity log for the integration).
-
There is also a row labeled “fan speed”, with five apparent options (0-4). However, clicking on them does nothing, as far as I can tell – there isn’t actually a way to set the fan speed on my electric fireplace using the remote or the app, so I’m assuming this is a feature, like the pilot light, that simply doesn’t exist for me.
-
There are two rows for “thermostat” – apparently one that turns it on and off, and one that sets the value. The row that turns it on and off doesn’t actually have any way to directly change its value (there’s no toggle button next to it). However, it’s value does change when I turn the thermostat on or off in some other way. The setpoint does allow an input, but it’s behavior is odd. When I first enter a value, this doesn’t actually change the value – it just turns the thermostat on. But if I enter a second value, that does change the value. Also interesting is that if I enter the value “0”, instead of changing the setpoint value, that turns the thermostat off. (The behavior of the “timer” rows appears to be similar – except that in the HA integration, there doesn’t seem to be a way to attempt to control the timer, though there are sensors associated with it.)
One last thing that might be relevant to the thermostat issue: when I clicked “refresh now” at the bottom, I noticed the server response had two separate fields, one labeled “thermostat” and one labeled “feature_thermostat”. As far as I can tell, it’s the first of these whose data correlates with the actual thermostat (and immediately after it is a “setpoint” value that also seems to make sense).
Anyways, I’m hoping some of this very long post has information that might help!
Thanks,
Nelia
Are you using an Inception Electric Fireplace by chance? If so, we never really did collaborate with @jeeftor to support this use case. The gas fireplaces using the IFT-WFM, yes those are supported. The Inception uses an onboard Intel NUC mini PC and custom software.
It relies on the same IntelliFire API, but uses it uniquely (ex: Pilot is used to turn on/off its heater, Height is not used, and Power “0, 1 or 2” levels denote whether the screen is OFF (“1”), ON LOGS ONLY (“1”), or FLAME ON (“2”). Our gas fireplaces only use 0 or 1 for OFF/ON.
I’m not sure if @jeeftor plans to work on the integration again anytime soon, but we’re in touch and could help differentiate these different products / fuel types if that is something he wants to take on. Hope this is helpful info to you!
Thanks for these kind words. Looks like you got our most recent WFM version as well, which is great. Did the IFT-WFM you ordered come with our updated ECM? This is helpful to avoid an issue some folks run into with “ECM Offline” behavior. The sticker beneath the IFT-WFM would indicate “FW 2.1.9” if it is the latest. We’re shipping all IFT-WFM with this updated ECM until it gets cut into our manufacturing lines late this year.
Yep, this was something I wanted to do away with. We do use it when you re-install a fireplace onto the same location or if using multiple fireplaces in one location. It is HTTPS encrypted, but I’d still like to see it removed in the future. TBD on when we get around to it.
The Inception uses an onboard Intel NUC mini PC and custom software.
There is an entire PC on the fireplace?
I’m happy to work on the API for electric… and/or work with somebody else if they want to help!
I REALLY REALLY want to make improvements to the integration → I just have too many kids and not enough free time to ever get ahead of stuff…
Yep! An interesting product for us for sure, entirely developed in house.
Interesting… do you guys want to have joint ownership on the plugin repo any time (let me know). Or we can talk about supporting the NUC setup at some point
My HACS integration looks broken with the latest HA updates FYI. A couple of errors, including:
Logger: homeassistant.config_entries
Source: config_entries.py:730
First occurred: 5:02:34 PM (3 occurrences)
Last logged: 5:02:34 PM
Error importing platform config_flow from integration intellifire_hacs to set up intellifire_hacs configuration entry: cannot import name ‘DhcpServiceInfo’ from ‘homeassistant.components.dhcp’ (/usr/src/homeassistant/homeassistant/components/dhcp/init.py)
Logger: homeassistant.util.loop
Source: util/loop.py:77
First occurred: 5:02:34 PM (1 occurrence)
Last logged: 5:02:34 PM
Detected blocking call to import_module with args (‘custom_components.intellifire_hacs.config_flow’,) in /usr/src/homeassistant/homeassistant/loader.py, line 1307: return importlib.import_module(f"{self.pkg_path}.{platform_name}“) inside the event loop; This is causing stability issues. Please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 229, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 215, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 289, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, *self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 928, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 672, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 728, in __async_setup_with_context await integration.async_get_platform(“config_flow”) File “/usr/src/homeassistant/homeassistant/loader.py”, line 1111, in async_get_platform platforms = await self.async_get_platforms((platform_name,)) File “/usr/src/homeassistant/homeassistant/loader.py”, line 1176, in async_get_platforms platforms.update(self._load_platforms(platform_names)) File “/usr/src/homeassistant/homeassistant/loader.py”, line 1101, in _load_platforms platform_name: self._load_platform(platform_name) File “/usr/src/homeassistant/homeassistant/loader.py”, line 1275, in _load_platform cache[full_name] = self._import_platform(platform_name) File “/usr/src/homeassistant/homeassistant/loader.py”, line 1307, in _import_platform return importlib.import_module(f”{self.pkg_path}.{platform_name}")
I am hoping this is an easy fix? I’m not really competent on the coding end but would be happy to test anyone’s potential solution.
@GarrettKranz - is this a legit bug?
I reported it and the change does fix the issue–I’m sure someone must be running into it assuming they have both the module and the RC400 remote and even use this functionality.
Left a comment over on GH! Thanks @xags for mentioning this.
@jeeftor this looks like DhcpServiceInfo no longer exists. Perhaps related to @homeontherocks HA version?
I actually made updates today and pushed various PRs out!! 
@homeontherocks → I really haven’t touched the HACS version in a while. If I recall yours only worked on local control is that right? I did submit a PR to HA today for local control → however it’s about 2-3 PRs deep so I left in draft for the moment.
- feat: version bump intellifire by jeeftor · Pull Request #162659 · home-assistant/core · GitHub
- feat: Add options flow for IntelliFire read/control mode configuration by jeeftor · Pull Request #162667 · home-assistant/core · GitHub (This is yours HomeonTherocks)
- Feature/intellifire double poll by jeeftor · Pull Request #162670 · home-assistant/core · GitHub
Regarding HACS → I’m a little afraid to open it up since it’s YEARS old… but → “maybe” I can just push a new version over to HACS. @homeontherocks → but remind me again you are local only right? (My system seems to be balking at local control today - however - I do have an instance of HA running so maybe adding a 2nd instance is spamming it today)
1 Like
This is awesome! Thank you! No I can use both local and cloud but have found cloud to be much more reliable (albeit slower) than local. Let me know what I should do if you’d like me to test. Last we talked HA was sitting on your core submissions for over a year, which is why we were living in HACS.
Hey Garrett,
I haven’t looked here in a bit because everything works pretty flawlessly. One time in December, I had the ECM offline error in the Intellifire app and had to power-cycle the ECM. It just happened again. So that’s 2 times in almost 4 months, not too bad. Power-cycle fixed it again.
Looks like my ECM is 2.1.2, is there anything I can do about this? I bought the IFT-ACM also to use the fan I installed which has been working great. I thought it was maybe that causing havoc but seems you might know what’s going on.
Yeah, we’ve still yet to truly understand why some people get it frequently (~weekly) and others sporadically like yourself. Power cycling will always for some period of time resolve an ECM Offline, but it will also always re-occur at some point.
Version 2.1.2 was a super common production version. We can help you get a new ECM that is version 2.1.9, which resolves the “ECM Offline” behavior entirely. This would require you swap the ECM yourself, but we have a printed manual/YouTube video you could reference to do it.
To get started on this, you’ll want to grab the serial number off your fireplace (should start with “LC” or “MP”) and then get in touch with us at [email protected]. We’ll also need a mailing address to ship the new ECM to.
@homeontherocks - I’m screen capturing your post here and putting it in my PR
@GarrettKranz → Lets talk in the near future about how I can update the code to support these NUC based fireplaces that have an entire computer in them!
Mine does this occasionally.
To the point where I put a Zooz Zen 04 inline with the unit. That way when it’s offline, I can just turn off the power without having to pull the façade off and get on my knees to unplug it.
I’m officially an old fart. Getting on my knees sucks.