# Escea Gas Fire Binding Investigation

**URL:** <https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896>\
**Category:** Bindings\
**Tags:** curl, heating, fire\
**Created:** [December 8, 2016, 9:12am UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896 "2016-12-08T09:12:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![wingers1290](https://community.openhab.org/user_avatar/community.openhab.org/wingers1290/32/12620_2.png) [@wingers1290](https://community.openhab.org/u/wingers1290)\
**Post date:** [December 8, 2016, 9:12am UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/1 "2016-12-08T09:12:47Z")

</div>

**Edit: 3/07/2017 - Removed as contains unpatched exploits**  
**Edit: 09/12/16 - Files removed at request of Escea**  
**Edit: 09/12/16 - Hashed values removed at request of Escea**

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [December 8, 2016, 4:44pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/2 "2016-12-08T16:44:48Z")

</div>

> [@wingers1290](#):
>
> Alternatively, is it possible to ask OpenHAB to make POST requests in rules…

You can.

> **[Actions](https://github.com/openhab/openhab1-addons/wiki/Actions#http-actions)**
>
> Add-ons for openHAB 1.x. Contribute to openhab/openhab1-addons development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![wingers1290](https://community.openhab.org/user_avatar/community.openhab.org/wingers1290/32/12620_2.png) [@wingers1290](https://community.openhab.org/u/wingers1290)\
**Post date:** [December 8, 2016, 7:15pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/4 "2016-12-08T19:15:41Z")

</div>

…that was quick!

Care to explain a little??

---

<div class="post-metadata">

**Author:** ![kubawolanin](https://community.openhab.org/user_avatar/community.openhab.org/kubawolanin/32/71363_2.png) [@kubawolanin](https://community.openhab.org/u/kubawolanin)\
**Post date:** [December 8, 2016, 7:22pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/5 "2016-12-08T19:22:22Z")

</div>

Sure!  
Just took these md5 hashes and pasted them in online [md5 decrypter](https://hashkiller.co.uk/md5-decrypter.aspx) I found in google 🙂

---

<div class="post-metadata">

**Author:** ![wingers1290](https://community.openhab.org/user_avatar/community.openhab.org/wingers1290/32/12620_2.png) [@wingers1290](https://community.openhab.org/u/wingers1290)\
**Post date:** [December 8, 2016, 7:33pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/6 "2016-12-08T19:33:23Z")

</div>

So they are straight MD5 hashes then? The code suggested they were being passed through a custom function, so I didn’t think to try that.

---

<div class="post-metadata">

**Author:** ![wingers1290](https://community.openhab.org/user_avatar/community.openhab.org/wingers1290/32/12620_2.png) [@wingers1290](https://community.openhab.org/u/wingers1290)\
**Post date:** [December 8, 2016, 10:17pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/7 "2016-12-08T22:17:37Z")

</div>

Just received these documents from the manufacturer - these will be incredibly useful.

[\* ESCEA Controller](https://drive.google.com/file/d/0B_DxF4ssjiwaMy1fRFZPeEk4Ynp1Sm5XUllDVmtsRVI3ejBn/view?usp=sharing)  
[\* ESCEA LAN Comms](https://drive.google.com/open?id=0B_DxF4ssjiwaN0FEYzVxMVEwNWVIVkJDZjJ3QXJrb0xHYndz)

I still maintain that there are security vulnerabilities here that could be easily addressed. Even if the protocols are designed to be open, that doesn’t mean that they should be open to unauthorized people.

I imagine the scenario when a household is on an external gas supply and everyone is away on vacation. An attacker could very easily gain unauthorized access, turn the fire on and accrue massive gas charges in addition to risking fire. Granted there is no financial benefit in this, but part of the problems of having Smart Homes is that screwing with people could become a motivation in itself.

Anyway, these documents should really help build a binding for the fireplace. Does anyone know of any resources OpenHAB has as a sort of introduction to building a binding? Would like to have a go if I can.

---

<div class="post-metadata">

**Author:** ![wingers1290](https://community.openhab.org/user_avatar/community.openhab.org/wingers1290/32/12620_2.png) [@wingers1290](https://community.openhab.org/u/wingers1290)\
**Post date:** [December 8, 2016, 10:48pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/8 "2016-12-08T22:48:17Z")

</div>

After looking at the MD5 script I realized that the MD5.js script is the same as this one I found online, which, as you discovered, simply hashed the strings with the MD5 algorithm.

> **[JavaScript MD5 | CSS-Tricks](https://css-tricks.com/snippets/javascript/javascript-md5/)**
>
> Like possibly snagging a Gravatar.

For some reason I thought they had defined a function called MD5 that did something else in addition to MD5 hashing it… Suppose Occam’s razor should have applied!

---

<div class="post-metadata">

**Author:** ![dastrix80](https://community.openhab.org/user_avatar/community.openhab.org/dastrix80/32/20582_2.png) [@dastrix80](https://community.openhab.org/u/dastrix80)\
**Post date:** [August 17, 2022, 11:27pm UTC](https://community.openhab.org/t/escea-gas-fire-binding-investigation/17896/9 "2022-08-17T23:27:48Z")

</div>

All, was a binding developed or is there a way to interface with OH ?
