I'm not here on this forum that often..

Anyway, it's a work in progress. Running on a pi2, so don't notice that one core is maxed out by the script. But yes dome kind of wait loop should be made instead of the current while loop, so it doesn't use max cpu.

And yes I'm using it with python3. I ...

downloaded pychromecast from github https://github.com/balloob/pychromecast

and then using the following python script


from __future__ import print_function
import time
import sys
import logging
import json
import codecs
from urllib.request import urlopen
from urllib.parse import urlencode ...

Another possible scenario is, that when you start playback on chromecast it could dim down the lights automatically, and if the playback is paused, it could turn up the lights to normal levels..

Right now I have almost accomplished this, with pychromecast reporting into domoticz, and setting a ...

I know, but wouldn't it make sense to auto assign the door icon, when it's a lock?

Anyways, if I use the door symbol, then the state is inverted, so that 0 is shown as door locked, and 1 is shown as door open. While the mysensors api states the opposite.

Hmm.. just updated to domoticz 2.3220

Using nodered to mock up a sensors, and inject the following


100;255;3;0;11;LockTest
100;255;3;0;12;0.1
100;1;0;0;19;Door lock


Then in domoticz a mysensor device with the id of 0064 turns up, with the type of "Lighting 2", and on the LightSwitch page it ...

There isn't a sketch for hvac yet, as I'm just preparing it. It's almost a chicken and egg situation

Could we get support for the new sensor / variable types, that has been added in Mysensors 1.5?

In particular I'm interested in getting V_RGB, V_RGBW, and V_HVAC_SETPOINT_COLD / V_HVAC_SETPOINT_HEAT to work in domoticz

The two first for LED strips for lightning in my Home theater, and the later ...