jonassam
(Jonas Samuelsson)
November 9, 2020, 8:40am
1
Hi!
I have bought this Z-Wave radiator thermostat with really nice price to functionality ratio, but unfortunately the default climate entity does not quite work with it. As far as I can tell, it follows the standard Z-Wave protocol so I would assume that most of needs to be done should be reusable. Or perhaps already there for some other device to be reused in order to support this.
Best regards,
Jonas
Product page: https://www.everspring.com/portfolio-item/ac301-trv-thermostatic-radiator-valve/
Product Manual: https://www.everspring.com/wp-content/uploads/2020/04/AC301-user-manual_04272020x.pdf
Device config excerpt from Z-Wave config XML
<Node id="5" name="" location="" basic="4" generic="8" specific="6" roletype="7" devicetype="4608" nodetype="0" type="General Thermostat V2" listening="false" frequentListening="true" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
<Manufacturer id="60" name="Everspring">
<Product type="15" id="1" name="Unknown: type=0015, id=0001" />
</Manufacturer>
<CommandClasses>
<CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="4" mapping="64">
<Instance index="1" />
</CommandClass>
<CommandClass id="34" name="COMMAND_CLASS_APPLICATION_STATUS" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="5" innif="true">
<Instance index="1" />
<Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="21.5" />
</CommandClass>
<CommandClass id="64" name="COMMAND_CLASS_THERMOSTAT_MODE" version="3" innif="true">
<Instance index="1" />
<Value type="list" genre="user" instance="1" index="0" label="Mode" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="1" size="1">
<Item label="Off" value="0" />
<Item label="Heat" value="1" />
<Item label="Heat Econ" value="11" />
</Value>
<SupportedModes>
<Mode index="0" label="Off" />
<Mode index="1" label="Heat" />
<Mode index="11" label="Heat Econ" />
</SupportedModes>
</CommandClass>
<CommandClass id="67" name="COMMAND_CLASS_THERMOSTAT_SETPOINT" version="3" request_flags="2" innif="true" base="1" typeInterpretation="B">
<Instance index="1" />
<Value type="decimal" genre="user" instance="1" index="2" label="Cooling 1" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
<Value type="decimal" genre="user" instance="1" index="8" label="Dry Air" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
<Value type="decimal" genre="user" instance="1" index="100" label="Unused 0_minimum" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0" />
<Value type="decimal" genre="user" instance="1" index="101" label="Heating 1_minimum" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="5.0" />
<Value type="decimal" genre="user" instance="1" index="200" label="Unused 0_maximum" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0" />
<Value type="decimal" genre="user" instance="1" index="201" label="Heating 1_maximum" units="C" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="35.0" />
</CommandClass>
<CommandClass id="90" name="COMMAND_CLASS_DEVICE_RESET_LOCALLY" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="94" name="COMMAND_CLASS_ZWAVEPLUS_INFO" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="byte" genre="system" instance="1" index="0" label="ZWave+ Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="1" />
<Value type="short" genre="system" instance="1" index="1" label="InstallerIcon" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="4608" />
<Value type="short" genre="system" instance="1" index="2" label="UserIcon" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="4608" />
</CommandClass>
<CommandClass id="112" name="COMMAND_CLASS_CONFIGURATION" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="113" name="COMMAND_CLASS_ALARM" version="8" request_flags="2" innif="true">
<Instance index="1" />
<Value type="byte" genre="user" instance="1" index="0" label="Alarm Type" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="byte" genre="user" instance="1" index="1" label="Alarm Level" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="byte" genre="user" instance="1" index="2" label="SourceNodeId" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="byte" genre="user" instance="1" index="11" label="Power Management" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="1" />
</CommandClass>
<CommandClass id="114" name="COMMAND_CLASS_MANUFACTURER_SPECIFIC" version="1" request_flags="4" innif="true">
<Instance index="1" />
</CommandClass>
<CommandClass id="115" name="COMMAND_CLASS_POWERLEVEL" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="system" instance="1" index="0" label="Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Normal" value="0" />
<Item label="-1dB" value="1" />
<Item label="-2dB" value="2" />
<Item label="-3dB" value="3" />
<Item label="-4dB" value="4" />
<Item label="-5dB" value="5" />
<Item label="-6dB" value="6" />
<Item label="-7dB" value="7" />
<Item label="-8dB" value="8" />
<Item label="-9dB" value="9" />
</Value>
<Value type="byte" genre="system" instance="1" index="1" label="Timeout" units="seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="button" genre="system" instance="1" index="2" label="Set Powerlevel" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="byte" genre="system" instance="1" index="3" label="Test Node" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="list" genre="system" instance="1" index="4" label="Test Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Normal" value="0" />
<Item label="-1dB" value="1" />
<Item label="-2dB" value="2" />
<Item label="-3dB" value="3" />
<Item label="-4dB" value="4" />
<Item label="-5dB" value="5" />
<Item label="-6dB" value="6" />
<Item label="-7dB" value="7" />
<Item label="-8dB" value="8" />
<Item label="-9dB" value="9" />
</Value>
<Value type="short" genre="system" instance="1" index="5" label="Frame Count" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
<Value type="button" genre="system" instance="1" index="6" label="Test" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="button" genre="system" instance="1" index="7" label="Report" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="list" genre="system" instance="1" index="8" label="Test Status" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Failed" value="0" />
<Item label="Success" value="1" />
<Item label="In Progress" value="2" />
</Value>
<Value type="short" genre="system" instance="1" index="9" label="Acked Frames" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
</CommandClass>
<CommandClass id="117" name="COMMAND_CLASS_PROTECTION" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="system" instance="1" index="0" label="Protection" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
<Item label="Unprotected" value="0" />
<Item label="Protection by Sequence" value="1" />
<Item label="No Operation Possible" value="2" />
</Value>
</CommandClass>
<CommandClass id="128" name="COMMAND_CLASS_BATTERY" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="byte" genre="user" instance="1" index="0" label="Battery Level" units="%" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="100" />
</CommandClass>
<CommandClass id="129" name="COMMAND_CLASS_CLOCK" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="user" instance="1" index="0" label="Day" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="2" size="1">
<Item label="Monday" value="1" />
<Item label="Tuesday" value="2" />
<Item label="Wednesday" value="3" />
<Item label="Thursday" value="4" />
<Item label="Friday" value="5" />
<Item label="Saturday" value="6" />
<Item label="Sunday" value="7" />
</Value>
<Value type="byte" genre="user" instance="1" index="1" label="Hour" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="18" />
<Value type="byte" genre="user" instance="1" index="2" label="Minute" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
</CommandClass>
<CommandClass id="133" name="COMMAND_CLASS_ASSOCIATION" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Associations num_groups="1">
<Group index="1" max_associations="1" label="Group 1" auto="true">
<Node id="1" />
</Group>
</Associations>
</CommandClass>
<CommandClass id="134" name="COMMAND_CLASS_VERSION" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="string" genre="system" instance="1" index="0" label="Library Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="3" />
<Value type="string" genre="system" instance="1" index="1" label="Protocol Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="6.04" />
<Value type="string" genre="system" instance="1" index="2" label="Application Version" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="1.01" />
</CommandClass>
<CommandClass id="152" name="COMMAND_CLASS_SECURITY" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="bool" genre="system" instance="1" index="0" label="Secured" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
</CommandClass>
</CommandClasses>
</Node>
codepig
February 13, 2022, 1:10am
2
Did you have any luck with this?
jonassam
(Jonas Samuelsson)
February 13, 2022, 6:45pm
3
It turned out that with Z-Wave-JS it worked straight up with no further config needed. Not all features of the AC301 is supported, but it is enough to get it to work as I see it. You can set the setpoint and it reports back the current temperature reading…
Hello Jonas
Did you get your radiator thermostat from Nexa to work fully?
I just started using HA and bought a Nexa thermostat for my water radiators but I don’t seam to be able to set any values on the device. I can only see the current temperature and the setpoint. Even if I change the setpoint it seam to be set in the web gui but it eventually resets to 22 degrees and unprotected.
Did you do any more tricks or have I missunderstood something, like it is not possible to change the setpoint in the gui without creating a rule to transfer the value or something like that.
I see your xml-file but have no idea what to do with it…
jonassam
(Jonas Samuelsson)
September 7, 2022, 2:39pm
5
Hi!
Well, not it works just like it should. I can access it through Z-Wave JS GUI or through HA GUI. It reports the current temperature, and updating the setpoint also works fine. I have not done anything in particular for this to work.
Best regards,
Jonas
davrex
September 18, 2022, 8:01pm
6
Hi i am also have the same problem as @kafferejsarn this is a new problem it works in the spring and now when the cold it getting here it not working it just sets the temp to 22degrees.
jonfe
September 21, 2022, 7:15pm
7
Any luck with this? I have the same problem. 22 degrees is nice but to be able to change it would be nicer.
Hi, another Nexa ZRT-106 user here.
Same as you guys I cant get the unit to accept any settings updates.
I can see in the Z-wave log that the message are sent, and received, and rejected.
Im new to Z-wave so cant determine why the unit will rejects messages to update settings.
Another thing I cant figure out is how to set date/time on the unit. HA GUI has no settings here, and cant find in the manual if there any magic button presses that could be used?
Robert
freshcoast
(Z-Wave AI Bot)
September 23, 2022, 4:18pm
9
Please post the logs.
There’s currently no UI or special service to set the clock. Here’s a discussion on how can set it using HA:
I missed that you can also set the day of the week.
service: zwave_js.invoke_cc_api
data:
command_class: '129'
method_name: set
parameters:
- 17
- 30
- 4
target:
device_id: 944c35a75395d3400c248ba317984b18
Day of week is 1 (Monday), 2 (Tuesday), …, 7 (Sunday).
Also, this conversation is really in the wrong place…
luff
September 25, 2022, 12:00pm
10
Same issue with ZRT-106, using an Aeotec Z-Stick 7. I’ve attached my logs.
Subscribed to Z-Wave JS Log Messages…
2022-09-25T11:33:48.785Z CNTRLR [Node 003] [setValue] calling SET_VALUE API ThermostatSetpointCCAPI:
property: setpoint
property key: 11
optimistic: true
2022-09-25T11:33:48.792Z SERIAL » 0x012200a90103169f03700015dfea74692e04eece34dc7ec3db1314c85a2500000 (36 bytes)
00043c6
2022-09-25T11:33:48.793Z DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 67
└─[Security2CCMessageEncapsulation]
│ sequence number: 112
└─[SupervisionCCGet]
│ session id: 36
│ request updates: true
└─[ThermostatSetpointCCSet]
setpoint type: Energy Save Heating
value: 23 °C
2022-09-25T11:33:48.801Z SERIAL « [ACK] (0x06)
2022-09-25T11:33:48.803Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-25T11:33:48.804Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:48.805Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-25T11:33:50.044Z SERIAL « 0x011d00a94300007a00a87f7f7f7f01010300000000420100007f7f7f7f7fe5 (31 bytes)
2022-09-25T11:33:50.045Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:50.047Z DRIVER « [REQ] [SendDataBridge]
callback id: 67
transmit status: OK, took 1220 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -88 dBm
ACK channel no.: 1
TX channel no.: 1
beam: 1000 ms
2022-09-25T11:33:50.070Z SERIAL « 0x011a00a8000103119f03d700113d44b2e4552158de9cdb51d700a8b0 (28 bytes)
2022-09-25T11:33:50.071Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:50.073Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -88 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 215
└─[SupervisionCCReport]
session id: 36
more updates follow: false
status: Fail
duration: 0s
2022-09-25T11:33:50.075Z CNTRLR [Node 003] [setValue] result of SET_VALUE API call for ThermostatSetpointCCAPI
: (SupervisionResult)
status: Fail
2022-09-25T11:33:50.076Z CNTRLR [Node 003] [setValue] not updating value
2022-09-25T11:33:55.081Z SERIAL » 0x011b00a901030f9f037100bb46d190ac47f89c81d8b725000000004411 (29 bytes)
2022-09-25T11:33:55.082Z DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 68
└─[Security2CCMessageEncapsulation]
│ sequence number: 113
└─[ThermostatSetpointCCGet]
setpoint type: Energy Save Heating
2022-09-25T11:33:55.089Z SERIAL « [ACK] (0x06)
2022-09-25T11:33:55.091Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-25T11:33:55.092Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:55.093Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-25T11:33:56.375Z SERIAL « 0x011d00a94400007e00a87f7f7f7f01010300000000420100007f7f7f7f7fe6 (31 bytes)
2022-09-25T11:33:56.376Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:56.378Z DRIVER « [REQ] [SendDataBridge]
callback id: 68
transmit status: OK, took 1260 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -88 dBm
ACK channel no.: 1
TX channel no.: 1
beam: 1000 ms
2022-09-25T11:33:56.402Z SERIAL « 0x011b00a8000103129f03d800dd2d9cb7dd98d18b13aabe639e1000a89e (29 bytes)
2022-09-25T11:33:56.404Z SERIAL » [ACK] (0x06)
2022-09-25T11:33:56.406Z CNTRLR [Node 003] [translateValueEvent: value updated]
commandClass: Thermostat Setpoint
endpoint: 0
property: setpoint
propertyKey: 11
internal: false
secret: false
event source: undefined
2022-09-25T11:33:56.407Z CNTRLR [Node 003] [~] [Thermostat Setpoint] setpoint[11]: 19 => 19 [Endpoint 0]
2022-09-25T11:33:56.407Z CNTRLR [Node 003] [translateValueEvent: value updated]
is root endpoint: true
is application CC: true
should hide root values: false
2022-09-25T11:33:56.409Z CNTRLR [Node 003] [translateValueEvent: value updated]
commandClass: Thermostat Setpoint
endpoint: 0
property: setpointScale
propertyKey: 11
internal: true
secret: false
event source: undefined
2022-09-25T11:33:56.409Z CNTRLR [Node 003] [~] [Thermostat Setpoint] setpointScale[11] [Endpoint 0] [internal]
: 0 => 0
2022-09-25T11:33:56.410Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -88 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 216
└─[ThermostatSetpointCCReport]
setpoint type: Energy Save Heating
value: 19 °C
Subscribed to Z-Wave JS Log Messages…
2022-09-25T11:54:06.387Z SERIAL » 0x012000a90103149f0372002887739f98c6eb0c59f7db3a2c8904fa25000000004 (34 bytes)
500
2022-09-25T11:54:06.388Z DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 69
└─[Security2CCMessageEncapsulation]
│ sequence number: 114
└─[SupervisionCCGet]
│ session id: 37
│ request updates: true
└─[ClockCCSet]
clock setting: Sunday, 13:53
2022-09-25T11:54:06.395Z SERIAL « [ACK] (0x06)
2022-09-25T11:54:06.397Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-25T11:54:06.398Z SERIAL » [ACK] (0x06)
2022-09-25T11:54:06.399Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-25T11:54:07.616Z SERIAL « 0x011d00a94500007700aa7f7f7f7f01010300000000420100007f7f7f7f7fec (31 bytes)
2022-09-25T11:54:07.618Z SERIAL » [ACK] (0x06)
2022-09-25T11:54:07.620Z DRIVER « [REQ] [SendDataBridge]
callback id: 69
transmit status: OK, took 1190 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -86 dBm
ACK channel no.: 1
TX channel no.: 1
beam: 1000 ms
2022-09-25T11:54:07.642Z SERIAL « 0x011a00a8000103119f03db0036ccd2dc28f25939e538e6c83600aa38 (28 bytes)
2022-09-25T11:54:07.644Z SERIAL » [ACK] (0x06)
2022-09-25T11:54:07.645Z DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -86 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 219
└─[SupervisionCCReport]
session id: 37
more updates follow: false
status: Fail
duration: 0s
jonfe
September 25, 2022, 6:28pm
11
I thought there might be a S2 security issue, and I’ve tried to use a lower security level with the same result. I can’t get the Thermostat to accept any settings. I tried to send different commands manually thru the Z-wave API service, with the same result. I wonder how jonassam got it to work
Hello and thanks for taking the time.
I will check out the date/time thread that you linked.
I agree that this thread no longer should be sorted as “feature request”.
I include the “silly log” of trying to change parameter 1 to the value 20
2022-09-26T18:55:27.261Z CNTRLR [Node 004] [setValue] calling SET_VALUE API ConfigurationCCAPI:
property: 1
property key: undefined
optimistic: true
2022-09-26T18:55:27.280Z SERIAL » 0x012200a90104169f030400e0f22be832fefc375d5877c4c4ec90112fe52500000 (36 bytes)
00009d0
2022-09-26T18:55:27.283Z DRIVER » [Node 004] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 9
└─[Security2CCMessageEncapsulation]
│ sequence number: 4
└─[SupervisionCCGet]
│ session id: 44
│ request updates: true
└─[ConfigurationCCSet]
parameter #: 1
reset to default: false
value size: 2
value format: SignedInteger
value: 20
2022-09-26T18:55:27.291Z SERIAL « [ACK] (0x06)
2022-09-26T18:55:27.295Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-26T18:55:27.296Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:27.299Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-26T18:55:28.582Z SERIAL « 0x011d00a90900007e00a77f7f7f7f01010300000000420100007f7f7f7f7fa4 (31 bytes)
2022-09-26T18:55:28.588Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:28.593Z DRIVER « [REQ] [SendDataBridge]
callback id: 9
transmit status: OK, took 1260 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -89 dBm
ACK channel no.: 1
TX channel no.: 1
beam: 1000 ms
2022-09-26T18:55:28.608Z SERIAL « 0x011a00a8000104119f03780050f34bde703444eeb65511115700a776 (28 bytes)
2022-09-26T18:55:28.614Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:28.617Z DRIVER « [Node 004] [REQ] [BridgeApplicationCommand]
│ RSSI: -89 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 120
└─[SupervisionCCReport]
session id: 44
more updates follow: false
status: Fail
duration: 0s
2022-09-26T18:55:28.625Z CNTRLR [Node 004] [setValue] result of SET_VALUE API call for ConfigurationCCAPI: (Su
pervisionResult)
status: Fail
2022-09-26T18:55:28.627Z CNTRLR [Node 004] [setValue] not updating value
2022-09-26T18:55:29.648Z SERIAL » 0x011b00a901040f9f030500af62c0c5ad595a8bd38a3225000000000a77 (29 bytes)
2022-09-26T18:55:29.651Z DRIVER » [Node 004] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 10
└─[Security2CCMessageEncapsulation]
│ sequence number: 5
└─[ConfigurationCCGet]
parameter #: 1
2022-09-26T18:55:29.656Z SERIAL « [ACK] (0x06)
2022-09-26T18:55:29.660Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-26T18:55:29.662Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:29.664Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-26T18:55:29.679Z SERIAL « 0x011d00a90a00000200a77f7f7f7f01010300000000020100007f7f7f7f7f9b (31 bytes)
2022-09-26T18:55:29.681Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:29.684Z DRIVER « [REQ] [SendDataBridge]
callback id: 10
transmit status: OK, took 20 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -89 dBm
ACK channel no.: 1
TX channel no.: 1
2022-09-26T18:55:29.705Z SERIAL « 0x011b00a8000104129f03790054e9eb388f1f67eca03d9c2bc62b00a7ab (29 bytes)
2022-09-26T18:55:29.710Z SERIAL » [ACK] (0x06)
2022-09-26T18:55:29.716Z CNTRLR [Node 004] [translateValueEvent: value updated]
commandClass: Configuration
endpoint: undefined
property: 1
propertyKey: undefined
internal: false
secret: false
event source: undefined
2022-09-26T18:55:29.718Z CNTRLR [Node 004] [~] [Configuration] 1: 120 => 120
2022-09-26T18:55:29.720Z CNTRLR [Node 004] [translateValueEvent: value updated]
is root endpoint: true
is application CC: true
should hide root values: false
2022-09-26T18:55:29.723Z DRIVER « [Node 004] [REQ] [BridgeApplicationCommand]
│ RSSI: -89 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 121
└─[ConfigurationCCReport]
parameter #: 1
value size: 2
value: 120
edit:
The device doesnt seem to accept changes in date either, heres the log:
type or paste code here2022-09-26T19:28:02.139Z SERIAL » 0x012000a90104149f0307003e10254b7bfccdc21cff418cad789d6725000000000 (34 bytes)
d1d
2022-09-26T19:28:02.142Z DRIVER » [Node 004] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 13
└─[Security2CCMessageEncapsulation]
│ sequence number: 7
└─[SupervisionCCGet]
│ session id: 46
│ request updates: true
└─[ClockCCSet]
clock setting: Monday, 21:26
2022-09-26T19:28:02.148Z SERIAL « [ACK] (0x06)
2022-09-26T19:28:02.152Z SERIAL « 0x010401a90152 (6 bytes)
2022-09-26T19:28:02.154Z SERIAL » [ACK] (0x06)
2022-09-26T19:28:02.156Z DRIVER « [RES] [SendDataBridge]
was sent: true
2022-09-26T19:28:03.416Z SERIAL « 0x011d00a90d00007c00a67f7f7f7f01010300000000420100007f7f7f7f7fa3 (31 bytes)
2022-09-26T19:28:03.419Z SERIAL » [ACK] (0x06)
2022-09-26T19:28:03.423Z DRIVER « [REQ] [SendDataBridge]
callback id: 13
transmit status: OK, took 1240 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI: -90 dBm
ACK channel no.: 1
TX channel no.: 1
beam: 1000 ms
2022-09-26T19:28:03.442Z SERIAL « 0x011a00a8000104119f037e006a5120c82c6de585fe2880568800a667 (28 bytes)
2022-09-26T19:28:03.445Z SERIAL » [ACK] (0x06)
2022-09-26T19:28:03.447Z DRIVER « [Node 004] [REQ] [BridgeApplicationCommand]
│ RSSI: -90 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 126
└─[SupervisionCCReport]
session id: 46
more updates follow: false
status: Fail
duration: 0s
Manuals:
Everspring AC301-1: https://manual.zwave.eu/backend/make.php?lang=en&sku=AC301-1&cert=ZC10-19126824
Nexa ZRT-106: https://manual.zwave.eu/backend/make.php?lang=en&sku=ZRT-106&cert=ZC10-22067099
Everspring AC301: Z-Wave JS Config DB Browser
jonfe
September 30, 2022, 4:44pm
13
Yes, this conversation should be moved to Zwave JS issues instead? I have contacted the manufacturer and after a while they found that with an old z-wave JS version there was no problems(don’t know which version they used) , but with the new version. So either there is a z-wave js problem or the thermostat firmware needs upgrade. Can someone verify this. Has anyone got the thermostat to work with the latest z-wave js version?
Is it possible to install an older version for debugging?
Is it possible that this issue is fixed?
I found this update relase from last week:
# Changelog
[Older changelog entries (v1...v8)](CHANGELOG_v8.md)
<!--
Add placeholder for next release with `wip` snippet
-->
## 10.3.0 (2022-09-29)
### Features
* Support opt-in to receive beta firmware releases via the update service (#5076)
* Implement Schedule Entry Lock CC (#4836)
* Sequencing of multi-target firmware updates is now handled in the driver, including waiting between targets, and re-interviewing only after the last one (#5121)
### Bugfixes
* Pin `xstate` dependency to version `4.29.0` to avoid a memory leak (#5108)
* Fix: the `ccId` parameter in the `CommandClass` constructor may be zero (#5115)
* Fixed an issue where multiple re-interview tasks for sleeping nodes could be queued and would be executed in parallel (#5105)
* Fixed an issue where firmware updates could use a too large fragment size after upgrading to v10, causing the update to fail (#5117)
### Config file changes
* Disable Supervision for Everspring AC301 (#5119)
This file has been truncated. show original
10.3.0 (2022-09-29)
onfig file changes
Disable Supervision for Everspring AC301 (#5119 )
Based on this issue that describes the same as we are discussing:
opened 10:26AM - 26 Sep 22 UTC
closed 03:27PM - 26 Sep 22 UTC
bug
config âš™
### Checklist
- [X] I am not using Home Assistant. Or: a developer has told me… to come here.
- [X] I have checked the troubleshooting section and my problem is not described there.
- [X] I have read the changelog and my problem is not mentioned there.
### Deploy method
Docker
### Z-Wave JS UI version
8.0.0
### ZwaveJS version
10.2.0
### Describe the bug
After upgrading to version 8.0.0 I found that I could no longer control my Everspring AC301. Values are still being reported in the GUI when they update. For example, the mode and temperature are updated when I change it manually on the device, but I cannot send any instructions to it from zwavejs2mqtt. I had not updated for a long time, and I don't know which version I ran before, but I tried to roll back to version 6.0.0 and then it started working again, but then after going back to 8.0.0 it stopped working.
Could it be related to this?: https://forum.z-wave.me/viewtopic.php?t=35497
### To Reproduce
Inlcude Everspring AC301 in zwavejs2mqtt version 8.0.0 and try to change any value from the GUI.
### Expected behavior
Changes in the GUI should update the device
### Additional context
Debug log when trying to change mode from "Heat" to "Off"
```
2022-09-26 12:11:05.097 INFO Z-WAVE: Calling api writeValue with args: [
{ nodeId: 4, commandClass: 64, endpoint: 0, property: 'mode' },
0,
{},
[length]: 3
]
2022-09-26 12:11:05.101 INFO Z-WAVE: Writing 0 to 4-64-0-mode
2022-09-26T10:11:05.128Z SERIAL » 0x010a001304039f01fc2509af (12 bytes)
2022-09-26T10:11:05.129Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 9
└─[Security2CCNonceGet]
sequence number: 252
2022-09-26T10:11:05.145Z SERIAL « [ACK] (0x06)
2022-09-26T10:11:05.151Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-26T10:11:05.151Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:05.152Z DRIVER « [RES] [SendData]
was sent: true
2022-09-26T10:11:06.432Z SERIAL « 0x010700130900008163 (9 bytes)
2022-09-26T10:11:06.432Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:06.435Z DRIVER « [REQ] [SendData]
callback id: 9
transmit status: OK
2022-09-26T10:11:06.458Z SERIAL « 0x011a00040004149f0270016cda089fc6a69d3ff06067155252b45ef6 (28 bytes)
2022-09-26T10:11:06.459Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:06.463Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 112
SOS: true
MOS: false
receiver entropy: 0x6cda089fc6a69d3ff06067155252b45e
2022-09-26T10:11:06.478Z SERIAL » 0x012c001304259f03fd011241f9593680acb31ca39ac28902e47ecdc1756421540 (46 bytes)
ebc4c74eb601b00e9920d250a06
2022-09-26T10:11:06.482Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 10
└─[Security2CCMessageEncapsulation]
│ sequence number: 253
│ extensions:
│ · type: SPAN
│ sender EI: 0xf9593680acb31ca39ac28902e47ecdc1
└─[SupervisionCCGet]
│ session id: 49
│ request updates: true
└─[ThermostatModeCCSet]
mode: Off
2022-09-26T10:11:06.497Z SERIAL « [ACK] (0x06)
2022-09-26T10:11:06.498Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-26T10:11:06.499Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:06.500Z DRIVER « [RES] [SendData]
was sent: true
2022-09-26T10:11:06.517Z SERIAL « 0x010700130a000003e2 (9 bytes)
2022-09-26T10:11:06.517Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:06.518Z DRIVER « [REQ] [SendData]
callback id: 10
transmit status: OK
2022-09-26T10:11:06.571Z SERIAL « 0x011700040004119f0371003669e94c7af4aaba47c545559173 (25 bytes)
2022-09-26T10:11:06.572Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:06.573Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 113
└─[SupervisionCCReport]
session id: 49
more updates follow: false
status: Fail
duration: 0s
2022-09-26 12:11:06.578 INFO Z-WAVE: Success zwave api call writeValue true
2022-09-26T10:11:11.588Z SERIAL » 0x01150013040e9f03fe00e54c02f25dc0680ded2c250bdf (23 bytes)
2022-09-26T10:11:11.594Z DRIVER » [Node 004] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 11
└─[Security2CCMessageEncapsulation]
│ sequence number: 254
└─[ThermostatModeCCGet]
2022-09-26T10:11:11.597Z SERIAL « [ACK] (0x06)
2022-09-26T10:11:11.602Z SERIAL « 0x0104011301e8 (6 bytes)
2022-09-26T10:11:11.607Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:11.609Z DRIVER « [RES] [SendData]
was sent: true
2022-09-26T10:11:12.913Z SERIAL « 0x010700130b00008464 (9 bytes)
2022-09-26T10:11:12.915Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:12.918Z DRIVER « [REQ] [SendData]
callback id: 11
transmit status: OK
2022-09-26T10:11:12.941Z SERIAL « 0x0115000400040f9f0372008686c4e45d8df5c19b749aba (23 bytes)
2022-09-26T10:11:12.943Z SERIAL » [ACK] (0x06)
2022-09-26T10:11:12.944Z CNTRLR [Node 004] [~] [Thermostat Mode] mode: 1 => 1 [Endpoint 0]
2022-09-26 12:11:12.945 INFO Z-WAVE: Node 4: value updated: 64-0-mode 1 => 1
2022-09-26T10:11:12.946Z DRIVER « [Node 004] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 114
└─[ThermostatModeCCReport]
mode: Heat
```
Z-wave.me forum post:
Nexa ZRT-106 / Everspring AC301 - forum
Seems like a bug on the device for “supervision” that known for several other devices.
Hopefully I will find a free evening this week, but if anyone can use this to solve it please let ut know
HA issue:
opened 07:59PM - 14 Sep 22 UTC
integration: zwave_js
### The problem
In April or may I set all the thermostat on 14C. Now when I w… ant to change to an higher degree (or any other parameters) on the thermostat I can’t get it through. It always has the old settings.
I can se the history from the thermostat. When I manual change the temperature on the thermostat can i see it in home assistant, but the default parameters say that will go back to the original after 4 hours.
I have try
-change the battery on the thermostat.
-reinstall both home assistant 7.6 and 8.5
-exclude and include the device
-factory reset the Z-Stick Gen5+
Nothing work.
I have some telldus switch that work just fine.
That I have:
Raspberry pi 4
Aeotec zw090+
danfoss thermostat
Nexa zrt-106 thermostat
Home assistant 7.6 and 8.5
Telldus 313510 ( that work fine)
### What version of Home Assistant Core has the issue?
8.5
### What was the last working version of Home Assistant Core?
I find my old raspberry pi 3 and everything work with it.
Home assistant OS 7.5
Core-2022.3.7
Z-wave js 0.1.55
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
Z-wave
### Link to integration documentation on our website
_No response_
### Diagnostics information
Can’t find
### Example YAML snippet
```yaml
-
```
### Anything in the logs that might be useful for us?
```txt
No
```
### Additional information
-
jonfe
October 4, 2022, 5:40pm
15
It definitely sounded like our problem and with the new z-wave JS update distributed today there was good hope that the problem was solved, but … no, not for me anyway.
I still can’t change any parameters. If you succeed , please let us know.
freshcoast
(Z-Wave AI Bot)
October 4, 2022, 6:01pm
16
Did you re-interview the device?
1 Like
jonfe
October 4, 2022, 6:27pm
17
Ahhh, I forgot! Made a complete reboot, but forgot to re-interview. Now it works. Great! Thank you for your help.
1 Like
davrex
October 17, 2022, 1:40pm
18
Nice that fixed my problems to.
filikun
(Filikun)
February 9, 2023, 9:39am
20
Is anyone using this one successfully with Better thermostat integration? One of mine is working like a charm but the other one is struggling and for some reason falls off and get’s stuck on full blast.
Something happened with the latest Z-wave JS update that broke one of my two TRV. After re-interview it shows up with some more settings and sensors for some reason. New is a “RF protection state” and rechagable, used as backup, overheating, fluid is low, battery is disconnected and battery temperature is low" they are all Unknown so I don’t know what’s happening here.