kevtuning
kevtuning
When I watch on MQTT side... Transmitted 8:50:12 AM QoS: 0 Payload: 21.0 Received 8:50:13 AM QoS: 0 Payload: 2 And 5 minutes later... Received 8:55:20 AM QoS: 0 Payload:...
It's a known limitation of the Fujitsu AC that only replies in the same subnet. The workaround is to use the local ip configuration. You'll find some documentation on it...
No, you're HA server should have an additional IP in the 192.168.30.x range, say 192.168.30.200 and so you should have local_ip: 192.168.30.200 That way, your Fujistu will reply back to...
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...
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...
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...
Any chance to get it merged with 2023.10 ?
@gyro-labs submitted two Pull Requests regarding this... Not really sure what is the privée to have it validated and integrated in the official add-on... I am also waiting for it...
Oh ... I get the same error from tonight... It was working this morning... and I didn't changed something... The AC is replying to the ping... Core 2024.2.5 Supervisor 2024.02.1...