search

ghoti57 / evofw3

Major overhaul of evofw2 Evohome listening software to use asynchronous radio mode
61 stars 11 forks source link

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

Closed FrankvdAa closed 3 years ago

FrankvdAa commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Not a bug :-)

ghoti57 commented 3 years ago

What version of evofw3 are you running?

FrankvdAa commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Logs with timestamps of possible.

On 15 Feb 2021, 08:43, at 08:43, FrankvdAa notifications@github.com 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: https://github.com/ghoti57/evofw3/issues/6#issuecomment-779059412

FrankvdAa commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

This is what I get through Arduino Serial Monitor:

20:07:00.421 -> # evofw3 0.6.7

FrankvdAa commented 3 years ago

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

ghoti57 commented 3 years ago

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

On 15 Feb 2021, 19:10, at 19:10, FrankvdAa notifications@github.com 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: https://github.com/ghoti57/evofw3/issues/6#issuecomment-779404470

ghoti57 commented 3 years ago

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

On 15 Feb 2021, 19:10, at 19:10, FrankvdAa notifications@github.com 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: https://github.com/ghoti57/evofw3/issues/6#issuecomment-779404470

ghoti57 commented 3 years ago

FYI evohome_rf is getting far more development effort than evohome_listener

FrankvdAa commented 3 years ago

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 commented 3 years ago

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

ghoti57 commented 3 years ago

Where did you buy the nanoCUL

FrankvdAa commented 3 years ago

Bought it from eBay, German reseller:

FrankvdAa commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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

FrankvdAa commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

Forget tracks just go for nano pins and cc1101 connections

FrankvdAa commented 3 years ago

Measures 20-40mV between GPO0/GPO2 and D2/D3

ghoti57 commented 3 years ago

I don't actually want volts. I need you to test connectivity between D2-GDO0 and D3-GDO2 ( might have D2/D3 swapped)

ghoti57 commented 3 years ago

If there's a hardware problem the most likely fault is that GDO0 is not connected properly

ghoti57 commented 3 years ago

Just checked and D3 should be connected to GDO0. Since RX is working D2 must be connected to GDO2.

FrankvdAa commented 3 years ago

I don't actually want volts. I need you to test connectivity between D2-GDO0 and D3-GDO2 ( might have D2/D3 swapped)

Thought you wanted volts as you asked for a voltmeter :D

Just checked and D2 is connected to GPO2, D3 is connected to GPO0.

ghoti57 commented 3 years ago

What options in the Arduino IDE did you use to build the firmware?

FrankvdAa commented 3 years ago

Do you mean board settings? Tried two options:

  1. Arduino AVR boards --> Arduino NANO Processor: ATmega328P (old bootloader)

  2. evofw3 AVR boards --> atmega328p (SW UART) Processor: atmega328P (5V, 16MHz) Pinout: Nano Bootloader: Old Bootloader

Then did a verify/compile and upload.

iMiMx commented 3 years ago

Just to add, I suspect I have the same problem - using a nanoCUL from the same eBay seller, with evohome_cc with Home Assistant. I can see all the various values, but I just tried to manually change the temperature in zone and nothing appeared to change.

Will do some more digging.

ghoti57 commented 3 years ago

Both build options should work but stick to the evofw3 avr boards option.

If you have two nanoCULs what does the second one report when you TX from the first? In the 'listening" one type !T3 in serial monitor.

ghoti57 commented 3 years ago

Sorry - didn't spot the second contributor there. Do either of you have two devices?

FrankvdAa commented 3 years ago

Unfortunately I only have one, so can't test that.

@iMiMx awaiting your results, sounds like there's something different with these nanoCULs.

iMiMx commented 3 years ago

I also tried the 2 board settings you mention above - without the custom board and with.

On the evohome_cc thread, in the Home Assistant forums, my zones took some time for the names to be retrieved - the dev there says this potentially suggests its not sending:

https://community.home-assistant.io/t/honeywell-ch-dhw-via-rf-hgi80-hgs80-includes-evohome/151584/675?u=imimx

... and then I stumbled upon this when I realised I couldn't set overrides, but can read all of the data.

ghoti57 commented 3 years ago

I'm not aware of anyone who's using one of these devices.

FrankvdAa commented 3 years ago

Same here, took some time for all devices to be discovered by Domoticz.

ghoti57 commented 3 years ago

do either of you have a logic analyser?

iMiMx commented 3 years ago 
2021-02-15 21:30:16 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:215029|3EF1|00): boff=1, want=RQ|13:215029|3EF1|00, tout=2021-02-15 21:30:16.528318: RE-SENT (1/1)
2021-02-15 21:30:17 ERROR (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:215029|3EF1|00): boff=1, want=RP|13:215029|3EF1|00, tout=2021-02-15 21:30:17.126126: EXPIRED
2021-02-15 21:30:17 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|0008|00): boff=1, want=RQ|13:246213|0008|00, tout=2021-02-15 21:30:17.459575: RE-SENT (1/1)
2021-02-15 21:30:17 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:30:17.888515: RE-SENT (1/1)
2021-02-15 21:30:17 ERROR (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:30:17.888515: EXPIRED
2021-02-15 21:31:06 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|0008|00): boff=1, want=RQ|13:246213|0008|00, tout=2021-02-15 21:31:07.068531: RE-SENT (1/1)
2021-02-15 21:31:07 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:31:07.336557: RE-SENT (1/1)
iMiMx commented 3 years ago

do either of you have a logic analyser?

Afraid not.

FrankvdAa commented 3 years ago 
2021-02-15 21:30:16 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:215029|3EF1|00): boff=1, want=RQ|13:215029|3EF1|00, tout=2021-02-15 21:30:16.528318: RE-SENT (1/1)
2021-02-15 21:30:17 ERROR (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:215029|3EF1|00): boff=1, want=RP|13:215029|3EF1|00, tout=2021-02-15 21:30:17.126126: EXPIRED
2021-02-15 21:30:17 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|0008|00): boff=1, want=RQ|13:246213|0008|00, tout=2021-02-15 21:30:17.459575: RE-SENT (1/1)
2021-02-15 21:30:17 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:30:17.888515: RE-SENT (1/1)
2021-02-15 21:30:17 ERROR (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:30:17.888515: EXPIRED
2021-02-15 21:31:06 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|0008|00): boff=1, want=RQ|13:246213|0008|00, tout=2021-02-15 21:31:07.068531: RE-SENT (1/1)
2021-02-15 21:31:07 WARNING (MainThread) [evohome_rf.transport] PktProtocolQos.send_data(RQ|13:246213|3EF1|00): boff=1, want=RQ|13:246213|3EF1|00, tout=2021-02-15 21:31:07.336557: RE-SENT (1/1)

Very similar to what I'm seeing with evohome_rf; in my case it tries 3 times and then expires.

FrankvdAa commented 3 years ago

do either of you have a logic analyser?

Sorry, I don't. Maybe a colleague of mine has, can ask him tomorrow.

ghoti57 commented 3 years ago

I'd trust zxdavb's interpretation. It really does seem like there's no TX working.

zxdavb commented 3 years ago

All - be careful - there is a different between all packets EXPIRED, and some packets EXPIRED. Please provide a HA log from the start - grep 'evohome'

FrankvdAa commented 3 years ago

All - be careful - there is a different between all packets EXPIRED, and some packets EXPIRED. Please provide a HA log from the start - grep 'evohome'

No HA here, but evohome_rf... would that be fine too?