patchworkboy / homebridge-edomoticz Goto Github PK
View Code? Open in Web Editor NEWDomoticz Homebridge-Plugin
License: Other
homebridge-edomoticz's People
Contributors
Stargazers
Watchers
Forkers
eddyk69 felix63 wulfy hnnweb gertvdw siebeclaes jeradm sockhamster alfonpd marcotini wajemen ijobain ruudverheijden wolfg1969 bluebunny jeylites jcwlim txiki31 knights1 gibbo520 lboue avgays fennec622 djrams10 hendrikmoree rswofxd david-spaeth sander1988 samwelnella napoliovunque skulblaka24 iw2fag-11 rudilgr reinvented0 ariankoster ngoralski cyrilb1531 akamming bertvdr bassduh ksacca odelma rvmetal madpatrickhomebridge-edomoticz's Issues
ssl does not work
Domoticz is running properly on 8080 and 443. User auth is not yet turned on (I thought that may be the issue so it's disabled).
pi@pi:~ $ wget --no-check-certificate -q -O - "$@" https://127.0.0.1/ | head
<!DOCTYPE html>
<html manifest="html5.appcache">
<head>
<meta charset="utf-8">
<title>Domoticz</title>
The important part of the config.json is:
{
"platform": "eDomoticz",
"name": "eDomoticz",
"server": "127.0.0.1",
"ssl": 1,
"port": "443",
"roomid": 0
}
],
"accessories": []
}
After starting homebridge I get this in the logs:
[Sun Sep 04 2016 19:50:10 GMT+0200 (CEST)] [eDomoticz] Initializing eDomoticz platform...
[Sun Sep 04 2016 19:50:10 GMT+0200 (CEST)] [eDomoticz] Fetching Domoticz lights and switches...
[Sun Sep 04 2016 19:50:10 GMT+0200 (CEST)] Loading 0 accessories...
[Sun Sep 04 2016 19:50:10 GMT+0200 (CEST)] [eDomoticz] There was a problem connecting to Domoticz.
Changing ssl to 0 and port to 8080 fixes the issue, homebridge will start fine.
Possible issue: certificate is issued to the FQDN and not 127.0.0.1?
Netatmo CO2 not working
The last update produces a crash of the homebridge server when reading CO2 values from domoticz. If those netatmo sensors are deactivated, homebridge starts: (Debian 8). Before the update of the node modules, everything worked.
/usr/local/lib/node_modules/homebridge-edomoticz/lib/domoticz_accessory.js:1194
airQualityService.getCharacteristic(Characteristic.AirParticulateDensity).on('get', this.getValue.bind(this));
^
TypeError: Cannot read property 'on' of undefined
at Object.eDomoticzAccessory.getServices (/usr/local/lib/node_modules/homebridge-edomoticz/lib/domoticz_accessory.js:1194:79)
at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:378:36)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:364:32)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at Object. (/usr/local/lib/node_modules/homebridge-edomoticz/index.js:197:7)
at Request._callback (/usr/local/lib/node_modules/homebridge-edomoticz/lib/domoticz.js:78:9)
at Request.self.callback (/usr/local/lib/node_modules/homebridge-edomoticz/node_modules/request/request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request. (/usr/local/lib/node_modules/homebridge-edomoticz/node_modules/request/request.js:1082:10)
Nest Thermostat Heating
Hi, now the cold weather is approaching and this is my first winter with a smart (Nest) thermostat I was hoping to get the most out of it. I have it setup within Domoticz and expose it using eDomoticz to Homebridge/Homekit. All is working except it always says its heating the house, this didn't really matter before however the other day I we were driving home from being out all day and the heating being off as a result. I said to Siri through the car set heating to 22 degrees, I thought it had gone through as I then said "Is the heating on?" and Siri said, your thermostat is heating the house. We came home to a cold house, then I realised within HomeKit the house always shows as heating.
Would it be possible to get the heating bit to work? In the native Home App it shows as heating which I didn't realise. There is a separate switch which shows if the heating is on so I could expose that to HomeKit via eDomoticz and ask is the Heating Switch on however it would be great if it could some how be incorporated into the exiting thermostat settings within HomeKit.
I have to apologise as I have mentioned this a while back within the eDomoticz forum however thought this would be a more appropriate place to put a request in.
Hope this makes sense!
Cheers!!! :D
Aeotec LED Bulb working in Domoticz, invisible in homebridge
I've got one of those Aeotec LED bulbs. It is showing up in Domoticz as an Applamp and an on/off switch so far (can only configure fully saturated colors, but hey). So controlling it from Domo works in principle.
Unfortunately, it isn't picked up by homebridge yet. One Fibaro RGBW Applamp and a switchable wall plug are working fine apart from that.
Let me throw some json at you as you usually ask for that on the Domoticz forums.
For the switch component:
{
"ActTime" : 1476462061,
"ServerTime" : "2016-10-14 18:21:01",
"Sunrise" : "07:47",
"Sunset" : "18:24",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Off",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "Razberry",
"HardwareType" : "OpenZWave USB",
"HardwareTypeVal" : 21,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "00000401",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-10-12 19:03:37",
"Level" : 100,
"LevelInt" : 100,
"MaxDimLevel" : 100,
"Name" : "Aeotec Switch",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Off",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "Switch",
"SwitchType" : "Dimmer",
"SwitchTypeVal" : 7,
"Timers" : "false",
"Type" : "Light/Switch",
"TypeImg" : "dimmer",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "19"
}
],
"status" : "OK",
"title" : "Devices"
}
And the RGBW component:
{
"ActTime" : 1476462149,
"ServerTime" : "2016-10-14 18:22:29",
"Sunrise" : "07:47",
"Sunset" : "18:24",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Off",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "Razberry",
"HardwareType" : "OpenZWave USB",
"HardwareTypeVal" : 21,
"HaveDimmer" : true,
"HaveGroupCmd" : false,
"HaveTimeout" : false,
"ID" : "00000465",
"Image" : "Light",
"IsSubDevice" : true,
"LastUpdate" : "2016-10-12 19:03:37",
"Level" : 99,
"LevelInt" : 99,
"MaxDimLevel" : 100,
"Name" : "Aeotec Farbe",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Off",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "RGBW",
"SwitchType" : "Dimmer",
"SwitchTypeVal" : 7,
"Timers" : "false",
"Type" : "Lighting Limitless/Applamp",
"TypeImg" : "dimmer",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "20"
}
],
"status" : "OK",
"title" : "Devices"
}
The output of DEBUG=* homebridge -D doesn't seem all too revealing to me either:
➜ ~ DEBUG=* homebridge -D
*** 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>
[Fri Oct 14 2016 18:24:56 GMT+0200 (CEST)] Loaded plugin: homebridge-edomoticz
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] Registering accessory 'homebridge-edomoticz.eDomoticz'
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] Registering platform 'homebridge-edomoticz.eDomoticz'
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] ---
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] Loaded config.json with 0 accessories and 1 platforms.
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] ---
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] Loading 1 platforms...
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] [Domoticz] Initializing eDomoticz platform...
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] [Domoticz] Fetching Domoticz lights and switches...
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] Loading 0 accessories...
[Fri Oct 14 2016 18:24:57 GMT+0200 (CEST)] [Domoticz] Initializing platform accessory 'Fernseher-LEDs'...
[Fri Oct 14 2016 18:24:58 GMT+0200 (CEST)] [Domoticz] Initializing platform accessory 'Lichterglas'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
[...]
EventedHTTPServer Server listening on port 51826 +0ms
[Fri Oct 14 2016 18:24:58 GMT+0200 (CEST)] Homebridge is running on port 51826.
EventedHTTPServer [::ffff:192.168.0.12] New connection from client +1s
EventedHTTPServer [::ffff:192.168.0.12] HTTP server listening on port 35390 +16ms
EventedHTTPServer [::ffff:192.168.0.12] HTTP request: /pair-verify +123ms
HAPServer [CC:21:3E:E4:DE:33] HAP Request: POST /pair-verify +7ms
HAPServer [CC:21:3E:E4:DE:33] Pair verify step 1/2 +41ms
EventedHTTPServer [::ffff:192.168.0.12] HTTP Response is finished +319ms
EventedHTTPServer [::ffff:192.168.0.12] Client connection closed +174ms
EventedHTTPServer [::ffff:192.168.0.12] HTTP connection was closed +48ms
EventedHTTPServer [::ffff:192.168.0.12] HTTP server was closed +15ms
Can you give a hint at what might be going wrong? Did I miss something?
Thermostats showing set point value for current temperature
The Domoticz web interface is correctly reporting that the temperature in the rooms (from Honeywell evoHome). For example the Games Room is currently 22.2 with a Set Point of 5.
The relevant JSON block returned from "http://[domoticz-host]:8080/json.htm?type=devices&filter=all&used=true&order=Name" is shown below:
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "22.2 C, (5.0 C), HeatingOff",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "EvoHome HGI80",
"HardwareType" : "Evohome USB (for HGI/S80)",
"HardwareTypeVal" : 39,
"HaveTimeout" : false,
"ID" : "",
"LastUpdate" : "2016-06-16 15:10:00",
"Name" : "Games Room Heating",
"Notifications" : "false",
"PlanID" : "2",
"PlanIDs" : [ 2 ],
"Protected" : false,
"SetPoint" : 5.0,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "HeatingOff",
"SubType" : "Zone",
"Temp" : 22.20,
"Timers" : "false",
"Type" : "Heating",
"TypeImg" : "override_mini",
"Unit" : 9,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "13"
},
When fetching the thermostats via HomeKit apps HomeBridge reports in the log:
"[6/16/2016, 2:43:06 PM] [Domoticz] Data Received for Games Room Heating: 5"
So the plugin is retrieving the SetPoint value and not the Temp value.
I'm using:
"npm -v homebridge-edomoticz" reports "2.14.2"
Domoticz v3.5169
All running on a Raspberry Pi.
A set value outside of the min & max value for the Characteristic causes Home app 'Error'
Using both the iOS 9 'Home' HomeKit app (by brutella) or the new iOS 10 Apple Home app I experienced Errors for Thermostats when the evoHome heating was set to 'Off' - which essentially sets the Target to only 5 degrees as frost protection. (I'm not clear on the semantics of when the Thermostat mode should be 'Off' vs 'Heating' given really the Heating is always on).
On analysis this error is due to the target (setPoint) value being less than the min value for the Target Temperature Characteristic. e.g. my evoHome setPoint is 5 degrees but the default min is 10 degrees.
The fix I've made on my local branch to correct this simply reduces the min value for the Characteristic to an acceptable value but probably the correct fix is to check the values for all Characteristics to ensure they're inside the min/max values for Current, Target et al.
Within the Heating Thermostat case I've done:
HeatingDeviceService.getCharacteristic(Characteristic.TargetTemperature).setProps({
minValue: 4
});
The image below shows the default output of this plugin exhibiting this issue and Issue 21.
Domoticz not responding to homekit commands.
I believe I have this all installed per the instructions, even started everything from scratch twice and get the same results.
Domoticz controls the three switches I currently have set up perfectly. Homebridge seems to poll the switches from domoticz but I cannot get it to control any of them.
I had this all working a few months ago but had to reinstall the os on the pi, since then cannot seem to get this to go.
Not sure where to go from here. Below is log from debug and attempting to change the state twice. Below that is my config.
Thanks!!
`[11/8/2016, 8:00:35 PM] Loaded plugin: homebridge-edomoticz
[11/8/2016, 8:00:36 PM] Registering accessory 'homebridge-edomoticz.eDomoticz'
[11/8/2016, 8:00:36 PM] Registering platform 'homebridge-edomoticz.eDomoticz'
[11/8/2016, 8:00:36 PM] ---
[11/8/2016, 8:00:36 PM] Loaded config.json with 0 accessories and 1 platforms.
[11/8/2016, 8:00:36 PM] ---
[11/8/2016, 8:00:36 PM] Loading 1 platforms...
[11/8/2016, 8:00:36 PM] [eDomoticz] Initializing eDomoticz platform...
[11/8/2016, 8:00:36 PM] [eDomoticz] Fetching Domoticz lights and switches...
[11/8/2016, 8:00:36 PM] [eDomoticz] Initializing platform accessory 'Kitchen'...
[11/8/2016, 8:00:36 PM] [eDomoticz] Initializing platform accessory 'Lights in the Backyard'...
[11/8/2016, 8:00:36 PM] [eDomoticz] Initializing platform accessory 'Master Bedroom'...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
EventedHTTPServer Server listening on port 51826 +0ms
[11/8/2016, 8:00:36 PM] Homebridge is running on port 51826.
[11/8/2016, 8:00:36 PM] [eDomoticz] Successfully connected to MQTT broker.
[11/8/2016, 8:00:36 PM] [eDomoticz] Data Received for Kitchen.
[11/8/2016, 8:00:36 PM] [eDomoticz] Data Received for Kitchen: 98
[11/8/2016, 8:00:36 PM] [eDomoticz] Data Received for Master Bedroom.
[11/8/2016, 8:00:36 PM] [eDomoticz] Data Received for Master Bedroom: 100
EventedHTTPServer [::ffff:10.0.0.71] New connection from client +1s
EventedHTTPServer [::ffff:10.0.0.71] HTTP server listening on port 46398 +3ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /pair-verify +18ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +1ms
HAPServer [CC:22:3D:E3:CE:30] Pair verify step 1/2 +6ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +43ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /pair-verify +146ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: POST /pair-verify +0ms
HAPServer [CC:22:3D:E3:CE:30] Pair verify step 2/2 +3ms
HAPServer [CC:22:3D:E3:CE:30] Client 3654C130-9AB3-4DA3-8525-34C258BC2429 verification complete +9ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +4ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /accessories +9ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: GET /accessories +0ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +9ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +109ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":12,"ev":true},{"aid":2,"iid":15,"ev":true},{"aid":3,"iid":11,"ev":true},{"aid":3,"iid":14,"ev":true},{"aid":4,"iid":12,"ev":true},{"aid":4,"iid":15,"ev":true}] +3ms
Accessory [Homebridge] Registering Characteristic "Reachable" for events +3ms
Accessory [Homebridge] Registering Characteristic "Category" for events +1ms
Accessory [Homebridge] Registering Characteristic "Reachable" for events +1ms
Accessory [Homebridge] Registering Characteristic "Category" for events +0ms
Accessory [Homebridge] Registering Characteristic "Reachable" for events +0ms
Accessory [Homebridge] Registering Characteristic "Category" for events +0ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +245ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":3,"iid":9,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +2ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +6ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":3,"iid":9,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +0ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +27ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":4,"iid":9,"ev":true},{"aid":4,"iid":10,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +0ms
Accessory [Homebridge] Registering Characteristic "Brightness" for events +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +10ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":4,"iid":9,"ev":true},{"aid":4,"iid":10,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +0ms
Accessory [Homebridge] Registering Characteristic "Brightness" for events +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +8ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +1ms
Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":9,"ev":true},{"aid":2,"iid":10,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +0ms
Accessory [Homebridge] Registering Characteristic "Brightness" for events +0ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +16ms
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":9,"ev":true},{"aid":2,"iid":10,"ev":true}] +1ms
Accessory [Homebridge] Registering Characteristic "On" for events +1ms
Accessory [Homebridge] Registering Characteristic "Brightness" for events +0ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +15s
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +1ms
Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":9,"value":1}] +2ms
Accessory [Homebridge] Setting Characteristic "On" to value 1 +0ms
EventedHTTPServer [::ffff:10.0.0.71] Muting event '2.9' notification for this connection since it originated here. +15ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP request: /characteristics +9s
HAPServer [CC:22:3D:E3:CE:30] HAP Request: PUT /characteristics +1ms
Accessory [Homebridge] Processing characteristic set: [{"aid":2,"iid":9,"value":0}] +8ms
Accessory [Homebridge] Setting Characteristic "On" to value 0 +0ms
EventedHTTPServer [::ffff:10.0.0.71] Muting event '2.9' notification for this connection since it originated here. +7ms
EventedHTTPServer [::ffff:10.0.0.71] HTTP Response is finished +1ms
`
Config.json
`{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{"platform": "eDomoticz",
"name": "eDomoticz",
"server": "127.0.0.1",
"port": "8080",
"ssl": 0,
"roomid": 2,
"mqttenable": 1,
"mqttserver": "127.0.0.1",
"mqttport": "1883",
"mqttauth": 0,
"mqttuser": "",
"mqttpass": ""}
]
}
`
Push On button wrong status
Hi,
There appears to be a small bug handling Push On devices. Basically whenever a homekit App is opened, say slider up to get the favourite devices on iOs10, it will show the device as On regardless of its real state - it's off I know.
Basically Homebridge shows this:
[10/17/2016, 9:38:41 AM] [eDomoticz] Data Received for Roller Shutters 40: 1
While Domoticz have:
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 1.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Off",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 15,
"HardwareName" : "Dummy",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "000140BA",
"Image" : "Light",
"InternalState" : "Off",
"IsSubDevice" : false,
"LastUpdate" : "2016-10-17 08:26:56",
"Level" : 0,
"LevelInt" : 0,
"MaxDimLevel" : 100,
"Name" : "Roller Shutters 40",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "Switch",
"SwitchType" : "Push On Button",
"SwitchTypeVal" : 9,
"Timers" : "false",
"Type" : "Light/Switch",
"TypeImg" : "push",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "107"
}
So clicking the device sends an Off command which does nothing since the device was already Off, clicking again and it sends an On command which finally "works".
Hope this makes sense
Changing colour w/ MQTT disabled
Changing a colour when mqttenabled=0 does not work.
NewFolk
All 3 command work fine for me.
But not from homekit app or Eve.
In log i see only on/off
CODE: SELECT ALL
MQTT: Topic: domoticz/in, Message: {"command":"switchlight","idx":117,"switchcmd":"On"}and brightness change
CODE: SELECT ALL
MQTT: Topic: domoticz/in, Message: {"command":"switchlight","idx":117,"level":100,"switchcmd":"Set Level"}but when color change I see only
CODE: SELECT ALL
User: Admin initiated a switch commandIf i disable MQTT by
CODE: SELECT ALL
"mqttenable":0
On any action I see
CODE: SELECT ALL
User: Admin initiated a switch commandAll works fine before upgrade(before MQTT integration) and all works fine from domoticz
rwijbenga, did you find the solution?
Btw I also you MilIght but not with RFlink. I use native WiFi interface and Domoticz.
EvoHome Temperature Shows Target Temp Not Actual Temp
Hello,
I'm using the EvoHome script integration, but I'm finding that the Eve and Home apps are showing the temperature of the room as the same as the target temperature, even though the JSON coming back from Domoticz is correct. Here's an example of the JSON for a particular room:
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "16.0 C, (22.0 C), PermanentOverride",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 2,
"HardwareName" : "evohome",
"HardwareType" : "Evohome via script",
"HardwareTypeVal" : 40,
"HaveTimeout" : false,
"ID" : "1769913",
"LastUpdate" : "2016-11-20 14:07:31",
"Name" : "Corner Bedroo",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"SetPoint" : 22.0,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "PermanentOverride",
"SubType" : "Zone",
"Temp" : 16.030,
"Timers" : "false",
"Type" : "Heating",
"TypeImg" : "override_mini",
"Unit" : 6,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "8"
}
As you can see the 'Temp' is showing as 16.03 degrees, but Home app is showing it as 22 degrees which is the SetPoint. Any ideas, or am I doing something wrong. I'm using the script version of the evohome client in Domoticz.
Thanks,
Henry
Possibility to add support for Energy meter (PVoutput)
Hi,
as requested in Domoticz forum, here's the json-output of energy meter:
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CounterToday" : "62.080 kWh",
"CustomImage" : 0,
"Data" : "50196.992 kWh",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 8,
"HardwareName" : "PVOutput",
"HardwareType" : "PVOutput (Input)",
"HardwareTypeVal" : 30,
"HaveTimeout" : false,
"ID" : "00000002",
"LastUpdate" : "2016-02-03 23:55:22",
"Name" : "Energy Consumption",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "kWh",
"SwitchTypeVal" : 0,
"Timers" : "false",
"Type" : "General",
"TypeImg" : "current",
"Unit" : 1,
"Usage" : "4019.0 Watt",
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "22"
}
],
It contains the current consumption ("Usage" : "4019.0 Watt"), daily usage ("CounterToday" : "62.080 kWh") and then I guess the lifetime usage ("Data" : "50196.992 kWh").
Thanks again!
Owl 113 / Electrisave Current Meter
json output from my Owl electricity monitor in Domoticz as requested on the Domoticz forums
{
"ActTime" : 1454858626,
"ServerTime" : "2016-02-07 15:23:46",
"Sunrise" : "07:29",
"Sunset" : "16:57",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 100,
"CustomImage" : 0,
"Data" : "529 Watt",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveTimeout" : false,
"ID" : "6C00",
"LastUpdate" : "2016-02-07 15:23:00",
"Name" : "Electricity Consumption",
"Notifications" : "false",
"PlanID" : "11",
"PlanIDs" : [ 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : 7,
"SubType" : "CM113, Electrisave",
"Timers" : "false",
"Type" : "Current",
"TypeImg" : "current",
"Unit" : 0,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"displaytype" : 1,
"idx" : "203"
}
],
"status" : "OK",
"title" : "Devices"
}
Many thanks if this could be added as a supported device in the next build.
ventian blind are not supported
Hi,
When changing blind type to "ventian blind" HomeKit do not recognize it (edomoticz). Is it possible to add that support to the plugin ? (it is needed to support stop command)
Counters, created as "General.Counter Incremental" in Domoticz, shown up as Contact
I created virtual counters of type General, subtype Counter Incremental in Domoticz.
Those counters used as water counters and got updated by ESP Easy (software for ESP8266 controller). They shows up total and current values in Domoticz in correct way (at Utility) tab.
But in Eve I see them as of Contact type - so no value, just 'NO' status.
JSON output shown below:
{
"ActTime" : 1464235958,
"ServerTime" : "2016-05-26 07:12:38",
"Sunrise" : "04:02",
"Sunset" : "20:52",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"Counter" : "0.410 m3",
"CounterToday" : "0.020 m3",
"CustomImage" : 0,
"Data" : "0.410 m3",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 3,
"HardwareName" : "Cold water instant",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveTimeout" : false,
"ID" : "82007",
"LastUpdate" : "2016-05-26 07:12:38",
"Name" : "Cold Incremental",
"Notifications" : "false",
"PlanID" : "2",
"PlanIDs" : [ 2 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "Counter Incremental",
"SwitchTypeVal" : 2,
"Timers" : "false",
"Type" : "General",
"TypeImg" : "counter",
"Unit" : 1,
"Used" : 1,
"ValueQuantity" : "",
"ValueUnits" : "",
"XOffset" : "608",
"YOffset" : "592",
"idx" : "8"
},
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"Counter" : "0.110 m3",
"CounterToday" : "0.000 m3",
"CustomImage" : 0,
"Data" : "0.110 m3",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "Hot water instant",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveTimeout" : false,
"ID" : "82008",
"LastUpdate" : "2016-05-26 07:12:37",
"Name" : "Hot Incremental",
"Notifications" : "false",
"PlanID" : "2",
"PlanIDs" : [ 2 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "Counter Incremental",
"SwitchTypeVal" : 2,
"Timers" : "false",
"Type" : "General",
"TypeImg" : "counter",
"Unit" : 1,
"Used" : 1,
"ValueQuantity" : "",
"ValueUnits" : "",
"XOffset" : "664",
"YOffset" : "592",
"idx" : "9"
}
],
"status" : "OK",
"title" : "Devices"
}
youless electricity meter not working
the youless kwh meter does not show values, the json is below as requested.
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"Counter" : "17263.158",
"CounterToday" : "6.651 kWh",
"CustomImage" : 0,
"Data" : "17263.158 kWh 370 Watt",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 3,
"HardwareName" : "Youless",
"HardwareType" : "YouLess Meter with LAN interface",
"HardwareTypeVal" : 6,
"HaveTimeout" : false,
"ID" : "80",
"LastUpdate" : "2016-02-02 22:27:12",
"Name" : "Youless",
"Notifications" : "false",
"PlanID" : "4",
"PlanIDs" : [ 4 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "YouLess counter",
"SwitchTypeVal" : 0,
"Timers" : "false",
"Type" : "YouLess Meter",
"TypeImg" : "counter",
"Unit" : 1,
"Usage" : "370 Watt",
"Used" : 1,
"XOffset" : "385",
"YOffset" : "366",
"idx" : "5"
},
Domoticz internal Security Panel
... support would be nice.
{
"ActTime" : 1476811451,
"ServerTime" : "2016-10-18 20:24:11",
"Sunrise" : "08:09",
"Sunset" : "18:04",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Normal",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 1,
"HardwareName" : "Domoticz Internal",
"HardwareType" : "Domoticz Internal interface",
"HardwareTypeVal" : 67,
"HaveDimmer" : false,
"HaveGroupCmd" : false,
"HaveTimeout" : false,
"ID" : "148702",
"LastUpdate" : "2016-10-18 15:36:07",
"MaxDimLevel" : 0,
"Name" : "Security Panel",
"Notifications" : "false",
"PlanID" : "5",
"PlanIDs" : [ 5 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Normal",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "Security Panel",
"SwitchType" : "Security",
"SwitchTypeVal" : 0,
"Timers" : "false",
"Type" : "Security",
"TypeImg" : "security",
"Unit" : 0,
"Used" : 1,
"XOffset" : "430",
"YOffset" : "192",
"idx" : "43"
}
],
"status" : "OK",
"title" : "Devices"
}
... and working nvalues.
Disarm - 0
Normal Delay - 1
Alarm - 2
Alarm Delayed - 3
Motion - 4
No Motion - 5
Panic - 6
Panic End - 7
? - 8
Arm Away - 9
Arm Away Delayed - 10
Arm Home - 11
Arm Home Delayed - 12
Disarm? - 13
LightwaveRF switch being turned off when already on
Bit of a weird problem I've observed with some of my LightwaveRF lights.
I have two lights in my living room that are controlled by a LightwaveRF master switch. Because the protocol is one way, when the lights are controlled from the master switch its impossible for Domoticz (and therefore HomeKit) to know that a light has been turned on or off.
In practice this shouldn't be a problem - if the light is on and HomeKit (or Domoticz) thinks its off then turning it on will just send a harmless on command which won't do anything.
However I'm sometimes finding that when HomeKit thinks a light is off (but its actually on), when I turn the light on using the Home app the light actually turns off!
Looking at the Homebridge and Domoticz logs, what seems to be happening is that instead of just sending an "on" command, Homebridge is sending an "on" and "off" command.
Example:
Light is on (turned on from master switch)
Domoticz and HomeKit show the light as being off.
Using Home app to turn light on results in following entries in Domoticz log:
[12/16/2016, 1:24:37 PM] [eDomoticz] Setting power state to on
[12/16/2016, 1:24:37 PM] [eDomoticz] Living Room sent command succesfully
[12/16/2016, 1:24:37 PM] [eDomoticz] Living Room sent command succesfully
And the following in the Domoticz event log for that light (with most recent commands at top):
2016-12-16 13:24:37 Off
2016-12-16 13:24:37 On
From the Homebridge log it definitely appears to be sending two commands even though its only receiving one instruction from HomeKit (to set power state to on).
I've tried this with another light that exhibits this behaviour and the same thing happens - two entries in the Domoticz log for sending a successful command and Domoticz showing an on followed by an off command.
I'll try and look into the code myself if I have time but wondered if anyone else has had this problem (its not necessarily a LightwaveRF specific problem).
I can't remember if the switches in Domoticz are emulating one of my remote switches or are directly paired up with the master switch, if that makes any difference (I suspect not). It also doesn't happen every time.
More Sensor Types?
Are there any plans to implement more sensor types? Sensors like contact, occupancy and motion sensors seems to have similar HomeKit ctypes and a wide array of domoticz virtual sensors would be supported based on this shared code...?
Opentherm Interface setpoint room temperature.
The Opentherm interface uses 2 different devices for the room setpoint and room temperature...
I there a way to combine them in homekit? So that just 1 switch / device is needed?
Now I have 2 devices, 1 for the setpoint and 1 displaying the temperature. And the setpoint device displays as room temperature the setpoint temperature... :(
The JSON output for the room setpoint:
{ "ActTime" : 1475018144, "ServerTime" : "2016-09-28 01:15:44", "Sunrise" : "07:34", "Sunset" : "19:19", "result" : [ { "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "14.0", "Description" : "", "Favorite" : 0, "HardwareID" : 7, "HardwareName" : "Verwarming", "HardwareType" : "OpenTherm Gateway with LAN interface", "HardwareTypeVal" : 20, "HaveTimeout" : false, "ID" : "0000005", "LastUpdate" : "2016-09-28 01:15:08", "Name" : "Kamer Temperatuur", "Notifications" : "false", "PlanID" : "5", "PlanIDs" : [ 5, 6 ], "Protected" : false, "SetPoint" : "14.0", "ShowNotifications" : true, "SignalLevel" : "-", "SubType" : "SetPoint", "Timers" : "false", "Type" : "Thermostat", "TypeImg" : "override_mini", "Unit" : 0, "Used" : 1, "XOffset" : "0", "YOffset" : "0", "idx" : "222" } ], "status" : "OK", "title" : "Devices" }
The room temperature JSON:
{ "ActTime" : 1475018187, "ServerTime" : "2016-09-28 01:16:27", "Sunrise" : "07:34", "Sunset" : "19:19", "result" : [ { "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "22.1 C", "Description" : "", "Favorite" : 0, "HardwareID" : 7, "HardwareName" : "Verwarming", "HardwareType" : "OpenTherm Gateway with LAN interface", "HardwareTypeVal" : 20, "HaveTimeout" : false, "ID" : "0008", "LastUpdate" : "2016-09-28 01:15:08", "Name" : "Woonkamer", "Notifications" : "false", "PlanID" : "5", "PlanIDs" : [ 5, 6 ], "Protected" : false, "ShowNotifications" : true, "SignalLevel" : "-", "SubType" : "LaCrosse TX3", "Temp" : 22.10, "Timers" : "false", "Type" : "Temp", "TypeImg" : "temperature", "Unit" : 8, "Used" : 1, "XOffset" : "0", "YOffset" : "0", "idx" : "224" } ], "status" : "OK", "title" : "Devices" }
Let me know if I can help / test anything more...
Motion Sensor Battery
Hi,
When I tried this plugin with a Fibaro Motion Sensor, I've got this error :
/usr/lib/node_modules/homebridge-edomoticz/index.js:1107motionService.getCharacteristic(new Characteristic.StatusLowBattery()).on('get', ^ TypeError: Cannot read property 'on' of undefined
Looking a the code for smoke sensor, I saw that the method used is addCharacteristic instead of getCharacteristic.
I tried to change the method with addCharacteristic for the motion sensor and it works.
Security panel not updating first time
bdormael
Small issue I've encountered is when the status changes in Domoticz from eg. Home to Away, when opening Home the first time, it is not updated.
When closing Home, then opening again, it is updated properly.
I don't have this with other switches from Domoticz.
MQTT-integration branch - loses accessories.
Something occurs within the MQTT-integration branch which causes the loss of a large number of accessories (54 in my case), and requires a restart of homeBridge to resolve. Don't know the trigger / cause as of yet.
geting this while plugin install
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
The plugin loads fine. But it Homebridge does not find the added devices. What am I doing wrong ?
Thermostat SetPoint support?
In domoticz I have added a dummy hardware and then created a thermostat setpoint with it but it's not showing up in my accessories, the homebridge-start log show it as initialized but as I've said it does not show... aren't they supported at the moment?
Dimmer sends "on" command right after "set value"
hpapagaj
Guys I just updated to iOS10 and now I am using the built in iOS 10 Home app.
There is a problem with slider switch (on iOS 9 with Eve app it worked fine). If I ask for any value it is switches back to a very low value. Ineresting, that in Domoticz the LED slider switch is at the correct position.
Here is a log:
Siri:
CODE: SELECT ALL
2016-11-02 20:27:03.516 User: Admin initiated a switch command (25/LED/Set Level)
2016-11-02 20:27:03.553 LUA: dev Set Level: 96 %
2016-11-02 20:27:03.553 LUA: Value received from Domoticz was 31
2016-11-02 20:27:03.553 LUA: Calculated value for ESP is 1023
2016-11-02 20:27:03.554 LUA: Dimming LED to 1023
2016-11-02 20:27:03.554 LUA: echo Fadetimer=2000,LED1_target=1023 | socat - TCP:192.168.1.10:43333
2016-11-02 20:27:03.518 (Quinled_1) Lighting 5 (LED)
2016-11-02 20:27:04.295 User: Admin initiated a switch command (25/LED/On)
2016-11-02 20:27:04.356 LUA: dev On
2016-11-02 20:27:04.356 LUA: Turning on LED
2016-11-02 20:27:04.357 LUA: echo Fadetimer=2000,LED1_target= 8 | socat - TCP:192.168.1.10:43333
2016-11-02 20:27:04.300 (Quinled_1) Lighting 5 (LED)Manual:
CODE: SELECT ALL
2016-11-02 20:28:38.825 User: Admin initiated a switch command (25/LED/Set Level)
2016-11-02 20:28:38.858 LUA: dev Set Level: 40 %
2016-11-02 20:28:38.858 LUA: Value received from Domoticz was 13
2016-11-02 20:28:38.858 LUA: Calculated value for ESP is 196
2016-11-02 20:28:38.858 LUA: Dimming LED to 196
2016-11-02 20:28:38.859 LUA: echo Fadetimer=2000,LED1_target=196 | socat - TCP:192.168.1.10:43333
2016-11-02 20:28:38.827 (Quinled_1) Lighting 5 (LED)From the log I see, that Siri is initiated a switch command 25/LED/Set Level -> that's correct, but immediately after that there is a 25/LED/On command. And this is the problem. The LED is already on and this should not be executed (my default brightness is 8 after switch on).
No output from the update command. Maybe I have the latest version (I installed around 12:00)?
Current state:
Siri Turn the LED off => works
Siri Turn the LED on => works
Siri set LED to 100% (LED was ON) => dim command -> then on command => NOT OK
Siri set LED to 100% (LED was OFF) => dim command -> then on command => NOT OKHome app => OK, after choosing the value it sends the dim command only.
tags
Being able to assign types of modules through tags (such as with the z-way plugin for homebridge) would make it far easier to get siri to properly manage devices.
Any plan in this area?
Realtime Updates
Need to add ability to subscribe to Domoticz’ native MQTT channel (domoticz/out flat architecture), parse and then run setValue against matched accessory after checking dtype in the stream to decide whether to use nvalue or svalue etc
This will allow (pretty much) realtime updates rather than manually having to initialise an update of sensor data.
Intend to use (and package.json is now modified to pull in) https://www.npmjs.com/package/mqtt ^1.0.0 unless a more suited alternative is found.
This side of things will take a while to evolve as we’ll need to add relevant bits into config.json to cover separate mqtt authentication etc.
All contributions should be pulled against https://github.com/PatchworkBoy/homebridge-eDomoticz/tree/mqtt-integration
Fibaro roller shutter appear as switches
I have 6 Fibaro devices to control the blinds and appear as normal switches, not as blinds. In addition, I see normal blinds have a switchtypeVal different depending on whether you are normal blinds (SwitchTypeVal 3) or percentage (SwitchTypeVal 13).
{
"ActTime" : 1463310917,
"ServerTime" : "2016-05-15 13:15:17",
"Sunrise" : "06:34",
"Sunset" : "21:02",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Set Level: 48 %",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 1,
"HardwareName" : "StickUSB",
"HardwareType" : "OpenZWave USB",
"HardwareTypeVal" : 21,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "00001B01",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-05-15 13:09:26",
"Level" : 48,
"LevelInt" : 48,
"MaxDimLevel" : 100,
"Name" : "Persiana dormitorio",
"Notifications" : "false",
"PlanID" : "3",
"PlanIDs" : [ 3 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Set Level: 48 %",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "Switch",
"SwitchType" : "Blinds Percentage",
"SwitchTypeVal" : 13,
"Timers" : "false",
"Type" : "Light/Switch",
"TypeImg" : "blinds",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "136"
}
],
"status" : "OK",
"title" : "Devices"
}
TypeError on start-up
Hi since the last update I did yesterday of both homebridge and edomoticz I have below error on start-up:
...
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister
[12/17/2016, 8:29:27 AM] Loaded plugin: homebridge-edomoticz
[12/17/2016, 8:29:27 AM] Registering accessory 'homebridge-edomoticz.eDomoticz'
[12/17/2016, 8:29:27 AM] Registering platform 'homebridge-edomoticz.eDomoticz'
[12/17/2016, 8:29:27 AM] ---
[12/17/2016, 8:29:27 AM] Loaded config.json with 0 accessories and 1 platforms.
[12/17/2016, 8:29:27 AM] ---
[12/17/2016, 8:29:27 AM] Loading 1 platforms...
[12/17/2016, 8:29:27 AM] [Domoticz] Initializing eDomoticz platform...
[12/17/2016, 8:29:27 AM] Loading 0 accessories...
...
[12/17/2016, 8:29:28 AM] [Domoticz] Initializing platform accessory 'Eetkamer CO2'...
/usr/lib/node_modules/homebridge-edomoticz/lib/domoticz_accessory.js:1188
airQualityService.getCharacteristic(Characteristic.AirParticulateDensity).on('get', this.getValue.bind(this));
^
TypeError: Cannot read property 'on' of undefined
at Object.eDomoticzAccessory.getServices (/usr/lib/node_modules/homebridge-edomoticz/lib/domoticz_accessory.js:1188:79)
at Server._createAccessory (/usr/lib/node_modules/homebridge/lib/server.js:378:36)
at Server. (/usr/lib/node_modules/homebridge/lib/server.js:364:32)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at Object. (/usr/lib/node_modules/homebridge-edomoticz/index.js:197:7)
at Request._callback (/usr/lib/node_modules/homebridge-edomoticz/lib/domoticz.js:78:9)
at Request.self.callback (/usr/lib/node_modules/homebridge-edomoticz/node_modules/request/request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request. (/usr/lib/node_modules/homebridge-edomoticz/node_modules/request/request.js:1082:10)
Cannot connect to MQTT
Hi - having issues with connection to MQTT - setup is
Homebridge with Homebridge-edomoticz running on same host as Domoticz with MQTT enabled and mosquitto.
Domoticz talking to MQTT (proved via a mosquitto_pub on the same host setting a value in domotocz - can also see domoticz/out messages via MQTT spy)
config.json has config for MQTT
(snippet from file - not complete file - has passed JSON validation)
"platform": "eDomoticz",
"name": "eDomoticz",
"server": "127.0.0.1",
"port": "8990",
"ssl": 0,
"roomid": 9,
"mqttenable": 1,
"mqttserver": "127.0.0.1",
"mqttport": "1883",
"mqttauth": 0,
"mqttuser": "",
"mqttpass": ""
homebridge starts, but then repeats this message every second.....
[eDomoticz] Retrying connection to MQTT broker...
I have also tried the actual IP of the host in the config file.
Host is Ubuntu 14.04 LTS (64bit) - all available updates for homebridge, homebridge-edomoticz, mosquitto applied.
Tried running homebridge with DEBUG - no additional info on screen - and I cannot find the homebridge/log and .err files in the location suggested by the homebridge wiki. Have also tried running homebridge under sudo - again - same issue.
Any pointers or ways of getting some more debug output appreciated.
update
Hi!
Awesome plugin!
Was just to update the plugin when I ran into this irritating issue:
When executing the following command:
>sudo npm update -g
I got:
npm ERR! Linux 4.1.14-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "update" "-g"
npm ERR! node v4.2.1
npm ERR! npm v2.14.7
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/homebridge-eDomoticz
npm ERR! 404
npm ERR! 404 'homebridge-eDomoticz' is not in the npm registry.
npm ERR! 404 Your package name is not valid, because
npm ERR! 404
npm ERR! 404 1. name can no longer contain capital letters
Logitech Media Server
As promised mate, Cheers (and no its not my dishwasher this time haha)
{
"ActTime" : 1475962220,
"ServerTime" : "2016-10-08 22:30:20",
"Sunrise" : "07:16",
"Sunset" : "18:21",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 6,
"HardwareName" : "Raspberry Pi",
"HardwareType" : "Logitech Media Server",
"HardwareTypeVal" : 60,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "000001B",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-10-08 00:13:48",
"Level" : 0,
"LevelInt" : 0,
"MaxDimLevel" : 15,
"Name" : "Conservatory Radio",
"Notifications" : "false",
"PlanID" : "4",
"PlanIDs" : [ 4 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Off",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "AC",
"SwitchType" : "Media Player",
"SwitchTypeVal" : 17,
"Timers" : "false",
"Type" : "Lighting 2",
"TypeImg" : "LogitechMediaServer",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "260"
}
],
"status" : "OK",
"title" : "Devices"
}
Evohome
I have installed this plugin and the Domoticz devices are available in Homebridge.
I have several Evohome zones. The values are shown well in Domoticz. In Homebridge I see all zones, but the temperature shown on the device in HomeKit is equal to the set temperature (and not to the actual zone temperature). I use the Insteon+ app in my iPhone.
EvoHome via Script (Heating system)
Hi there,
Details for Honeywell EvoHome (using the script integration method), this is 1 heating zone information.
Many thanks
{
"ActTime" : 1455379812,
"ServerTime" : "2016-02-13 16:10:12",
"Sunrise" : "07:25",
"Sunset" : "17:18",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "23.0 C, (23.0 C), TemporaryOverride until 2016-02-13T23:30:00Z",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 20,
"HardwareName" : "evohome",
"HardwareType" : "Evohome via script",
"HardwareTypeVal" : 40,
"HaveTimeout" : false,
"ID" : "621833",
"LastUpdate" : "2016-02-13 16:10:08",
"Name" : "Living Room",
"Notifications" : "false",
"PlanID" : "18",
"PlanIDs" : [ 18 ],
"Protected" : false,
"SetPoint" : 23.0,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "TemporaryOverride",
"SubType" : "Zone",
"Temp" : 23.0,
"Timers" : "false",
"Type" : "Heating",
"TypeImg" : "override_mini",
"Unit" : 9,
"Until" : "2016-02-13T23:30:00Z",
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "363"
}
],
"status" : "OK",
"title" : "Devices"
}
Devices showing as dimmable when they are not really (and vice-versa)
As requested
This device is a genuine dimmer and shows properly as such in Eve
{
"ActTime" : 1454957927,
"ServerTime" : "2016-02-08 18:58:47",
"Sunrise" : "07:27",
"Sunset" : "16:59",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Off",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "004DDA2",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-02-08 17:46:14",
"Level" : 100,
"LevelInt" : 15,
"MaxDimLevel" : 15,
"Name" : "Ruby's Ceiling Light",
"Notifications" : "false",
"PlanID" : "8",
"PlanIDs" : [ 8, 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : 5,
"Status" : "Off",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "AC",
"SwitchType" : "Dimmer",
"SwitchTypeVal" : 7,
"Timers" : "false",
"Type" : "Lighting 2",
"TypeImg" : "dimmer",
"Unit" : 12,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "860",
"YOffset" : "556",
"idx" : "62"
}
],
"status" : "OK",
"title" : "Devices"
}
This device is a simple on/off outside light but also shows as a disable device in Eve
{
"ActTime" : 1454958005,
"ServerTime" : "2016-02-08 19:00:05",
"Sunrise" : "07:27",
"Sunset" : "16:59",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 125,
"Data" : "On",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "0005B77",
"Image" : "OutsideLantern",
"IsSubDevice" : false,
"LastUpdate" : "2016-02-08 16:59:00",
"Level" : 0,
"LevelInt" : 0,
"MaxDimLevel" : 15,
"Name" : "Outside Front Door",
"Notifications" : "false",
"PlanID" : "10",
"PlanIDs" : [ 10, 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "On",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "AC",
"SwitchType" : "On/Off",
"SwitchTypeVal" : 0,
"Timers" : "true",
"Type" : "Lighting 2",
"TypeImg" : "lightbulb",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "929",
"YOffset" : "519",
"idx" : "26"
}
],
"status" : "OK",
"title" : "Devices"
}
Finally this is a dimable device which shows as On/Off in Eve
{
"ActTime" : 1454958079,
"ServerTime" : "2016-02-08 19:01:19",
"Sunrise" : "07:27",
"Sunset" : "16:59",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "On",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "F298E1",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-02-06 13:50:45",
"Level" : 100,
"LevelInt" : 32,
"MaxDimLevel" : 32,
"Name" : "Scarlett's Ceiling Light",
"Notifications" : "false",
"PlanID" : "9",
"PlanIDs" : [ 9, 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "On",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "LightwaveRF",
"SwitchType" : "Dimmer",
"SwitchTypeVal" : 7,
"Timers" : "false",
"Type" : "Lighting 5",
"TypeImg" : "dimmer",
"Unit" : 16,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "155",
"YOffset" : "193",
"idx" : "188"
}
],
"status" : "OK",
"title" : "Devices"
}
Actually on investigation, I have a mixture of LightwaveRF devices (one dimmable) which are Lighting 5 and HomeEasy (Type AC Lighting 2) and all of these are showing as dimable devices whereas only one really is, whereas all the Lightwave devices show as just being On/Off.
Switchtype selector
Hi! thanks for the plugin so far! its working great!! but i just made an switch to control my TV. is it possible with homekit to have an switch with more options? like this one below?
`
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 2,
"Data" : "Off",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 7,
"HardwareName" : "Virtuele switch",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "0001415A",
"Image" : "TV",
"IsSubDevice" : false,
"LastUpdate" : "2016-08-15 13:47:44",
"Level" : 0,
"LevelActions" : "script%3A//request.sh%20off|script%3A//request.sh%20on|script%3A//request.sh%20hdmi1|script%3A//request.sh%20hdmi2",
"LevelInt" : 0,
"LevelNames" : "Off|TV|Apple TV|PS4",
"LevelOffHidden" : false,
"MaxDimLevel" : 100,
"Name" : "TV Selector",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"SelectorStyle" : 0,
"ShowNotifications" : true,
"SignalLevel" : "-",
"Status" : "Off",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "Selector Switch",
"SwitchType" : "Selector",
"SwitchTypeVal" : 18,
"Timers" : "false",
"Type" : "Light/Switch",
"TypeImg" : "Light",
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "267"
},`
TypeError: undefined is not a function
Loaded config.json with 0 accessories and 1 platforms.
Loading 1 platforms...
[eDomoticz] Initializing eDomoticz platform...
[eDomoticz] Fetching Domoticz lights and switches...
Loading 0 accessories...
[eDomoticz] Initializing platform accessory 'Amp'...
[eDomoticz] Initializing platform accessory 'Amp Background Volume'...
[eDomoticz] Initializing platform accessory 'Amp Vol Normal'...
[eDomoticz] Initializing platform accessory 'AppleTV'...
[eDomoticz] Initializing platform accessory 'Barometer'...
[eDomoticz] Initializing platform accessory 'CPU_Usage'...
[eDomoticz] Initializing platform accessory 'HDD /'...
[eDomoticz] Initializing platform accessory 'HDD /boot'...
[eDomoticz] Initializing platform accessory 'Helens Light'...
[eDomoticz] Initializing platform accessory 'Homebridge Temp'...
[eDomoticz] Initializing platform accessory 'Household Electricity'...
/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Service.js:52
this.getCharacteristic(Characteristic.Name) ||
^
TypeError: undefined is not a function
at Function.Service (/usr/local/lib/node_modules/homebridge/node_modules/hap->nodejs/lib/Service.js:52:12)
at Function.eDomoticzPlatform.MeterDeviceService (/usr/local/lib/node_modules/homebridge->eDomoticz/index.js:119:10)
at Object.eDomoticzAccessory.getServices (/usr/local/lib/node_modules/homebridge->eDomoticz/index.js:364:49)
at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:235:36)
at Server. (/usr/local/lib/node_modules/homebridge/lib/server.js:221:32)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:15:19
at callbackLater (/usr/local/lib/node_modules/homebridge-eDomoticz/index.js:132:27)
at Object. (/usr/local/lib/node_modules/homebridge-eDomoticz/index.js:159:5)
at Request.self.callback (/usr/local/lib/node_modules/homebridge->eDomoticz/node_modules/request/request.js:198:22)
at Request.emit (events.js:110:17)
There’s something I’m not understanding about custom characteristics and services... when it comes to adding a “General” sensor of SubType “kWh” (i.e.: a General Power Meter Virtual Sensor for CC EnvIR in Domoticz), the above error is thrown.
Code for creating custom characteristics and services was based on homebridge-yamaha
Negative temperature is shown as positive
negative T is correctly shown in Domoticz, and in Domoticz mqtt output, but HomeKit (both Elgato and Home app) shows +2c.
Undetected Dimmer
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : “Off”,
"Description" : “”,
"Favorite" : 1,
"HardwareID" : 1,
"HardwareName" : "RFLink Gateway”,
"HardwareType" : "RFLink Gateway USB”,
"HardwareTypeVal" : 46,
"HaveDimmer" : false,
"HaveGroupCmd" : false,
"HaveTimeout" : false,
"ID" : “012DD986”,
"Image" : “Light”,
"IsSubDevice" : false,
"LastUpdate" : "2016-02-07 12:44:19”,
"Level" : 40,
"LevelInt" : 40,
"MaxDimLevel" : 100,
"Name" : “Main”,
"Notifications" : “false”,
"PlanID" : “2”,
"PlanIDs" : [ 2 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : “-“,
"Status" : “Off”,
"StrParam1" : “”,
"StrParam2" : “”,
"SubType" : “AC”,
"SwitchType" : “Dimmer”,
"SwitchTypeVal" : 7,
"Timers" : “false”,
"Type" : "Light/Switch”,
"TypeImg" : “dimmer”,
"Unit" : 1,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : “0”,
"YOffset" : “0”,
"idx" : “32”
},
Getting a doorbell working
I have my 433mhz doorbell hooked up in Domoticz. I currently use a combination of scripts and IFTTT to send push notifications to my phone when the bell rings but it would be great to get this working natively via HomeKit.
HAP-NodeJS has support for the new iOS 10 doorbell type already:
https://github.com/KhaosT/HAP-NodeJS/issues/303
Does homebridge-edomoticz support this yet and if not what would be necessary to get this working?
Opentherm Gateway
hello,
here is some information about the opentherm gateway i sea the heating item now as a switch in Eve.
is it possible to support this?
{ "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "16.0", "Description" : "", "Favorite" : 1, "HardwareID" : 1, "HardwareName" : "OpenTherm Gateway", "HardwareType" : "OpenTherm Gateway USB", "HardwareTypeVal" : 18, "HaveTimeout" : false, "ID" : "0000005", "LastUpdate" : "2016-02-15 23:46:43", "Name" : "Room Setpoint", "Notifications" : "false", "PlanID" : "3", "PlanIDs" : [ 3, 12 ], "Protected" : false, "SetPoint" : "16.0", "ShowNotifications" : true, "SignalLevel" : "-", "SubType" : "SetPoint", "Timers" : "true", "Type" : "Thermostat", "TypeImg" : "override_mini", "Unit" : 0, "Used" : 1, "XOffset" : "0", "YOffset" : "0", "idx" : "17" },
{ "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "CustomImage" : 15, "Data" : "Off", "Description" : "", "Favorite" : 0, "HardwareID" : 1, "HardwareName" : "OpenTherm Gateway", "HardwareType" : "OpenTherm Gateway USB", "HardwareTypeVal" : 18, "HaveDimmer" : true, "HaveGroupCmd" : true, "HaveTimeout" : false, "ID" : "0000071", "Image" : "Heating", "IsSubDevice" : false, "LastUpdate" : "2016-02-15 23:12:43", "Level" : 0, "LevelInt" : 0, "MaxDimLevel" : 15, "Name" : "FlameOn", "Notifications" : "false", "PlanID" : "0", "PlanIDs" : [ 0 ], "Protected" : true, "ShowNotifications" : true, "SignalLevel" : "-", "Status" : "Off", "StrParam1" : "", "StrParam2" : "", "SubType" : "AC", "SwitchType" : "On/Off", "SwitchTypeVal" : 0, "Timers" : "false", "Type" : "Lighting 2", "TypeImg" : "lightbulb", "Unit" : 1, "Used" : 1, "UsedByCamera" : false, "XOffset" : "0", "YOffset" : "0", "idx" : "11" },
{ "AddjMulti" : 1.0, "AddjMulti2" : 1.0, "AddjValue" : 0.0, "AddjValue2" : 0.0, "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "18.6 C", "Description" : "", "Favorite" : 1, "HardwareID" : 1, "HardwareName" : "OpenTherm Gateway", "HardwareType" : "OpenTherm Gateway USB", "HardwareTypeVal" : 18, "HaveTimeout" : false, "ID" : "0008", "LastUpdate" : "2016-02-15 23:46:43", "Name" : "Room Temperature", "Notifications" : "false", "PlanID" : "3", "PlanIDs" : [ 3, 12 ], "Protected" : false, "ShowNotifications" : true, "SignalLevel" : "-", "SubType" : "TFA 30.3133", "Temp" : 18.60, "Timers" : "false", "Type" : "Temp", "TypeImg" : "temperature", "Unit" : 8, "Used" : 1, "XOffset" : "0", "YOffset" : "0", "idx" : "18" },
usage/consumption graphs in Eve.app
Some notes on tapping into the Eve.app graphing abilities
I presume Homebridge needs the v.latest version of @KhaosT’s hap-nodejs submodule, to provide the ‘log’ characteristic.
Then I presume either Eve.app will handle that characteristic if it detects it, or it’ll need linking in via elgato-specific characteristics (as discovered by @gomfunkel)
Retrieving log points from Domoticz:
http://127.0.0.1:8080/json.htm?
type=lightlog
&idx={_ID_}
http://127.0.0.1:8080/json.htm?
type=graph
&sensor={counter|Percentage|temp|rain|fan|wind|uv}
&idx={_ID_}
&method={int}
&range={day|week|month|year}
{
&actmonth={month}
&actyear={year}
}
Lux sensor
Hello,
I noticed when the brightness of the room where I placed a light sensor is 0 lux with edomoticz in Home app, the switch loses signal. The Home app shows me that the switch is unavailable. And whenever there is a bit of brightness (1 lux for example), I get the switch in the system HomeKit.
is it normal?
Thanks.
Possibility to add support for a Temp+Hum sensor
Hi,
as requested (http://www.domoticz.com/forum/viewtopic.php?f=36&t=10272&start=20#p73066), here's the json-output of temp+hum sensor:
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "22.3 C, 35 %",
"Description" : "",
"DewPoint" : "6.10",
"Favorite" : 1,
"HardwareID" : 3,
"HardwareName" : "TelldusLive",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveTimeout" : false,
"Humidity" : 35,
"HumidityStatus" : "Normal",
"ID" : "14069",
"LastUpdate" : "2016-02-03 09:38:17",
"Name" : "Olohuone",
"Notifications" : "false",
"PlanID" : "2",
"PlanIDs" : [ 2 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "THGN122/123, THGN132, THGR122/228/238/268",
"Temp" : 22.30,
"Timers" : "false",
"Type" : "Temp + Humidity",
"TypeImg" : "temperature",
"Unit" : 1,
"Used" : 1,
"XOffset" : "1100",
"YOffset" : "1034",
"idx" : "26"
}
],
Thanks a lot for the work on the plugin! :)
Somfy RFY Domoticz blinds
Hi there! got edomoticz/Homebridge working. Many thanks for your great work!
One issue that I have is that all of my Somfy RFY domoitcz blinds (shutters) are being loading into eve as power switches.
Are you able to change this?
By the way in the eve accessory info they are listed as Manufacturer: edomoitcz, Model:RFY
If I can be of any assitance with please let me know.
Thanks in advance!
Lock support
Fantastic work so far, congrats!
Any chance we can get proper "lock" support?
"SubType" : "Switch",
"SwitchType" : "Door Lock",
"SwitchTypeVal" : 11,
This was I could tell Siri to "lock/unlock Garage Gate" instead of "Turn On/Off Garage Gate" if that makes sense
Door and Windows Sensors
I am wondering if it would be at all possible to also include support for Open / Close door and Window sensors. I have two types, one made by LightwaveRF and the other by HomeEasy. The json output results for an example of both is below.
Again many thanks for all your good work.
The Lightwave Version
{
"ActTime" : 1454859550,
"ServerTime" : "2016-02-07 15:39:10",
"Sunrise" : "07:29",
"Sunset" : "16:57",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Closed",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "2C25CC",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-02-05 07:09:03",
"Level" : 0,
"LevelInt" : 0,
"MaxDimLevel" : 32,
"Name" : "Bathroom Window",
"Notifications" : "false",
"PlanID" : "6",
"PlanIDs" : [ 6, 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : 6,
"Status" : "Closed",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "LightwaveRF",
"SwitchType" : "Contact",
"SwitchTypeVal" : 2,
"Timers" : "false",
"Type" : "Lighting 5",
"TypeImg" : "contact",
"Unit" : 10,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "41",
"YOffset" : "638",
"idx" : "46"
}
],
"status" : "OK",
"title" : "Devices"
}
The HomeEasy version which differs in just the Type and Subtype
{
"ActTime" : 1454859576,
"ServerTime" : "2016-02-07 15:39:36",
"Sunrise" : "07:29",
"Sunset" : "16:57",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Closed",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "RFXCOM",
"HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
"HardwareTypeVal" : 1,
"HaveDimmer" : true,
"HaveGroupCmd" : true,
"HaveTimeout" : false,
"ID" : "001488C",
"Image" : "Light",
"IsSubDevice" : false,
"LastUpdate" : "2016-01-25 08:13:14",
"Level" : 0,
"LevelInt" : 0,
"MaxDimLevel" : 15,
"Name" : "Ruby's Room Window",
"Notifications" : "false",
"PlanID" : "8",
"PlanIDs" : [ 8, 11 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : 5,
"Status" : "Closed",
"StrParam1" : "",
"StrParam2" : "",
"SubType" : "AC",
"SwitchType" : "Contact",
"SwitchTypeVal" : 2,
"Timers" : "false",
"Type" : "Lighting 2",
"TypeImg" : "contact",
"Unit" : 10,
"Used" : 1,
"UsedByCamera" : false,
"XOffset" : "936",
"YOffset" : "517",
"idx" : "59"
}
],
"status" : "OK",
"title" : "Devices"
No switch status update in homekit. Siri does not know the switch status (state) in Domoticz
Hi,
I have a couple of virtual switches in domoticz which can be turned on and off by Siri thanks to homebridge-domoticz plugin. Thank you for your great job!
However, Siri cannot tell the state of the switches when I want to check by asking her: what is the status of my Ceiling Fan (name of my domoticz switch)?
The same question gets correct answer by Siri for other devices over homebridge such as my Lifx bulbs (namely Lamp). Siri would say: your Lamp is on (or off).
The same question also works for my blinds in domoticz, as I just updated the index.js as per instruction in this forum (And all my blinds turned from Switches to Positions in my Eve homekit app). Siri would say: your Living-room Curtain (name of my blind) is set at 100% (or 0%). Previously, when the blinds were treated by homekit as switches, Siri did not understand the question.
If I try to refresh (pull down) the Eve homekit application I can see the state of my domoticz virtual switches still get updated in the terminal command line running homebridge. It seem the switch state is updated in homebridge like my Lifx bulbs , and Blinds, but just Siri does not recognize it. Please help!
A request to add a Water Counter type
Here is the JSON outcome for the device:
{
"ActTime" : 1472668145,
"ServerTime" : "2016-08-31 21:29:05",
"Sunrise" : "05:34",
"Sunset" : "19:24",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"Counter" : "211.200 m3",
"CounterToday" : "100 Liter",
"CustomImage" : 0,
"Data" : "211.200 m3",
"Description" : "",
"Favorite" : 1,
"HardwareID" : 2,
"HardwareName" : "My GW",
"HardwareType" : "MySensors Gateway USB",
"HardwareTypeVal" : 41,
"HaveTimeout" : false,
"ID" : "0501",
"LastUpdate" : "2016-08-31 20:43:05",
"Name" : "Water Cold",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "RFXMeter counter",
"SwitchTypeVal" : 2,
"Timers" : "false",
"Type" : "RFXMeter",
"TypeImg" : "counter",
"Unit" : 0,
"Used" : 1,
"ValueQuantity" : "",
"ValueUnits" : "",
"XOffset" : "0",
"YOffset" : "0",
"idx" : "1"
}
],
"status" : "OK",
"title" : "Devices"
}
No accessories showing up in HMCatalog or Eve.app
Hello,
I'm just taking my first steps with homebridge as well as homebridge-edomoticz. I have Domoticz 3.4834 running on a Raspberry Pi B 512MB. It has the zwave.me daughter board attached and happily controls a Fibaro RGBW controller. So far, so good.
Now I have pulled homebridge from git, built it and installed homebridge-edomoticz via npm. Configuration:
{
"bridge": {
"name": "Homebridge",
"username": "CC:21:3E:E4:DE:33",
"port": 51826,
"pin": "031-45-154"
},
"description": "Configuration file for Domoticz platform.",
"platforms": [
{
"platform": "Domoticz",
"name": "Domoticz",
"server": "127.0.0.1",
"port": "8080",
"ssl": 0,
"roomid": 2
}
],
"accessories": []
}
➜ homebridge git:(master) ✗ ./bin/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>
[Thu Jun 16 2016 19:40:10 GMT+0200 (CEST)] Loaded plugin: homebridge-edomoticz
[Thu Jun 16 2016 19:40:10 GMT+0200 (CEST)] Registering accessory 'homebridge-edomoticz.eDomoticz'
[Thu Jun 16 2016 19:40:10 GMT+0200 (CEST)] Registering platform 'homebridge-edomoticz.eDomoticz'
[Thu Jun 16 2016 19:40:10 GMT+0200 (CEST)] ---
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
[Thu Jun 16 2016 19:40:10 GMT+0200 (CEST)] Homebridge is running on port 51826.
This looks as expected to me. I also paired successfully using Eve.app on one device, the "home" shows up in HMCatalog.app on another device. Its just... no RGBW controller (components) showing up anywhere.
Running homebridge with DEBUG=* revealed some HTTP queries being processed but I could spot no errors. I can paste the output of Eve.app querying something of course if that helps.
Do you have any idea where I could get more information from or what I might have missed?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.