OK - got it authenticating and I can read back the token etc. via the framework - thanks for the help on that - found that if I didn't tell the server I would accept gzipped content then it returns uncompressed - how very civil of it - will need to deal with gzip'ed content if I got as far as ...

Thanks for the quick response and the pointers - some more options there - if I can use the framework I will - if not - will fall back to urllib (or probably urllib2 for the flexibility) In the case of the HTTP.py example - I see the header getting constructed - thats useful. The auth sequence is a ...

Hi - looking at the possibility of developing a plugin for the Blink Home Monitoring Camera's - there's a couple of libraries out there (a python one - unfortunately it depends heavily on the requests module so I can't just use that) There is also good docs on driving Blink via curl, so between the ...

To get the info from domoticz you need to use GET not POST. The response is in JSON - not the query. GET over HTTPS does not expose the remainder of the URL - wireshark it if you don't agree - SSL handshake basically does the high level bit first, something like connect to www.myfakedomain.com:443 ...

I would like to create a plugin to support the following virtual device A device I am calling "fake-o-stat" - I need a SINGLE device that can take a setpoint, return a temperature and (for now) optionally have a "demandHeat" function if current temp < setpoint (with some maths to adjust for ...

Yes, as far as I can see - server address 127.0.0.1 (have also tried the "public IP)" and 1883 for the port - same config as the MQTT agent in Domoticz - running on the same host. That's weird.. Did you enable authentication by any chance? Or do you have a username/password set in MQTT perhaps? No ...

Yes, as far as I can see - server address 127.0.0.1 (have also tried the "public IP)" and 1883 for the port - same config as the MQTT agent in Domoticz - running on the same host. That's weird.. Did you enable authentication by any chance? Or do you have a username/password set in MQTT perhaps? No ...

Having a problem with MQTT. I have Domoticz (with the MQTT hardware device added), mosquitto and homebridge/edomoticz all running on the same host. ks MQTT and DOMOTICZ talking fine via mosquitto - I can set device values via mosquitto_pub ..... as per wiki, but when I enable MQTT in the config ...

Having a problem with MQTT. I have Domoticz (with the MQTT hardware device added), mosquitto and homebridge/edomoticz all running on the same host. ks MQTT and DOMOTICZ talking fine via mosquitto - I can set device values via mosquitto_pub ..... as per wiki, but when I enable MQTT in the config.json ...

The scheduling is fixed in domoticz. ALL "device" scripts (scripts with "device" in their name) run everytime ANY device status changes ALL "time" scripts (scripts with "time" in their name) run every MINUTE. It looks like you have a device changing value regularly - that is triggering your script ...

I'd like to add my request to this (I already have a feature request in tracker for the ability to update a switch even if the new value is the same as the old). I want to do this to implement a heartbeat for a sensor that changes infrequently but my solution is less elegant that surfacing the ...

but received the wrong radio's had the nrf24l01 instead of the plus version

I seem to remember some notes on the non + version on the mysensors forum - I think a couple of "DEFINE" statements can be used to get them to work.

you could run it in a script (lua) as a "time" event - they run every minute - and you could update the status from that script - there may be a side effect of any on action (like the http:// string) being run when you update the status. Not sure if that would be suitable for motion sensors though

I have something "basic" - its not running in cron yet - but theres no reason it will have an issue - but I have checked with some friends who are running Domoticz on a PI - and the python install there doesn't have one of the libraries I use, nor does it have the python installers (pip or easy ...

Triggering should be easy - add yourself the dummy hardware - create a switch (you can use any type - I "pretend" things are x10 type in that case you set a house and unit code - they are not used they just create a unique switch) on that hardware - and then edit the resulting switch - in there is ...

The red tag on the UI is coded into domoticz and has fixed values (not sure what they are but I think orange after x and read after x+some). The issue with mysensors (and others perhaps) - is that if nothing changes (a switch that is on stays on, or a temp that is "21" stays at "21") then NOTHING at ...

Take a look at this discussion around this topic - there is a bug and a feature request in place - and I have documented how I made it work - another forum user has taken a different approach to get to the same place.

viewtopic.php?f=42&t=9272

Hope this helps.

For notification you could run a script that checks last seen time - there are a few people describing that on the forums. Personally - I don't like to resort to scripts to do these things - I think there may be issues with some of the time based lua scripts (because they all run every minute) - so ...

The MySensorsBase.cpp is part of the source code - if you have not built the software from source you won't have the file (building from source isn't something that "right" for everyone). Basically - my solution involves changing the source code and then making my own "special" version of the my ...

I use a virtual switch - with two timers set Switch called "IsDay" timer on set to 10 mins after sunrise and set to off 10 mins before sunset. You can trigger a blockly from that on/off if you want - or any other kind of script - and you can adjust the timings to suit the difference between ...