search

alextud / ha-prana

Prana recuperators (fan) for Home Assistant
23 stars 2 forks source link

Issues on HA running on RaspberryPi4 #2

Open ValiEne opened 4 years ago

ValiEne commented 4 years ago

Hi @alextud can you tell me what I'm doing wrong? I've followed your indication and I was able to see the fan but I have only four entities: Screenshot 2020-08-27 at 18 57 23 Screenshot 2020-08-27 at 18 58 38

ValiEne commented 4 years ago

And when pressing that button named "Prana" nothing happens (it moves to "on" position for a moment and then turns itself off)

alextud commented 4 years ago

hey @ValiEne can you try to get latest changes it should work now.

ValiEne commented 4 years ago

Hi Alex, After replacing all the files in /custom_components/prana with the newest ones all entities are unavailable. With log set to debug I get this type of error messages:

2020-08-27 23:21:03 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for prana which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-08-27 23:21:11 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:22:14 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:23:14 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:24:16 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:25:11 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:26:12 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:27:11 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:28:11 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:29:11 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None 2020-08-27 23:30:13 ERROR (PranaWorker) [custom_components.prana.prana] Prana communication failed. Stopping trying. NoneType: None

alextud commented 4 years ago

Here is a sample of debug logs generated by prana on my side:

2020-08-27 21:12:09 DEBUG (PranaWorker) [custom_components.prana] Updating Prana device... 00:A0:50:D3:17:91 2020-08-27 21:12:09 DEBUG (PranaWorker) [custom_components.prana.prana] Sending command BEEF0501000000005A to prana 00:A0:50:D3:17:91 2020-08-27 21:12:09 DEBUG (PranaWorker) [custom_components.prana.prana] Connecting to Prana... 2020-08-27 21:12:12 DEBUG (PranaWorker) [custom_components.prana.prana] Connected to Prana. 2020-08-27 21:12:12 DEBUG (PranaWorker) [custom_components.prana.prana] speed: 2 CO2: 828 VOC: 436, AUTO_MODE: 0, HEATER: 0, THAW: 0 2020-08-27 21:12:12 DEBUG (PranaWorker) [custom_components.prana] Update success...

In your case it seems that there is no connection.

In terminal you can test connection to your bluetooth device by running 1 of the following examples:

EX 1:

sudo bluetoothctl 
connect MAC_ADDRESS
menu gatt
select-attribute 0000cccc-0000-1000-8000-00805f9b34fb
notify on
write "0xBE 0xEF 0x05 0x01 0x00 0x00 0x00 0x00 0x5A"

EX 2:

gatttool -b MAC_ADDRESS -I
connect
char-write-req 0x000f 0100
mtu 200
char-write-req 0x000e BEEF0501000000005A