Setting controller mode or set point not working from Domoticz #6

FrankvdAa · 2021-02-14T20:23:02Z

Hi,

I bought a NanoCUL a few months back to be able to control my Evohome from Domoticz.

Have been able to discover all valve, but I'm not able to set the controller mode (normal, economy, off, ...) or set points.

I do see Domoticz sending the command, but don't see any response to that:

000 W --- 18:003618 01:204708 --:------ 2E04 008 01FFFFFFFFFFFF00
000 W --- 18:003618 01:204708 --:------ 2E04 008 00FFFFFFFFFFFF00

Somebody I know has a real HGI80 and he sees the following when changing controller mode:

095 W --- 18:012786 01:072015 --:------ 2E04 008 01FFFFFFFFFFFF00
049 I --- 01:072015 --:------ 01:072015 2E04 008 01FFFFFFFFFFFF00
047 I --- 01:072015 01:072015 --:------ 2E04 008 01FFFFFFFFFFFF00
095 W --- 18:012786 01:072015 --:------ 2E04 008 00FFFFFFFFFFFF00
049 I --- 01:072015 --:------ 01:072015 2E04 008 00FFFFFFFFFFFF00
047 I --- 01:072015 01:072015 --:------ 2E04 008 00FFFFFFFFFFFF00

Not sure what the three digits at the beginning of each line represent, but I noticed that in my setup it's always 000 when the second column is showing 'W'.

I understood that TX should be working with the latest firmware, or am I wrong?

Please let me know if you need me to run any tests or in case you need more information.

Thanks,

Frank

ghoti57 · 2021-02-15T08:20:41Z

The 3 digits at the front of the message indicate the signal strength of the received messages (RSSI). Low numbers are better than high numbers.

The HGI80 prints a non-zero value (always the same) when it TXs a message, Evofw3 always prints zero. neither value makes more sense than the other because RSSI can only be measured by the RX device. It does make TX message much more visible in evofw3 though.

ghoti57 · 2021-02-15T08:20:51Z

Not a bug :-)

ghoti57 · 2021-02-15T08:21:38Z

What version of evofw3 are you running?

FrankvdAa · 2021-02-15T08:28:24Z

Running latest version (v0.6.7) as of yesterday. Updated before running above tests. Haven't seen it working, even with older versions.

Any idea why my Evohome is not responding to those set requests? Where should I start looking?

ghoti57 · 2021-02-15T08:37:25Z

My first thought is that the nanoCUL is not close enough to the controller.
I'm not aware of any reason why 0.6.7 should not work.

Do you have any logs that include other messages from the controller?

FrankvdAa · 2021-02-15T08:43:32Z

Distance between controller and nanoCUL is about 1-1.5m so I would expect that to be okay.

I will add some logs later today.

ghoti57 · 2021-02-15T08:56:22Z

Logs with timestamps of possible.

…

On 15 Feb 2021, 08:43, at 08:43, FrankvdAa ***@***.***> wrote: Distance between controller and nanoCUL is about 1-1.5m so I would expect that to be okay. I will add some logs later today. -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: #6 (comment)

FrankvdAa · 2021-02-15T11:01:49Z

Here's a log with timestamps:

