Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Multi-FritzBox-Support #53

Open
Wolfpaxx opened this issue Apr 11, 2019 · 7 comments · May be fixed by #54
Open

[Feature Request] Multi-FritzBox-Support #53

Wolfpaxx opened this issue Apr 11, 2019 · 7 comments · May be fixed by #54

Comments

@Wolfpaxx
Copy link

Hi andig,

with the mesh-support, I came across a new problem:
Normally, smarthome devices status should be sent across different FritzBoxes to the master box. However this does not apply for HAN-FUN-Devices.
In my case, the Telekom SmartHome Smoke Detectors are connected to a mesh slave FritzBox due to signal range issues. The device itself is forwarded to the mesh master, but not the detector status. Neither on the web-interface, nor accessible by the http-request. So the status remains "unknown".

I'd love to kindly ask, if you could spend some time in making the plugin "Multi-FritzBox-capable"? As offered before, I'm willing to chip in a donation to support your work.

I thought about this feature and found other benefits (beside helping me out of my personal mess):

  • Surveillance of multiple remote FritzBoxes in the local network or over the internet could be possible (e.g. for your parents, customers, vacation home) and enable a one-dashboard-overview for all of them
  • Devices and Requests can be split among FritzBoxes. As we discovered earlier, FritzBoxes lower than the 75xx generation started to pile up requests and causing heavy delays. This would allow to increase the total number of devices and/or use faster polling intervals.

I'd love to hear your thoughts about this and give any possible support (sorry, no programmer - but maybe testing, data collection, etc.).

Best regards,
Wolfpaxx

@andig
Copy link
Owner

andig commented Apr 11, 2019

First of all I don't have such a setup. I'm using an FB plus a 1750 als Wifi range extender. Therefore I'm not sure how that would even look UI-wise or if there's any kind of API. To get a better understanding you could pm me (cpuidle@gmx.de) and provide access credentials to such a setup.

I'd love to kindly ask, if you could spend some time in making the plugin "Multi-FritzBox-capable"?

Then I'm really not sure what that capability should include- could you be more specific?

In my case, the Telekom SmartHome Smoke Detectors are connected to a mesh slave FritzBox due to signal range issues. The device itself is forwarded to the mesh master, but not the detector status. Neither on the web-interface, nor accessible by the http-request. So the status remains "unknown".

This sounds a lot like an issue on the AVM side. Did you open a support ticket to get an opinion if that's the expected behaviour?

As offered before, I'm willing to chip in a donation to support your work.

That would be most welcome, a donation button is in the readme ;)

@Wolfpaxx
Copy link
Author

Hi andig,
thank you for your quick reply!
I will try to gather some information and screenshots and make a litte drawing (please don't expect it before next week).
Is it OK if I write it in German (I assume you're German)?!

To be short on the capability: A possibility to add a second (or more) FritzBox-Host (URL & Credentials) in the config which is also polled and usable - just like the first one.

I talked to AVM and there are still a lot of restrictions on HAN-FUN devices. One of the biggest is the incapability of using and roaming between DECT-repeaters and base-stations (which the thermostat devices and switch outlets can). They connect to only one single base-station and won't use repeaters. This restrictions also cause that you can see/use the HAN-FUN devices action tab only on the base-station it is registered to (will be a lot clearer when I send you the screenshots and drawing). Those restrictions are not on their near-time agenda.

Anyway, I'll send you an email soon! :-)

@andig
Copy link
Owner

andig commented Apr 12, 2019

Moin- deutsch ist kein Problem.

To be short on the capability: A possibility to add a second (or more) FritzBox-Host (URL & Credentials) in the config which is also polled and usable - just like the first one.

Hast Du schonmal probiert einfach die komplette Config zu doppeln? Ggf. kann ja die "platform" auch 2x angegeben werden- habe ich aber noch nciht getestet.

They connect to only one single base-station and won't use repeaters.

Würde mit dem Vorschlag ja passen.

@andig
Copy link
Owner

andig commented Apr 12, 2019

/cc @mwittig siehst Du eine Möglichkeit das mehrfache Laden von Plugins in Pimatic zu erlauben? Das würde hier erlauben ein Plugin je vorhandener Fritzbox zu starten.

@mwittig
Copy link
Contributor

mwittig commented Apr 14, 2019

Hallo Andreas. Nein, das mehrfache Laden von Plugins in Pimatic ist derzeit nicht möglich und auch nicht ganz einfach zu realisieren.

Willst Du generell beliebige Multi-Fritzbox Szenarien unterstützen, oder geht es hauptsächlich um den hier vorliegenden Fall (Mesh-Setup). Siehe dazu auch meine Erläuterungen zu "Support multiple AVRs?"

@andig
Copy link
Owner

andig commented Apr 15, 2019

Referenz: mwittig/pimatic-yamaha-avr#13

@andig andig linked a pull request Apr 15, 2019 that will close this issue
@andig
Copy link
Owner

andig commented Apr 17, 2019

@mwittig mir geht es jetzt noch um den allgemeinen Fall. Mehrere Fritzboxen ist vielleicht etwas ungewöhnlich. Mehrere Receiver kann ich mir durchaus eher vorstellen, bestimmt gibt es auch noch andere Fälle. Ich habe daher die Diskussion im Denon Repo bzgl. mehrfachem Laden mal aufgelassen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants