We understand that some customers are frustrated with the recent security fix we put in place, as it closed access to private local API controls. So I guess now the HarmonyHub.AuthorizationToken was created somewhere where Domoticz Lua can once again use it? Wonder where it is created (I noticed it was usually created on the directory where I run the command from). I tested the other scripts (where I did not change owner at any point - and confirmed they did not work yesterday) -> all working. I wonder why this is.Д®dit2: Well well, I changed owner back to pi -> still works. Strange thing is, if I change the owner of the lua script to root, vГіila, it works again like it used to. So it really is puzzling to me what did change at that point, but I guess the only option for now is to look again into running it from a wrapper of some sort.Д®dit: running from from it command line inside Domoticz directory yields:Д®RROR : swapAuthorizationToken : NULL csocket or empty authorization token provided It was rather slow to connect, though, so I tested your forked HarmonyHubControl and was very impressed how quickly it was able to send the commands in comparison.ДЄ few months ago I started using it, without any wrapper scripts, and everything worked great until yesterday. Then I moved on to HamonyHubCLI (node) as it could do multiple commands and other nice features like setting a delay between commands. Way back when I used the original HamonyHubControl I remember I had to use a. Just cannot think of anything that would have changed in my setup around that time.Д¬hecked again now that I'm home, from command line: Communication itself was working ok as I was testing it from command line at the same time as from Lua. Cannot remember now what it says when running from command line, I thought it said 'SUCCESS' on both but it may be I remember wrong and it is 'BYPASSED' instead. Just to be on the safe side I checked and gave additional permissions to use HarmonyHub.AuthorizationToken file and also tried os.execute with sudo. At present I'm clueless about the why and the what. It seems that the Hub locks up from time to time, failing to respond to ping and next not allow reconnect for up to several minutes. The communication login error is something I get quite frequently on the integrated client as well (different message, but the same issue). When I run that it usually says `BYPASSED` on the web service login, so my guess is that when you run it from LUA you are unable to access the file where the authorization token is kept (HarmonyHub.AuthorizationToken) and you are also not allowed to create/write one following the successful web service login. Gordonb3 wrote: в†‘ Monday 10 December 2018 10:55

Harmony remote login