Supported hardware

[corvis]

This thread is for gathering information about supported hardware. As this software is based on reverse engineering records, and we have no official information about the protocol there are a good chances it might not work with particular devices or newer firmware.

If you use the prana_rc please leave the message under this thread following this format:

### Hardware 

**Model:** <model here>
**Market:** <e.g. United Kingdom / Italy / Ukraine>
**Link (optional)**: <url pointing the page describing this particular model>

### Software environment

**Prana RC version**: <version you use e.g. 0.4.0>
**I use dockerized version**: <yes/no>
**Host**: <briefly describe the host, e.g. raspberry PI 3 running Raspbian / linux machine x64 Ubuntu / etc>
**I use HomeAssistant integration**: <yes/no>
**Integration**: <describe the way you use prana_rc - connect it to node red / use with home assistant / etc>

The hardware related information will be really useful for other users and I'll appreciate any input related to the software environment as I'm keen to see how people use it and which features are more important.

[alexliit]

Sure!

Actually I already sucessfully extracted CO2 + VOC values from sensors with another Python software.
The values comes from 63th (VOC) and 61th (Co2) characters pair from the BT status quesry response.
Pression from 77th caracter pairs.

Anyway here the form:

Hardware

Model: Prana 160 ERP Pro Mini
Market: Italy
Link (optional): https://shop.prana24.com/prodotto/prana-160-erp-pro-mini/

Software environment

Prana RC version: 0.4.0 (Latest)
I use dockerized version: yes
Host: Ubuntu x64 testing - raspberry PI 3 target final environment
I use HomeAssistant integration: no
Integration: node red to integrate with Domotciz

[corvis]

Many thanks! If you possible, please send me a sample of status message coming from your device together with VOC and CO2 values you see via mobile app.

In order to get the message just add environment variable PRANA_LOGGING=true and watch the logs for the output like this:

2021-03-04 20:10:22,330 PranaDevice DEBUG: State data:
2021-03-04 20:10:22,330 PranaDevice DEBUG: 0xbe,0xef,0x05,0x01,0x00,0x00,0x00,0x00,0x5a,0xc0,0x01,0xc0,0x20,0xc0,0x01,0xc0,0x00,0xc0,0x00,0x00,0x00,0xc0,0x01,0x80,0x01,0xc0,0x14,0x00,0x01,0x40,0x14,0x00,0x01,0x40,0x14,0x00,0x00,0x80,0x00,0x00,0x00,0xc0,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0xc0,0x00,0x00,0x00,0x00,0x00,0x8f,0xd3,0x3e,0xde,0x67,0xf4,0xfe,0x3a,0xfc,0x34,0x6e,0xde,0xca,0x66,0xa4,0xca,0x73,0xed,0xc5,0x0f,0xeb,0xca,0xd3,0xc8,0x29,0x2e,0x1d,0x25,0x1a,0xce,0x01,0x64,0x65,0x16,0x7c,0xdd,0x23,0x73,0xcc,0xde,0x7c,0x3a,0x06,0xc7,0x6c,0x1d,0x17,0xe2,0x6c,0x34,0x76,0x31,0x1a,0x88,0x38,0xc7,0x67,0x19,0x4c,0xc6

[alexliit]

Hello Corvis
I'm using the dockerized version of the http server ...where I should add this env variable?

Also I noted that even if the R-Pi Is in the same room of the Prana (few meters away) the requests are not always answered: I got many times

..
message: "Illegal state: device must be connected before running any commands"
...

Other times it answer immediatly. Is there some BVT configuration need to be done ?

Thanks

[corvis]

Hi @alexliit

To pass env. variable to the docker container you should use -e key like this:

docker run -e PRANA_LOGGING=true --volume /run/dbus/system_bus_socket:/run/dbus/system_bus_socket -p 8881:8881 --restart=unless-stopped corvis/prana-rc:latest

If you use docker-compose then just add environment section (see instructions)

As for the error message you mentioned too me it sounds more like a bug related to multi-threading/locks than misconfiguration. I guess node-red initiates multiple calls to the prana server nearly at the same time and due to some issue in the prana code it won't delay execution...

