I’m currently developing this binding and will be looking for beta testers soon. This Wi-Fi module is used in Majestic, Heat & Glo, Heatilator, Quadra-Fire, Vermont Castings, Monessen and SimpliFire fireplaces with the IFT-ECM and IFT-ACM modules. The IFT-WFM Wi-Fi module will work along side of the IFT-RFM and corresponding IFT-RC400 touchscreen remote control.
Let me know if you are interested in beta testing. Thanks.
I have an intellifire Heat & Glo fireplace with the wifi module installed. I would be interested in testing this.
I played around with the Python stuff that a person developed for Home Assistant and was able to get that connected to the fireplace, but I didn’t get it incorporated into my openHAB instance.
It allows you to connect to the fireplace and then control the flame, fan speed and light. It gets an api key from the intellifire cloud, but then it can control it locally without using the cloud connection. I’m including a couple of links that give information about it. When I first looked at it, I think there was some question about whether the api key needed to be refreshed occasionally. I don’t know how or if this was resolved.
On first sight, the python script was developed to work with HA and cannot be integrated into openHAB directly.
Sorry to say but I don‘t see a quick solution.
Great. I have a working beta version almost ready to share. My IDE just crashed. Once that I have that rebuilt and back online, I will share a JAR file for a test drive.
I set up a test OH system using OH 4.3 on an RPI 3. I dropped the intellifire jar file into my add-ons directory. After a reboot, the intellifire binding showed up and I created the intellifire bridge thing using. It then found 4 additional Intellifire things, the fan, the fireplace, the light and the remote. I would think the fan and the light would be channels in the fireplace, but that wasn’t the case.
I created items for all of the available channels. The fan and light things had one channel each. The fireplace and remote each had several channels.
Once everything was created, I was able start and stop the flame, adjust the flame height, fan speed, and light intensity. The “error” text string also shows the same messages I see in the IOS app. When first started, it gives the 3 minute fan delay message. It also gives a message if the fireplace is offline.
The thing properties list the IP address and the API Key, among other things. I was hoping that the binding would use local communication once it had the API key, but it didn’t. I tested it by disconnecting my router from the internet. With the internet disconnected, the things lost the fireplace IP address and the API key, even though it was still connected locally which verified by pinging the fireplace from my laptop. When I reconnected the router to the internet, the things eventually recovered the IP address and API key. I checked the API key to see if it had changed, but it remained the same.
Also, with the internet disconnected, the things status showed them as online. When I tried to turn on the flame, the fireplace thing status would switch to offline, and then back to online when the start switch returned to the off position.