Need to restart add-on before giving a command

[kevtuning]

My HA and AC are working fine since years... but since a couple of days I need to constantly restart the add-on to give some orders to the AC.

Nothing in the logs except a lot of

D0331 18:12:02.077 notifier.py:112] [KeepAlive] Sending PUT http://192.168.5.246/local_reg.json {"local_reg": {"ip": "192.168.5.142", "notify": 0, "port": 8888, "uri": "/local_lan"}}

I even tried to restart the AC ... but it makes no senses to me.

Any idea where the issue could come from ?

Thanks

[kevtuning]

I am trying to debug this today and I discovered something strange but maybe interesting:

• when I have the issue... the Fujitsu AC is also not responsive from FGLair ....

That brings me to a question... How many KeepAlive have you per seconds ?

In my case, it varies from 5 to 10 each seconds...

Is it overflooding the small wifi dongle ?

[kevtuning]

In the meantime, as workaround, I've added a add-on restart after one minute of command without action in my node-red flows ...

(it's clearly more boring when the heater has not been turned on in the morning...)

[kevtuning]

What I've tried is to rename the json config file and to restart the add-on... and for the moment (16 hours) it makes the trick...

but there's absolutely no sense since the new json is exactly the same that the old one.

[colino17]

I'm seeing the same issue. Everything will work great for a few hours and then HA commands will stop working. I will try to change the state of the heat pump in HA and it won't respond even though it still shows as available.

[djm193]

Same for me. Habe a Hisense multisplit AC

[kevtuning]

rename the json config file and to restart the add-on

Since then... no more issue

[colino17]

rename the json config file and to restart the add-on

Since then... no more issue

No luck. Problem always reappears after a few hours.

[kevtuning]

Damn, I have again the issue....

We absolutely need to understand what's happening... to fix it

It seems like that the AC isn't working with FGLair neither... so I would reboot the AC module...

what is making just no sense with working fine after an add-on restart.

I have juste done the folling test right now :

1. Try to turn on trough HA => not working
2. try to turn on trough FGLair => not working
3. Restart add-on
4. Try to turn on trough HA => working
5. Checking FGLair => OK .. it appears working
6. try to turn off trough FGLair => not working
7. Try to turn off trough HA => not working
8. Restart add-on
9. Try to turn off trough HA => working
10. Checking FGLair => NOK .. the AC is still appearing ON but after app close/open => OK

I'll reboot the AC when I'll be home (test done trough Nabu casa)

[kevtuning]

Indeed rebooting the AC seems like to solve the issue ... for the moment.

My theory is that the module is receiving too much requests and finally blocks...

But anyway all of this doesn't makes any sense

[kevtuning]

Got the problem again...

Is someone having a lead?

I am always concerned by the number of keep alive requests...about 4/sec

[colino17]

Got the problem again...

Is someone having a lead?

I am always concerned by the number of keep alive requests...about 4/sec

I ended up giving up on this project and switched back to the HACS FGLair Cloud Integration and also an IR Blaster. Could never get any stability. It would work great for several days or hours before completely borking itself.