Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

 

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

Label of the router. I need to read the model number so I know if that firmware is good for you or not. 

  @Clive_A - here you go:

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

 

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

Label of the router. I need to read the model number so I know if that firmware is good for you or not. 

  @Clive_A - here you go:

 

 

Should be good. That link I gave to you is the EU version for your model. Try the manual upgrade. 

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

 

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

Label of the router. I need to read the model number so I know if that firmware is good for you or not. 

  @Clive_A - here you go:

 

 

Should be good. That link I gave to you is the EU version for your model. Try the manual upgrade. 

  @Clive_A - apparently not:

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

Also, I am in Australia and the support page for the FR365 on the regional site does not show any firmware upgrade: Festa FR365 Support - AU.

 

Are you sure that I can use the firmware from the page that you linked to? I don't want to brick my router!

Label of the router. I need to read the model number so I know if that firmware is good for you or not. 

  @Clive_A - here you go:

 

 

Should be good. That link I gave to you is the EU version for your model. Try the manual upgrade. 

  @Clive_A - apparently not:

 

 

  @Clive_A - OK, I have updated the firmware. I'll reboot the Netgear NAS and see what happens to its IP address.... fingers crossed, although there was nothing specific to Fixed IPs in the release notes.

@Clive_A - no improvement, I'm afraid.

My Logitech Harmony Hub has been reassigned a new IP address, despite me specifying a fixed IP:

The result being that my Home Assistant server now cannot find the Harmony Hub because its IP address has changed. I have to remove the integration and then add it again with the new IP address until Uncle Festa decides to reassign yet another new IP.

Do I need to formally report this as a bug or do you have enough information to progress this internally?

  @Mr_Orange 

Mr_Orange wrote

@Clive_A - no improvement, I'm afraid.

 

My Logitech Harmony Hub has been reassigned a new IP address, despite me specifying a fixed IP:

 

 

 

The result being that my Home Assistant server now cannot find the Harmony Hub because its IP address has changed. I have to remove the integration and then add it again with the new IP address until Uncle Festa decides to reassign yet another new IP.

 

Do I need to formally report this as a bug or do you have enough information to progress this internally?

I am not familiar with any hub devices. I cannot rule out the possibility that there is a problem with them, as they are weak in hardware and performance. I don't think I would use it as a test result. 

What's the result for the NAS or regular PC? Let's keep the subject simple.

From the eyesight verification and device output, they are set with the fixed IP and rebooted or reconnected the cable, yet ipconfig or show IP addr tells the same result that IP is not fixed as the config? 

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

@Clive_A - no improvement, I'm afraid.

 

My Logitech Harmony Hub has been reassigned a new IP address, despite me specifying a fixed IP:

 

 

 

The result being that my Home Assistant server now cannot find the Harmony Hub because its IP address has changed. I have to remove the integration and then add it again with the new IP address until Uncle Festa decides to reassign yet another new IP.

 

Do I need to formally report this as a bug or do you have enough information to progress this internally?

I am not familiar with any hub devices. I cannot rule out the possibility that there is a problem with them, as they are weak in hardware and performance. I don't think I would use it as a test result. 

 

What's the result for the NAS or regular PC? Let's keep the subject simple.

From the eyesight verification and device output, they are set with the fixed IP and rebooted or reconnected the cable, yet ipconfig or show IP addr tells the same result that IP is not fixed as the config? 

  @Clive_A - the Harmony Hub is just a wireless remote control hub. It is nothing complicated and was working with a fixed IP on my previous Eero 6 system.

The NAS seems to have kept the fixed IP for now.

I have literally never used a router, that offered DHCP reservation, not honour those reservations no matter the number of reboots of the client or the router. It's very obvious that this is an issue with the Festa products not the client devices. My clients that have been impacted by this bug so far are:

• Netgear ReadyNAS;
• Synology DS1019+ NAS;
• Raspberry Pi 4;
• Logitech Harmony Hub;
• Desktop PC running Windows 11; and
• Anthem AVM60 AV Processor.

As you can see, that is a diverse list of client devices. The only common item between them is the Festa FR365 and how it handles DHCP Reservation. Please raise a bug report with the software team.

  @Mr_Orange 

Mr_Orange wrote

Clive_A wrote

  @Mr_Orange 

Mr_Orange wrote

@Clive_A - no improvement, I'm afraid.

 

My Logitech Harmony Hub has been reassigned a new IP address, despite me specifying a fixed IP:

 

 

 

The result being that my Home Assistant server now cannot find the Harmony Hub because its IP address has changed. I have to remove the integration and then add it again with the new IP address until Uncle Festa decides to reassign yet another new IP.

 

Do I need to formally report this as a bug or do you have enough information to progress this internally?

I am not familiar with any hub devices. I cannot rule out the possibility that there is a problem with them, as they are weak in hardware and performance. I don't think I would use it as a test result. 

 

What's the result for the NAS or regular PC? Let's keep the subject simple.

From the eyesight verification and device output, they are set with the fixed IP and rebooted or reconnected the cable, yet ipconfig or show IP addr tells the same result that IP is not fixed as the config? 

  @Clive_A - the Harmony Hub is just a wireless remote control hub. It is nothing complicated and was working with a fixed IP on my previous Eero 6 system.

 

The NAS seems to have kept the fixed IP for now.

 

I have literally never used a router, that offered DHCP reservation, not honour those reservations no matter the number of reboots of the client or the router. It's very obvious that this is an issue with the Festa products not the client devices. My clients that have been impacted by this bug so far are:

 

• Netgear ReadyNAS;
• Synology DS1019+ NAS;
• Raspberry Pi 4;
• Logitech Harmony Hub;
• Desktop PC running Windows 11; and
• Anthem AVM60 AV Processor.

 

As you can see, that is a diverse list of client devices. The only common item between them is the Festa FR365 and how it handles DHCP Reservation. Please raise a bug report with the software team.

I have kept asking for this: What is the reading from the device, Windows 11? Not reading the IP from the controller.

Look, Festa is a system that is based on the cloud. Sync would be delayed. You cannot just read the controller client list as it is not instantly synced. 

The DHCP is a basic standard. If you need to verify it, you need to read the IP from the device and see if it gets the IP after you set it on the controller and reboot it. I shared the guides previously about how DHCP works. 

My job is to evaluate and make sure the steps are done correctly before sending it to the test or dev team. 

Or you insist, provide the remote environment for the team to use Wireshark to verify if the DHCP server sends the wrong IP. I will simply step back and let the test team do the work, and I will only reply with necessary information from their instructions. 

I have spent a lot of attention on this, but it is not going to confirm key points. 

  @Clive_A - OK, I performed a simple test with the Netgear NAS. Before I unplugged the ethernet cable, the IP was 192.168.0.119. I changed the Fixed IP setting to match this a couple of days ago after I last rebooted the NAS.

I unplugged the ethernet cable and then plugged it back in after about 5 minutes. The assigned IP address is now 192.168.0.87. This is visible in the Switch Client list:

however, the Fixed IP setting still says:

The NAS itself is only reachable via the newly assigned IP of 192.168.0.87 and when I log in, the NAS confirms that this is its IP address:

The main client list in the Festa CBC has also updated to show the new IP address:

Is that conclusive enough?

Do you need me to test anything else?