Anyway I can't reproduce it now so please create an issue with description and attach a piece of logs (with logging enabled) when this happens (preferably multiple times).

[alexliit]

Here it comes the log file:

2021-03-15 21:22:51,299 bleak.backends.bluezdbus.client DEBUG: Connecting to BLE device @ yy:yy:yy:yy:yy:E5 with hci0
2021-03-15 21:22:51,914 bleak.backends.bluezdbus.client DEBUG: Connection successful.
2021-03-15 21:22:53,612 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d, domain: org.bluez.GattCharacteris
2021-03-15 21:22:53,900 bleak.backends.bluezdbus.client DEBUG: Write Characteristic 0000cccc-0000-1000-8000-00805f9b34fb | /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service\x00\x00\x00\x00Z')
2021-03-15 21:22:54,104 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d, domain: org.bluez.GattCharacteris, 0, 0, 90, 192, 1, 192, 32, 192, 0, 192, 0, 192, 0, 0, 2, 192, 0, 64, 0, 0, 10, 192, 1, 192, 30, 192, 1, 192, 30, 0, 0, 128, 0, 0, 0, 192, 0, 0, 1, 0, 0, 0, 128, 192, 71, 129, 144, 132, 200, 0, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 130, 225, 0, 0, 0, 0, 0, 0, 0, 128, 1, 0, 0, 0, 0, 0, 0, 192, 0, 0, 0, 0, 0, 31, 223, 79, 180, 180, 253, 27, 247, 79, 27, 216, 25, 100, 214, 39, 107, 106, 194, 27, 251, 178, 219, 52, 251, 75, 135, 53, 172, 38, 196, 174, 87, 117, 74, 58, 2, 212, 131, 42, 251, 28, 231, 138, 1
2021-03-15 21:22:54,106 bleak.backends.bluezdbus.client DEBUG: GATT Char Properties Changed: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d | [{'Value': [1932, 192, 0, 192, 0, 192, 0, 0, 2, 192, 0, 64, 0, 0, 10, 192, 1, 192, 30, 192, 1, 192, 30, 0, 0, 128, 0, 0, 0, 192, 0, 0, 1, 0, 0, 0, 128, 192, 0, 128, 138, 0, 128, 203,, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 130, 225, 0, 0, 0, 0, 0, 0, 0, 128, 1, 0, 0, 0, 0, 0, 0, 192, 0, 0, 0, 0, 0, 31, 223, 79, 180, 180, 253, 232, 156, 226, 215, 68, 15100, 214, 39, 107, 106, 194, 27, 251, 178, 219, 52, 251, 75, 135, 53, 172, 38, 196, 174, 87, 117, 74, 58, 2, 212, 131, 42, 251, 28, 231, 138, 117, 228, 101, 93, 190, 19
2021-03-15 21:22:54,182 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5, domain: org.bluez.Device1, body: {'ServicesResolved':
2021-03-15 21:22:54,197 PranaDevice DEBUG: State data:
2021-03-15 21:22:54,199 PranaDevice DEBUG: 0xbe,0xef,0x05,0x01,0x00,0x00,0x00,0x00,0x5a,0xc0,0x01,0xc0,0x20,0xc0,0x00,0xc0,0x00,0xc0,0x00,0x00,0x02,0xc0,0x00,0x40,0x00,0,0x1e,0x00,0x00,0x80,0x00,0x00,0x00,0xc0,0x00,0x00,0x01,0x00,0x00,0x00,0x80,0xc0,0x00,0x80,0x8a,0x00,0x80,0xcb,0x00,0x80,0xad,0x00,0xab,0x81,0x90,0x84,0xc8,0x00,0xd3,0,0x00,0x82,0xe1,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x80,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0xc0,0x00,0x00,0x00,0x00,0x00,0x1f,0xdf,0x4f,0xb4,0xb4,0xfd,0xe8,0x9c,0xe2,0x0x1b,0xd8,0x19,0x64,0xd6,0x27,0x6b,0x6a,0xc2,0x1b,0xfb,0xb2,0xdb,0x34,0xfb,0x4b,0x87,0x35,0xac,0x26,0xc4,0xae,0x57,0x75,0x4a,0x3a,0x02,0xd4,0x83,0x2a,0xfb,0x1c,0xe7,0x8
2021-03-15 21:22:54,207 tornado.access INFO: 200 POST / (192.168.10.94) 2936.22ms
2021-03-15 21:22:54,632 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5, domain: org.bluez.Device1, body: {'ServicesResolved':
2021-03-15 21:22:54,633 bleak.backends.bluezdbus.client DEBUG: Device yy:yy:yy:yy:yy:E5 disconnected.
2021-03-15 21:22:54,635 bleak.backends.bluezdbus.client DEBUG: Removing rule PropChanged, ID: 1

But this was the second attempt to query the prana state: the first one got too many reties and the caller node time-out:

2021-03-15 21:10:32,926 bleak.backends.bluezdbus.client DEBUG: Connecting to BLE device @ yy:yy:yy:yy:yy:E5 with hci0
2021-03-15 21:10:33,378 bleak.backends.bluezdbus.client DEBUG: Connection successful.
2021-03-15 21:10:41,095 PranaDeviceManager WARNING: Connection failed. Attempt #1 Re-connecting...
2021-03-15 21:10:41,623 bleak.backends.bluezdbus.client DEBUG: Connecting to BLE device @ yy:yy:yy:yy:yy:E5 with hci0
2021-03-15 21:10:42,592 bleak.backends.bluezdbus.client DEBUG: Connection successful.
2021-03-15 21:10:50,206 PranaDeviceManager WARNING: Connection failed. Attempt #2 Re-connecting...
....
2021-03-15 21:12:32,516 PranaDeviceManager WARNING: Connection failed. Attempt #21 Re-connecting...
2021-03-15 21:12:33,044 bleak.backends.bluezdbus.client DEBUG: Connecting to BLE device @ yy:yy:yy:yy:yy:E5 with hci0
2021-03-15 21:12:33,885 bleak.backends.bluezdbus.client DEBUG: Connection successful.
2021-03-15 21:12:37,676 bleak.backends.bluezdbus.client DEBUG: Get Services...
2021-03-15 21:12:37,764 bleak.backends.bluezdbus.client DEBUG:
Primary Service
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c
        0000baba-0000-1000-8000-00805f9b34fb
        Vendor specific
2021-03-15 21:12:37,765 bleak.backends.bluezdbus.client DEBUG:
Characteristic
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d
        0000cccc-0000-1000-8000-00805f9b34fb
        Vendor specific
2021-03-15 21:12:37,766 bleak.backends.bluezdbus.client DEBUG:
Descriptor
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d/desc000f
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
2021-03-15 21:12:37,768 bleak.backends.bluezdbus.client DEBUG:
Primary Service
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service0008
        00001801-0000-1000-8000-00805f9b34fb
        Generic Attribute Profile
2021-03-15 21:12:37,769 bleak.backends.bluezdbus.client DEBUG:
Characteristic
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service0008/char0009
        00002a05-0000-1000-8000-00805f9b34fb
        Service Changed
2021-03-15 21:12:37,770 bleak.backends.bluezdbus.client DEBUG:
Descriptor
        /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service0008/char0009/desc000b
        00002902-0000-1000-8000-00805f9b34fb
        Client Characteristic Configuration
2021-03-15 21:12:38,073 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d, domain: org.bluez.GattCharacteristic1, body: {'Notifying': True}
2021-03-15 21:12:38,168 bleak.backends.bluezdbus.client DEBUG: Write Characteristic 0000cccc-0000-1000-8000-00805f9b34fb | /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d: bytearray(b'\xbe\xef\x05\x01\x00\x00\x00\x00Z')
2021-03-15 21:12:38,269 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d, domain: org.bluez.GattCharacteristic1, body: {'Value': [190, 239, 5, 1, 0, 0, 0, 0, 90, 192, 1, 192, 32, 192, 0, 192, 0, 192, 0, 0, 2, 192, 0, 64, 0, 0, 10, 192, 1, 192, 30, 192, 1, 192, 30, 0, 0, 128, 0, 0, 0, 192, 0, 0, 1, 0, 0, 0, 128, 194, 0, 128, 138, 0, 128, 203, 0, 128, 174, 0, 171, 129, 144, 132, 75, 0, 214, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 130, 225, 0, 0, 0, 0, 0, 0, 0, 128, 1, 0, 0, 0, 0, 0, 0, 192, 0, 0, 0, 0, 0, 31, 223, 79, 180, 180, 253, 232, 156, 226, 215, 68, 156, 59, 12, 142, 157, 247, 79, 27, 216, 25, 100, 214, 39, 107, 106, 194, 27, 251, 178, 219, 52, 251, 75, 135, 53, 172, 38, 196, 174, 87, 117, 74, 58, 2, 212, 131, 42, 251, 28, 231, 138, 117, 228, 101, 93, 190, 196, 94, 220]}
2021-03-15 21:12:38,269 bleak.backends.bluezdbus.client DEBUG: GATT Char Properties Changed: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5/service000c/char000d | [{'Value': [190, 239, 5, 1, 0, 0, 0, 0, 90, 192, 1, 192, 32, 192, 0, 192, 0, 192, 0, 0, 2, 192, 0, 64, 0, 0, 10, 192, 1, 192, 30, 192, 1, 192, 30, 0, 0, 128, 0, 0, 0, 192, 0, 0, 1, 0, 0, 0, 128, 194, 0, 128, 138, 0, 128, 203, 0, 128, 174, 0, 171, 129, 144, 132, 75, 0, 214, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 130, 225, 0, 0, 0, 0, 0, 0, 0, 128, 1, 0, 0, 0, 0, 0, 0, 192, 0, 0, 0, 0, 0, 31, 223, 79, 180, 180, 253, 232, 156, 226, 215, 68, 156, 59, 12, 142, 157, 247, 79, 27, 216, 25, 100, 214, 39, 107, 106, 194, 27, 251, 178, 219, 52, 251, 75, 135, 53, 172, 38, 196, 174, 87, 117, 74, 58, 2, 212, 131, 42, 251, 28, 231, 138, 117, 228, 101, 93, 190, 196, 94, 220]}, []]
2021-03-15 21:12:38,295 PranaDevice DEBUG: State data:
2021-03-15 21:12:38,296 PranaDevice DEBUG: 0xbe,0xef,0x05,0x01,0x00,0x00,0x00,0x00,0x5a,0xc0,0x01,0xc0,0x20,0xc0,0x00,0xc0,0x00,0xc0,0x00,0x00,0x02,0xc0,0x00,0x40,0x00,0x00,0x0a,0xc0,0x01,0xc0,0x1e,0xc0,0x01,0xc0,0x1e,0x00,0x00,0x80,0x00,0x00,0x00,0xc0,0x00,0x00,0x01,0x00,0x00,0x00,0x80,0xc2,0x00,0x80,0x8a,0x00,0x80,0xcb,0x00,0x80,0xae,0x00,0xab,0x81,0x90,0x84,0x4b,0x00,0xd6,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x82,0xe1,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x80,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0xc0,0x00,0x00,0x00,0x00,0x00,0x1f,0xdf,0x4f,0xb4,0xb4,0xfd,0xe8,0x9c,0xe2,0xd7,0x44,0x9c,0x3b,0x0c,0x8e,0x9d,0xf7,0x4f,0x1b,0xd8,0x19,0x64,0xd6,0x27,0x6b,0x6a,0xc2,0x1b,0xfb,0xb2,0xdb,0x34,0xfb,0x4b,0x87,0x35,0xac,0x26,0xc4,0xae,0x57,0x75,0x4a,0x3a,0x02,0xd4,0x83,0x2a,0xfb,0x1c,0xe7,0x8a,0x75,0xe4,0x65,0x5d,0xbe,0xc4,0x5e,0xdc
2021-03-15 21:12:38,299 tornado.access INFO: 200 POST / (192.168.10.94) 125785.59ms
2021-03-15 21:12:42,513 bleak.backends.bluezdbus.client DEBUG: DBUS: path: /org/bluez/hci0/dev_yy_yy_yy_yy_yy_E5, domain: org.bluez.Device1, body: {'ServicesResolved': False, 'Connected': False}
2021-03-15 21:12:42,514 bleak.backends.bluezdbus.client DEBUG: Device yy:yy:yy:yy:yy:E5 disconnected.
2021-03-15 21:12:42,543 bleak.backends.bluezdbus.client DEBUG: Removing rule PropChanged, ID: 1

I really don't get why it took so many attempt one time, and it got it stright at the first one another.

Is there any configuration I can made? Can I use another BT dongle?
It should'nt be a power/range issue on the bluetooth since the Raspberry and the Prana are in the same room.

Thanks!

[corvis]

Hey @alexliit sorry for late reply. The way you identify the version is ok.

I'm a bit confused as what I previously did is just included implementation from the python file you've attached and expected it should work fine at least for you...

@francesco-re-1107 and @alexliit in version 0.4.3 I did the following changes regarding sensors handling:

In case there is no co2 sensor - apply our previous logic (the one which worked for @francesco-re-1107), otherwise the new one. For the new one I swapped temp_in and temp_out as @alexliit reported the issue.

Below is the logic for parsing sensors. Again to me it's more like another shot in the dark so hope you could share some feedback with actual data in the app\on screen and json coming from prana_rc:

       # Reading sensors
        sensors = PranaSensorsState()
        sensors.humidity = int(data[60] - 128)
        sensors.pressure = 512 + int(data[78])
        # co2 and voc
        sensors.co2 = int(struct.unpack_from(">h", data, 61)[0] & 0b0011111111111111)
        sensors.voc = int(struct.unpack_from(">h", data, 63)[0] & 0b0011111111111111)
        if 0 < sensors.co2 < 10000:
            # Different version of firmware ???
            sensors.temperature_in = float(struct.unpack_from(">h", data, 51)[0] & 0b0011111111111111) / 10.0
            sensors.temperature_out = float(struct.unpack_from(">h", data, 54)[0] & 0b0011111111111111) / 10.0
        else:
            sensors.temperature_in = float(data[49]) / 10
            sensors.temperature_out = float(data[55]) / 10
        # Add sensors to the state only in case device has corresponding hardware
        if sensors.humidity > 0:
            s.sensors = sensors

@alexliit I changed the way I handle reconnections so it might make overall solution more stable and decrease the number of failures after multiple attempts. Please let me know if you notice any difference.

[corvis]

After playing and thinking a bit more I decided to make thread locks more strict and prevent attempts of simultaneous connections to different devices. This might help to minimize connection failures a bit more... So please skip version 0.4.3 and try 0.4.4

[francesco-re-1107]

Hi @corvis
I've tested version 0.4.4 and it's working properly.
Hope this is the definitive solution :)

[alexliit]

Hi @corvis and @francesco-re-1107 !
I can confirm it is working now: the sensor section match the data displayed.
Thank you!

...now I'm wondering how can I change fans speed or auto on/off...

[corvis]

Great to hear.

Switching speed and modes is described here: https://github.com/corvis/prana_rc#set-state

[austrisv]

Hardware

Model: PRANA 150 PREMIUM PLUS (aka PRANA 150 ECO LIFE)
Market: Latvia (bought in Latvia, but came with Ukrainian packaging)
Link (optional): [https://prana.ua/en/products/prana150el/]

Software environment

Prana RC version: 0.4.4
I use dockerized version: no
Host: Raspberry Pi Zero 2 W Rev 1.0
I use HomeAssistant integration: no
Integration: custom .py script to send CO2 values over MQTT; openhab/influxdb/grafana; comparing CO2 readings with Aranet4 (prana not doing great there 😞 )

Update: apparently for Prana Online app there is also www dashboard https://prana.sensesaytech.com available;
And ESP32 on the device communicates with the central through unencrypted MQTT:iot.sensesaytech.com using randomly generated username and empty password.

Topic: v1/devices/me/attributes
Message: 7b227374617465223a22433030314330303843303031433030304330303030303030433030303430303030303634433030314330314543303031433031453030303038303030303030304330303030303031303030303030383041343030383033313030383043413030383038453030414538313243383030303030434230303030303030303030303030303030303030303832464130303030303030303030303030303030303030303030303030303030464643303030303030303030303031333030304645394645227d