Setup #39
Comments
|
I've spent more time digging and I can't seem to figure out why I do not have any sensors being added. I even went through the logs, I even get confirmation the py is setting up the sensor (INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.fpl). Yet, there are zero entities in my HA which are written into the integration py. |
|
Same thing here, except I did the manual install. Upon reloading the integration with debug enabled, I get the following in the logs: 2023-08-11 21:30:03.415 INFO (MainThread) [custom_components.fpl] Configuring the client |
|
Same here. My setup: |
|
FPL doesnt have a public api at all, but for NW region they use AWS cognito to login, my personal account is for main region its hard to develop while not able to test how it works, sorry |
|
No worries. Appreciate your efforts.
…On Mon, Oct 9, 2023, 00:39 dotKrad ***@***.***> wrote:
FPL doesnt have a public api at all, but for NW region they use AWS
cognito to login, my personal account is for main region its hard to
develop while not able to test how it works, sorry
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHR3E4S4XIPFPHDAEW2DTCLX6OE2LAVCNFSM6AAAAAAV7BLENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGM3TIMRQGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I made a friend close to the internal FPL NW team and it appears they are working on integrating soon. Respectfully, Corey ***@***.*** from my iPhoneOn Oct 9, 2023, at 00:39, dotKrad ***@***.***> wrote:
FPL doesnt have a public api at all, but for NW region they use AWS cognito to login, my personal account is for main region its hard to develop while not able to test how it works, sorry
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Integrating the API to match the main Fpl region?
…On Mon, Oct 9, 2023, 08:13 Bazl624 ***@***.***> wrote:
I made a friend close to the internal FPL NW team and it appears they are
working on integrating soon. Respectfully, Corey ***@***.*** from my
iPhoneOn Oct 9, 2023, at 00:39, dotKrad ***@***.***> wrote:
FPL doesnt have a public api at all, but for NW region they use AWS
cognito to login, my personal account is for main region its hard to
develop while not able to test how it works, sorry
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHR3E4RMUJYOZ52AMT54C73X6PZ5XAVCNFSM6AAAAAAV7BLENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSHE4DSMJZGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Yea, I didn’t get a lot of details because it was just dad chat at a kids birthday party but he said we was on NW FPL team responsible for web facing infrastructure, and mentioned how they are in the middle of a major over haul with a complete rebuild to provide an API along with realtime customer analytics. I mentioned to him I was playing with this add on which started the conversation. It is hear say, but at least gave me some hope. Respectfully, Corey ***@***.*** from my iPhoneOn Oct 9, 2023, at 10:01, John Chiasson ***@***.***> wrote:
Integrating the API to match the main Fpl region?
On Mon, Oct 9, 2023, 08:13 Bazl624 ***@***.***> wrote:
I made a friend close to the internal FPL NW team and it appears they are
working on integrating soon. Respectfully, Corey ***@***.*** from my
iPhoneOn Oct 9, 2023, at 00:39, dotKrad ***@***.***> wrote:
FPL doesnt have a public api at all, but for NW region they use AWS
cognito to login, my personal account is for main region its hard to
develop while not able to test how it works, sorry
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHR3E4RMUJYOZ52AMT54C73X6PZ5XAVCNFSM6AAAAAAV7BLENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSHE4DSMJZGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
that sounds like good news !! |
|
Sounds great! Might want to let him know we'd be glad to beta (or even
alpha) test for them.
…On Mon, Oct 9, 2023, 12:06 Bazl624 ***@***.***> wrote:
Yea, I didn’t get a lot of details because it was just dad chat at a kids
birthday party but he said we was on NW FPL team responsible for web facing
infrastructure, and mentioned how they are in the middle of a major over
haul with a complete rebuild to provide an API along with realtime customer
analytics. I mentioned to him I was playing with this add on which started
the conversation. It is hear say, but at least gave me some
hope. Respectfully, Corey ***@***.*** from my iPhoneOn Oct 9, 2023, at
10:01, John Chiasson ***@***.***> wrote:
Integrating the API to match the main Fpl region?
On Mon, Oct 9, 2023, 08:13 Bazl624 ***@***.***> wrote:
> I made a friend close to the internal FPL NW team and it appears they
are
> working on integrating soon. Respectfully, Corey ***@***.*** from my
> iPhoneOn Oct 9, 2023, at 00:39, dotKrad ***@***.***> wrote:
> FPL doesnt have a public api at all, but for NW region they use AWS
> cognito to login, my personal account is for main region its hard to
> develop while not able to test how it works, sorry
>
> —Reply to this email directly, view it on GitHub, or unsubscribe.You are
> receiving this because you authored the thread.Message ID: ***@***.***>
>
> —
> Reply to this email directly, view it on GitHub
> <#39 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AHR3E4RMUJYOZ52AMT54C73X6PZ5XAVCNFSM6AAAAAAV7BLENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSHE4DSMJZGQ>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHR3E4UYIKRCEMLIB2AY7EDX6QVILAVCNFSM6AAAAAAV7BLENKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTGM3DONBTGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did the HACS install, I logged in with my FPL NorthWest credentials and I don't have anything populating in my sensors. I have checked through the documentation and open cases and I cannot figure out where I am going wrong with the setup. Am I supposed to manually add the sensors or make any modifications in my config?
The text was updated successfully, but these errors were encountered: