Sinope Zigbee Thermostat (Edge Driver): Outside Temperature?

As I said at the time, I did not change anything in the driver compared to the stock, I do not know why the outside temperature started to work.

Perhaps, when making the driver change, some preference configuration is made by writing to some attribute of the thermostat.

Are you tried perform a driver change to stock driver y/o return to Mc driver?

My theory was that the thermostat acquires the outdoor temperature from the internet via wifi of the router and not through the zigbee driver, since it is impossible.

I don’t know how the thermostat acquires the outside temperature or how it uses it. If it is only informative or intervenes in the control of the interior temperature in some way.

If it is only informative it should not be a problem to be able to use the thermostat.

according to the manual, it can report the temp set point or the outside temperature, but I don’t know how to select one or the other

1 Like

It worked for a bit when I changed the driver but it reverted to not showing anymore

I received this from Sinope on Oct 2. Probably broke everything now.

Dear customer,

We are pleased to inform you that the outdoor temperature displayed on our thermostats and in Neviweb is available again!

Our new API provider will now be OpenWeather for all our customers in North America.

Thank you for your patience.

Have a nice day,
The Sinopé team

@Mariano_Colmenarejo, there are discussions on other hub forums like Hubitat and Home Assistant about how the SmartThings DTH acquired and displayed the outdoor temperature. It appears that the DTH made use of the internal weather service of the SmartThings Groovy platform and wrote the outdoorTemp to the device via Zigbee. If you search for outdoorTemp in the Sinope DTH, you’ll see.

https://www.sinopetech.com/wp-content/uploads/2019/03/Sinope-Technologies-TH1123ZB_TH1124ZB-V.1.0.5-SVN-503.txt

This email was intended for Neviweb users. The weather feature was not functional for everyone recently due to the hacking incident involving MétéoMédia. Therefore, Sinope now points to the OpenWeather API to obtain temperature data for thermostats controlled on their platform. Unfortunatly, they don’t care much about smartthings users.

Thanks for the clarification. Yeah, I am thinking of jumping on the WiFi version of Sinope.

Sucks how it ST broke it and neither company decided on fixing the problem.

Is anyone using an Edge driver that works like it did before?

Does someone know if an edge driver is able to do an http call and parse just a value like a temperature number and pass it to the device? We could tweak the driver to set by configuration the postal code and maybe api credential to fetch and set the temperature.

1 Like

From what I was able to read TAustin was able to develop his Edge weather driver in order to get temperature from provider in smartthings, only downside is the fact to have a driver bridge running on a computer.
On a positive note, I started my first driver yesterday and I am able in a background thread to change and display the outside temperature on my Sinope thermostat, for now the temperature is a random number but my goal is to merge soon my driver with the Edge weather code and get real temperature.
I will keep you updated when I will succeed it.

4 Likes

@jamer007: Thanks for the hard work on this. Can’t wait to see the outside temperature again on my thermostats!

I got a little excited when I saw your post and then quickly realized that it didn’t matter anymore because I got old and even if it was displayed that I wouldn’t be able to see it anyway.

Hi,
So I was able to create the driver, I tested it with my TH1123ZB and TH1124ZB.
The way I did the driver is by merging some part of the code of the Edge Weather of TAustin and the Thermostat from MC. Big thanks to them.

In my driver you can select 2 weather source parsers (US GOV and Canadian Weather).
If you live in the US and so want the US GOV source, the configuration will be:
EdgeDriver → Edgebridge (TAustin) running on a server or computer in your local network → us government public API running on the internet.
If you live in Canada, the configuration will be:
EdgeDriver → Canadian Weather API (Jamer007) running on a server or computer in your local network.
In any situation you will need to have a service running locally, that’s a Smartthings limitation right now, the driver can only have the LAN permission and not WEB permission.

I have added the PowerMeter in the driver, so you can see live how many watts the heaters are using.

Here is the link to my driver: https://bestow-regional.api.smartthings.com/invite/Pw2DkDvx39M3
The state of the driver is Alpha or Beta, this is my first driver :slight_smile:

For the TAustin edgebridge: https://github.com/toddaustin07/edgebridge/blob/main/README.md

For the Canadian Weather Rest service that you need to run locally, I have found and modified a GitHub script and added the Rest API capability and hosted it as a docker image: GitHub - jamer007/canadian_weather_rest

Here is a settings example:

3 Likes

I’m probably missing something here or someone may have already asked but why can’t we just ask the hub for the temp? Since we can have hub rules based of of the weather it would seem possible for the driver running on the hub to do the same.

Wow :star_struck: amazing in progress work !!!

Btw, it doesn’t seem possible to save the driver settings in the current version.

@LLwarrenP, I wish I could find how to do it, that would have been the easiest solution for the users.

@jsdecarie Which Sinope model do you have?

TH1300ZB it is a floor heating thermostat.

@jamer007

Thanks for your work and help, I will be trying it with the canadian weather option. I am also using the TH1300ZB thermostat.

Will let you know the results

I have a bit of progress:

Installed the restapi
Working well, getting the canadian weather in a browser
Installed the edge driver, replaced the current driver for the new one.

Not getting the weather, losing the settings for the current weather url, and keep getting proxy type = standard proxy server instead of none

@jamer007, yes, thanks for your work on this!

I’m getting the same results. Primarily, the settings are not saving. I’m also using the TH1300ZB thermostat.

Here’s the trace from the CLI:

2023-11-09T10:37:01.952618289+00:00 TRACE Zigbee Thermostat Jamer007  Setup driver zigbee-thermostat with lifecycle handlers:
DeviceLifecycleDispatcher: zigbee-thermostat
  default_handlers:
    driverSwitched:
    added:
    doConfigure:
  child_dispatchers:
    DeviceLifecycleDispatcher: zigbee-thermostat -> Sinope Thermostat Handler
      default_handlers:
        init:
        infoChanged:
        doConfigure:
      child_dispatchers:

2023-11-09T10:37:01.962040498+00:00 TRACE Zigbee Thermostat Jamer007  Setup driver zigbee-thermostat with Capability handlers:
CapabilityCommandDispatcher: zigbee-thermostat
  default_handlers:
    thermostatMode:
      off
      heat
      auto
      cool
      setThermostatMode
      emergencyHeat
    thermostatHeatingSetpoint:
      setHeatingSetpoint
    thermostatCoolingSetpoint:
      setCoolingSetpoint
    thermostatFanMode:
      fanAuto
      setThermostatFanMode
      fanOn
    refresh:
      refresh
    energyMeter:
      resetEnergyMeter
  child_dispatchers:
    CapabilityCommandDispatcher: zigbee-thermostat -> Sinope Thermostat Handler
      default_handlers:
        refresh:
          refresh
      child_dispatchers:

2023-11-09T10:37:01.962577349+00:00 TRACE Zigbee Thermostat Jamer007  Setup driver zigbee-thermostat with Zigbee handlers:
ZigbeeMessageDispatcher: zigbee-thermostat
  default_handlers:
    attr:
      ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
      ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
      ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryAlarmState
      ZclClusterAttributeValueHandler: cluster: Basic, attribute: PowerSource
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: ThermostatRunningState
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedHeatingSetpoint
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: ControlSequenceOfOperation
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: SystemMode
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: ThermostatRunningMode
      ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedCoolingSetpoint
      ZclClusterAttributeValueHandler: cluster: TemperatureMeasurement, attribute: MeasuredValue
      ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerMultiplier
      ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerDivisor
      ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
      ZclClusterAttributeValueHandler: cluster: RelativeHumidity, attribute: MeasuredValue
      ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: InstantaneousDemand
      ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Multiplier
      ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
      ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
      ZclClusterAttributeValueHandler: cluster: FanControl, attribute: FanModeSequence
      ZclClusterAttributeValueHandler: cluster: FanControl, attribute: FanMode
    global:
    cluster:
    zdo:
  child_dispatchers:
    ZigbeeMessageDispatcher: zigbee-thermostat -> Sinope Thermostat Handler
      default_handlers:
        attr:
          ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
          ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OutdoorTemperature
          ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: PIHeatingDemand
        global:
        cluster:
        zdo:
      child_dispatchers:

2023-11-09T10:37:02.032024806+00:00 WARN Zigbee Thermostat Jamer007  Device does not support cluster 0x0702 not adding configured attribute
2023-11-09T10:37:02.042606511+00:00 INFO Zigbee Thermostat Jamer007  Device does not support cluster 0x0702 not adding monitored attribute
2023-11-09T10:37:02.043394196+00:00 TRACE Zigbee Thermostat Jamer007  Zigbee Device: 94a6899d-48b0-4c7b-b593-f0e58235f39e
Manufacturer: Sinope Technologies Model: TH1300ZB
        [1]: server: Basic, Identify, Groups, Scenes, Thermostat, ThermostatUserInterfaceConfiguration, TemperatureMeasurement, ElectricalMeasurement, Diagnostics, 0xFF01 | client: Identify, OTAUpgrade
