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

[Device Support Request] Eurotronic Spirit ZigBee #1098

Closed
micha91 opened this issue Jan 7, 2019 · 518 comments
Closed

[Device Support Request] Eurotronic Spirit ZigBee #1098

micha91 opened this issue Jan 7, 2019 · 518 comments

Comments

@micha91
Copy link

micha91 commented Jan 7, 2019

Hi,

I just bought this thermostat device (on a random guess) to move away from other wireless protocols. I would love to see support for it in deCONZ. At the moment there is nearly no documentation for this device, but at least some clusters are recognised and it is possible to set the desired temperature using the attribute in the cluster.
Node Info
image
Basic Cluster:
image
Power Configuration:
image
Thermostat:
image

Thank you very much in advance

Michael

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 7, 2019

Interesting! Still looking for something like these, at a reasonable price.

Is it this one: https://eurotronic.org/produkte/zigbee-heizkoerperthermostat/spirit-zigbee/ ? Where did you buy it? I see Reichelt sells them for EUR 50,81.

Indeed, no Bedienungsanleitung for this device on their website. Did it come with a French/Spanish/Italian/Polish-only manual or also German and/or English? (I can read German, but I don't write it well).

The specs mention supported transitions (Schaltzeiten) per day/week, suggesting you can store a schedule on the device. Looking at the ZCL spec (6.3.2.2.3), there's an awful lot of more attributes in the 0x0201 cluster for this. I think first order of business is to add these to general.xml, as well as the commands to set/clear/get the schedule. I doubt if the deCONZ GUI can handle a variable number of parameters to the set schedule command, though.

@manup, modelling the schedules will be a nice challenge for the /devices endpoint.

@manup
Copy link
Member

manup commented Jan 7, 2019

Absolutely, guess the attributes should be added into new ResourceItems.

A colleague has bought the Eurotronic thermostat a few days ago and is also very keen to get support into deCONZ and homebridge-hue, we will do some sniffing to get more insights.

@micha91
Copy link
Author

micha91 commented Jan 7, 2019

Yes, it's exactly that one. I got it from voelkner via amazon for EUR 41.97. The printed manual only describes the installation/mounting and is available in german and english language. I hopped to see a little more of the protocol specification like in case of the zwave version: https://eurotronic.org/wp-content/uploads/2018/08/Spirit_Z-Wave_BAL_web_DE_view_V5.pdf

However, if I can provide some more logs, I will do my very best to do so, but at the moment I am very busy at work and do not want to shut my deCONZ installation down to get clear logs of the device before Thursday.

@Oliviakrkk
Copy link

I found info that it uses home automation profile 1.2 and presents itself as HVAC device...

Will this be tough and time consuming to implement? If you get this then deconz connected to home assistant may be the best zigbee solution on the market.

@ma-ca
Copy link
Contributor

ma-ca commented Jan 8, 2019

I would also like to get homebridge-hue to support the Thermostat Cluster.

The Thermostat Cluster 0x0201 is already supported with PR #1003.

Using the REST-API it is possible to change the heating temperature, get/set scheduler, turn on/off the scheduler, set offset.

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 8, 2019

@ma-ca, I will need some help with that. It's going to be challenging without a device to test.

The HomeKit Thermostat service requires the following characteristics:

  • CurrentHeatingCoolingState (read-only, values: Off, Heat, Cool) - I assume this is provided by state.on: false: Off; true: Heat?
  • TargetHeatingCoolingState (read/write, values: Off, Heat, Cool, Auto) - This should probably be mapped to config.scheduleron? Or should it be fixed to Auto and expose config.scheduleron as a separate switch?
  • CurrentTemperature (read-only, in 0.1°C) - This would be state.temperature?
  • TargetTemperature (read/write, in 0.1°C) - This would be config.heatsetpoint?

There's also an optional characteristic HeatingThresholdTemperature.

I wouldn't know how to expose the schedule - They haven’t reverse-engineered the interface for the Eve Thermo yet (see simont77/fakegato-history#11, simont77/fakegato-history#40), but I suppose you'd want to use deCONZ rules and/or HomeKit automations to set config.heatsetpoint?

@ma-ca
Copy link
Contributor

ma-ca commented Jan 9, 2019

@ebaauw I am glad that you are looking into this and I am happy to help.

CurrentHeatingCoolingState (read-only, values: Off, Heat, Cool) - I assume this is provided by state.on: false: Off; true: Heat?

Yes, the state.on:true corresponds to heat on. The cool is (currently) not implemented in the REST-API.

TargetHeatingCoolingState (read/write, values: Off, Heat, Cool, Auto) - This should probably be mapped to config.scheduleron? Or should it be fixed to Auto and expose config.scheduleron as a separate switch?

Perhaps yes. How is this property displayed in HomeKit and which command is associated? If this is associated to the Siri command turn off thermostat then indeed it would make sense to turn off the scheduler.

CurrentTemperature (read-only, in 0.1°C) - This would be state.temperature?

Yes. Currently the temperature value needs to be divided by 100 as defined in the Zigbee spec, for example state.temperature : 2150 is 21.5 °C.

TargetTemperature (read/write, in 0.1°C) - This would be config.heatsetpoint?

Yes, also needs to be divided by 100.

I would like to use HomeKit to set config.heatsetpoint and config.scheduleron. I don't see any benefit is in changing the scheduler from HomeKit, because after setting up the scheduler using the REST-API, there is no really need to change this.

In my use cases I would like to use HomeKit to

  • turn off the scheduler when leaving for holiday
  • and then being able to turn on again a day before returning home.
  • setting the temperature.

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 11, 2019

Please check out homebridge-hue v0.11.7.

@ma-ca
Copy link
Contributor

ma-ca commented Jan 11, 2019

Very nice. After installing homebridge-hue v0.11.7 the iOS Home App shows the Thermostat icons with temperature and heating value.

Changing the heating does change the config.heatsetpoint. Setting mode on or off does set config.scheduleron to true or false.

The only issue is that the displayed temperature seems to be rounded to 0.5 °C, but the thermostat display has 0.1°C resolution. For example the App shows 22.5 °C but display has 22.3 °C and the state.temperature is 2230. And the heating value has a random offset, for example 17.0 °C changes the config.heatsetpoint to 1710, value 17.5°C to 1770, value 18.0°C to 1800.

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 11, 2019

Can you please attach the debug log of homebridge-hue? And the dump file, just to be sure. See the README. Are you only using Apple’s Home app, or did you check other HomeKit apps. I think Home rounds the temperature to 0.5°C when displaying it. At least that’s what I see for my temperature sensors.

@ma-ca
Copy link
Contributor

ma-ca commented Jan 11, 2019

[1/11/2019, 8:24:13 PM] [Hue] Phoscon-GW: 000D6F000C2B8B3D: Bitron Home 902010/32 "Thermostat 40"
[1/11/2019, 8:24:13 PM] [Hue] Phoscon-GW: /sensors/40: ZHAThermostat "Thermostat 40"
[1/11/2019, 8:24:15 PM] [Hue] Initializing platform accessory 'Thermostat 40'...
[1/11/2019, 8:25:06 PM] [Hue] Thermostat 40: homekit target temperature changed from 17.6 to 18.2
[1/11/2019, 8:25:06 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1820,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:15 PM] [Hue] Thermostat 40: homekit target temperature changed from 18.2 to 17.5
[1/11/2019, 8:25:16 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1750,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:34 PM] [Hue] Thermostat 40: homekit target temperature changed from 17.5 to 16.8
[1/11/2019, 8:25:34 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1680,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: homekit target temperature changed from 16.8 to 16.3
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: set homekit target temperature from 16.3°C to 16.8°C
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1630,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: set homekit target temperature from 16.8°C to 16.3°C
[1/11/2019, 8:26:01 PM] [Hue] Thermostat 40: homekit target temperature changed from 16.3 to 15.8
[1/11/2019, 8:26:01 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1580,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:26:09 PM] [Hue] Thermostat 40: homekit target temperature changed from 15.8 to 14.9
[1/11/2019, 8:26:09 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1490,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:26:30 PM] [Hue] Thermostat 40: homekit target temperature changed from 14.9 to 13.7
[1/11/2019, 8:26:30 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1370,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:27:08 PM] [Hue] Thermostat 40: homekit target temperature changed from 13.7 to 12.7
[1/11/2019, 8:27:09 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1270,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:27:20 PM] [Hue] Thermostat 40: state changed event: {"lastupdated":"2019-01-11T19:27:20","on":false,"temperature":2220}

@ma-ca
Copy link
Contributor

ma-ca commented Jan 11, 2019

I am only using the Apple Home App.

@ma-ca
Copy link
Contributor

ma-ca commented Jan 11, 2019

Just in case there is a relation, in the beginning the Window Covering icons in the Home App did have 1% resolution when showing open state between 0% and 100%. Later this changed to 5% resolution. I thought that this was changed on purpose in homebridge-hue.

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 11, 2019

I really need the full output of homebridge -D, please see https://github.com/ebaauw/homebridge-hue#debug-log-file.

I am only using the Apple Home App.

What temperatures does Eve or another HomeKit app show?

Later this changed to 5% resolution. I thought that this was changed on purpose in homebridge-hue.

Yes, I found my lumi.curtain doesn't always report a position of 0 or 254 when fully open or closed. Even after re-calibration, it's sometimes a little bit off. I worked around that by rounding to multiples of 5. This is completely unrelated to the Thermostat, though.

@ma-ca
Copy link
Contributor

ma-ca commented Jan 11, 2019

The full debug logfile from before.

homebridge.log.gz

What temperatures does Eve or another HomeKit app show?

The Eve app does show the temperature correct with 0.1 °C resolution. Also the target temperature is translated correctly when increasing the 0.5 °C steps.

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 12, 2019

Thanks!

[1/11/2019, 8:25:06 PM] [Hue] Thermostat 40: homekit target temperature changed from 17.6 to 18.2 
[1/11/2019, 8:25:06 PM] [Hue] Phoscon-GW: gateway request 22: put /sensors/40/config {"heatsetpoint":1820}
[1/11/2019, 8:25:06 PM] [Hue] Phoscon-GW: gateway request 22: ok
[1/11/2019, 8:25:06 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1820,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:06 PM] [Hue] Thermostat 40: ignore unknown attribute config.scheduler

This is looking good. The thermostat is changed from HomeKit to 18.2°C. homebridge-hue sets config.heatsetpoint to 1820 and deCONZ issues a web socket notification with the new heatsetpoint. I do need to ditch the config.scheduler message, though.

[1/11/2019, 8:25:48 PM] [Hue] Phoscon-GW: gateway request 50: get /sensors
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: homekit target temperature changed from 16.8 to 16.3
[1/11/2019, 8:25:48 PM] [Hue] Phoscon-GW: gateway request 51: put /sensors/40/config {"heatsetpoint":1630}
[1/11/2019, 8:25:48 PM] [Hue] Phoscon-GW: gateway request 50: ok
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: set homekit target temperature from 16.3°C to 16.8°C
[1/11/2019, 8:25:48 PM] [Hue] Phoscon-GW: gateway request 51: ok
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: config changed event: {"battery":100,"heatsetpoint":1630,"offset":0,"on":true,"reachable":true,"scheduler":"Monday,Tuesday,Wednesday,Thursday,Friday 04:00 2200 05:00 2300 06:00 1700 16:00 2300 17:00 2000 21:00 1800;Saturday,Sunday 06:00 2200 21:00 1800;","scheduleron":true}
[1/11/2019, 8:25:48 PM] [Hue] Thermostat 40: set homekit target temperature from 16.8°C to 16.3°C

The joy of asynchronous processing. The target temperature is updated while homebridge-hue is polling /sensors. homebridge-hue reverts HomeKit to the previous value (retrieved from the poll), but this is corrected when homebridge-hue receives the web socket notification of the change by the put.

And the heating value has a random offset, for example 17.0 °C changes the config.heatsetpoint to 1710, value 17.5°C to 1770, value 18.0°C to 1800.

I don't see this. In both above cases homebridge-hue sends the (to 0.1°C) correct temperature to the deCONZ gateway, and the gateway confirms this through the websocket notification. I suspect the Home app might do something funny here as well. I double-checked that both Current Temperature and Target Temperature have a 0.1°C resolution.

Some other remarks:

[1/11/2019, 8:24:09 PM] [Hue] config.json: {"platform":"Hue","host":"127.0.0.1","users":{"00212EFFFF00893F":"*********1"},"sensors":true,"excludeSensorTypes":["CLIPPresence","Geofence"],"lights":true,"wallSwitch":true,"hueMotionTemperatureHistory":true}
[1/11/2019, 8:24:09 PM] [Hue] config.json: {"platform":"Hue","host":"192.***.***.252","users":{"001788FFFE12CA51":"***************************************1"},"sensors":true,"lights":true,"wallSwitch":true}

You have specified two "Hue" platforms in config.json. While that currently works, it will break when moving to dynamic platform accessories. You can expose both the Hue bridge and the deCONZ gateway from a single entry by:

{
  "platform": "Hue",
  "hosts": ["127.0.0.1", "192.***.***.252"],
  "users": {
    "00212EFFFF00893F": "*********1",
    "001788FFFE12CA51": "***************************************1"
  }
}

Ah the ubisys S2. I have been waiting to see the full model S2 (5502) to expose the ZHASwitch sensor. I can read the buttonevent values from the deCONZ REST API, but not the full model. Do you get good values for consumption and power? My D1 (running a later firmware version) gives garbage for these.

[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: 001FEE000000170A: ubisys S2 (5502) "Light 1"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /lights/1: On/Off output "Light 1"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /lights/1: config: {"on":true,"bri":false,"ct":false,"xy":false,"wallSwitch":true,"windowCovering":false,"unknown":true}
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /lights/2: On/Off output "Light 2"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /lights/2: config: {"on":true,"bri":false,"ct":false,"xy":false,"wallSwitch":true,"windowCovering":false,"unknown":true}
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /sensors/5: ZHAConsumption "Consumption 5"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /sensors/6: ZHAPower "Power 6"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /sensors/4: ZHASwitch "S2 (5502) 4"
[1/11/2019, 8:24:11 PM] [Hue] Phoscon-GW: /sensors/4: warning: ignoring unknown ZHASwitch sensor {"config":{"group":null,"mode":"momentary","on":true,"reachable":true},"ep":3,"etag":"423162415d68374a920ef22184c6c540","manufacturername":"ubisys","mode":1,"modelid":"S2 (5502)","name":"S2 (5502) 4","state":{"buttonevent":null,"lastupdated":"none"},"swversion":"20160302-DE-FB0","type":"ZHASwitch","uniqueid":"00:1f:ee:00:00:00:17:0a-03-0006"}

@ebaauw
Copy link
Collaborator

ebaauw commented Jan 12, 2019

Note to self: Eve history.

ebaauw added a commit to ebaauw/homebridge-hue that referenced this issue Jan 12, 2019
- Suppress message `ignore unknown attribute config.schedular` for _Thermostat_, see dresden-elektronik/deconz-rest-plugin#1098 (comment) and #426,
@ebaauw
Copy link
Collaborator

ebaauw commented Jan 12, 2019

Please checkout homebridge-hue v0.11.8 which should:

Let's continue the conversation about homebridge-hue support to the homebridge-hue issues.

@thommyDD
Copy link

I would like to add the Eurotronic device to the restAPI, but there is an error:

{ "config": { "on": true "reachable": true } "manufacturername": "Eurotronic" "modelid": "SPZB0001" "name": "Thermo WZ ET" "swversion": "20181205" "type": "ZHAThermostat" "uniqueid": "0x00158d0001922f50" }

[{ "error": { "address": "/sensors", "description": "Not allowed to create sensor type", "type": 501 } }]

The newest versions of deCONZ (2.05.54) and homebride-hue (v0.11.8) are installed

@manup
Copy link
Member

manup commented Jan 16, 2019

@thommyDD please try with this interims version :)

https://www.dresden-elektronik.de/rpi/deconz/alpha/deconz-2.05.56-qt5.deb

Thermostat needs to be rejoined again, while sensor search is running.

@thommyDD
Copy link

@manup it does not work :(

I reset the thermostat while the sensor search is running, but the thermostat was not found.

@manup
Copy link
Member

manup commented Jan 16, 2019

Hmmm not sure what's happening. Just ordered one via Amazon should arrive next Monday.

@wvuyk
Copy link

wvuyk commented Jan 17, 2019

Is interesting, subscribing to see the progress ;-)

manup added a commit that referenced this issue Jan 21, 2019
* Fix creating sensor resources (was skipped when not reading basic cluster manually)
* Fix repeated binding by recording 'local temperature' value
* Refactor thermostat module, keep variables more local and use library zcl attribute code
* Add some notes for polling and manufacturer specific attributes

Issue #1098
@tkintscher
Copy link
Contributor

I also stumbled over this device recently. The Z-Wave version has the interesting feature of supporting external temperature sensors (which may give more realistic readings than the internal one).
Of those that already have the device, do you know if this is (or will be) possible via Zigbee, too? The manufacturer's website is unfortunately very sparse.

@sawfear
Copy link

sawfear commented Jan 24, 2019

Hey there, I recently also got this device. Right now I only can set the Occupied Heating Setpoint, which is then copied by the device to the attribute Current Temperature Setpoint via deCONZ Gui. Will you also add the scheduling attributes to the deCONZ Gui? As I really don´t know right now, how I would do this via REST API, as this is out of my knowledge right now. Would be much appreciated.

Cheers

@Howaner
Copy link

Howaner commented Jan 23, 2021

Just a quick update: Regarding a mail I received from Eurotronic Support, the OTA update should be released within the next 2-3 weeks.

See: EUROTRONIC-Technology/Spirit-ZigBee#1

Thank you for the information.
This means the release date was delayed from 1-2 weeks to 2-3 weeks.

I will have to return the product if the problems are not fixed in the next 2 weeks.
Otherwise, I can not return the non-functioning thermostat if the vendor isn't able to fix the issues :(

@jeankone
Copy link

@magicdude4eva Yes, OTA firmware updates are supported and firmware will be available on Eurotronic GitHub page.

I'm not able to complete the update. Following the procedures mentioned in your wiki and it just says "idle" and nothing happens.

@magicdude4eva
Copy link

I had to click a few times on update. I aborted the update as the firmware looked older than what I had (see EUROTRONIC-Technology/Spirit-ZigBee#9).

@Witriol
Copy link

Witriol commented Jan 30, 2021

@jeankone Similiar issues are being talked about in this issue EUROTRONIC-Technology/Spirit-ZigBee#1 Unfortunately all of my 5 TRVs (all had 20191014 firmware) could have been updated as mentioned in guide...

@FlyingPersian
Copy link

Hello,

I bought two Spirits about 2 years ago and used them successfully for a while. I don't remember why, but at some point I dismounted them because of some issues. I wanted to re-use them a while ago, but I was unable to connect them to my Raspberry Pi running Home Assistant with a Raspbee and the deCONZ addon (as of now, v6.7.0 which is using deCONZ 2.9.3). Today, I deleted the two old ghost connections via VNC (within the addon) and the within Phoscon. I'm still unable to connect. Both devices just say "Jin" untill "Error" shows up.

I'm also unable to reset both devices (by holding - and +). Nothing happens when I hold them. Weirdly, it's with both devices. Am I doing something wrong? Do I need to do anything specific? I should mention that when I want to connect them, I go into Phoscon --> Sensors --> Add new Sensor --> Other.

@ebaauw
Copy link
Collaborator

ebaauw commented Feb 12, 2021

You need to hold all three buttons to reset, just + and - toggles the child lock.

@FlyingPersian
Copy link

Well, now I feel stupid :D I was sure it was + and -! Thanks!

@FlyingPersian
Copy link

FlyingPersian commented Feb 13, 2021

Am I right to assume that the ghosting issue has not been resolved yet? I cannot add one of my Spirits after I had to reset it once it was connected. The ghosting device shows up in deCONZ (0xD2EB) when I start the Spirit and it's in "Jin" mode. Right click --> delete won't permamentally remove it. The Spirit doesn't connect and moves on to "Err" after a while. Resetting the Spirit didn't resolve it. It's been roughly 14h since I removed it the first time.

Unbenannt

@jeankone
Copy link

Am I right to assume that the ghosting issue has not been resolved yet? I cannot add one of my Spirits after I had to reset it once it was connected. The ghosting device shows up in deCONZ (0xD2EB) when I start the Spirit and it's in "Jin" mode. Right click --> delete won't permamentally remove it. The Spirit doesn't connect and moves on to "Err" after a while. Resetting the Spirit didn't resolve it. It's been roughly 14h since I removed it the first time.

Sometimes i have the same issue with one of mine, too. Dont really have a solution, but to reset and search for it in phoscon again and again (sometimes upto 30times). Suddenly it will connect properly.

@FlyingPersian
Copy link

These stupid thermostats are so frustrating :( One won't connect, the other is connected, but somehow just stopped taking commands. I don't feel like resetting it as it will probably not be able to connect :( Are there any alternative devices you guys have good experience with? I'm using them with Home Assistant

@bcutter
Copy link

bcutter commented Feb 23, 2021

These stupid thermostats are so frustrating :( One won't connect, the other is connected, but somehow just stopped taking commands. I don't feel like resetting it as it will probably not be able to connect :( Are there any alternative devices you guys have good experience with? I'm using them with Home Assistant

Oh damn... have two of those here, one unboxed ready to set up. Using deCONZ with a ConBee 2 and Home Assistant too. I'm not too excited from what to read here about those devices.

What about the firmware updates mentioned? Are there any, do they fix things? Or is it (as many times, personal experience) deCONZ/ConBee that screws things up?

@easybeat
Copy link

easybeat commented Feb 23, 2021

These stupid thermostats are so frustrating :( One won't connect, the other is connected, but somehow just stopped taking commands. I don't feel like resetting it as it will probably not be able to connect :( Are there any alternative devices you guys have good experience with? I'm using them with Home Assistant

Good morning

well I went through all this too but not with the Eurotronic ones. I have 3 other devices tested now:

  1. Moes TRV from Ali
    this did look really good. OK it's a pain to include until I figured out to include it 2x and then it shows up correctly in Deconz. Then I did test one device about 6 meters away from my box and it did work perfect. Then I moved one level up to another room as far as possible away from the box and troubles started. It did not pick a router to connect, lost connection etc.
    I had an order of 12 coming in and so I decided to order Ikea range extenders. With them installed as close as possible to the device it works. And now since Deconz 2.9.3 all these connection problems are gone. They find routers such as lamps etc. and work. Not sure about battery life. Looks like battery is not reported properly. But they work.

  2. Danfoss Ally
    After I did face so many problems with the Moes TRV's I decided to test also the Danfoss ones which are about 3x the price. They are OK but also with this I did face connection problems far away from the box. I have not tested it further with Deconz 2.9.3

  3. Essentials TRV from Amazon
    I also bought on of them for Test. I was already on Deconz 2.9.3 when I got it and it looks the best of all of them BUT it makes a lot of noise when opening fully in one go. This device managed to do a direct connect to the box even far away from the box on level upstairs. So it looks like it has a pretty good antena or whatever it is.

As I wanted to change my TRV's from Danfoss Zwave to Zigbee, I can also compare to Danfoss Zwave device and I have to rate this as the best of all. I never faced connection problems. They are running very silent. So I might stay on the Zwave solution.

If you would like to test some Moes TRV's, I'm happy to send you one or two and if they work you can pay them. I'm based in Switzerland and could send by post.

I hope this helps.

@Maurizion
Copy link

Maurizion commented Feb 24, 2021

1. Moes TRV [from Ali](https://de.aliexpress.com/item/4001065031604.html?spm=a2g0s.9042311.0.0.27424c4dvx76c2)

I agree that those are good but with poor battery autonomy from my experience.
Just one question : why you would like to move from Zwave to Zigbee ?

@cleversmart
Copy link

interesting observation: I'm working with deconz 2.9.3 and homebridge 1.3.4. I have 6 Eurotronic Spirits with firmware 22190930. 2 Spirits near by the Coordinator, they are stable without interruptions. From time to time the other 4 Spirits are orphanded, and not able to contol. In this situation, if you get basic informations from the orphanded Spirit again. the status led is red, if you click again to get basic informations after few seconds, the status led is blinking blue and you get all informations. after this manual intervention, the orphanded Spirits are controllable maybe for 3-4 days. Then repeat it.... Whats happend?

@univok
Copy link

univok commented Mar 17, 2021

There seem to be many workarounds to get the orphaned back. Yesterday, I could reestablish connection by pressing "leave" and "join" network again in the deCONZ GUI window. After a short time, I could talk to the Spirit again, the red LED was gone.

@easybeat
Copy link

There seem to be many workarounds to get the orphaned back. Yesterday, I could reestablish connection by pressing "leave" and "join" network again in the deCONZ GUI window. After a short time, I could talk to the Spirit again, the red LED was gone.

Well I'm fighting with devices losing connection since months now. I have 2 Aqara Opple switches which losing randomly connection. For me only rejoin the devices helps. So I don't think this is a Spirit problem as I had exactly the same behaviour with losing connection with 3 different types of TVR's (Moes, Essentials and Danfoss). And I they did even lose connection when I placed a ikea range extender less than 1 meter to them...I start believing that here is something wrong with deconz!

Sorry guys!

@KartoffelToby
Copy link

Hey, i have a matching issue in general. (think all TVRs exept Tuya are have the same issue or Tuya too i havent a test device)

I'm workt on a PR (home-assistant/core#47767) on Home Assistiant but now we think its a gerneral problem in how deCONZ is handling TVRs that uses "heat" mode for boost, and "auto" for normal heating with set temperature

i'm playing with some changes but currently only for SPZB0001.

That will look like:

{
    "config": {
        "battery": 65,
        "displayflipped": false,
        "heatsetpoint": 2200,
        "locked": false,
        "mode": "heat",
        "offset": -300,
        "on": true,
        "preset": "auto",
        "reachable": true
    },
    "ep": 1,
    "etag": "9cf5d1f8d5e7b3e355f0963ea8378403",
    "lastseen": "2021-03-19T16:07Z",
    "manufacturername": "Eurotronic",
    "modelid": "SPZB0001",
    "name": "Heizung - Bad",
    "state": {
        "lastupdated": "2021-03-19T16:07:10.330",
        "on": true,
        "temperature": 2234,
        "valve": 45
    },
    "swversion": "22190930",
    "type": "ZHAThermostat",
    "uniqueid": "00:15:8d:00:01:ff:91:f0-01-0201"
}

so mode "heat" with preset "auto" means the same as currently mode "auto"
and mode "heat with preset "boost" means the same as currently mode "heat"

Think such a behavior is better for thinks like HA intigration and Google Home stuff, like i write allready in die PR (home-assistant/core#47767)

What do you guys think? Is it only for the Sprit or every TVR that works with heat mode as boost?

Other point ist that mode "auto" with preset "auto" can stand for scheduler run.

If this how TVR s should work i will make a PR

@Mimiix
Copy link
Collaborator

Mimiix commented Mar 23, 2021

This is something unrelated to this topic @KartoffelToby

I think i'll close this issue, as the bugs are pointed out in the Firmware and such. If there is any (big) problems, feel free to open a new issue!

@Mimiix Mimiix closed this as completed Mar 23, 2021
@univok
Copy link

univok commented Mar 31, 2021

I found new workaround. Spirit with updated FW was unreachable after working nice for days, but neighboor links in green where still existent. It shows the red LED when requesting Basic Cluster Info. I could reastablish the connection by pressing +/- button on the Sprit device once. It seems to me that it slept and woke up somehow, talking to the network again.

Is this because of a flaky power management, or doesn't deCONZ knock the door correctly? Have no idea.

@bcutter
Copy link

bcutter commented Apr 4, 2021

It sometimes takes a loooooooong time (sometimes even never) for changed values (e. g. set new target temperature on the device with +/- buttons) to show up in the home automation system (Home Assistant). The other way (setting new target temperature remotely) works fine.

In the Thermostat cluster I can only find Local Temperature (measured), but no SET temperature. Where can I find this information in deCONZ to track down if the information from Thermostat to Home Assistant get´s lost on the part
a) Spirit to deCONZ
b) deCONZ to Home Assistant
?

grafik

If this is not the right place to ask these questions (anymore) please guide me to the right one.

@Memphistheghost
Copy link

Hello everyone, we have the problem that we have multiple Eurotronic Spirit Zigbee's about 1-2 years old they are all running on an old firmware 18181120 we are trying to update them via deCONZ however, unsuccessful

zigbee-thrmostat

Zigbee

As you can see we getting it connected in Phoscon, but it won't let us to any groups or either configure the temperature only on the device itself.

Now I ask myself what am I doing wrong? Sometimes the deCONZ program reconnects I thought maybe about that, it cannot build any stable connection otherwise when we try to update it in the progress idle/Queuing and waited 1-2 hours nothing happen. Do I have maybe a wrong version etc... I get lost and very frustrated, maybe some of you guys have had the same problem and can share his experience since I'm very new to it and try my best.

progress-fehler

@Smanar
Copy link
Collaborator

Smanar commented Jun 4, 2021

Sometimes the deCONZ program reconnects

I don't think it s a good thing for ota update, The first thing to do is stabilizing your connexion.

If I m right there is logging just for OTA, logs can be usefull too.

@githtz

This comment has been minimized.

@fabmsg
Copy link

fabmsg commented Nov 6, 2021

Hello everyone, we have the problem that we have multiple Eurotronic Spirit Zigbee's about 1-2 years old they are all running on an old firmware 18181120 we are trying to update them via deCONZ however, unsuccessful

zigbee-thrmostat Zigbee

As you can see we getting it connected in Phoscon, but it won't let us to any groups or either configure the temperature only on the device itself.

Now I ask myself what am I doing wrong? Sometimes the deCONZ program reconnects I thought maybe about that, it cannot build any stable connection otherwise when we try to update it in the progress idle/Queuing and waited 1-2 hours nothing happen. Do I have maybe a wrong version etc... I get lost and very frustrated, maybe some of you guys have had the same problem and can share his experience since I'm very new to it and try my best.

progress-fehler

Hi. Were you able to find a solution? I am facing the same

@Smanar
Copy link
Collaborator

Smanar commented Nov 6, 2021

There is something bad on your network.
It miss one circle on the coordinator node, first time I m seing that for the coordinator, can you try to enable it using request available in the first circle ?

@olliox
Copy link

olliox commented Nov 6, 2021 via email

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

No branches or pull requests