Same here - it’s popping offline and back constantly.
Hi I just purchased the WiFi module and installed it but I’m having an issue with the toggle switch in home assistant not updating. As you can see in the screenshot, the sensor detects the fireplace flame is on but the fireplace flame toggle switch is still off, so I have no way of turning it off from home assistant. In the Intellifire app it does show that the flame is on and I can toggle it off.
The “ECM Offline” (“3269”) does need to have the ECM (Electronic Control Module) inside your fireplace power cycled in order to clear out. Are you doing that and it is coming back or is it just not reporting for some of these intervals?
Sometimes it works… sometimes it just doesnt seem to come back online…
@GarrettKranz Is there currently an HTT server outage? My appliance disappeared from the Intellifire iOS app, I cannot log in to iftapi.net, and my Home Assistant integration isn’t working. Anyone else experiencing this?
I was away for a couple of week, back now and updated HA. I now get these errors in the log. Control still works.
Logger: homeassistant
Source: components/sensor/init.py:901
First occurred: 2:42:41 PM (31 occurrences)
Last logged: 2:50:23 PM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 168, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 316, in _async_refresh
self.async_update_listeners()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 121, in async_update_listeners
update_callback()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 381, in _handle_coordinator_update
self.async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 556, in async_write_ha_state
self._async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 597, in _async_write_ha_state
state = self._stringify_state(available)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 562, in _stringify_state
if (state := self.state) is None:
File “/usr/src/homeassistant/homeassistant/components/sensor/init.py”, line 901, in state
raise ValueError(
ValueError: Sensor sensor.fireplace_timer_end has a state class and thus indicating it has a numeric value; however, it has the non-numeric device class: timestamp
Logger: homeassistant.helpers.entity
Source: components/sensor/init.py:901
First occurred: 2:45:23 PM (1 occurrences)
Last logged: 2:45:23 PM
Update for switch.fireplace_flame fails
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 538, in async_update_ha_state
await self.async_device_update()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 736, in async_device_update
raise exc
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 392, in async_update
await self.coordinator.async_request_refresh()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 175, in async_request_refresh
await self._debounced_refresh.async_call()
File “/usr/src/homeassistant/homeassistant/helpers/debounce.py”, line 82, in async_call
await task
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 201, in async_refresh
await self._async_refresh(log_failures=True)
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 316, in _async_refresh
self.async_update_listeners()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 121, in async_update_listeners
update_callback()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 381, in _handle_coordinator_update
self.async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 556, in async_write_ha_state
self._async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 597, in _async_write_ha_state
state = self._stringify_state(available)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 562, in _stringify_state
if (state := self.state) is None:
File “/usr/src/homeassistant/homeassistant/components/sensor/init.py”, line 901, in state
raise ValueError(
ValueError: Sensor sensor.fireplace_timer_end has a state class and thus indicating it has a numeric value; however, it has the non-numeric device class: timestamp
It’s on my todo list. Locally my on off switches aren’t updating status correctly. Maybe I can work on it at jury duty tomorrow
1 Like
Well I just shut down my HA server. Since Hubitat now connects directly to HomeKit (long time Hubitat user) I wanted to simplify my setup. The only thing left to do is install Intellifire code on Hubitat (today or tomorrow).
@jeeftor thank you for all work getting this working and seeding the Hubitat code!
Eventually there will be a cloud/local version of the code. It’s half written and has been that way for some time 
I’m just getting started with this code (not in HA per se). But when I try to connect to my fireplace and start the fire, I get a 403 error. I have logged in using the credentials I have with Intelllifire and get a valid API token back. But still, 403 from the fireplace (local API control). Am I missing a step?
#1 thing to do is see if you can hit:
I’m having tons of outages today btw…
Next thing you could try is: HHT Web Wifi Module Interface - user page
and see if you can navigate to the device.
And after that … let me know what happened… you may need to reboot the intellifire module.
For what its worth, I have to reboot my intellifire module at least weekly. It stays connected to wifi but loses connection with the intellifire app (and thus everything else) until I reboot it manually. Nothing to do with the HA integration as far as I can tell.
2023-02-10 10:42:05.487 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.fireplace_timer_end (<class 'homeassistant.components.intellifire.sensor.IntellifireSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+intellifire%22
2023-02-10 12:32:13.289 ERROR (MainThread) [homeassistant.components.intellifire] Error fetching intellifire data:
2023-02-10 12:38:43.289 ERROR (MainThread) [homeassistant.components.intellifire] Error fetching intellifire data:
2023-02-10 12:41:58.289 ERROR (MainThread) [homeassistant.components.intellifire] Error fetching intellifire data:
2023-02-10 12:44:28.133 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Fireplace A24DBBB7B0214461F6F1F68C5804A944' for intellifire integration not ready yet; Retrying in background
2023-02-10 12:49:13.375 ERROR (MainThread) [intellifire4py] Unhandled Exception <class 'asyncio.exceptions.TimeoutError'>
What behavior do you see in the Intellifire app when it’s not working? Can you tap the buttons but the fireplace doesn’t respond?
How do you reboot the module? Unplug the fireplace power cord and plug it back in?
Sometimes the fireplace disappears completely from the app. Most of the time, though, yes, I can tap the buttons but the fireplace doesnt respond. And the HA integration says unavailable. I usually pop the wifi module off, wait a couple seconds, then plug it back in. It reconnects to wifi and works correctly for a couple days until I have to do it again. Interestingly, though, according to my router, when it breaks, it doesn’t lose connection to wifi. So im not sure whats actually going wrong.
So → I think my IFT module might have blown up. I just went through the entire “Re-pairing” process and nothing. Doesn’t open a local access point and doesn’t connect to my network - isn’t detectable whatsoever… so ya’ll be a little on your own for now
Mine is too. Looks like its connected to wifi, but nothing is working in the app or otherwise 
I’m able to log in, navigate to the fireplace and turn it on via the web interface. After that, I was able to connect and send the beep command, but after that, now the REST API interface is hung and unresponsive. Poll and get_challenge don’t work now.
Crap, These things are a real letdown.
3 Likes
These modules are junk. I’ve been through 3 of them now in the past year. I opened the last one and there is a serial port (TTL) on it that was connectable, but since that module was bad (boot looping) I was unable to investigate any further. Anyone else having major issues with these things just completely biting the dust? It seems like the wifi chipset just dies in them completely and they won’t connect to wifi or broadcast their own SSID anymore.