Fritz-Plugin - Performance and Integration of Contact Devices

---

Hello everybody,

I’m using the (AVM) pimatic-fritz-plugin from andig and I really like it - but now I face some problems which I hope you can help me to find a workaround.

Since the current FritzBox beta releases, you can connect HAN-FUN devices to the FritzBox.
Currently, I have the following devices connected to my FritzBox 7490:

• 6x AVM DECT 200 switch devices
• 2x AVM DECT 210 switch devices
• 1x AVM DECT 100 dect-repeater device
• 12x AVM DECT 301 thermostat devices
• 4x Magenta SmartHome smoke detector devices (HAN-FUN)
• 1x Magenta SmartHome dual-button device (HAN-FUN)

I was so happy when andig updated the plugin to “support” contact sensors. But at the current stage, it seems that only the (Magenta SmartHome) window contact is practically usable, as the button and smoke detector devices have a too small “closed” state to be detected by the pimatic in time.
Currently, the FritzBox beta natively only supports to switch a switch device and/or send an email when the contact device is triggered.

Detection in time is the next big thing.
I’m aware that I got a lot of devices to check - 8 switch states, 12 thermostates, 21 temperature sensors and 6 contact devices.
When I set down the polling interval to 10 seconds some time ago with less than half of the devices, the polling tasks stacked up. The tasks prevented any actions. This was so harsh that it could take up to two hours until a switch command was executed. And I’m working with a daily reboot to keep my pimatic fresh and healthy.
So I went back to the default interval of 60 seconds. But with the growing amount of devices, I feel polling tasks are stacking up again and with the current load, switch tasks take about 10-15 seconds to be executed.

Now I come to the following questions:

• What is the bottleneck when it comes to polling the devices? Pimatic or the FritzBox? Will changing for a FB7590 improve the performance?
• Is there anything I can do except reducing the polling intervalls and/or amount of polled devices (e.g. deleting some temperature sensors)?
• What is your suggestion for the smoke detectors and the button device? Currently my only idea is to let them switch one common empty socket switch by the integrated FritzBox mechanism and then let pimatic detect that switch status change, followed by a notification rule.

Thank you for your ideas and suggestions!

@wolfpack With the pimatic-fritz plugin each device is polled individually and for some devices like the FritzOutletDevice multiple callouts are made to gather the status information in each cycle. This causes a lot of overhead at both ends (pimatic & FB) with a larger number of devices as you have. Certainly, it would be better to have a single bulk read (read all status information for all devices), but I am not sure this is possible with the FB API.

What do you mean by smoke detector devices have a too small “closed” state? If I fire alarm is raised the FB device shall remain in closed state.

@mwittig Thank you for clarifying the multiple callouts - that explains a lot. If andig is reading this - it would be great if a bulk read was possible to realize.

You’re right with the too small closed state regarding the smoke detectors - i confused it with the button-device. In my case with the current polling cycles, the pimatic should hopefully detect the closed state in a maximum of 3 minutes. I should test that with a smoke detector test-spray. Pressing the test-button gives alarm, but does NOT trigger the closed state.
And hopefully a potential fire isn’t growing so fast that it kills the smoke detector before the pimatic notices that it’s burning…

@wolfpack said in Fritz-Plugin - Performance and Integration of Contact Devices:

it would be great if a bulk read was possible to realize.

Unfortunately, the AHA API does not provide for bulk access. It might be possible using the TR64 API.

https://avm.de/fileadmin/user_upload/Global/Service/Schnittstellen/AHA-HTTP-Interface.pdf

Little feedback from my side:
I switched to a 7590 and the performance boost is outstanding! I also encountered that switching operations are more quickly done. Now there is almost no delay between acitvating an Amazon Dash Button and the Fritz outlet switching. So for everyone with the same problem: a hardware upgrade will do the trick!

Very nice to hear and thx for the feedback!!

@wolfpack said in Fritz-Plugin - Performance and Integration of Contact Devices:

So for everyone with the same problem: a hardware upgrade will do the trick!

Thanks for the info.

@Wolfpack did you try to update your 7490 with a lab firmware before buying new hardware? maybe this would have speed up something, too

@quotschmacher said in Fritz-Plugin - Performance and Integration of Contact Devices:

maybe this would have speed up something, too

According to my experience the AVM lab firmware is slower than the stable version most of the time as it usually has additional debug output and reporting activated.

@quotschmacher said in Fritz-Plugin - Performance and Integration of Contact Devices:

@Wolfpack did you try to update your 7490 with a lab firmware before buying new hardware? maybe this would have speed up something, too

I’m totally sorry and I fully understand that you want to avoid hardware investments, but: yes, I tested it!

The 7490 was slow on stable and slow on all lab versions. A friend of mine was updating his 7490 parallel to mine, but as soon as I switched to the 7590, my setup left his far behind. Regarding several years of embedded cpu evolvement between both models makes this difference reasonable.