This works quite well, but you have to remember that this is one-way communication, so the A/C device does not give any feedback. I have support for quite a few different models, just see the readme of the library: https://github.com/ToniA/arduino-heatpumpir I have for example built an automation ...

I'm using this version of ESPEasy on my projects: https://github.com/ToniA/ESPEasy, build it with PlatformIO (http://platformio.org/), as I needed to increase the MQTT message size buffer (Domoticz is VERY verbose). With Arduino IDE you need to manually modify the PubSubClient code... In Domoticz I ...

Oh yes, that was it... And I thought a simple reload would be enough.

Yes, there is a delay between tries.

But speaking of MyDomoticz, I just upgraded to V3.5995, and it connects to the Proxy. But I don't see anything in https://my.domoticz.com/mydomoticz/dashboard, and also the 'Proxy' tab is missing from Domoticz.

The proxy seems to be down at the moment, but I guess your fix works, as if I pull the network cable, it still does not stop trying. I.e. I get 'Error: PROXY: Error resolving domoproxy.domoticz.com: The requested name is valid, but no data of the requested type was found' multiple times into the log.

I'll try to get this done over the weekend.

Ouch, sorry if I caused that... It should probably have some retry delay. Anyway, without my patch all you need is to disconnect the network for a short while -> MyDomoticz connection never comes back. It's very easy to reproduce this for example with the Windows version, just by placing a ...

Probably this is a network or DNS configuration issue on your end. That StartThread() is not rescheduled is on purpose. We don't want to reconnect if there´s no network to avoid error messages every 15 seconds. No, this had to be fixed (and was fixed by that pull request). Without this, any short ...

Yes, I understand your point. Actually I'm just developing a remote-controlled heating system for a holiday cottage (the point is to be able to switch between maintenance heating (~ +10 C) and normal heating remotely, and to control both electric radiators and the air-to-air heatpump). Solutions ...

http://domoticz.com/wiki/MyDomoticz ?

Yes, I'm not blaming you, but the Arduino software... The worst thing is that it's not that easy to fix it nicely if you are using the Arduino IDE. Platformio (see http://platformio.org/) has global defines, though, and is compatible with Arduino IDE projects. ESP8266 has enough RAM to not be ...

Domoticz MQTT & ESPEasy has one issue, though... The max. MQTT message size ESPEasy will handle by default is 128 bytes, and Domoticz is VERY verbose: https://github.com/knolleary/pubsubclient/blob/master/src/PubSubClient.h#L26 https://github.com/ESP8266nu/ESPEasy/blob/master/Controller.ino#L49 The ...

Domoticz instance goes offline in the MyDomoticz portal, and does not come back before Domoticz is restarted. In the logs I have: 2016-11-13 07:16:30.112 Error: PROXY: timeout occurred, reconnecting 2016-11-13 07:16:45.115 Error: PROXY: StartThread(): Exception: resolve: Host not found (non ...

I have written an Arduino library for this purpose, here are some links:

https://github.com/ToniA/arduino-heatpumpir
https://www.openhardware.io/view/41/Hea ... controller
http://www.esp8266.nu/forum/viewtopic.p ... 8870#p8870

Just run the HeatpumpIR example sketch on your MySensors node: https://github.com/mysensors/Arduino/tr ... Controller

I added the 'otherdevices_idx[]' a while ago, as some of the commands absolutely require the IDX, and there was no way to get it in Lua. Like, updating the state of a multiselector device so that it also fires a new event on the selector: commandArray['OpenURL'] = 'http://127.0.0.1:8080/json.htm ...

It's not that simple. What I want to update in my event script is a set of multiselectors, and I want the multiselector event to fire when the multiselector value is updated through the event script. So I need to use the "commandArray['UpdateDevice'] = idx|nValue|sValue" format, instead of the ...

I'm writing some event code based on virtual switches. Now I'm wondering about an inconsistency about the firing of subsequent events. I.e. my event script should cause device updates which fire other events. So, if my Lua event script updates the status of an another device, I can do it in two ways ...

As of the latest beta (V2.4547, published today), there's a new Lua table called 'otherdevices_idx'. This makes the background script way more beautiful, I don't need to hardcode device idx values any more. This is my current backend script to turn the dummy device widgets into a single command ...

And now when I have actually tried weaved.com, I can only recommend it. Given that you trust a cloud provider... You really only need to register to weaved.com, and install & configure the weaved software on Raspberry. After that you can access your Domoticz easily through the weaved.com portal ...