Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request device support] Elko thermostat #1291

Closed
Gaute64Bit opened this issue Feb 22, 2019 · 38 comments
Closed

[Request device support] Elko thermostat #1291

Gaute64Bit opened this issue Feb 22, 2019 · 38 comments

Comments

@Gaute64Bit
Copy link

@Gaute64Bit Gaute64Bit commented Feb 22, 2019

ELKO Thermostat
http://proff.elko.no/elko-smart-home-super-termostat/esh-plus-super-tr-rf-ph-article2629-1779.html

Need support for reading local temp and setting Heating (and cooling?) Setpoint.

image

image

image

image

Contact me if more infor is required.

@epiespen
Copy link

@epiespen epiespen commented Jun 10, 2019

Yes, a big +1 here. Kinda dissappointed there were no support for this.

@avassdal
Copy link

@avassdal avassdal commented Jul 7, 2019

+1

2 similar comments
@thomas70
Copy link

@thomas70 thomas70 commented Jul 30, 2019

+1

@Haalandi
Copy link

@Haalandi Haalandi commented Aug 6, 2019

+1

@t112013
Copy link

@t112013 t112013 commented Sep 25, 2019

oh yes please. this is very much needed :D

@epiespen
Copy link

@epiespen epiespen commented Oct 17, 2019

Is there any way we can add this our self and make a pull request? If other thermostats are supported, I'm sure we could use those as a template for this one. Any tips would be greatly appreciated @manup @ChrisHae @ebaauw

@dreuf83
Copy link

@dreuf83 dreuf83 commented Oct 23, 2019

Making a +1 on this and hope that someone with the knowledge sees it :)

@ricmik
Copy link

@ricmik ricmik commented Oct 23, 2019

This would be really nice to have implemented. Even though I do not own any Elko RF thermostats at the moment, I would probably upgrade my non-RF thermostats is there was support for them in Deconz. Is there any chance to implement support for the Elko thermostats in Deconz @manup @ebaauw ? Elko is kind of the de facto standard for electrical installation in Norway.

@jyrki69
Copy link

@jyrki69 jyrki69 commented Nov 5, 2019

+1
Would really appreciate support for Elko Thermostats. Let me know if I can help in any way.

@epiespen
Copy link

@epiespen epiespen commented Nov 5, 2019

@ma-ca Is this what you need in reference to #2009 ?

image

image

@t112013
Copy link

@t112013 t112013 commented Nov 6, 2019

Plsss someone be kind and fix it :)

ma-ca added a commit to ma-ca/deconz-rest-plugin that referenced this issue Nov 7, 2019
@eidsaa
Copy link

@eidsaa eidsaa commented Nov 19, 2019

Hi

There are several more vendor specific attributes, such as floor temperature, child lock, heating on/off etc. In the link below there is a list showing vendor specific attributes.

https://github.com/prj84/com.Elko/blob/master/drivers/ESHSUPERTR/ST_Code/Elko%20Thermostat%20-%20Vendor%20Specific%20attributes.txt

@ricmik
Copy link

@ricmik ricmik commented Nov 19, 2019

@eidsaa Maybe Elko will be helpful and give you a specification for the vendor specific attributes if you contact them?

@eidsaa
Copy link

@eidsaa eidsaa commented Nov 19, 2019

@ricmik Yes, it could be. The linked text file list both clusters and encoding. I've implemented floor temp, room temp, child lock and heating on/off in my local ZCL.xml-file. This gives me ability to read and set values from deconz-gui, but not through the REST

@corvy
Copy link

@corvy corvy commented Nov 21, 2019

What needs to be done to get this accessible via REST?

@epiespen
Copy link

@epiespen epiespen commented Nov 22, 2019

This is released now, right? How do I even add thermostats in Phoscon?

@corvy
Copy link

@corvy corvy commented Nov 22, 2019

It will probably only work in the old web interface. But I do not get it there even if I have it added and it shows in VNC. Have also tried reading the node info to see if that works but I see nothing.

@corvy
Copy link

@corvy corvy commented Nov 22, 2019

Phoscon is closed source development.... Sadly.

@eidsaa
Copy link

@eidsaa eidsaa commented Nov 26, 2019

What needs to be done to get this accessible via REST?

After the last update, its possible to read and set name, setpoint, etc. through REST.

@epiespen
Copy link

@epiespen epiespen commented Nov 26, 2019

