Intellifire (Wifi Fireplace Module) - Hearth and Home

Share your Projects!
182

Yes, any control via HA will be better than what we have now. What’s the outlook for the official support in HA?

183

Yes, I’d be thrilled with “it kinda works” control in HA. Happy to report the results here. :+1:

184

Current PRs (some live some draft)

1 Like
185

Looks like there might be a holdup on this one:

Feel free to browse / comment :slight_smile:

1 Like
186

I’ve read through the github page conversation and don’t quite know what it all means, but hopefully you’ll be able to address their requests so that control is added. Thanks again for spending much of your personal time working on this!

187

I mean I can pull the forced updates and we just have to wait a while which means it’s less responsive.

188

So what I’m doing is forcibly updating the Home Assistant state after issuing a command. Apparently that’s not totally kosher and that should be hidden on the backend.

So my thought was like when I tell the fan to turn on it’ll update in Home Assistant of the fan is on rather than waiting for it to successfully query the unit and find out the fan is on

189

Makes sense. Control would be very nice to have now, even if the reported status takes a while to update.

Honestly, I’ll probably use voice control or a physical button with HA to turn the fireplace on and won’t even look at the status in that moment.

Plus, the Intellifire app is slow to show status updates for me as well, so I’m already used to that behavior :slight_smile:

190

I came here because I was trying to figure out why I was seeing messages about discovering an “Intellifire” in my logs. I have no such device. I wasn’t even trying to add your integration. I think it was triggered by some sort of home assistant discovery feature.

I have a Rheem heat pump water heater which is also built on the zentri platform, so it matches the hostname based on the "zentrios-*" glob you added.

Given that zentri os seems to be a general-purpose IoT platform, I imagine there are likely many more classes of devices that use it besides Intellifire fireplaces and Rheem hot water heaters.

I think you should remove that glob, or figure out a way to only use it when actually adding the integration.

191

Ok so updates:

  1. I need to fix the auto-detection (@mbbush) - I was dealing with some personal matters which took away all my extra coding time - should be able to work on stuff soon … we can look into removing this and/or just hiding the error message

  2. I’ve changed the code for power (on/off) to remove the fast updates - so we’ll get control it will just be very slow to update the state… (in the current PR right now)

2 Likes
192

It is doing a DHCP based discovery - to autodetect - and then tries to verify its an intellifire device. I “guess” the issue is maybe with the error reporting → I’m wondering if we could just make it an info/debug if it would go away. I think the auto-detect is great but its not 100% required I guess…

193

Can you actually post the log with the error message?

194

Ok guys first update is control is coming in next release (at least power on/off) - more features will eventually come.

I’m also working on a refactor of the backing lib to fix @mbbush’s issue hopefully.

Also the refactor will pre-update states prior to getting a poll return. Aka → send the on message and tell HA the fireplace is on → then query the fireplace to make sure we didn’t lie. I’m hoping this will be a worthwhile change - but if it ends up being a mistake I can always roll it out later

2 Likes
195

@mbbush - I have an open PR but I’ve started working on your issue

196

Anybody else get this notice? Wonder what they are changing…

Dear IntelliFire App User,

We are making upgrades to the IntelliFire app service. The ability to operate your fireplace or stove using the IntelliFire app and voice control will be periodically unavailable May 31, 6:00 a.m. to 10:00 a.m. (CDT).

During the maintenance time, please use other controls to run your gas fireplace or stove. We appreciate your patience.

— Hearth & Home Technologies IntelliFire App Team

197

Yup and it’s the perfect time to test out my no cloud local control im working on

1 Like
198

Just upgraded to 2022.6.0 and can turn it on and off!
This is great, I just need the lights and fan control before next winter (was 92 here yesterday). Thanks!!

Also has there been any progress on solving the hang issue?

1 Like
199

So I completely restricted how the library works to try to get the responsiveness up and there is a pull request in which will hopefully help out.

That being said → its still problematic.

What I basically did was:

  • Set up a loop that queries every 15 seconds the fire place state
  • Then we copy that state data and deliver it to HA - so if the querying times out the fireplace won’t go unavailable
  • When we send commands I STOP the polling (to reduce load on the fireplace) until the command can get sent
  • Once sent - update the local state (state you see in HA… aka if we send power on - tell HA the fireplace is on
  • Restart the querying of state loop

This in theory will make things more responsive.

This update also will store the local API credential locally - so if you are super anti-cloud you can only hit the cloud once.

I also have a Fan/Climate(thermostat) PR in queue to add once the v2 goes through.

After that its lights and maybe adding in support for cloud commands

200

It was flurries two days ago here in Colorado :snowflake:

201

I am seeing a lot of timeouts

Logger: homeassistant.components.intellifire
Source: helpers/update_coordinator.py:197
Integration: IntelliFire (documentation, issues)
First occurred: 9:09:01 AM (9 occurrences)
Last logged: 1:02:44 PM

Timeout fetching intellifire data