bashGroup / node-red-contrib-fritz

Generic Fritzbox node for node-RED, giving access to tr064 api
MIT License
51 stars 15 forks source link

Version 1.45 does not work with FRITZ!Box 7490 version 7.28 #86

Closed FrankP2 closed 2 years ago

FrankP2 commented 3 years ago

Hello,

after updating my FRITZ! Box 7490 to FRITZ! OS 07.28, communication between Node-RED (node-red-contrib-fritz, version 1.45) and the FRITZ! Box no longer works. The Node-RED log now contains entries such as [error] [fritzbox-in: read guest WLAN password] No Services response received.

In Node-RED, when I try to update the "Service" list box in a "FRITZ! Box" node, I only get a list with no entries, there is no error message. I can make changes in the configuration node for the FRITZ! Box, but I cannot see the effects or error messages.

In the FRITZ! Box, under Home Network / Network / Network Settings / Home Network Approvals, the item "Allow access for applications" is activated so that TR-064 access should be possible. Same with upnp-Setting. In the changes to FRITZ! OS 7.28 provided by AVM (https://download.avm.de/fritzbox/fritzbox-7490/deutschland/fritz.os/info_de.txt), I cannot see what happens with regard to access by outside has changed.

Perhaps https://avm.de/service/schnittstellen or https://avm.de/fileadmin/user_upload/Global/Service/Schnittstellen/Recommendations%20for%20user%20guidance%20for%20logging%20into%20a%20FRITZBox_v1.1_EN.pdf plays a role here?

Does anybody have the same Problem? What's the solution for that? ;-)

gon0 commented 2 years ago

I have a 6490 Cable and the same issue with 7.28. The node just returns "No Services response received."

mh-82 commented 2 years ago

Same issue here FRITZ!Box 7590 with FRITZ!OS 7.28 running Node-Red node-red-contrib-fritz 1.4.5 Only getting "No Services response received" for all my calls to the FRITZ!Box. No solution found so far

armageddon421 commented 2 years ago

Same with 6890 LTE on FritzOS 7.21 Okay correction: Started working again for whatever reason. But thanks for the heads up, not updating to .28 unless this is resolved.

gon0 commented 2 years ago

Indeed, there were changes in the log-in process: https://avm.de/service/schnittstellen/ I was told from AVM Support. Right now, I have no time to look into that, but I wanted to leave the information here.

gon0 commented 2 years ago

Strangely, the node works again as before - in the meantime I restarted the Fritzbox, added a VPN-Connection again which was lost after the update. I don't think my changes had an impact on this function. However, the node works again as expected.

FrankP2 commented 2 years ago

@gon0: Thanks for your hint. I still get "No Service response received." What have I done? a) Unplug FRITZ! Box 7490 from power supply, wait 10 secs and plug again with power supply. b) Check the users in fritz.box. Strange: my user for VPN has no rights to access via internet!? Ok, right is granted. Changed the password for the NodeRED user and also change it in the configuration node in NodeRED. c) Update NodeRED to 2.0.6 and restart NodeRED.

Is there anything else you changed to get node-red-contrib-fritz work with FRITZ!OS 7.28?

gon0 commented 2 years ago

Dear @FrankP2, sorry, I cannot provide more information than before. I am still wondering why the node suddenly works again. regarding a) Yes, I did the same b) The VPN-User does not need the "access via internet" checkbox. You can also check the AVM guide to set up the VPN-connection. Here, the "access via internet" checkbox is not mentioned. c) I did not update my node-Red, because last time I lost everything (I have Node-Red running in a docker on a QNAP container station)

So far I have no idea, what started the node to work again. I checked, that I have version 1.4.5 of the node. I am sorry, that I do not have a solution so far.

mh-82 commented 2 years ago

Can confirm here, same thing.

The node works again, nothing changed, no reboot of NodeRed or the Fritzbox. Also no update on anything.

Still on Version 1.4.5. of the Node and 7.28 Fritz!OS.

gon0 commented 2 years ago

I found something: Since 3rd of November, the node responds "No Services response received." again. When the node responded with the "No Services response received."-Error again, my NAS-System running Node-Red in a docker was physically disconnected from the network. This response makes sense, since the NAS was not connected to the network. After reconnection of the NAS to the network, the node was still reporting "No Services response received.", although the network connection was established again.

Today, I changed a flow (just enabling a debug node) and pressed "deploy". From this time on, the node-red-contrib-fritz is working fine again. It seems that starting the docker container containing node-red does not do the same as "deploy".

@FrankP2, could you try to deploy in node-red and watch the response of the contrib-fritz-node?

FrankP2 commented 2 years ago

The nodes from node-red-contrib-fritz (version 1.45) are all working well again. I don't know why, I just restartet the FRITZ!Box and hit "deploy" in NodeRED. Thanks for all your support.

bartrail commented 11 months ago

Just wanted to add almost 2 years later: I recognized the same error message after looking into Node red after a couple of months. I'm currently running a Fritzbox 7590 v7.57 with node-red-contrib-fritz (version 1.45). Restarting the Fritzbox, restarting all Flows did the trick for me as well 👍