Breezyken

And then I created a new account at Resideo.com and I still can't log in to the redirect in API configuration. error shown in attached clip.

I'm having similar problems. I've had a developer account for several years, but my old API did not work. I created a new API, got my Keys, and when I enter my Keys on the azure website and asked to log into Honeywell Home, I'm told my login is incorrect. I'm not sure if this is the same site I use to access my thermostats, but I can log into that site (https://www.mytotalconnectcomfort.com/portal) successfully. Do I need an account on a third site? Attempts to reset my password fail (as others have stated above), saying my email address is unrecognized in the system. I'll stay tuned here to see what develops.

Thanks Bob, that fixed the Daily and Month observations. The log is still showing the same parsing error for the yearly obs. Ken

I have installed the current DavisWeather poly (2.0.1), configured the settings, and loaded all the nodes. However, only the current conditions from the console are displayed. None of the observations data is being filled in. I queried the server with https://api.weatherlink.com/v1/NoaaExt.json?user=<my Station ID>&pass=<my password>&apiToken=<my token> and that returns ALL the data, including Daily, Month, and Yearly (But maybe not enough data to parse?). My configuration parameters were copied directly from the node configuration and pasted into the URL. Why is it not populating on the admin console? My station is a Vantage Pro 2. I don't have a solar radiation sensor. I've attached the first part of the log, but the rest is just repetition of the parse error. I also attached a sanitized response to the API call. DavisWeather Debug Log.txt JSON Message.txt

I just upgraded to EISY and Kasa is one of the first node servers I have installed, although I had WeatherLink running on Raspberry Pi earlier. I have been having similar problems as above with the HS300 power strip, with the admin console showing Kasa connected, but no nodes appeared. I have Iox 5.7.1, Kasa 3.1.4, PG3x 3.2..16, udx ?.? (don't know where to find that one). I finally installed the Dev packages, reinstalled Kasa node server, restarted everything, and the power strip appeared in the admin console, so now it is working fine. Thanks for all the background and answered queries above.