Closed mnikashov closed 1 year ago
Yeah. Looks like you have two problems. 605C does sound a bit on the hot side. :) What does your thermostat say when it's reporting that? Do you get a room temperature reading in the FGLAir app?
What are you putting in the IP field? If you put anything at all it needs to be to the device running Homebridge. If you put nothing the plugin will just use the first IP that doesn't point to localhost.
Could you try v1.1.0? It may fix the IP issue.
If you could also let me know what the FGLair app and thermostat say your temperature is at when Homebridge complains about it being 600 degrees C that'd be helpful.
I'm closing this. Let me know if this is still an issue.
You get this error message when running in Child bridge: This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 605.4000000000001 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info. Error: listen EADDRNOTAVAIL: address not available IP at Server.setupListenHandle [as _listen2] (node:net:1355:21) at listenInCluster (node:net:1420:12) at doListen (node:net:1559:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)
Edit 1: And you get this error when running as a regular plugin: Error: listen EADDRNOTAVAIL: address not available IP at Server.setupListenHandle [as _listen2] (node:net:1355:21) at listenInCluster (node:net:1420:12) at doListen (node:net:1559:7) at processTicksAndRejections (node:internal/process/task_queues:84:21)
Edit 2: if you remove IP from the settings when running in regular plugin mode you starting to get the same warning as with the child bridge: This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 605.4000000000001 exceeded maximum of 100. See https://homebridge.io/w/JtMGR for more info. but starting to work.