Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help connecting #84

Closed
AndrewAkinson opened this issue Nov 20, 2024 · 1 comment
Closed

Help connecting #84

AndrewAkinson opened this issue Nov 20, 2024 · 1 comment

Comments

@AndrewAkinson
Copy link

Hi, I'm floundering a bit. Just installed HA 2024.11.1 with ESP home 2024.10.3.

I’m trying to connect to a Comfoair Q450

I’ve installed the .yaml on a

https://raw.githubusercontent.com/AchimPieters/esp32-homekit-camera/master/Images/ESP32-30PIN-DEVBOARD.png

(well I think it is that)

esphome:
  name: play32a
  friendly_name: Play32A

esp32:
  board: esp32doit-devkit-v1
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
<snip>
ota:
<snip>
wifi:
<snip>

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:

captive_portal:

external_components:
  - source: github://vekexasia/comfoair-esp32
    components: [ comfoair ]

comfoair:
    id: comfo
    rx_pin: GPIO14
    tx_pin: GPIO13

web_server:
  port: 80
  version: 2
  ota: false

I’m using usb to power it, as I don’t have a 12V stepdown, I assume that is only for power, so can be replaced by usb power?

I’m using a CAN Bus Transceiver – TJA1051T/3 as it is the one I happen to have! It has a termination switch, that I have tried on and off.

I can add the device to HA dashboard and it shows lots of sensors starting with lay32A analog_input_0_10v_1, but the results are all shown as unknown

Looking at the logs through HA I get the standard connection then it just sits there. Pressing the boot physical boot switch it shows this

WARNING play32a @ 192.168.0.112: Connection error occurred: [Errno 104] Connection reset by peer
INFO Processing unexpected disconnect from ESPHome API for play32a @ 192.168.0.112
WARNING Disconnected from API
INFO Successfully connected to play32a @ 192.168.0.112 in 0.007s
INFO Successful handshake with play32a @ 192.168.0.112 in 0.085s
[09:20:54][D][comfoair.component:166]: update_next 218 - iterator 21
[09:20:55][D][comfoair.component:166]: update_next 227 - iterator 22
[09:20:56][D][comfoair.component:166]: update_next 209 - iterator 23
[09:20:57][D][comfoair.component:166]: update_next 212 - iterator 24
[09:20:58][D][comfoair.component:166]: update_next 220 - iterator 25
[09:20:59][D][comfoair.component:166]: update_next 221 - iterator 26
[09:21:00][D][comfoair.component:166]: update_next 274 - iterator 27
[09:21:01][D][comfoair.component:166]: update_next 275 - iterator 28
[09:21:02][D][comfoair.component:166]: update_next 276 - iterator 29
[09:21:03][D][comfoair.component:166]: update_next 277 - iterator 30
[09:21:04][D][comfoair.component:166]: update_next 278 - iterator 31
[09:21:05][D][comfoair.component:166]: update_next 290 - iterator 32
[09:21:06][D][comfoair.component:166]: update_next 291 - iterator 33
[09:21:07][D][comfoair.component:166]: update_next 292 - iterator 34
[09:21:08][D][comfoair.component:166]: update_next 293 - iterator 35
[09:21:09][D][comfoair.component:166]: update_next 294 - iterator 36
[09:21:10][D][comfoair.component:166]: update_next 369 - iterator 37
[09:21:10][D][api:103]: Accepted 192.168.0.100
[09:21:10][D][api.connection:1446]: Home Assistant 2024.11.1 (192.168.0.100): Connected successfully
[09:21:11][D][comfoair.component:166]: update_next 370 - iterator 38
[09:21:12][D][comfoair.component:166]: update_next 371 - iterator 39
[09:21:13][D][comfoair.component:166]: update_next 372 - iterator 40
[09:21:14][D][comfoair.component:166]: update_next 49 - iterator 41
[09:21:15][D][comfoair.component:166]: update_next 66 - iterator 42
[09:21:16][D][comfoair.component:166]: update_next 67 - iterator 43
[09:21:17][D][comfoair.component:166]: update_next 210 - iterator 44
[09:21:18][D][comfoair.component:166]: update_next 211 - iterator 45
[09:21:19][D][comfoair.component:166]: update_next 56 - iterator 46
[09:21:20][D][comfoair.component:166]: update_next 16 - iterator 47
[09:21:21][D][comfoair.component:166]: update_next 70 - iterator 48
[09:21:22][D][comfoair.component:166]: update_next 71 - iterator 49
[09:21:34][I][safe_mode:041]: Boot seems successful; resetting boot loop counter
[09:21:34][D][esp32.preferences:114]: Saving 1 preferences to flash...
[09:21:34][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed

Accessing the webpage states are all NA, I can change from Cool to Heat

09:33:10	[D]	[climate:011]	'' - Setting
09:33:10	[D]	[climate:015]	 Mode: HEAT
09:33:11	[W]	[component:237]	Component web_server took a long time for an operation (1028 ms).
09:33:11	[W]	[component:238]	Components should block for at most 30 ms.

However the unit is in AUTO and it does not change on the unit.

However, I'm not sure this helps, as if I remove the links between the ESP and the CAN transceiver I get the same results.

So it looks like it is not actually sending/receiving anything, but I do not know how I can trouble shoot this?
Issue #77 seems to have been using the RJ45, but I'm using the push in connectors.
Issue #40 seems to be a broken CAN bus, can this be tested, I only have one of them.

I'm struggling to find a way to proceed, except buy more parts in case they are broken! Any suggestions welcome
thanks
Andrew

@AndrewAkinson
Copy link
Author

Oh that is embarrassing, I had done the standard swap the rx and tx across the two boards as you would if connecting between two esp etc. However in this case the GPIO is listing which to connect to the rx and tx pin not setting them to rx and tx. Anyway data coming in on some of them, now just need to work out how to get that fancy front end,

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

No branches or pull requests

1 participant