joeyhage / homebridge-alexa-smarthome

Connect Alexa devices to HomeKit
MIT License
93 stars 22 forks source link

Air quality monitor - InvalidResponse (State not available) #170

Open ma-armenta opened 2 months ago

ma-armenta commented 2 months ago

Describe The Bug:

After the initial setup, specifying a single device (air quality monitor), and signed on using MFA code I get an error InvalidResponse(State not available)

To Reproduce:

Log in as instructed on readme file.

Expected behavior:

Logs:

[9/14/2024, 11:22:23 AM] [HomebridgeAlexaSmartHome] Alexa login cookie updated. Storing cookie in file: /var/lib/homebridge/persist/.homebridge-alexa-smarthome
[9/14/2024, 11:22:24 AM] [HomebridgeAlexaSmartHome] Added accessory: AirQSensor humidity
[9/14/2024, 11:22:24 AM] [HomebridgeAlexaSmartHome] Added accessory: AirQSensor
[9/14/2024, 11:22:24 AM] [HomebridgeAlexaSmartHome] Added accessory: AirQSensor carbon monoxide
[9/14/2024, 11:22:26 AM] [HomebridgeAlexaSmartHome] AirQSensor - Get air quality - InvalidResponse(State not available)
[9/14/2024, 11:22:27 AM] [HomebridgeAlexaSmartHome] AirQSensor - Get PM2.5 density - InvalidResponse(State not available)
[9/14/2024, 11:22:27 AM] [HomebridgeAlexaSmartHome] AirQSensor - Get VOC density - InvalidResponse(State not available)

Plugin Config:

{
            "devices": [
                "AirQSensor"
            ],
            "excludeDevices": [],
            "auth": {
                "refreshInterval": 4,
                "proxy": {
                    "clientHost": "192.168.68.67",
                    "port": 9000
                }
            },
            "amazonDomain": "amazon.com",
            "language": "en-US",
            "performance": {
                "cacheTTL": 60
            },
            "debug": false,
            "platform": "HomebridgeAlexaSmartHome"
        }

Screenshots:

Environment:

saveriospeziali commented 1 month ago

I have the same issue

saveriospeziali commented 1 month ago

Hi, try to downgrade to v2.1.5, let us know

newspeer commented 1 month ago

Same issue with 2.2.1 Working fine with 2.1.5

Any indication when this will be fixed in a newer release?