Its probably doable → I “think” - but - it really depends on seeing the API key … reading over the API I think its possible…
What does it report if not `ZentriOS-~ ?
The new wifi module doesn’t say ZentriOS- but instead just appears as blank or Unknown Device/Unnamed Device in my router’s device list. If I use an app like Fing it lists the device as “Generic.”
If I followed your instructions from post 101 in terminal on my mac and both commands appear to run but return nothing.
However, the good news is that the new wifi module has stayed connected the whole time and I haven’t seen a single “Error - Your appliance is currently offline” message in the app since installing it. Except for when their HTT server went down on Wednesday night.
How’s the new module working now that you have had it for a while? Any hangs?
It’s working great! It hasn’t gone offline even once! It’s a huge improvement over the old WiFi module that would go offline nearly every day.
However, sometimes in the Intellifire app I’ll tap a button and the fireplace won’t respond. If I go back a page and then return, the button is back to its original state as though I never toggled it. It usually works on the second try.
HTT told me that might be a problem they’ve been noticing with some ECM modules. They’re going to order a replacement to swap it out and see if that improves things.
That’s awesome. Thank you again! What changes are in the queue for the next release?
Right now I’m working though the API token config entry…
After that it really should be straight forward adding control.
Control elements get added type by type
On/Off switch for flame/pilot
Fan
Climate
Flame Height (selectable thing)
1 Like
OMG Jeef you have really made impressive progress on this integration! Thank you!!
I see on your “to do” list light control is listed. I would love to have on/off control of my LED lights via this integration. How is the progress on that? I have 3 different wireless modules each with LED lighting that I would be happy to help testing with if I can be of any use. Thank you again!
Working through this one now.
Last impediment to control
Currently I’m stuck on this very minor issue where when you load the integration it will prompt you to re-auth and ender credentials - and on the GUI its not displaying correctly:
This is what I want
This is what I’m getting:
And although it works → even though it doesn’t print the right stuff - I’d like it to work “correctly”
Anyhoo → I’ve fixed the current bugs so now we wait…
I was just thinking it would be nice to map;
Flame to a “sensor”
0=off
1=(flame height 0)
5=(Max height)
But maybe that will come in time… I expect some breaking changes in the near future (all for the best)
3 Likes
Well… nothing major has happened yet with my current PR (control credentials)… but I was also on vacation so hopefully we’ll move some stuff forward this week…
2 Likes
Can’t wait - getting tired of holding my breath with the beta control component every time i upgrade HA!
And so it begins…
2 Likes
For folks running the beta are you seeing any performance issues? I’m designed the backing library to maintain a connection and recreate it if it ever dropped… On my testing I’m seeing TONS of drops:
however this is on my dev server - haven’t tried on my main server so not sure if its something I should try to address.
I wonder if its related to the polling - because it looks like that 84 second data poll the connection was dropped during the entire time…
i haven’t noticed any, but i really just turn the thing on in the morning when i get up, and off a few hours later. so I’m not exactly stress testing it.
my “test box” is a 2011 iMac running ubuntu … my prod machine is a 2020 Pi4… 
I think the intellifire Apps actually use the cloud polling instead of local polling - which may be more reliable in some ways because it may only send updates on data changes - so I could look to implement that eventually …
On this topic, I’m having a lot of issues with the Intellifire app sending commands to the fireplace and showing the status reliably.
Justin, the developer from HHT, was back at my house on Wednesday and plugged my wifi module into his laptop to update the code on it. He also replaced the ECM. We talked about how the app communicates to the fireplace and to the HHT server. The app receives the fireplace status from the HHT server and that reporting delay often causes my app status and fireplace to be out of sync for a while.
For example, when I use the app to turn on the “lights,” the fireplace sometimes does not respond. Then I’ll turn the lights off and back on and after a few seconds, the fireplace will respond. But then the app takes a moment to refresh and show the current state.
I’m really looking forward to HA control so I can avoid the Intellifire app entirely.
So from what I gather there are two ways to get status:
- Local Polling (xxx.xxx.xxx.xxx/poll)
- Cloud Polling (seen via the iftapi.net webapp/mobile app)
My library has implemented the local polling version - but - like the mobile app it seems to be inconsistent …
My guess would be that the local delays/timeouts also get “forwarded” to the cloud as well and it displays a similar behavior. That being said if I recall in the API docs there is a provision for doing a “long poll” with an option to time-out.
I’m considering adding something to the lib with a way to say if a request times out don’t change the values and only error after 10 fails or something like that …
So I can’t say my implementation will avoid these issues either → but at the very least it will maybe make it more apparent what’s going on. If I had less kids and more free time I’d be happy to debug the ECM module myself but I don’t know when I’ll get to that unfortunately … so for now its mostly fixes and patches to make it “work ok”… 
Also if the user community is ok with “it kinda works” control then I can push on ahead - and as we identify “issues” like the communications drops we can work on those as well…
2 Likes
I’m more than ok with “it kinda works” control. That’s better than what i already had with the intellifire app itself.