Closed gpvdlinden closed 5 years ago
Are you running the beta version of this app?
Yes, I am. I tried both..
Van: Diederik Bakker notifications@github.com Verzonden: woensdag, december 12, 2018 1:39 PM Aan: DiedB/SolarPanels CC: gpvdlinden; Author Onderwerp: Re: [DiedB/SolarPanels] Solar Edge with Homey v2 not working (#33)
Are you running the beta version of this app?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDiedB%2FSolarPanels%2Fissues%2F33%23issuecomment-446574112&data=02%7C01%7C%7Cb24a6f8e1d4f4a5c13b708d6602ed379%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636802151556457494&sdata=Kt%2FMpec59M%2BKCpLSiF1hwKHjiSNriisocv%2FopjVTKD8%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArrbzUlamJEWMAe-l_beMtPqH4WAP_Sgks5u4PjygaJpZM4ZOFDR&data=02%7C01%7C%7Cb24a6f8e1d4f4a5c13b708d6602ed379%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636802151556457494&sdata=LDt6Gg9i7WjdLQxSMgJ20twEsVXvet7MciSiT9PhpW0%3D&reserved=0.
What are you trying exactly? Where does it go wrong?
I do not receive input from SolarEdge. The values shown are 6 days old.
Van: Diederik Bakker notifications@github.com Verzonden: woensdag, december 12, 2018 1:49 PM Aan: DiedB/SolarPanels CC: gpvdlinden; Author Onderwerp: Re: [DiedB/SolarPanels] Solar Edge with Homey v2 not working (#33)
What are you trying exactly? Where does it go wrong?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDiedB%2FSolarPanels%2Fissues%2F33%23issuecomment-446576851&data=02%7C01%7C%7C1d56378586294257166a08d660304f73%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636802157931398213&sdata=JI%2B35Lg7yVrns%2B45WPPHrwMFElF1BFMB8UY%2BBCTi9Eg%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArrbzXOhR8AvyLVnp4WrX-A_lMsuCSenks5u4PtvgaJpZM4ZOFDR&data=02%7C01%7C%7C1d56378586294257166a08d660304f73%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636802157931554463&sdata=lY1S9at0YZXRmH9ExxntCMxJFv8XEGQwsZaEMtPYo9M%3D&reserved=0.
Did you try to remove the SolarEdge device from Homey, then reinstall the app and add the device again? Sounds like a scheduled job (for retrieving inverter data) hung from the moment you updated Homey.
Hi Diederik, i have installed the Beta (started from scratch), when trying to connect to Solaredge (systemID and APIkey) getting unknown error 412d8b4f-b34e-4d2e-9e26-875523ac336f thanks, Menno
Using Beta version
I tried removing the panels and adding the SolarEdge again, but I get an unknown error. I am using the beta. Can you please check? Thanks!
From: mveck notifications@github.com Sent: zaterdag 15 december 2018 18:50 To: DiedB/SolarPanels SolarPanels@noreply.github.com Cc: gpvdlinden gpvdlinden@outlook.com; Author author@noreply.github.com Subject: Re: [DiedB/SolarPanels] Solar Edge with Homey v2 not working (#33)
Hi Diederik, i have installed the Beta (started from scratch), when trying to connect to Solaredge (systemID and APIkey) getting unknown error 412d8b4f-b34e-4d2e-9e26-875523ac336f thanks, Menno
Using Beta version
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDiedB%2FSolarPanels%2Fissues%2F33%23issuecomment-447585667&data=02%7C01%7C%7C7289212ee3334f86fc8208d662b5b6c4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636804929932085174&sdata=cGkfOogqd1ZK1e6wVDMV8jGG8c3ioOZx3nYYtc0r4v8%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArrbzQhx-Rnv6wSk4kDW-JHqaHTBdGwcks5u5TY-gaJpZM4ZOFDR&data=02%7C01%7C%7C7289212ee3334f86fc8208d662b5b6c4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636804929932085174&sdata=hH6oh63eA9qJ5HFR3pZ1BIdU4BWu1%2FOvSGhcvNcXaZk%3D&reserved=0.
There are two issues. The setting page is not working correctly in v2 and there is bug in homey v2 that does not start the cron entry.
I have investigated a little further, and the pairing process is broken for all inverters. I will look into that as soon as possible.
Inverters that were already added before the update to 2.0 are mostly working (mine did), but some broke due to the cron job unlinking during the update process. That's a bug in Homey and doesn't have anything to do with the code behind this app.
Hi Diederik, thanks for the confirmation. Since my Homey needed to be reset to default during the 2.0 upgrade, all settings were lost.
Version 2.4 has been submitted to the Athom App Store, should be published over the next few days. That should fix this issue.
The new version has been published. Please confirm if the app is working again for you!
Hi Diederik, did do some experiments with PVoutput and found to my shame that I was using wrong API key (although you mention read-only API in your screen, my read-only API key was not accepted). I have updated, now it works, data is coming in.
Thanks
Just tested it, my read-only key is accepted just fine. Does your key have any strange properties (like non-alphanumeric characters)?
Also, did you get SolarEdge working directly?
Mines is working again, thanks!
Van: Diederik Bakker notifications@github.com Verzonden: dinsdag, december 25, 2018 12:31 AM Aan: DiedB/SolarPanels CC: gpvdlinden; Author Onderwerp: Re: [DiedB/SolarPanels] Inverter pairing results in an error (#33)
Just tested it, my read-only key is accepted just fine. Does your key have any strange properties (like non-alphanumeric characters)?
Also, did you get SolarEdge working directly?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDiedB%2FSolarPanels%2Fissues%2F33%23issuecomment-449778129&data=02%7C01%7C%7C8c05fea859e841c04bee08d669f7f6ee%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636812911045750142&sdata=H6cNF%2Fk5op8%2BAdmJvhgjEqdYr%2BHbDGXKJAU5Rn%2B9%2B40%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArrbzTxPMV_YKVZVdhrF48SwWvxz8XBJks5u8WPfgaJpZM4ZOFDR&data=02%7C01%7C%7C8c05fea859e841c04bee08d669f7f6ee%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636812911045750142&sdata=KdjeDnTes0U3yN%2BAcpE2cQRpcPgwHoimxl%2FwmrIQqAw%3D&reserved=0.
Hi Diederik, regarding Pvoutput API was using special char, replaced by hex string working fine now. Regarding Solaredge, am not sure about the API key. To be honest the Solaredge monitoring site is limited to the nr of calls per hour, so PVoutput solves that for me.
Cool to hear the use cases for this app! I'm marking this issue as solved.
There seems to be no communication possible with the SolarEdge device. I cannot see the setup like API either. Diagnostics: 744d0d8e-025a-4122-a906-62e030c4de8c