2023-11-09T10:37:02.044100966+00:00 DEBUG Zigbee Thermostat Jamer007  driver device thread event handled
2023-11-09T10:37:02.044749665+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler _resync
2023-11-09T10:37:02.045397197+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler environment_info
2023-11-09T10:37:02.046168082+00:00 DEBUG Zigbee Thermostat Jamer007  Z-Wave hub node ID environment changed.
2023-11-09T10:37:02.082801973+00:00 TRACE Zigbee Thermostat Jamer007  Found DeviceLifecycleDispatcher handler in zigbee-thermostat -> Sinope Thermostat Handler
2023-11-09T10:37:02.088924575+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.089440082+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler environment_info
2023-11-09T10:37:02.090086114+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler device_lifecycle
2023-11-09T10:37:02.090691416+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received lifecycle event: added
2023-11-09T10:37:02.091724349+00:00 TRACE Zigbee Thermostat Jamer007  Found DeviceLifecycleDispatcher handler in zigbee-thermostat
2023-11-09T10:37:02.092360834+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0011 > > >
2023-11-09T10:37:02.096897809+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0012 > > >
2023-11-09T10:37:02.106182783+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-11-09T10:37:02.112211504+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x001B > > >
2023-11-09T10:37:02.122428568+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0029 > > >
2023-11-09T10:37:02.137035618+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x001E > > >
2023-11-09T10:37:02.142180314+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x001C > > >
2023-11-09T10:37:02.147959369+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: FanControl >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0001 > > >
2023-11-09T10:37:02.162258807+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: FanControl >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-11-09T10:37:02.175591553+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0020 > > >
2023-11-09T10:37:02.181363271+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x003E > > >
2023-11-09T10:37:02.188738123+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-11-09T10:37:02.201493164+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.202324621+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler device_lifecycle
2023-11-09T10:37:02.203145490+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received lifecycle event: driverSwitched
2023-11-09T10:37:02.204091504+00:00 TRACE Zigbee Thermostat Jamer007  Found DeviceLifecycleDispatcher handler in zigbee-thermostat
2023-11-09T10:37:02.204742163+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.211319783+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler capability
2023-11-09T10:37:02.216472442+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.222221773+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler capability
2023-11-09T10:37:02.222707224+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received command: {"args":{},"positional_args":{},"capability":"refresh","command":"refresh","component":"main"}
2023-11-09T10:37:02.223683712+00:00 TRACE Zigbee Thermostat Jamer007  Found CapabilityCommandDispatcher handler in zigbee-thermostat -> Sinope Thermostat Handler
2023-11-09T10:37:02.224336205+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-11-09T10:37:02.238795598+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0012 > > >
2023-11-09T10:37:02.244226145+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0008 > > >
2023-11-09T10:37:02.263016994+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x001C > > >
2023-11-09T10:37:02.268823187+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2023-11-09T10:37:02.296941031+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.301914433+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:02.302366159+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -49, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3D, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0011, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:02.310819300+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received command: {"args":{},"positional_args":{},"capability":"refresh","command":"refresh","component":"main"}
2023-11-09T10:37:02.311843478+00:00 TRACE Zigbee Thermostat Jamer007  Found CapabilityCommandDispatcher handler in zigbee-thermostat -> Sinope Thermostat Handler
2023-11-09T10:37:02.312476670+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2023-11-09T10:37:02.318084556+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0012 > > >
2023-11-09T10:37:02.324174933+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0008 > > >
2023-11-09T10:37:02.347402582+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x001C > > >
2023-11-09T10:37:02.348792235+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xFD7C, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2023-11-09T10:37:02.378663622+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.388444510+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:02.388908408+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -50, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0012, ZclStatus: SUCCESS, DataType: Int16, OccupiedHeatingSetpoint: 1000 > > > >
2023-11-09T10:37:02.393101587+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.394013793+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:02.394841915+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xF7, rssi: -49, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Int16, LocalTemperature: 2492 > > > >
2023-11-09T10:37:02.461192866+00:00 TRACE Zigbee Thermostat Jamer007  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2023-11-09T10:37:02.468896257+00:00 INFO Zigbee Thermostat Jamer007  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedHeatingSetpoint
2023-11-09T10:37:02.469878540+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> emitting event: {"attribute_id":"heatingSetpoint","capability_id":"thermostatHeatingSetpoint","state":{"value":10.0,"unit":"C"},"component_id":"main"}
2023-11-09T10:37:02.529533436+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.534684135+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:02.535599592+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -50, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x40, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x001B, ZclStatus: SUCCESS, DataType: Enum8, ControlSequenceOfOperation: ControlSequenceOfOperation[HEATING_ONLY] > > > >
2023-11-09T10:37:02.611153309+00:00 TRACE Zigbee Thermostat Jamer007  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2023-11-09T10:37:02.618501731+00:00 INFO Zigbee Thermostat Jamer007  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature2023-11-09T10:37:02.619678694+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> emitting event: {"attribute_id":"temperature","capability_id":"temperatureMeasurement","state":{"value":24.92,"unit":"C"},"component_id":"main"}
2023-11-09T10:37:02.670130282+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:02.670791571+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:02.671476664+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -49, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x41, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0029, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:02.785070015+00:00 TRACE Zigbee Thermostat Jamer007  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2023-11-09T10:37:02.786932196+00:00 INFO Zigbee Thermostat Jamer007  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: ControlSequenceOfOperation
2023-11-09T10:37:02.787758567+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> emitting event: {"attribute_id":"supportedThermostatModes","capability_id":"thermostatMode","visibility":{"displayed":false},"state":{"value":["off","heat","emergency heat"]},"component_id":"main"}
2023-11-09T10:37:03.128473715+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.129796876+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.292896051+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.297806714+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -49, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x42, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x001E, ZclStatus: SUCCESS, DataType: Enum8, ThermostatRunningMode: ThermostatRunningMode[HEAT] > > > >
2023-11-09T10:37:03.410435250+00:00 TRACE Zigbee Thermostat Jamer007  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2023-11-09T10:37:03.421877510+00:00 INFO Zigbee Thermostat Jamer007  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: ThermostatRunningMode
2023-11-09T10:37:03.491227501+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> emitting event: {"attribute_id":"thermostatMode","capability_id":"thermostatMode","state":{"value":"heat"},"component_id":"main"}
2023-11-09T10:37:03.547956851+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.553562027+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.554225442+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xFF, rssi: -49, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x43, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x001C, ZclStatus: SUCCESS, DataType: Enum8, SystemMode: SystemMode[HEAT] > > > >
2023-11-09T10:37:03.578282381+00:00 TRACE Zigbee Thermostat Jamer007  Found ZigbeeMessageDispatcher handler in zigbee-thermostat
2023-11-09T10:37:03.586950297+00:00 INFO Zigbee Thermostat Jamer007  Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: SystemMode
2023-11-09T10:37:03.587982521+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> emitting event: {"attribute_id":"thermostatMode","capability_id":"thermostatMode","state":{"value":"heat"},"component_id":"main"}
2023-11-09T10:37:03.667921554+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.671115441+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.671915508+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: FanControl >, lqi: 0xFF, rssi: -49, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x44, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0001, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:03.680444937+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.691532562+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.692558533+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: FanControl >, lqi: 0xFF, rssi: -50, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x45, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:03.709002667+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.710691178+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler device_lifecycle
2023-11-09T10:37:03.733008706+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received lifecycle event: infoChanged
2023-11-09T10:37:03.733939963+00:00 TRACE Zigbee Thermostat Jamer007  Found DeviceLifecycleDispatcher handler in zigbee-thermostat -> Sinope Thermostat Handler
2023-11-09T10:37:03.735198467+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.739524421+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.749247780+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xFF, rssi: -50, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x46, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0020, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:03.751846037+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.752474726+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee
2023-11-09T10:37:03.753105916+00:00 INFO Zigbee Thermostat Jamer007  <ZigbeeDevice: 94a6899d-48b0-4c7b-b593-f0e58235f39e [0xFD7C] (Ensuite Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xFD7C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xFF, rssi: -50, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x47, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x003E, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2023-11-09T10:37:03.763717094+00:00 DEBUG Zigbee Thermostat Jamer007  Ensuite Thermostat device thread event handled
2023-11-09T10:37:03.765674656+00:00 TRACE Zigbee Thermostat Jamer007  Received event with handler zigbee





Unfortunately, I don’t have this model only the TH1123 and TH1124.
I did try for a test to set the TH1300 setting page to my other model and at first like you I couldn’t save the settings!
I have tried a second time by filling the field Proxy server address with a fake value http://192.168.1.100:8088 as an example, I have also modified the Floor sensor type, Ambient limit, floor limit and floor high limit with new values and this time the settings were saved.

Can you try to play with the existing fields even if they already with a value and fill the Proxy server address?

Is there a way to have the driver you made give an option to display fahrenheit or Celsius?

Aparently they are not pulling the correct setting from the hub or profile.