#SouthernCompanyAPI

1 messages · Page 1 of 1 (latest)

balmy island
lament ember
#

@junior nova @dark osprey Sorry to revive this dead thread, but I'm working on this problem right now. Except I'm building it as a core integration instead of a addon. I converted the api to Python and I am going to copy tibbers method of loading in the delayed data to home assistant.

Was curious if either of you wanted to help. I have GPC, so it would be good to have test cases from other southern company companies.

Custom python api allows a lot of freedom when something needs to be changed and it means no container has to be run locally, it is all handled inside the integration code.

dark osprey
#

I'd be happy to help. Let me know how I can

lament ember
#

I'll dm you

spice spruce
#

hi, just found that thread after my add-on stopped working (probably because of changed auth mechanism and not updated NPM for southern api) are you guys hosting it on GH somewhere?

lament ember
#

I think he does have it on github. https://github.com/alex-hall/southern_company_hass_addon
I think that is the addon.
In developing the integration, I noticed they changed some of the auth last night. jwt now gets SouthernJwtCookie instead of ScWebToken

If you want to just look at what I did, you can look at my python package: https://github.com/Lash-L/southern_company_api

However, I'm not sure if the hass addon is able to be fixed. As I think the original southern_company_api npm repo is dead and doesn't get updated. And the hass addon uses it.

I hope to have the integration done within a few days, then I'll have to go through the HA approval process which will take a bit, but I could potentially throw together a custom component so you could use it temporarily until the integration gets officially approved (If we are lucky it would be 2023.3, in reality, it will probably be 2023.4).

If you know Python, I'm taking any help I can get to try to get it functioning asap

@spice spruce

spice spruce
#

cool, I’ll start looking at it. will first try to fix that npm. thanks for the tips

lament ember
#

Of course. good luck!

spice spruce
#

thanks! and if your api works for me I’ll just build up another docker file using it with python instead of that npm and node. can be the same custom add-on locally

lament ember
#

Ah fair enough! I have only tested it with georgia power, so no promises if you have someone else, but if you have issues, I'm more than happy to help out

junior nova
#

SouthernCompanyAPI

#

Cool, let me know if I can help

dark osprey
#

we should define on a location for the code. Which github repo do we want to use

junior nova
#

I don't care about github stars if you want to host it @dark osprey

#

Otherwise, If you're worried about being a maintainer, I don't mind hosting.

dark osprey
#

I've got a pretty big deliverable at work due tomorrow so I might not get to the add-on tonight. I'll try to but feel free to look into it yourself if you have time.

#

Just FYI 🙂

#

And/or maybe start thinking about how you want to expose the energy consumption data to HASS.

junior nova
#

Can do. And I’m in the same boat, this is very much a side project so I’ll likely be working on this during the weekends

junior nova
#

FYI @dark osprey I added you as a collaborator to this repo: https://github.com/alex-hall/southern_company_hass_addon and I got the basic e2e process for addons working. The docker image works and the node server starts. Now we just need to figure out how we want this thing to work. I'm thinking it'll run on a batch schedule to consume data from the Georgia Power API since there aren't exactly webhooks to work with.

junior nova
#

The config ENVs now work and I got it to call the API successfully. The plumbing work is ✅

nocturne pendant