2021-02-15 11:54:12 >> 035 I --- 01:204708 --:------ 01:204708 1F09 003 FF073A
2021-02-15 11:54:12 >> 035 I --- 01:204708 --:------ 01:204708 2309 027 00076C0105DC02076C0303E80403E80503E80605DC07064008076C
2021-02-15 11:54:12 >> 036 I --- 01:204708 --:------ 01:204708 30C9 027 0007760106CE02074C03061A0405860505BA06062B07061008075F
2021-02-15 11:54:31 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 00
2021-02-15 11:54:32 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 01
2021-02-15 11:54:33 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:54:33 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 02
2021-02-15 11:54:35 >> 035 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:54:35 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 04
2021-02-15 11:54:36 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 05
2021-02-15 11:54:37 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:54:37 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 06
2021-02-15 11:54:38 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 07
2021-02-15 11:54:39 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 08
2021-02-15 11:54:40 >> 000 RQ --- 18:003618 01:204708 --:------ 1260 001 00
2021-02-15 11:55:15 >> 035 RQ --- 01:204708 10:030173 --:------ 22D9 001 00
2021-02-15 11:55:15 >> 064 RP --- 10:030173 01:204708 --:------ 22D9 003 001E82
2021-02-15 11:55:16 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0000050000
2021-02-15 11:55:16 >> 066 RP --- 10:030173 01:204708 --:------ 3220 005 00C00500FF
2021-02-15 11:55:16 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0000110000
2021-02-15 11:55:16 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C0110000
2021-02-15 11:55:16 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0000120000
2021-02-15 11:55:16 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C0120600
2021-02-15 11:55:16 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0080130000
2021-02-15 11:55:16 >> 066 RP --- 10:030173 01:204708 --:------ 3220 005 00C01347AB
2021-02-15 11:55:16 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0080190000
2021-02-15 11:55:16 >> 066 RP --- 10:030173 01:204708 --:------ 3220 005 0040194D00
2021-02-15 11:55:17 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 00801A0000
2021-02-15 11:55:17 >> 065 RP --- 10:030173 01:204708 --:------ 3220 005 00C01A47AB
2021-02-15 11:55:17 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 00801C0000
2021-02-15 11:55:17 >> 065 RP --- 10:030173 01:204708 --:------ 3220 005 00C01C47AB
2021-02-15 11:55:17 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0080730000
2021-02-15 11:55:17 >> 066 RP --- 10:030173 01:204708 --:------ 3220 005 00B0730000
2021-02-15 11:55:24 >> 067 I --- 10:030173 --:------ 10:030173 1FD4 003 004828
2021-02-15 11:55:33 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:55:33 >> 067 RP --- 10:030173 01:204708 --:------ 3EF0 009 0000100A00FF034E00
2021-02-15 11:56:33 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:56:33 >> 067 RP --- 10:030173 01:204708 --:------ 3EF0 009 0000100A00FF034E00
2021-02-15 11:56:42 >> 044 I --- 02:004323 --:------ 01:204708 3150 002 0886
2021-02-15 11:56:48 >> 044 I --- 02:004323 --:------ 02:004323 0008 002 FC00
2021-02-15 11:56:48 >> 044 I --- 02:004323 --:------ 02:004323 3150 002 FC86
2021-02-15 11:57:17 >> 036 I --- 01:204708 --:------ 01:204708 1F09 003 FF073A
2021-02-15 11:57:17 >> 036 I --- 01:204708 --:------ 01:204708 2309 027 00076C0105DC02076C0303E80403E80503E80605DC07064008076C
2021-02-15 11:57:17 >> 036 I --- 01:204708 --:------ 01:204708 30C9 027 0007760106CE02074C03061A0405860505BA06062B07061008075F
2021-02-15 11:57:33 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:57:33 >> 067 RP --- 10:030173 01:204708 --:------ 3EF0 009 0000100A00FF034E64
2021-02-15 11:57:49 >> 043 I --- 02:004323 --:------ 02:004323 0008 002 FA00
2021-02-15 11:57:49 >> 043 I --- 02:004323 --:------ 02:004323 22D0 004 00000002
2021-02-15 11:57:57 >> 067 I --- 10:030173 --:------ 10:030173 1FD4 003 004829
2021-02-15 11:58:07 >> 063 I --- 04:009093 --:------ 04:009093 30C9 003 000629
2021-02-15 11:58:31 >> 071 I --- 34:038973 --:------ 34:038973 30C9 003 000760
2021-02-15 11:58:34 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:58:34 >> 067 RP --- 10:030173 01:204708 --:------ 3EF0 009 0000100A00FF034E64
2021-02-15 11:59:31 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 00
2021-02-15 11:59:32 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 01
2021-02-15 11:59:33 >> 075 I --- 04:009067 --:------ 04:009067 30C9 003 000625
2021-02-15 11:59:33 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 02
2021-02-15 11:59:34 >> 035 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:59:34 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 03
2021-02-15 11:59:35 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 04
2021-02-15 11:59:36 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:59:36 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 05
2021-02-15 11:59:37 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 06
2021-02-15 11:59:38 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 11:59:38 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 07
2021-02-15 11:59:39 >> 000 RQ --- 18:003618 01:204708 --:------ 30C9 001 08
2021-02-15 11:59:40 >> 000 RQ --- 18:003618 01:204708 --:------ 1260 001 00
2021-02-15 11:59:41 >> 000 W --- 18:003618 01:204708 --:------ 2E04 008 02FFFFFFFFFFFF00
2021-02-15 11:59:47 >> 000 W --- 18:003618 01:204708 --:------ 2E04 008 07FFFFFFFFFFFF00
2021-02-15 11:59:54 >> 000 W --- 18:003618 01:204708 --:------ 2E04 008 03FFFFFFFFFFFF00
2021-02-15 12:00:00 >> 000 W --- 18:003618 01:204708 --:------ 2E04 008 00FFFFFFFFFFFF00
2021-02-15 12:00:17 >> 036 RQ --- 01:204708 10:030173 --:------ 22D9 001 00
2021-02-15 12:00:17 >> 068 RP --- 10:030173 01:204708 --:------ 22D9 003 001E82
2021-02-15 12:00:17 >> 035 RQ --- 01:204708 10:030173 --:------ 3220 005 0000050000
2021-02-15 12:00:18 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C00500FF
2021-02-15 12:00:18 >> 035 RQ --- 01:204708 10:030173 --:------ 3220 005 0000110000
2021-02-15 12:00:18 >> 066 RP --- 10:030173 01:204708 --:------ 3220 005 00C0110000
2021-02-15 12:00:18 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0000120000
2021-02-15 12:00:18 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C0120600
2021-02-15 12:00:18 >> 035 RQ --- 01:204708 10:030173 --:------ 3220 005 0080130000
2021-02-15 12:00:18 >> 068 RP --- 10:030173 01:204708 --:------ 3220 005 00C01347AB
2021-02-15 12:00:18 >> 035 RQ --- 01:204708 10:030173 --:------ 3220 005 0080190000
2021-02-15 12:00:18 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 0040195000
2021-02-15 12:00:18 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 00801A0000
2021-02-15 12:00:19 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C01A47AB
2021-02-15 12:00:19 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 00801C0000
2021-02-15 12:00:19 >> 067 RP --- 10:030173 01:204708 --:------ 3220 005 00C01C47AB
2021-02-15 12:00:19 >> 036 RQ --- 01:204708 10:030173 --:------ 3220 005 0080730000
2021-02-15 12:00:19 >> 068 RP --- 10:030173 01:204708 --:------ 3220 005 0070730000
2021-02-15 12:00:22 >> 035 I --- 01:204708 --:------ 01:204708 1F09 003 FF073A
2021-02-15 12:00:22 >> 036 I --- 01:204708 --:------ 01:204708 2309 027 00076C0105DC02076C0303E80403E80503E80605DC07064008076C
2021-02-15 12:00:22 >> 036 I --- 01:204708 --:------ 01:204708 30C9 027 0007760106CE02074C03061A0405860505BA060629070625080760
2021-02-15 12:00:22 >> 061 I --- 04:007040 --:------ 01:204708 2309 003 0303E8
2021-02-15 12:00:29 >> 067 I --- 10:030173 --:------ 10:030173 1FD4 003 00482A
2021-02-15 12:00:38 >> 036 RQ --- 01:204708 10:030173 --:------ 3EF0 001 00
2021-02-15 12:00:38 >> 066 RP --- 10:030173 01:204708 --:------ 3EF0 009 0000100A00FF034E64

Just before 12:00:00 you can see me changing the controller mode a few times.

ghoti57 · 2021-02-15T17:52:52Z

I don't know why this isn't working. I'm in regular contact with at least one other Domoticz user who is not reporting this problem.

Have you raised this problem on Domoticz or other forums where other users have indicated they're using evofw3?
If so which ones?

FrankvdAa · 2021-02-15T17:59:11Z

No, only reported it here because I see the command to set the controller mode coming from Domoticz.

Therefor I thought it had to be related to evofw3 firmware, but as I don't fully know how it's working I might be wrong here ;-)

I guess all other data is only RX which seems to be working fine.

FrankvdAa · 2021-02-15T18:53:39Z

I've installed evohome-listener and that is also reporting an error:

2021-02-15 19:51:39 |1/042| ZONE_HEAT_DEMAND | I | 02:004323 -> CONTROLLER | 54.0% [Zone 9 ]
2021-02-15 19:51:39 |1/042| ZONE_HEAT_DEMAND | I | UFH 02:004323 -> BROADCAST MESSAGE | 54.0% [Zone 1 ]
2021-02-15 19:51:55 |1/043| SETPOINT_UFH | I | UFH 02:004323 -> BROADCAST MESSAGE | 19.00°C [Zone 1 ]
2021-02-15 19:52:06 |1/038| SYNC | I | CONTROLLER -> BROADCAST MESSAGE | Next sync at 19:55:11 (in 185.0 secs)
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 19.00°C [Zone 1 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 15.00°C [Zone 2 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 19.00°C [Zone 3 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 10.00°C [Zone 4 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 10.00°C [Zone 5 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 10.00°C [Zone 6 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 15.00°C [Zone 7 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 16.00°C [Zone 8 ]
2021-02-15 19:52:06 |1/038| SETPOINT_CTL | I | CONTROLLER -> BROADCAST MESSAGE | 19.00°C [Zone 9 ]
2021-02-15 19:52:07 |1/037| ZONE_TEMPERATURE | I | CONTROLLER -> BROADCAST MESSAGE | 20.08°C [Zone 1 ]
2021-02-15 19:52:07 | | ERROR | '1' on line 723 [Command ZONE_TEMPERATURE, data: '--- 037 I --- 01:204708 --:------ 01:204708 30C9 027 0007D80107640207A90306530405C60505FB06064D070621080788', port: 1]
Traceback (most recent call last):
File "evogateway.py", line 723, in process_received_message
COMMANDSmsg.command_code
File "evogateway.py", line 904, in zone_temperature
mqtt_publish("{}/{}".format(zones[zone_id], msg.source_name), "temperature",temperature)
KeyError: 1

2021-02-15 19:52:16 |1/042| RELAY_HEAT_DEMAND | I | UFH 02:004323 -> BROADCAST MESSAGE | 100.0% @ OTB OpenTherm Bridge
2021-02-15 19:52:16 |1/043| ZONE_HEAT_DEMAND | I | UFH 02:004323 -> BROADCAST MESSAGE | 54.0% [Zone 252]
2021-02-15 19:52:18 |1/038| ACTUATOR_STATE | RQ| CTL 01:204708 -> OTB 10:030173 | Request actuator state update
2021-02-15 19:52:18 |1/073| ACTUATOR_STATE | RP| OTB 10:030173 -> CONTROLLER | OFF

Don't know if it is somehow related, but I'll take that up with the maintainer of evohome-listener in parallel.

ghoti57 · 2021-02-15T18:57:28Z

Please confirm the version of evofw3 by obtaining the first line of the raw output from the nanoCUL after you connect the serial port. Use the arduino Serial monitor.

FrankvdAa · 2021-02-15T19:07:37Z

This is what I get through Arduino Serial Monitor:

20:07:00.421 -> �# evofw3 0.6.7

FrankvdAa · 2021-02-15T19:09:44Z

Can I somehow send the command to set controller mode through Arduino Serial Monitor?

ghoti57 · 2021-02-15T19:52:06Z

Cut and paste a message from your log. Everything after the 000

…

On 15 Feb 2021, 19:10, at 19:10, FrankvdAa ***@***.***> wrote: Can I somehow send the command to set controller mode through Arduino Serial Monitor? -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: #6 (comment)

ghoti57 · 2021-02-15T19:56:05Z

Make sure you set the serial monitor line ending to CR&NL

…

On 15 Feb 2021, 19:10, at 19:10, FrankvdAa ***@***.***> wrote: Can I somehow send the command to set controller mode through Arduino Serial Monitor? -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: #6 (comment)

ghoti57 · 2021-02-15T20:01:34Z

FYI evohome_rf is getting far more development effort than evohome_listener

FrankvdAa · 2021-02-15T20:04:18Z

Sending below message through Arduino Serial Monitor is showing the same:
W --- 18:003618 01:204708 --:------ 2E04 008 00FFFFFFFFFFFF00
W --- 18:003618 01:204708 --:------ 2E04 008 01FFFFFFFFFFFF00

FYI evohome_rf is getting far more development effort than evohome_listener

Thanks, I'll look into that also then ;-)

ghoti57 · 2021-02-15T20:06:24Z

I don't know why this isn't working. You might ask at evohome_rf if they have ideas.

ghoti57 · 2021-02-15T20:11:19Z

Where did you buy the nanoCUL

FrankvdAa · 2021-02-15T20:13:45Z

Bought it from eBay, German reseller:

FrankvdAa · 2021-02-15T20:13:52Z

https://www.ebay.nl/itm/nanoCUL-USB-Stick-FTDI-CC1101-868MHz-FW-1-67-Knick-Antenne-FHEM-CUL-868-Adapter/372221622516?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

FrankvdAa · 2021-02-15T20:22:59Z

Beginning to think it might be hardware related.

Now running evohome_rf and every 'send_data' call is being retried 3 times and then I receive a timeout:

FrankvdAa · 2021-02-15T20:23:10Z

21:20:44.166 PktProtocolQos.send_data(RQ|01:204708|10E0|00): boff=1, want=RQ|01:204708|10E0|00, tout=2021-02-15 21:20:44.266409: RE-SENT (1/3)
21:20:44.204 || HGI:003618 | CTL:204708 | RQ | device_info | 00 || {}
21:20:44.611 PktProtocolQos.send_data(RQ|01:204708|10E0|00): boff=2, want=RQ|01:204708|10E0|00, tout=2021-02-15 21:20:44.810766: RE-SENT (2/3)
21:20:44.636 || HGI:003618 | CTL:204708 | RQ | device_info | 00 || {}
21:20:45.443 PktProtocolQos.send_data(RQ|01:204708|10E0|00): boff=3, want=RQ|01:204708|10E0|00, tout=2021-02-15 21:20:45.843070: RE-SENT (3/3)
21:20:45.485 || HGI:003618 | CTL:204708 | RQ | device_info | 00 || {}
21:20:47.090 PktProtocolQos.send_data(RQ|01:204708|10E0|00): boff=3, want=RP|01:204708|10E0|00, tout=2021-02-15 21:20:47.086022: EXPIRED

ghoti57 · 2021-02-15T20:29:35Z

Do you have a voltmeter. Can you check connection between Nano D3/D4 and cc1101 GDO0/GDO2

FrankvdAa · 2021-02-15T20:37:37Z

Do you have a voltmeter. Can you check connection between Nano D3/D4 and cc1101 GDO0/GDO2

Do have a volt meter, but nanoCUL is shrinkwrapped so cannot access the tracks with my meter.

My nanoCUL has a circuitboard between Arduino and CC1101.

Am I right when saying that D4 is not used and D3 is connected to GDO2? Can't see where GDO0 is going, also seems not to be connected.

ghoti57 · 2021-02-15T20:40:18Z

D4 is not connected. If D3 is connected to GDO2 then D2 should be connected to GDO0.
Can you pierce wrap with needles. If so try to test connection on cc1101 board not on daughter board.

ghoti57 · 2021-02-15T20:42:08Z

Forget tracks just go for nano pins and cc1101 connections

ghoti57 · 2021-02-22T12:33:11Z

And while I'm here, You should get into the habit of always using the evofw3 board definitions to build the firmware. I think there's a change that's about to come that will stop the code building properly using the Arduino board definitions.

iMiMx · 2021-02-22T13:03:00Z

I can only say that by following the steps I set out above, I've gone from having absolutely no responses to RQs on any evofw3 firmware, to pretty much (as far as I can see) getting a response every single time.

HA can now query the controller at start up, I can make zone overrides every time, I see less 'Expired' notices in my logs - the latter I believe, although understand there might be other unknown variables, was one of the key differences between the 3 autotuned frequencies I ended up with, consistency of operation.

2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Controller, id={"01:050858": {"controller": "01:050858", "system": {"heating_relay": null}, "orphans": ["30:177552"], "stored_hotwater": {"hotwater_sensor": "07:014869", "hotwater_valve": "13:215029", "heating_valve": "13:246213"}, "underfloor_heating": {}, "zones": {"00": {"heating_type": "radiator_valve", "sensor": "22:245508", "devices": ["04:055594"]}, "01": {"heating_type": "radiator_valve", "sensor": "22:245512", "devices": ["04:055596", "22:245512"]}, "02": {"heating_type": "radiator_valve", "sensor": "04:055510", "devices": ["04:055510"]}, "03": {"heating_type": "radiator_valve", "sensor": "04:055480", "devices": []}, "04": {"heating_type": "radiator_valve", "sensor": "22:245517", "devices": ["04:055506"]}, "05": {"heating_type": "radiator_valve", "sensor": "04:055486", "devices": ["04:055486"]}, "06": {"heating_type": "radiator_valve", "sensor": "04:055482", "devices": ["04:055482"]}, "07": {"heating_type": "radiator_valve", "sensor": null, "devices": ["04:055600"]}}}}
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=00, name=Living Room
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=01, name=Front Room
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=02, name=Utility
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=03, name=Guest Bed
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=04, name=Master Bed
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=05, name=XX Office
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=06, name=X Office
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.climate] Found a Zone (radiator_valve), id=07, name=Hallway
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.water_heater] Found a Water Heater (stored DHW), id=HW, name=Stored HW
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055594, zone=00
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055596, zone=01
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055510, zone=02
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055480, zone=03
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055506, zone=04
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055486, zone=05
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055482, zone=06
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=04:055600, zone=07
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (heat demand), id=01:050858, zone=FF
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (relay demand), id=13:215029, zone=FA
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (relay demand), id=13:246213, zone=F9
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=07:014869, zone=FA
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055594, zone=00
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=22:245508, zone=00
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055596, zone=01
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=22:245512, zone=01
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055510, zone=02
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055480, zone=03
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055506, zone=04
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=22:245517, zone=04
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055486, zone=05
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055482, zone=06
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temp), id=04:055600, zone=07
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (actuator), id=13:215029, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (actuator), id=13:246213, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=07:014869, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055594, zone=01:050858_01:050858_00 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=22:245508, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055596, zone=01:050858_01:050858_01 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=22:245512, zone=01:050858_01:050858_01 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055510, zone=01:050858_01:050858_02 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055480, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055506, zone=01:050858_01:050858_04 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=22:245517, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055486, zone=01:050858_01:050858_05 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055482, zone=01:050858_01:050858_06 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (battery), id=04:055600, zone=01:050858_01:050858_07 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055594, zone=01:050858_01:050858_00 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055596, zone=01:050858_01:050858_01 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055510, zone=01:050858_01:050858_02 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055480, zone=None
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055506, zone=01:050858_01:050858_04 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055486, zone=01:050858_01:050858_05 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055482, zone=01:050858_01:050858_06 (RAD)
2021-02-22 13:13:51 INFO (MainThread) [custom_components.evohome_cc.binary_sensor] Found a Binary Sensor (window), id=04:055600, zone=01:050858_01:050858_07 (RAD)

domb80 · 2021-02-22T13:05:42Z

I have sent my device to ghoti57. I did get the odd response in the packet log for the first few minutes, but a lot of things were missing and/or replying after 3 RQ resends. The controller config never downloaded completely even in the same room as the unit. I never got around to trying the calibrate branch.

…

On Mon, Feb 22, 2021 at 1:03 PM iMx ***@***.***> wrote: I can only say that by following the steps I set out above, I've gone from having absolutely no responses to RQs on any evofw3 firmware, to pretty much (as far as I can see) getting a response every single time. HA can now query the controller at start up, I can make zone overrides every time, I see less 'Expired' notices in my logs - the latter I believe, although understand there might be other unknown variables, was one of the key differences between the 3 autotuned frequencies I ended up with, consistency of operation. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AROO5TVBVIXKDJZKLYXTNLTTAJIZZANCNFSM4XTSEJEQ> .

danrp-git · 2021-02-22T15:07:45Z

@iMiMx Your description of the necessary process using your HA system is accurate.

The !CS command is redundant. All the data you need is saved by !FS

You can check whether autotune is complete at any time by !F
If it's still tuning it will say so.

There is no difference between evofw2 and evofw3 about how the frequency is initially set.

The reason I've started to introduce the autotune process is that we discovered the 26MHz crystals being used on some cc1101 modules were too inaccurate. This resulted in the carrier signal being selected by the cc1101 being too far away from the expected 868.3MHz.

For instance, given your apparent sweet spot of F=2165db ( which is pretty much the same value you got 5 days ago)
The frequency of the 26MHz crystal appears to be 25,998,657 Hz (i.e. 26MHz - 1343Hz )

This may not sound much but it's sufficient to cause lots of problems. The cc1101 specification states a tolerance of 40ppm for the crystal frequency. This is 26MHz +/- 1040Hz and your crystal is outside that range.

Autotune compensates for this by adjusting the parameters that depend on the Crystal Frequency

!!! NOTE !!! If you switch back to the current master branch the code will revert to using the default frequency configuration. It doesn't use the save frequency yet. There's no significant difference between the two branches at the moment other than autotune.

There is no need to actually run autotune connected to HA shut away in a cupboard.
You should get the same result using the Arduino Serial monitor and you don't have to mess with your HA config.
In fact the better the received signals the better the autotune process will probably work.

The 1% transmit limit is a regulatory thing for the license free 868MHz band. In order to make sure it's generally useable by everybody you're not supposed to transmit more than 1% of the time.

Getting working TX using the calibrate branch. Majority of transmit requests are now getting responses.

ghoti57 · 2021-02-22T15:34:48Z

@danrp-git so what did you do differently to 5 days ago when it didn't appear to work?
What id the F value now? DO you have the value from 5 days ago?

danrp-git · 2021-02-22T16:03:17Z

@danrp-git so what did you do differently to 5 days ago when it didn't appear to work?
What id the F value now? DO you have the value from 5 days ago?

Stayed on the calibrate firmware, currently using F=2165bc which resulted from a second calibration. Going to calibrate again later with the Nano in clear sight of the controller, as the second calibration appears to have regressed the TX success rate slightly.

iMiMx · 2021-02-22T16:14:21Z

Stayed on the calibrate firmware, currently using F=2165bc which resulted from a second calibration. Going to calibrate again later with the Nano in clear sight of the controller, as the second calibration appears to have regressed the TX success rate slightly.

I found that F=2165d4 and/or F=2165d3 gave me perhaps 75% success.

F=2165db and also moving the antenna 90 degrees took me to more or less 100%

I believe there was a noticeable difference between them anyway, but perhaps there was another variable coming into play.

And for some reason or other, I didn't have anywhere near the success after calibrating, when I didn't do it 'in place' - i.e how my nanoCUL will be, where it will be, cupboard door shut, etc.

ghoti57 · 2021-02-22T17:53:34Z

@iMiMx How different was the Frequency value when you didn't calibrate "in place" compared to the value obtained "in place"

iMiMx · 2021-02-22T17:56:46Z

@ghoti57 When on my laptop, I think I got either F=2165d4 and/or F=2165d3.

Only when I started testing/auto-tuning/calibrating "in place" (rack under the stairs, controller in the same hallway) did I see F=2165db, along with the 2 former as well.

I was unable to replicate tuning to F=2165db when NOT "in place".

ghoti57 · 2021-02-23T07:41:55Z

Can anyone in touch with the supplier ask him if he's aware of any issues with the 26MHz crystal on the cc1101 modules he's used.

iMiMx · 2021-02-23T07:44:10Z

Can anyone in touch with the supplier ask him if he's aware of any issues with the 26MHz crystal on the cc1101 modules he's used.

I just ordered another one this morning to 'play' with, as I'd like to keep my current one 'as is' for now - as it's working wonderfully.

I know you don't like the evofw2 (fifo branch) comparison, and I get that, but evofw2 (fifo branch) RP-ed to an RQ every single time - and I know you'll probably say 'well everything is different between them', but... something seems to be fundamentally different with how they TX and/or chosen frequencies.

P.S. I have emailed the seller about the 26Mhz crystal question, along with your earlier description above of the frequency differences.

ghoti57 · 2021-02-23T08:17:21Z

@iMiMx Glad your system appears to be working well now.

There is no difference between the way evofw2 and evofw3 (pre calibrate) choose frequencies. They both use identical compiled data to configure the cc1101.

The fifo branch was fundamentally flawed for RX (too complicated to explain).

TX is different between the two. evofw2 loads a fifo in the cc1101 with the data to be transmitted so it's using the cc1101 crystal to control the data bitrate. evofw3 uses an atmega328p timer (derived from the 16MHz crystal) to drive the data into the cc1101 in a serial bit stream.

I'm not convinced the cc1101 calibration has really fixed this problem (it will almost certainly improve reception). It doesn't seem to work for all of you and the difference between 2165d3 and 2165db in your case is too small to really be significant by itself.
(The theoretical value for a perfect crystal is 21656A)

I'm suspicious about the 16Mhz crystal that is used by the atmega328 because I've recently seen problems on the host facing side of the atmega328p (associated with the comment above about problems at 115200). This HW UART interface also derives its clock from the 16MHz crystal.

In the past I've considered a hybrid approach, RX using the evofw3 approach but TX using the evofw2/fifo approach. I may reconsider this when I've got time.

ghoti57 · 2021-02-28T13:19:00Z

I've run autotune on @domb80's nano and I see the same.
TX work's a lot of the time but not always.
This means that there is no fundamental hardware problem.

I also tried running evofw2/fifo on @domb80's nano. I get the same result as @iMiMx.
I am definitely going to have to investigate the hybrid approach of evofw3-RX and evofw2/fifo-TX

You should switch back to the master branch of evofw3 because I've merged the autotune support (into version 0.6.12)
Those of you that have already run autotune and saved the result the latest master branch will pick up that data so you don't have to rerun it.

Please make sure you ALWAYS use the evofw3_avr board definitions with the arduino gui to build. There's a change coming that you are all going to want to improve the interface with evohome_cc/evohome_rf and you won't be able to use it with the arduino board definitions. I had always planned to remove support for the arduino boards anyway and that is now a step closer.

I'm going to leave this issue open and I'll use it to let you know when I've done anything to improve TX performance.

iMiMx · 2021-02-28T15:53:21Z

Perhaps someone else will chime in if they're having similar issues... but...

My 2nd nanoCUL arrive on Friday, so I tried this as suggested with the evofw3_avr board and the latest master. Tuning seems to be slower (not sure if that's intentional, or just my perception) and for the 2nd time it seems to have hung (it's about 30 minutes since it last changed frequency).

I haven't yet tried the same calibrate branch that I'm still running on my other nanoCUL.

14:53:58.971 -> �# evofw3 0.6.12
14:54:01.611 -> # !F F=21656a
14:54:03.919 -> # !F Tune
14:54:10.007 -> 063  I --- 04:055600 --:------ 01:050858 2309 003 070640
14:54:10.007 -> # !c 0d 21 65 6a
14:54:17.252 -> 064  I --- 01:050858 --:------ 01:050858 1F09 003 FF0645
14:54:17.252 -> # !c 0d 21 65 5a
14:54:17.288 -> 065  I --- 01:050858 --:------ 01:050858 30C9 024 00093701086602083403072F0407F40508180607C607086B
14:54:17.321 -> # !c 0d 21 65 4a
14:54:17.956 -> 060 RQ --- 30:177552 01:050858 --:------ 0005 002 0000
14:54:17.956 -> # !c 0d 21 65 3a
14:54:17.956 -> 065 RP --- 01:050858 30:177552 --:------ 0005 004 0000FF00
14:54:18.033 -> # !c 0d 21 65 2a
14:54:19.452 -> 060 RQ --- 30:177552 01:050858 --:------ 10A0 001 00
14:54:19.452 -> # !c 0d 21 65 1a
14:54:19.452 -> 065 RP --- 01:050858 30:177552 --:------ 10A0 006 001C200001F4
14:54:19.502 -> # !c 0d 21 65 0a
14:54:23.156 -> 060 RQ --- 30:177552 01:050858 --:------ 0006 001 00
14:54:23.156 -> # !c 0d 21 64 fa
14:54:23.156 -> 066 RP --- 01:050858 30:177552 --:------ 0006 004 00050E10
14:54:23.189 -> # !c 0d 21 64 ea
14:54:26.110 -> 060 RQ --- 30:177552 01:050858 --:------ 0005 002 0004
14:54:26.110 -> # !c 0d 21 64 da
14:54:26.144 -> 064 RP --- 01:050858 30:177552 --:------ 0005 004 0004FF00
14:54:26.144 -> # !c 0d 21 64 ca
14:55:22.427 -> 061 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
14:55:22.427 -> # AA.5A.9D.
15:02:27.082 -> 062  I --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:02:27.082 -> # A9.6A.F5.
15:02:27.082 -> # !c 0d 21 64 d2
15:02:27.082 -> 046 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:02:27.082 -> # 33.
15:02:27.082 -> 045 RQ --- 18:141846 --:------ --:------ ???? ???  * Invalid Manchester Code
15:02:27.082 -> # AA.5A.9A.66.A6.66.A9.96.A5.95.9A.95.9D.
15:03:42.101 -> # !F F=2164d2 tuning
15:04:24.056 -> 066 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:04:24.056 -> # F5.
15:04:27.069 -> 061 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:04:27.069 -> # AA.DA.
15:04:59.344 -> 071 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:04:59.344 -> # FD.
15:10:01.404 -> 059 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:01.404 -> # BA.
15:10:01.404 -> # !c 0d 21 64 d6
15:10:01.404 -> 061 RP --- 01:050858 --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:01.404 -> # A5.5A.AA.9A.5A.96.66.66.95.66.65.99.79.
15:10:20.057 -> 060 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:20.057 -> # B5.
15:10:26.183 -> 059 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:26.183 -> # E9.
15:10:26.183 -> 059 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:26.183 -> # E9.
15:10:26.183 -> 059 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:10:26.183 -> # E9.
15:12:29.496 -> 062  I --- 13:215029 --:------ 13:215029 3EF0 003  * Invalid Manchester Code
15:12:29.496 -> # A9.6A.A5.95.9A.95.55.99.A5.95.9A.95.55.99.A5.56.55.AA.AA.A5.AA.BA.
15:14:00.537 -> # !F F=2164d6 tuning
15:14:07.728 -> 060 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:14:07.758 -> # A5.DA.
15:14:07.758 -> # !c 0d 21 64 d8
15:14:16.252 -> 064 RQ --- 30:177552 01:050858 --:------ ???? ???  * Invalid Manchester Code
15:14:16.252 -> # AA.5A.95.66.65.99.69.AA.AA.9A.5A.96.66.66.A9.AA.66.EA.
15:14:16.252 -> 062 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:14:16.286 -> # A5.FA.
15:14:21.470 -> 064 RQ --- 30:177552 --:------ --:------ ???? ???  * Invalid Manchester Code
15:14:21.504 -> # AA.5A.95.66.65.99.69.AA.AA.9A.7A.
15:19:27.397 -> 064 RQ --- 30:177552 01:050858 --:------ ???? ???  * Invalid Manchester Code
15:19:27.397 -> # AA.5A.95.66.65.99.69.AA.AA.9A.5A.96.66.66.AA.9A.A9.7A.
15:19:27.397 -> # !c 0d 21 64 d9
15:21:03.578 -> 067 RQ --- 30:177552 01:050858 --:------ ???? ???  * Invalid Manchester Code
15:21:03.578 -> # AA.5A.95.66.65.99.69.AA.AA.9A.5A.96.66.66.A6.E5.
15:21:03.578 -> 070 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:21:03.578 -> # FD.
15:22:43.841 -> 062 RP --- 13:215029 18:141846 --:------ 3EF1 007 00025802 * Invalid Manchester Code
15:22:43.841 -> # A5.5A.A5.95.9A.95.55.99.9A.66.A6.66.A9.96.A5.56.55.A9.AA.95.AA.AA.AA.A6.99.6A.AA.A6.9D.
15:22:43.841 -> 050 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:22:43.841 -> # AA.5A.9A.66.A6.62.
15:22:43.841 -> 062 RP --- 13:215029 18:141846 --:------ ???? ???  * Invalid Manchester Code
15:22:43.841 -> # A5.5A.A5.95.9A.95.55.99.9A.66.A6.66.A9.96.AA.EA.
15:23:29.415 -> 070 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:23:29.415 -> # AA.5A.95.66.65.99.E9.
15:23:29.415 -> # !c 0d 21 65 6a
15:23:29.415 -> 065 RP --- 01:050858 30:177552 --:------ 0006 004 00050E10
15:23:29.415 -> # !c 0d 21 65 7a
15:23:29.415 -> 073  I --- 22:245512 --:------ 22:245512 30C9 003 0008BE
15:23:29.415 -> # !c 0d 21 65 8a
15:23:44.041 -> 064  I --- 01:050858 --:------ 01:050858 1F09 003 FF0645
15:23:44.041 -> # !c 0d 21 65 9a
15:23:44.041 -> 065  I --- 01:050858 --:------ 01:050858 30C9 024 0009630108BE02082203074304083005082B0607D607085D
15:23:44.041 -> # !c 0d 21 65 aa
15:23:59.585 -> 070 RQ --- 30:177552 01:050858 --:------ 10A0 001 00
15:23:59.585 -> # !c 0d 21 65 ba
15:23:59.585 -> 065 RP --- 01:050858 30:177552 --:------ 10A0 006 001C200001F4
15:23:59.585 -> # !c 0d 21 65 ca
15:24:08.545 -> 067 RQ --- 30:177552 01:050858 --:------ 10A0 001 01
15:24:08.545 -> # !c 0d 21 65 da
15:24:08.545 -> 063 RP --- 01:050858 30:177552 --:------ 10A0 006 011C200001F4
15:24:08.545 -> # !c 0d 21 65 ea
15:24:19.335 -> 066 RQ --- 30:177552 01:050858 --:------ 0006 001 00
15:24:19.335 -> # !c 0d 21 65 fa
15:24:19.335 -> 064 RP --- 01:050858 30:177552 --:------ 0006 004 00050E10
15:24:19.335 -> # !c 0d 21 66 0a
15:24:44.365 -> 073 RQ --- --:------ --:------ --:------ ???? ???  * Invalid Manchester Code
15:24:44.365 -> # A9.2A.
15:24:54.397 -> 072  I --- 22:245512 --:------ 22:245512 30C9 003 0008D4
15:24:54.397 -> # !c 0d 21 66 1a
15:24:54.397 -> 076  I --- 04:055596 --:------ 01:050858 2309 003 010640
15:24:54.397 -> # !c 0d 21 66 2a
15:25:18.819 -> 067 RQ --- 30:177552 01:050858 --:------ 0006 001 00
15:25:18.819 -> # !c 0d 21 66 3a
15:25:18.819 -> 063 RP --- 01:050858 30:177552 --:------ 0006 004 00050E10
15:25:18.819 -> # !c 0d 21 66 4a
15:25:57.209 -> 070  I --- 22:245512 --:------ 22:245512 30C9 003 0008EA
15:25:57.209 -> # !c 0d 21 66 5a
15:26:01.185 -> 068  I --- 22:245512 --:------ 22:245512 30C9 003 0008EA
15:26:01.185 -> # !c 0d 21 66 6a
15:26:14.760 -> 059 RQ --- 30:177552 01:050858 --:------ 0006 001 00
15:26:14.760 -> # !c 0d 21 66 7a
15:26:14.760 -> 067 RP --- 01:050858 30:177552 --:------ 0006 004 00050E10
15:26:14.796 -> # !c 0d 21 66 8a
15:26:23.276 -> 069  I --- 01:050858 --:------ 01:050858 1F09 003 FF0645
15:26:23.276 -> # !c 0d 21 66 9a
15:26:23.276 -> 070  I --- 01:050858 --:------ --:------ ???? ???  * Invalid Manchester Code
15:26:23.313 -> # A9.6A.AA.9A.5A.96.66.66.AA.9A.5A.96.64.
15:26:32.201 -> 067  I --- 04:055482 --:------ 01:050858 3150 002 0600
15:26:32.201 -> # !c 0d 21 66 aa
15:26:34.019 -> 049  I --- 04:055594 --:------ 04:055594 30C9 003 0009E8
15:26:34.019 -> # !c 0d 21 66 ba
15:34:13.482 -> # !F F=2166ba tuning
15:49:23.321 -> # !F F=2166ba tuning

UPDATE: Just seen that 0.6.14 has been committed, so am now trying this. For anyone else reading, make sure you update your board definitions from Board Manager first, it needs the 'host' baud rate option which isn't present otherwise.

UPDATE 2: Seem to see the same there as well, not posting the full log but after leaving it running for around 70 minutes:

16:14:13.904 -> ⸮�# evofw3 0.6.14
16:14:15.744 -> # !F F=21656a
...
16:44:40.106 -> # !c 0d 21 66 ca
16:46:38.373 -> # !F F=2166ca tuning
16:46:53.008 -> # !F F=2166ca tuning
16:47:20.983 -> # !F F=2166ca tuning
17:01:27.303 -> # !F F=2166ca tuning
17:04:09.634 -> # !F F=2166ca tuning
17:24:07.182 -> # !F F=2166ca tuning

Bit reluctant to try it on my currently working nanoCUL, I will try the Calibrate branch on this new device that I'm using elsewhere.

phdelodder · 2021-03-05T12:16:38Z

Is there a way to reset the autotune?

ghoti57 · 2021-03-05T13:06:46Z

!FR
I can't remember if you need !FS afterwards

iMiMx · 2021-03-14T12:03:02Z

Had another play with the current version, 0.6.15, when autotuning on this version (as opposed to the calibrate branch) does the tuning now wait for a packet, before moving onto the next frequency step?

I find that it appears to 'hang' when it is no longer receiving messages, if you send an RP it then steps to the next frequency... but if it has tuned outside of the window where it can 'see' packets, it never progresses itself?

ghoti57 · 2021-03-14T13:28:00Z

@iMiMx I've just committed a change to the master branch that fixes your autotune hangup

ghoti57 · 2021-03-14T13:28:47Z

Working on better TX behaviour

ghoti57 · 2021-03-21T11:14:05Z

I've just posted a new release of evofw3 that should resolve all TX problems.

Since you're all using atmega328p boards it's not strictly necessary but there is a new version of evofw3_avr as well so you should update the board definitions.

hughb8on · 2021-03-21T12:01:00Z

I thought you might like some feedback on 0.7.0, which I've been testing this morning.
I have made six setpoint changes in a row in Domoticz and every one has worked. My previous record was, er, 1.
I am using a U4 with HW UART by the way.
Thank you!

FrankvdAa · 2021-03-21T12:24:06Z

Tested it here also and working like a charm. Thank you!

roblomq · 2023-03-15T20:55:42Z

@FrankvdAa I've also bought a nanocul with evofw3 on it and try to get it to work in Domoticz. I do get some boiler devices but not the zone information, and get some errors .
Did you also get the zone info in Domoticz? If yes what did you do to get this working? How did you obtain the system id? Or is that not needed?

zxdavb · 2023-03-17T04:36:38Z

You have revived an old thread, with a question best asked elsewhere. I would ask you seek help on a Domoticz forum.

However, I strongly advise you switch to Home Assistant, IMHO it has a significantly better offering for both the web and RF version of evohome.

For example, ramses_cc (in HA) is much less likely to suffer from the problems you describe.

roblomq · 2023-03-18T20:25:41Z

Of course I already asked the question on the Domoticz forum but did not receive any reactions so far.
Switching from 8+ years Domoticz to HA is not something that is easily done and I also use a lot of different hardware, custom scripts and have a lot of historical data doesn't make it easier.

ghoti57 closed this as completed Feb 15, 2021

ghoti57 reopened this Feb 15, 2021

ghoti57 closed this as completed Mar 14, 2021

ghoti57 reopened this Mar 14, 2021

ghoti57 closed this as completed Mar 21, 2021

Maikel-K mentioned this issue Dec 8, 2021

Starting tuning process on Raspberry Pi #26

Closed

trailro mentioned this issue Oct 16, 2022

nanoCUL not transmitting #31

Closed

Setting controller mode or set point not working from Domoticz #6

Setting controller mode or set point not working from Domoticz #6

Comments

FrankvdAa commented Feb 14, 2021

ghoti57 commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021 via email

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021 via email

ghoti57 commented Feb 15, 2021 via email

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

FrankvdAa commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

ghoti57 commented Feb 15, 2021

ghoti57 commented Feb 22, 2021

iMiMx commented Feb 22, 2021 • edited Loading

domb80 commented Feb 22, 2021 via email

danrp-git commented Feb 22, 2021

ghoti57 commented Feb 22, 2021 • edited Loading

danrp-git commented Feb 22, 2021

iMiMx commented Feb 22, 2021 • edited Loading

ghoti57 commented Feb 22, 2021

iMiMx commented Feb 22, 2021 • edited Loading

ghoti57 commented Feb 23, 2021

iMiMx commented Feb 23, 2021 • edited Loading

ghoti57 commented Feb 23, 2021

ghoti57 commented Feb 28, 2021

iMiMx commented Feb 28, 2021 • edited Loading

phdelodder commented Mar 5, 2021

ghoti57 commented Mar 5, 2021

iMiMx commented Mar 14, 2021

ghoti57 commented Mar 14, 2021

ghoti57 commented Mar 14, 2021

ghoti57 commented Mar 21, 2021

hughb8on commented Mar 21, 2021

FrankvdAa commented Mar 21, 2021

roblomq commented Mar 15, 2023

zxdavb commented Mar 17, 2023

roblomq commented Mar 18, 2023

iMiMx commented Feb 22, 2021 •

edited

Loading

ghoti57 commented Feb 22, 2021 •

edited

Loading

iMiMx commented Feb 22, 2021 •

edited

Loading

iMiMx commented Feb 22, 2021 •

edited

Loading

iMiMx commented Feb 23, 2021 •

edited

Loading

iMiMx commented Feb 28, 2021 •

edited

Loading