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.

Thanks to everyone that jumped in to solve this mystery. The technique in the YouTube video to start linking revealed that what my old eyes thought was a 40 was actually a 4D. Everything went smoothly once that was corrected. Fri 09/10/2021 12:50:09 PM : Start Insteon Device Linking Mode Fri 09/10/2021 12:50:09 PM : [LNK-BGN ] 02 64 01 00 06 Fri 09/10/2021 12:51:03 PM : [LNK-STAT ] 02 53 M(01) gid=00 4D.4E.13 0124 42 Fri 09/10/2021 12:51:03 PM : [4D.4E.13 00] Linked device type=01.24 fw=42 Fri 09/10/2021 12:51:03 PM : [4D 4E 13 0 ] Added to list of devices to link to ISY Fri 09/10/2021 12:51:03 PM : [LNK-BGN ] 02 64 01 00 06 Thank You

Attached is the diagnostic results of trying to add the 2474d dimmer. It looks like there is no communication to the device. I am using a valid load (2 60 watt incandescent bulbs). Thanks for the links to the Insteon command list and device tables. The Youtube video is helpful and I will check all the details and try the method in the video to establish communication.

Attached is the diagnostic results of trying to add the 2474d dimmer. It looks like there is no communication to the device. I am using a valid load (2 60 watt incandescent bulbs). Thanks for the links to the Insteon command list and device tables. The Youtube video is helpful and I will check all the details and try the method in the video to establish communication.

I am using a compatible load (2 60 watt incandescent bulbs). I have tried both 2474D modules as well as the auto detect function. The error "Cannot determine Insteon Engine" says to me the device has been detected but the software is not correct (and I'm probably wrong. It would be nice if the device type was ordered by part number, but Category and subcat must mean something to someone. Any more thoughts and is there a definition/description of Cat & Subcat? Thanks

I have installed a new 2474D 2-wire dimmer switch but when I try to add it to the ISY994i I receive the error message "Cannot determine Insteon Engine". I know this device is RF only, but there are several dual mode Insteon devices nearby. In the list of Insteon devices the 2474D is described as a "Companion Dimmer'; not sure what that means. Any hints to decrypt the error message and get this linked would be appreciated.

OK, now that makes sense since there is no common reference point between AC ground/neutral and the 12 (20) volt unregulated supply. That can float almost anywhere referenced to "ground". Let's hope these things keep working until a quality interface becomes available.

Now I'm curious where you are measuring the unregulated supply voltage. Are these functioning modules? 330K should have no effect on the voltage measurement. Maybe try using a simple VOM? I'm not adverse to putting a meter on any point in a line powered device, but if I need to use the scope I use an isolation transformer on the device.

There is an isolation boundary separating the AC line from the primary 12 volt supply voltage consisting of T1 and U2, the optical isolator which provides feedback to the switching supply. There is no "ground" on the AC side of the supply where the 4 power diodes are. The 12 volt supply is referenced to the isolated side of the supply, such as the negative sides of C7, C13, and C14, and of course T1. Maybe you are picking up some stray field from T1 and associated high frequency traces. It's been almost four years since I repaired my 2413S PLM V1.B/1351 and it is still going strong!

I'm not really concerned with the status of the relay because I am using it in momentary mode 'C' with the logic. I have it displayed because that is the icon that seems to control the door. Although I'm using momentary mode 'C', the relay status seems to toggle On after I touch the status icon, and the door does not operate. Sometimes a second touch of the status will operate the door and toggle the relay status. This is just not repeatable or reliable. I'll try your suggestion on mode B and maybe a single press on the status will work. I'm old school: the only thing I find reliable is hard wired and old fashioned relays. Thanks for listening.

I am using Orchestrated Mobilinc on my iPad & iPhone. There appear to be two apps called Mobilinc, so perhaps that adds to the problems. I know I am confused. The I/O linc relay is configured for momentary to work with my hard wired buttons. The Garage Door Status Icon on both the iPad & iPhone is labeled as a status device only. There is no option there for control, and touching it does nothing. When I use something like a mini remote to control it everything is OK. When I use one of the wired buttons (which are used 80% of the time) it's all out of sync.