Node-red-contrib-fritzapi

General
1

I used the nodes provided by node-red-contrib-fritzapi for many years in my flows.
Since a few weeks I get "Device not ready" messages in my debug window.
I use "outlet" nodes provided by the api to retrieve things like energy and power from my Fritz power outlets or I simply want to switch a bulp. This does not work any more.
I still see the specific outlet node being connected (little green indicator below the node) but it does not return a result any more.

2

Related?

At a guess, the API has changed and unfortunately, this node has been abandoned: GitHub - dnknth/node-red-contrib-fritzapi: Home automation node for Fritz!Box, Fritz!DECT and FRITZ!Powerline devices.

There is a fork updated 2 weeks ago here: GitHub - Tobi-ctrl/node-red-contrib-fritzapi: Home automation node for Fritz!Box, Fritz!DECT and FRITZ!Powerline devices.
but i dont think it has been published to NPM or the Node-RED catalog however it is still possible to try it.

  1. stop node red
  2. cd to .node-red dir
  3. uninstall non working node npm remove Node-red-contrib-fritzapi
  4. install direct from github using npm install Tobi-ctrl/node-red-contrib-fritzapi
  5. start node-red

Worth a go

3

Same Problem as Andreas. Spend a lot of time to build a user interface,
visualizing home parameters (power, energy, temperature, ...) just to see
it being smashed to pieces. I use a couple of FRITZ-devices, which are
no longe accessible. Has anyone followed Steve's advice? Is it working
with FRITZ!OS 8.02?
Thanks
Peter

4

I am having the same issue after updating from FritzOS 7.XX to 8.03. I can no longer control my Rollotron DECT Blinds which were working fine for the past 3 years.

I followed Steves advice and installed the fork Tobi-ctrl/node-red-contrib-fritzapi, however this did not help at all.

Hopefully someone can help fix this issue. Does anyone know if there is documentation from AVM available regarding what has been changed?

5

I let Cline run widly over the original package and just provided it the pdf with the api changes. Took some fixing and adjusting, but this is working now on my end:

You can just download the .tgz in /dist and install it via upload on node-red

6

Thank you @praul

Unfortunately, I literally just got done setting up an old fritzbox 7430 in IP Client mode just to run my SmartHome devices as it is stuck on 7.31 anyways and therefore still works with the old api.

I will probably try to move everything back next weekend and try your fork on 8.03.

7

Hi folks, my system is running again.
Here my system environment: fritzbox 7530, updated to 8.02, DECT200-switch, node-red-contrib-fritzapi v 0.5.2.
I searched the fritzbox-environment and found under "SmartHome/Geräte und Gruppen", aside from my 7 registered DECT-devices ("Status" = OK) an unknown device which was not connected, according to the reading in "Status". I simply removed this device. And that was it!
I could use the fritzapi-nodes, like i did beforehand.
I really do not know, what caused this erroneous entry, nor do I know how it could influence operation. I tried a lot, including the removal of all fritzapi-nodes, deletion and re-installation of the fritzapi-environment, but all in vain.

I hope you can solve your problems as easy as I was able to do it.

Peter

8

Hey @Peter2,

I had the same unknown device entry on my end. Deleting it fixed it for me as well, no api changes needed.

Looks like the update to 8.03 created an unknown device in the FritzBox SmartHome Device list somehow. Deleting it was the fix!

1 Like
9

Could it be this simple? Lol, looks like my time for the refactor was a waste. Thanks for finding out. Will try when I get home

10

Peter2, you got it! Thank you for this fix! My problem is solved now.