Ok, so there's still no simple way to get this thermostat working in Home Assistant?

@eidsaa
Copy link

@eidsaa eidsaa commented Nov 26, 2019

I dont think so, Im using Node-RED to send messages and commands between deconz and domoticz.

@corvy
Copy link

@corvy corvy commented Nov 27, 2019

It should be possible to get it in Home Assistant but you would need to use REST API to get it, and to set values etc. I just polled with REST now and get the thermostat like this:

{
"config": {
"heatsetpoint": null,
"offset": 0,
"on": true,
"reachable": false,
"scheduler": null,
"scheduleron": null
},
"ep": 1,
"etag": "ee228d7305c3644d519311c652db9033",
"manufacturername": "Heiman",
"modelid": "Super TR",
"name": "Thermostat 25",
"state": {
"lastupdated": "2019-11-21T05:55:05",
"on": false,
"temperature": 1950
},
"type": "ZHAThermostat",
"uniqueid": "00:0d:6f:00:0f:41:45:3a-01-0201"
}

To find it just connect over a REST client like this:

curl -X GET -i 'http://:40850/api//sensors/'

Just omit the part to list all sensors, then find the ID for this one. You can poll and set states etc. More information on REST here:
https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/

I might write a guide to add it to HA in a week or two... :)

@ricmik
Copy link

@ricmik ricmik commented Nov 27, 2019

How about creating a request to add support for thermostats in the DeCONZ integration on the home assistant repository?

@corvy
Copy link

@corvy corvy commented Nov 30, 2019

Yes I agree @ricmik but I have not investigated that option right now.

Just put the thermostat into HA with REST API:

Screenshot 2019-11-30 09 56 19

Configuration in configuration.yaml:

sensor:

  • platform: rest
    resource: http://:40850/api//sensors/

Create a new sensor section or append to your existing. Replace IP and key and sensor number with your setup. Remember you must setup deconz REST API first: https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/

@dreuf83
Copy link

@dreuf83 dreuf83 commented Jan 2, 2020

It looks like the only temperature reading the thermostat is sending is the airtemp. I have my thermostat outside of the bathroom with a floor tempsensor. Is it possible to include it to read the floortemp?

