Domoticz

TheRamon wrote:If they are off, an on command is sent following a dimmer command. If they were already on, only a dimmer command is sent.

I'm guessing you don't have the right version, even though it says you're up to date. Try removing the folder with rm. Then in the node_modules folder type:

git clone https://github.com/PatchworkBoy/homebri ... moticz.git

rom https://github.com/PatchworkBoy/homebridge-edomoticz
   2cd5432..72068b5  master     -> origin/master
Updating 2cd5432..72068b5
Fast-forward
 CHANGELOG                 |   16 +-
 InstallGuide              |   60 +-
 LICENSE                   |   19 +-
 README.md                 |   33 +-
 index.js                  | 1363 ++++-----------------------------------------
 lib/constants.js          |   33 ++
 lib/domoticz.js           |  112 ++++
 lib/domoticz_accessory.js | 1218 ++++++++++++++++++++++++++++++++++++++++
 lib/helper.js             |  101 ++++
 lib/mqtt.js               |   85 +++
 lib/services.js           |  290 ++++++++++
 package.json              |    7 +-
 12 files changed, 2036 insertions(+), 1301 deletions(-)
 create mode 100644 lib/constants.js
 create mode 100644 lib/domoticz.js
 create mode 100644 lib/domoticz_accessory.js
 create mode 100644 lib/helper.js
 create mode 100644 lib/mqtt.js
 create mode 100644 lib/services.js

TheRamon wrote: Yeah, I had to fall back to http for colour changing. MQTT does not support that yet. Dimming works through MQTT though so that's why it's sending level 100 through MQTT.

thom wrote:

simon_rb wrote:@Thom

Your config file is wrong. Are you using the latest plugin, if you are you need the MQTT info in their too and make sure you have a broker running and that you have added it to Domoticz under the hardware..

Sorry, I try to reinstalled the Homebridge with MQTT, but I don't understand the way to have the broker running. I installed the MQTT Client in my Domoticz /Hardware. I put this config.json:

Code: Select all

{
    "bridge": {
        "name": "Homebridge",
        "username": "B8:27:EB:0C:D1:C6",
        "port": 51826,
        "pin": "031-45-154"
    },
    "description": "Configuration file for (e)xtended Domoticz platform.",
    "platforms": [
        {
            "platform": "Homebridge",
            "name": "Homebridge",
            "server": "127.0.0.1",
            "port": "8080",
            "ssl": 0,
            "roomid": 2,
            "mqttenable": 1,
            "mqttserver": "127.0.0.1",
            "mqttport": "1883",
            "mqttauth": 0,
            "mqttuser": "",
            "mqttpass": ""
        }
    ],
    "accessories": []
}

The result of npm run start:

Code: Select all

pi@raspberrypi:~/.homebridge$ npm run start
npm ERR! Linux 4.4.26-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
npm ERR! node v4.2.1
npm ERR! npm  v2.14.7

npm ERR! missing script: start
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/.homebridge/npm-debug.log

and the result of home bridge command:

Code: Select all

pi@raspberrypi:~$ homebridge
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] Loaded plugin: homebridge-edomoticz
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] Registering accessory 'homebridge-edomoticz.eDomoticz'
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] Registering platform 'homebridge-edomoticz.eDomoticz'
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] ---
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] Loaded config.json with 0 accessories and 1 platforms.
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] ---
[Sun Nov 06 2016 16:05:49 GMT-0500 (EST)] Loading 1 platforms...
/usr/local/lib/node_modules/homebridge/lib/api.js:118
      throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
      ^

Error: The requested platform 'Homebridge' was not registered by any plugin.
    at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:118:13)
    at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:281:45)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:77:36)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)

Thank you for the support.

TheRamon wrote: Yeah, I had to fall back to http for colour changing. MQTT does not support that yet. Dimming works through MQTT though so that's why it's sending level 100 through MQTT.

"mqttenable": 1

User: Admin initiated a switch command 

hpapagaj wrote:@TheRamon

"More iOs 10 problem:" -> today I moved my whole installation to my Ubuntu server (from rPi). We will see if it is happens again. It worth to enable the MQTT?

The updated version should fix my problem too /dimmer/

TheRamon wrote:@simon_rb, hpapagaj:

Please see the issue on GitHub:
https://github.com/PatchworkBoy/homebri ... /issues/57

I have just fixed the dimming issue (kind of a workaround) on master.
Please git pull