I’ve been poking about some more and have eventually got the Home Assistant emoncms integration to work (thanks for writing it, Brian :slight_smile: ). I lost the will to live along the way, but hey ho.

So I’m still no closer to understanding why setup code that is supposed to run on first use is still being run months later, but I’ve discovered on the login screen that as well as the login dialog box there’s a little button up on the top right of the screen and if I click that it just logs me in straight away wihout asking for a password, so I’m a happy bunny for human access.

And the error message that was being given to HA changed from the setup failure to an 401 permissions error, for reasons I don’t understand, and after a lot of faffing around I found that the Inputs API help page was lying to me and only showing me part of the APIKEYs (I think it’s something to do with zooming the firefox screen but I’m not sure). Once I discovered what the full APIKEYs were and put them into HA everything started working.

I don’t understand the bizarre CSS formatting of the grey boxes showing the APIKEYs. Putting a box sized in pixels around text seems weird to me, and putting a no entry sign cursor over an area where you explicitly expect people to be trying to copy the text seems weird, and assigning a text string value to a boolean attribute like readonly seems weird, and as I say, I lost the will to live.