0x409 (encoding:29 value:
0x403 (encoding:30, value: <verified 00=airsensor, 01=floorsensor, 03=gulv vakt (max temp on the floor>
0x408 (encoding:21 value: floating values ex: 001a, 01a9, 01dd, 0000, 0087 <- Average power consumption last 10 min.
0x415 (floating encoding:10, value: <verified heating active/inactive> 00=idle 01=heating

@prj84
Copy link

@prj84 prj84 commented Jan 6, 2020

LocalTemp attribute is always the Air measurement on this thermostat

0x409 attribute is always the floor temp

0x403 indicates witch sensor that is programed to be used against the setpoint temp on the thermostat itself.

I use the 0x403 attribute in a app I wrote for Athom Homey to show "correct" measured temp in the app, 00=Air, 01=floor, 03=floor guard>

0x415 attribute is just indicating if the heating is active or not. Not possible to override this (Of my knowing)

Power
0x408 - Reports average power usage last 10 minutes

Child Lock
0x413 - 00=unlocked 01=locked

@gbbirkisson
Copy link

@gbbirkisson gbbirkisson commented Jan 10, 2020

Hi,
I am not able to see the sensor in the REST API when I add the thermostat to the Deconz. I am wondering if you guys know what I am doing wrong.

Rest API Info:
curl core-deconz:40850/api/<key>/config | jq -r '.apiversion' -> 1.16.0
curl core-deconz:40850/api/<key>/config | jq -r '.swversion' -> 2.5.72

I add the thermostat by going to the Phoscon UI and doing add sensor and then make the Thermostat rejoin the Zigbee network. I can see the thermostat in the Deconz VNC view but it does not show up when I call: curl core-deconz:40850/api/<key>/sensors

Can someone point to what I am doing wrong? @corvy are those the steps you followed to make it show up in the API?

Edit: It now shows up in the REST api.

@chairman2s
Copy link

@chairman2s chairman2s commented Apr 28, 2020

Just got mine installed yesterday :) I am running HA and deconz. I added it and it appeared immediately in HA. But it only shows the air temp. not the floor temp. And I think there is some trouble setting the temperature and so on... So I vote for better support... What firmware version are you guys running? Mine has 1.2.5R

@oywino
Copy link

@oywino oywino commented Apr 28, 2020

Just put the thermostat into HA with REST API:
Configuration in configuration.yaml:

sensor:

  • platform: rest
    resource: http://:40850/api//sensors/

I can see the ELKO Thermostat in the deConz VNC interface, but I cannot see it in the REST API or in Phoscon or in HA (after updating the sensor: section). Can you please tell me how to get in touch with this "bugger" ?

@kojax-net
Copy link

@kojax-net kojax-net commented May 10, 2020

@ricmik Yes, it could be. The linked text file list both clusters and encoding. I've implemented floor temp, room temp, child lock and heating on/off in my local ZCL.xml-file. This gives me ability to read and set values from deconz-gui, but not through the REST

How did you implement these attributes? When I add these to zcl/general.xml under cluster 0201 I only get unsupported attribute.

<!-- ELKO manufacturer specific -->
<attribute-set id="0x400" description="ELKO">
    <attribute id="0x403" name="Sensing" type="enum8" default="0" access="r" required="o" mfcode="0x1002">
        <value name="Local temperature mode" value="0"></value>
        <value name="Floor temperature mode" value="1"></value>
        <value name="Floor max temperature mode" value="3"></value>
    </attribute>
    <attribute id="0x0409" name="Floor Temperature" type="s16" range="0x954d,0x7fff" access="r" required="o" mfcode="0x1002">
    </attribute>
    <attribute id="0x0415" name="Thermostat Running Mode" type="bool" default="0" access="r" required="o" mfcode="0x1002">
        <value name="Idle" value="0"></value>
        <value name="Heating" value="1"></value>
    </attribute>
</attribute-set>

@Offpiste84
Copy link

@Offpiste84 Offpiste84 commented May 23, 2020

How to get rele status?

@Mimiix
Copy link
Collaborator

@Mimiix Mimiix commented Jun 5, 2020

It seems this issue is inactive / resolved. If it is not, please re-open or create another issue!

@Offpiste84 If you have a specific question, please open another issue or ask it on Discord :)

@Mimiix Mimiix closed this as completed Jun 5, 2020
@corvy
Copy link

@corvy corvy commented Aug 5, 2020

Could we open this issue again to add the floor sensor temperature as-well?

From a developer of Homey I found that the floor sensor is attributt 0x409, but this does not show in REST. Local Temperature is always the air temperature. Would that be possible? @Mimiix

@Mimiix
Copy link
Collaborator

@Mimiix Mimiix commented Aug 6, 2020

@corvy I'd rather have a new device request for that.

@oywino
Copy link

@oywino oywino commented Aug 6, 2020

@corvy I'd rather have a new device request for that.

Why open yet another thread instead of having everything in one place?
It becomes impossible to gather all neccessary information when the discussion is split up into many independant threads.
What's the point?
This thread has an excellent headline - let's leave it alive until the problem is solved, please!

@Mimiix
Copy link
Collaborator

@Mimiix Mimiix commented Aug 6, 2020

@oywino I have to disagree. How i understand it, it is a floor sensor and slightly different. The title on this issue only suggests the thermostat.

As this is closed already, it doesn't make sense to re-open it because it doesn't comply no more with older changelogs. Having a new issue makes more sense.

Grouping stuff is easier then ungrouping in the end. And: What is the difference :)?

@corvy
Copy link

@corvy corvy commented Aug 6, 2020

Ok great, I will create a new one.

@oywino
Copy link

@oywino oywino commented Mar 23, 2021

My ELKO Super TR Thermostat keeps generating these log entries:

21:16:16:949 [INFO] - No button map for: Super TR, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0201, command: 0x0A, payload: 010421D007, zclSeq: 225      
21:16:16:949 ZCL attribute report 0x000D6F000E9DC646 for cluster: 0x0201, ep: 0x01, frame control: 0x08, mfcode: 0x0000                                      
21:16:18:957 [INFO] - No button map for: Super TR, unicast to: 0x0000, endpoint: 0x01, cluster: 0x0201, command: 0x0A, payload: 170428E4, zclSeq: 226        
21:16:18:957 ZCL attribute report 0x000D6F000E9DC646 for cluster: 0x0201, ep: 0x01, frame control: 0x08, mfcode: 0x0000

Does this mean that there is a mismatch somewhere in the button map file for this device?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests