Plans to contine??

[Mr-HaleYa]

I think this project would be awesome to have! Would love to see it keep going and be added in via hacs. Been a while since this has been touched and it seems to no longer work... Hope you can continue building this out!

[yourjelly]

I've not done much to develop it further, but it's working for me what issue are you having with it.

On Sat, Sep 23, 2023, 4:30 AM Koby Hale @.***> wrote:

I think this project would be awesome to have! Would love to see it keep going and be added in via hacs. Been a while since this has been touched and it seems to no longer work... Hope you can continue building this out!

— Reply to this email directly, view it on GitHub https://github.com/yourjelly/home-assistant_owie/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGIX76K2CSBFJM3FV6JOFMDX32MYVANCNFSM6AAAAAA5EBLURA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Mr-HaleYa]

I get these two warnings on reboot

Placed the folder in the right place

And this is in my sensors.yaml

But sensors never update...

configured the OWIE to connect to my network and I've seen it online in my router settings

[yourjelly]

if you navigate to 192.168.50.60 on your home network do you see owie?

[Mr-HaleYa]

Got it working now

Had to plug in and reflash the OWIE board, something about changing settings multiple times made it unstable to the point it would not connect to the network and would reboot every couple of minutes randomly...

[Mr-HaleYa]

After thinking a bit more I don't see too many things to change/add.

I do like the Idea of it being in Hacs with an easy and clean frontend setup.

Solving the issue of losing battery value on reboot would be a nice fix.

A boolean of whether the Owie is connected to the network or not would be nice to have built into this, it is doable in many other ways but makes sense. Since you're collecting packets on a timer if it misses 3 or more then consider it disconnected. Could then have it sample for packets less frequent, i.e. 5 min. At which point, it would realize it's online and go back to fast sampling, saving unneeded overhead.

Would like to get the cell voltages and temps in as well. Pretty much all the data from the Owie board would be nice to have and let users do what they want with it. I could totally go ham on making a nice UI that would pretty much mirror OWIE in HASS for something like my wall-mount tablet to just check stats when heading out the door. With that, I could have it give me alerts or whatever if something weird like a cell drifted or a temp warning when charging.

---

Unrelated but curious, do you think it's possible to connect the OW directly to HASS via BT or use an ESP32 as a middleman to connect and then relay the data in? I would love to just have all the stats in HASS. Looking at how OWCE hasn't even been able to get the board to connect to their app directly I hesitate to think this would work.

[yourjelly]

Solving the issue of losing battery value on reboot would be a nice fix.

Yeah, although with a stable Hass setup that issue is less prevelant

A boolean of whether the Owie is connected to the network or not would be nice to have built into this, it is doable in many other ways but makes sense. Since you're collecting packets on a timer if it misses 3 or more then consider it disconnected. Could then have it sample for packets less frequent, i.e. 5 min. At which point, it would realize it's online and go back to fast sampling, saving unneeded overhead.

There is a way to have Hass handle the requests and do all that stuff natively but wasn't able to figure it out last I tried.

Would like to get the cell voltages and temps in as well. Pretty much all the data from the Owie board would be nice to have and let users do what they want with it. I could totally go ham on making a nice UI that would pretty much mirror OWIE in HASS for something like my wall-mount tablet to just check stats when heading out the door. With that, I could have it give me alerts or whatever if something weird like a cell drifted or a temp warning when charging.

This is probably the easiest add but I was reading that having a lot of additional attributes to a sensor isn't best practice for Hass databases and got lost looking for another solution

Unrelated but curious, do you think it's possible to connect the OW directly to HASS via BT or use an ESP32 as a middleman to connect and then relay the data in? I would love to just have all the stats in HASS. Looking at how OWCE hasn't even been able to get the board to connect to their app directly I hesitate to think this would work.

I'm not sure about this, the board would need to be on and can only connect to one bluetooth device at a time. I wouldnt want Hass blocking my phone from connecting to the board. There are ways to connect directly tho with rewheel, looking into the code for rewheel and OWCE might get you a solution.

[yourjelly]

Actually, my Pint's BMS just fried itself. So any lingering interest in continued development of this has been lost for me.

[Mr-HaleYa]

Can I take the project over then?

[yourjelly]

If you would like to; you're more than welcome to. You just might have to tell me how to do that, cuz I am still v new to all this code & git stuff w/ no formal training.

[Mr-HaleYa]

Under your repository name, click Settings At the bottom of the page, in the "Danger Zone" section, click Transfer.

[yourjelly]

Can't transfer while you have a fork annoyingly enough, added you as a contributor so you can merge all your changes and close your fork then I can transfer