Closed Mickaelh51 closed 8 years ago
can you please create a thread at community.openhab.org and try to volunteers to create a PR for this?
@lolodomo @clinique can you probably help here?
If there is a problem with firmware 3.3, I will upgrade only when I am sure to have the time to debug and fix the problem. I don't want to loose my current automations. But !maybe this weekend...
Hi @lolodomo can I help you ? I use Openhab 1.8.0 but your jar file will work fine with this version.
@Mickaelh51 : so what is working and what is not working ? What version of openHAB are you running ? What version of the binding are you running ? I first understood that all was OK for you but then after upgrading firmware to version 3.3, nothing is then working ? Is this your problem ?
Hi, I'm not sure for binding version. I'm using Openhab 1.8.
And after freebox firmware upgrade (automatic upgrade) the binding didn't work. On Feb 20, 2016 11:03 AM, "lolodomo" notifications@github.com wrote:
@Mickaelh51 https://github.com/Mickaelh51 : so what is working and what is not working ? What version of openHAB are you running ? What version of the binding are you running ? I first understood that all was OK for you but then after upgrading to firmware to 3.3, nothing is then working ? Is this your problem ?
— Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4026#issuecomment-186562358.
Firmware upgradr in progess... I come back later.
Thanks a lot Have a good weekend
Upgrade done. Then I rebooted my RPI running opehnHAB. The binding is working well.except one thing that is now unfortunately broken: the control of the FTP server. As mentioned in the release note, Free added a secured remote access to the FTP server. What I can see is that they added a new API field named "remote_domain" and believe me this new field is even not yet documented ! There is no bug in the binding itself but something has to be fixed in the freeboxos-java project the binding is relying on and then the binding would have to be "recompiled" to use the fixed jar library. I will do it later. But it is not a blocking issue, hopefully.
I submitted PR #4115 fixing the error relative to new firmware 3.3 described in my previous message. The initial problem described in this issue could probably be closed. @Mickaelh51, can you confirm ?
since #4115 has been merged i assume this issue can be closed?
We are waiting for a comment from the topic creator. I niticed no problem with the binding after my fix.
thanks for the update @lolodomo! I'll close this one meanwhile. Please feel free to reopen if this issue still occurs …
Hi, I'm sorry I had no time to check this.
But I will check it this week.
2016-03-23 9:35 GMT+01:00 lolodomo notifications@github.com:
We are waiting for a comment from the topic creator. I niticed no problem with the binding after my fix.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/openhab/openhab/issues/4026#issuecomment-200246557
Hi all, Since 02 February 2016, Freebox Binding didn't work. I have this issue:
2016-02-03 11:20:14.978 [INFO ] [.o.b.f.internal.FreeboxBinding] - SystemConfiguration: Erreur interne 2016-02-03 11:20:15.028 [INFO ] [.o.b.f.internal.FreeboxBinding] - ConnectionStatus: Erreur interne 2016-02-03 11:20:15.087 [INFO ] [.o.b.f.internal.FreeboxBinding] - WifiGlobalConfig: Erreur interne 2016-02-03 11:20:15.140 [INFO ] [.o.b.f.internal.FreeboxBinding] - LCDConfig: Erreur interne 2016-02-03 11:20:15.198 [INFO ] [.o.b.f.internal.FreeboxBinding] - xDslStatus: Erreur interne 2016-02-03 11:20:15.249 [INFO ] [.o.b.f.internal.FreeboxBinding] - FtpConfig: Erreur interne 2016-02-03 11:20:15.304 [INFO ] [.o.b.f.internal.FreeboxBinding] - LanConfig: Erreur interne
It was an firmware update: http://www.freebox-v6.fr/index.php/blog/article/478/Mise-jour-de-la-Freebox-Server-en-3.3.0
I already to try re-add (reconfigure) this binding, but there is not good result.
Thanks in advance