search

keshavdv / victron-hacs

Home Assistant plug-in for Victron Instant Readout compatible devices
68 stars 23 forks source link

Instructions #89

Open kroese opened 1 year ago

kroese commented 1 year ago

Can you please add some instructions to the README file on how to setup the integration?

Because it asks for an "Advertisement key", etc. and I have no idea how to find this key.

xbmcnut commented 1 year ago

Seems there is a fair bit of info here https://www.reddit.com/r/homeassistant/comments/13ip2mt/victron_bluetooth_devices_to_home_assistant/. Sadly, it looks like that at the moment, it's quite the challenge to retrieve the required key?

kroese commented 1 year ago

Yes, its very difficult. I already figured you either need a desktop PC (Linux or Windows) or an Apple device. I dont have any Apple devices and bringing a desktop PC + monitor/keyboard to my boat will be really cumbersome.

I dont really understand why these keys cannot be retrieved with a simple Python script that makes a a connection and prints them out. Or otherwise a custom Android app.

david-collett commented 1 year ago

The latest android app will show you the key.

select device, in overflow menu select product info, select show next to encryption data

fodder427 commented 11 months ago

As a maybe noob, there is no information on what hardware you need to run this. Clearly, you need a Victron SHUNT, and there are mentions of using a SHELLY as a conduit, but there are no instructions on what that entails. If they are around, can you please point me at some?

kroese commented 11 months ago

@fodder427 I use a Victron SmartShunt and a Victron Smart Battery Sense with this project. Both work excellent. I dont know what you mean by a conduit? Its just running on a Raspberry Pi4.

fodder427 commented 11 months ago

Ok, so i understand that this integration is somehow connecting to the Bluetooth signal from the Victron shunt. I was a little unclear HOW it was doing that. I understand that the RPi4 has Bluetooth on board so that is probably what it is using in your case. I had seen that people were using a SHELLY as a conduit for the Bluetooth signals.

I have checked that I have Bluetooth setup on the RPi4 and now I have to put the electrical system back together after the smoke got out of the charger. I am not sure that the Shunt has power at the moment.

kroese commented 11 months ago

Technically speaking it does not even connect (in the traditional sense). BLE devices just send public advertisements containing the sensor values periodically, so the bluetooth chip in the rPi4 just listens for these announcements and records the catched values. This uses much less battery than establishing a connection to the shunt.

But yes, as long as you have Bluetooth working in HomeAssistant you should be able to use this integration without any problem.

Dosturbo68 commented 8 months ago

I installed this and it recognized both the Shunt and the VeDeirect bluetooth extender. I added the advertisement key and all looked well. I have rebooted a number of times and it does not add any devices or entities. I am now to this. Any idea where to start looking for the issue?

Victron

sayer commented 7 months ago

I installed this and it recognized both the Shunt and the VeDeirect bluetooth extender. I added the advertisement key and all looked well. I have rebooted a number of times and it does not add any devices or entities. I am now to this. Any idea where to start looking for the issue?

Victron

I have the same issue.

Dosturbo68 commented 7 months ago

Do you have the mid point wire connected and enabled?Larry CallahanSent from a phone with a tiny keyboard.On Apr 10, 2024, at 8:58 PM, Stephen Ayers @.***> wrote:

I installed this and it recognized both the Shunt and the VeDeirect bluetooth extender. I added the advertisement key and all looked well. I have rebooted a number of times and it does not add any devices or entities. I am now to this. Any idea where to start looking for the issue?

I have the same issue.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>