[solved] Controlling AVM Fritz Powerline 546e
Hi Guys,
is there any possibility to control the AVM Powerline Series esp. the 546e plug by the actual fritz plugin provided by Andreas Goetz?
After knowing that Andreas can switch and read the 546e plugs Github to fritzapi, he also mentioned to use the MAC as AIN to use the Powerline devices.
I tried to connect my 4 546e devices to pimatic, with no luck 
The Dect200 device works perfect…
Is there anybody who has successfully connected a powerline device to pimatic?
Greets Andre
@propeller Did you try to setup the device with the AIN, manually? Maybe the device discovery function is not able to detect it, but possibly device control works with AIN printed on the device.
EDIT: Where did Andreas mentioned to use the MAC as AIN for Powerline? Can you please add a reference? Thanks.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig Sure, the devices are set up manually. No device detection is used.
There is a combined AIN/MAC address shown on the device label. I tried to use the AIN/MAC with and without the colons without success.
-> Andreas DID NOT mention using MAC as AIN functionality… my fault. shame on me!
I think it was a crosslinked document, i will get this information that evening.
The MAC as AIN information was based on this site: openhab
There is also a hint for a possible MAC address in AVM Homeauto.PDF
section “service tables”: possible values for the AIN string is a “:” as well.
The web interface of the 546e device also shows the MAC address as AIN (firmware version 7.01).
greets Andre
@Propeller I haven’t used pimatic for some time and would need a bit longer to get up to speed again. Do you have any logfile to show whats going on?
Hi Andreas,
great to hear from you.
Logs enclosed:
10:49:36.720 [pimatic-fritz] error: Cannot access http://192.168.178.1/webservices/homeautoswitch.lua?0=0&sid=c918d6a01b976fc4&switchcmd=getswitchstate&ain=5C4979ED1A4B: 400
Unhandled rejection (<{"error":null,"response":{"statusCode"...>, no stack trace)
10:49:49.299 [pimatic] info: Recreating "fritz-546e"...
10:49:49.835 [pimatic-fritz] error: Cannot access http://192.168.178.1/webservices/homeautoswitch.lua?0=0&sid=c918d6a01b976fc4&switchcmd=getswitchstate&ain=5C:49:79:ED:1A:4B: 400
Unhandled rejection (<{"error":null,"response":{"statusCode"...>, no stack trace)
Do you need additional data?
Greets Andre
@propeller said in Controlling AVM Fritz Powerline 546e:
Do you need additional data?
What you can do is to restart pimatic and check the log for fritz plugin messages. The plugin dumps the AIN of the found devices on startup. Please check how many Switch AINs you get.
21:08:22.756 [pimatic-fritz] Switch AINs: 047110815232
21:08:24.179 [pimatic-fritz] Thermostat AINs:
21:08:24.373 [pimatic-fritz] Contact sensor AINs:
@Andreas-Goetz I have filed a PR with a fixture for the “unhandled rejection” issue
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Only debug info from the fritz plugin is:
info [pimatic-fritz]: Switch AINs: 116300039687
Thats a DECT200 device.
My DECT100 Repeater is not listet in the log after restarting pimatic.
Maybe it is a issue with the newer Fritzbox firmware:
The Powerline devices are not longer listed on the web interface in the smarthome section.
Greets Andre
@propeller said in Controlling AVM Fritz Powerline 546e:
The Powerline devices are not longer listed on the web interface in the smarthome section.
Does this mean you are no longer able to switch it via the Fritz!OS WebUI? If so, it may be a firmware mismatch between the plug and the router.
If you upgraded the plug to Fritz!OS 7.01 the router should have Fritz!OS 6.90, at least. Normally, this should be the case as the new plug firmware is no longer provided for download, but it is a part of the router firmware upgrade procedures.
In my case the upgrade of the powerline adapters (I have 1000e not 645e, so I can’t reproduce your case) as part of router upgrade did not work at all because they were running a very old firmware. So, it may be sensible to check which firmware version you have on the router and on the plug.
To solve my case (even manual upgrade via UI wasn’t possible), I used the Fritz!Powerline desktop software to upgrade the plug firmware to the latest firmware offered.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig
Right, i can not switch the powerline devices via the Fritz!box webUI anymore.
Only devices listed here are the dect ones. Only devices which can be newly paired are dect devices.
I think this happens at firmware versions >6.9
I can see all of them in the network listing or mesh listing with name/connection speed/ip…
Here they are also declared as “smart home” devices. You can even see details from the device here.
Firmware fritz!box is 07.01, firmware 546e is 07.01
I just checked the firmware version of my 1220E: 2.6.0.2-25
@propeller said in Controlling AVM Fritz Powerline 546e:
Right, i can not switch the powerline devices via the Fritz!box webUI anymore.
OK, but then I suppose it is not an issue with the fritz plugin. See the following link. Maybe it is worth giving a try.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Problem solved.
On Fritzbox firmwares <6.92 the Poweline devices are used as smart home devices just as connected to the local network.
For firmware version >6.92 the Poweline devices must be separately paired to use mesh/smart home funktions.
My powerline devices have only been connected to the local network through the powerline pairing. After additionaly pairing them to the mesh they showed up in the web UI smart home section and could be switched on/off plus power metering (546e).
Also the fritz-pluging is working with the powerline MAC/AIN (separated with colon “:”) as AIN.
Hint: the powerline devices can not be paired at once, the process must be done one after another. For smooth pairing just to be sure, unplug and plug the Poweline device before pairing.
@mwittig: thanks for your support. 