Great work. A few days back I upgraded to the latest domoticz beta, from a januari 2016 version. A lot of progress. I like the relay values (valve settings). At first I was confused a bit, until I found the "all sensors" button. Then I got readings making sense. I experience one issue: I am missing ...

Hi, The devices will be automatically added when everything is configured right. The plugwise-2-py NodeRed code needs to be configured. I noticed that I never came around adding a manual to my github stuff. So please go in your browser to NodeRed, Plugwise-2-py, and edit the node at the top line ...

The power I get from all of my Plugs are negative values. Why is that? Is that normal? That could be me causing this. When in plugwise-2-py, for a given circle production = yes, I negate that values in the nodered script, as plugwsie-2-py reports production as negative numbers, while Domoticz seems ...

So how is the MQTT hardware item configured? Should I keep the username and password empty (Domoticz Pi image is used for installation). How about the "Publish Topic"? I don't understand the choices. (flat/hierarchical/combined/none) :?: I assume that you followed the instructions on the MQTT wiki ...

No, going back to one MQTT broker did not solve it. Next hang-up after 48 hours. This makes it pretty unworkable.

Maybe GizMoCuz can advise?

SevenW

@dannybloe if you are not afraid of the arduino world you could get a seedstudio rfbee and follow this:
https://github.com/fullTalgoRythm/Evoho ... tureSensor

SevenW

I have removed all evohome from domoticz, and did a factory reset of the evohome controller. Rejoined some TRV's and resinstalled the hardware in domoticz. Now I cna control form domoticz. Finally! :mrgreen: The only real difference is that the time on my evohome controller was now set correctly ...

On another thread with a similar issue a saw two suggestions. 1. out of memory: check with df -h on command line if a mount is full (not the case with me) 2. Two MQTT brokers in the hardware list. -> delete one. I happened two have two brokers, listening to different MQTT servers, but I now deleted ...

.. and for me as well. It occurs after 1-1.5 days of operation.

SevenW

... modified setpoints are now sent back and forth from Domoticz to the EvoHome controller as well. So I dunno, it seems to work now... Well, then there is hope for me as well. Pairing the HGI80 and the Evohome was just a matter of connecting the HGI80 to the raspi, and creating the evohome ...

Today I got my HGI80 working in combination with the latest EvoHome Wifi. ... And...it is not clear to me what the relationship is between Domoticz and the EvoHome controller. I was expecting that when I change a setpoint in Domoticz that I should see this on the EvoHome controller and vice-versa ...

so what hardware id did you assign then? Can it be arbitrary? Or did you use the MQTT hardware id?

SevenW

I have added the NodeRed scripts to my github, as well as some very rudimentary instructions, to be found in the domoticz folder: https://github.com/SevenW/Plugwise-2-py/tree/master/domoticz It is required that you update your PlugWise-2-py from github master if you have it already installed before ...

Is it also possible to completely eliminate NodeRed and let plugwise2py work directly with the /domoticz/in/# /domoticz/out/# MQTT ? Or is that the next step? Or do you still need NodeRed for the circle power readout? I tested it a bit, and looked into the MQTT source code of domoticz, but ...

Is there a way to get a list of (all) devices through MQTT, and is there a way to create a virtual sensor or switch?

Looking at the code hardware/MQTT.cpp I believe one always has to know the idx, before the interface can be used.
Right?

Regards,
SevenW

... and I found a way to break the update loop. It is also a simpler setup. I do not use the On / Off actions anymore. I stopped listening to http calls to node-red from domoticz, but I subscribe to domticz/out MQTT messages. I filter them so that I get only MQTT switch messages. With only a minor ...

I am making some interesting progress. Per circle I have two virtual switches. The first is the switch, and the second switches the schedule on or off. With the schedule switched on, the switch should follow the state of the plugwise circle. The following graph shows that the switch gets updated ...

What Galoula wants is update status, not turn on/off the switch, is it oll right?. That's: update status according the real status of the switch. Polling is a solution. Or you can see https://www.domoticz.com/forum/viewtopic.php?f=17&t=7043 bye To opening post specifically mentions the issue with ...

I could perfectly live with a dedicated command that updates the switch status, but does not execute the on/off actions. I also have been looking into contributing to the domoticz source code to have a better plugwise support. The code is however rather intimidating (I have programming skills ...

I have been looking into setting the switch-state of a circle to domoticz, and switching it with domoticz using the on/off actions. As a starting point I took the Nov. 5th node-red scripts of bloemkool. Where I stand: - Virtual switches will be added automatically to the devices tab. Only enabled ...