Comments (49)
what kind of devices are this? what is your exact configuration?
from homebridge-fhem.
Hey,
I have exactly the same problem. All devices like WifiLight or HomeMatic seem to update their status correctly except the itswitch devices. I've tried some things like reinstalling the whole thing but nothing helped.
Starting it via "homebridge --debug" in terminal it only shows that the new values of the devices that are working are cached. For the 433Mhz radio plugs only the toggle command is executed but no caching-process is shown?
I'm running a Intel-NUC with Ubuntu. Yesterday I've installed NodeJS v6.3.1 an the newest release of the homebridge files.
On my Pi I had the same problem a while ago.
from homebridge-fhem.
this is probably a different problem. there is/was a bug/strange behaviour in the it module. this should be fixed with a fhem update from today.
from homebridge-fhem.
I updated fhem. Now it seems to work! Thanks!!
from homebridge-fhem.
I noticed that my HM-Sec-SCo are not updating their status. Do you probably know the issue?
from homebridge-fhem.
my HM-Sec-SCo and HM-SEC-RHS do update. so it is not a general problem.
please show the console output if starting homebridge with --debug
are the events for the HM-Sec-SCo visible in the fhem eventmonitor?
do you have any special configurations for the HM-Sec-SCo?
from homebridge-fhem.
yes, the events are visible in the event monitor. I don't think I have any special configurations.
I only have created a group and an alias.
the information for one of the sensors:
homebridge --debug
*** WARNING *** The program 'nodejs' 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=nodejs
*** WARNING *** The program 'nodejs' 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=nodejs&f=DNSServiceRegister
[2016-09-20 17:05:00] Loaded plugin: homebridge-fhem
homebridge API version: 2
[2016-09-20 17:05:00] Registering platform 'homebridge-fhem.FHEM'
[2016-09-20 17:05:00] ---
[2016-09-20 17:05:00] Loaded config.json with 0 accessories and 1 platforms.
[2016-09-20 17:05:00] ---
[2016-09-20 17:05:00] Loading 1 platforms...
[2016-09-20 17:05:00] [FHEM] Initializing FHEM platform...
starting longpoll: https://127.0.0.1:8083/fhem.pl?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1474383900964
[2016-09-20 17:05:00] [FHEM] Checking genericDeviceType...
[2016-09-20 17:05:00] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2016-09-20 17:05:00] [FHEM] Fetching FHEM devices...
[2016-09-20 17:05:00] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=Homekit&XHR=1
[2016-09-20 17:05:00] Loading 0 accessories...
Server listening on: http://:8282
[2016-09-20 17:05:01] [FHEM] got: 16 results[2016-09-20 17:05:01] [FHEM] WZ.Fenster is ContactSensor
[2016-09-20 17:05:01] [FHEM] WZ.Fenster has
[2016-09-20 17:05:01] [FHEM] StatusLowBattery [battery]
[2016-09-20 17:05:01] [FHEM] FirmwareRevision [D-firmware]
[2016-09-20 17:05:01] [FHEM] ContactSensorState [contact]
[2016-09-20 17:05:01] [FHEM] CurrentDoorState [contact]
[2016-09-20 17:05:01] [FHEM] value2homekit_re: [ { re: '.', to: 1 } ]
[2016-09-20 17:05:01] [FHEM] value2homekit: { ok: 0 }
[2016-09-20 17:05:01] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-20 17:05:01 caching: WZ.Fenster-battery: ok
[2016-09-20 17:05:01] [FHEM] WZ.Fenster-battery values: value ok mapped to 0
[2016-09-20 17:05:01] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2016-09-20 17:05:01 caching: WZ.Fenster-D-firmware: 1.0
[2016-09-20 17:05:01] [FHEM] caching: FirmwareRevision: 1.0 (as string; from '1.0')
[2016-09-20 17:05:01] [FHEM] value2homekit_re: [ { re: '^closed', to: 0 }, { re: '.', to: 1 } ]
[2016-09-20 17:05:01] [FHEM] homekit2name: { '0': 'CONTACT_DETECTED', '1': 'CONTACT_NOT_DETECTED' }
2016-09-20 17:05:01 caching: WZ.Fenster-contact: open (to hmusb)
[2016-09-20 17:05:01] [FHEM] WZ.Fenster-contact values: value open (to hmusb) mapped to 1
[2016-09-20 17:05:01] [FHEM] caching: ContactSensorState: 1 (as number; means CONTACT_NOT_DETECTED; from 'open (to hmusb)')
[2016-09-20 17:05:01] [FHEM] value2homekit_re: [ { re: '^closed', to: 1 }, { re: '.*', to: 0 } ]
[2016-09-20 17:05:01] [FHEM] homekit2name: { '0': 'OPEN', '1': 'CLOSED' }
[2016-09-20 17:05:01] [FHEM] WZ.Fenster-contact values: value open (to hmusb) mapped to 0
[2016-09-20 17:05:01] [FHEM] caching: CurrentDoorState: 0 (as number; means OPEN; from 'open (to hmusb)')[2016-09-20 17:05:01] [FHEM] Initializing platform accessory 'WZ.Fenster'...
[2016-09-20 17:05:01] [FHEM] creating services for WZ.Fenster
[2016-09-20 17:05:01] [FHEM] information service for WZ.Fenster
[2016-09-20 17:05:01] [FHEM] manufacturer, model and serial number characteristics for WZ.Fenster
[2016-09-20 17:05:01] [FHEM] firmware revision characteristic for WZ.Fenster
[2016-09-20 17:05:01] [FHEM] ContactSensor service for WZ.Fenster
[2016-09-20 17:05:01] [FHEM] StatusLowBattery characteristic for WZ.Fenster:battery
[2016-09-20 17:05:01] [FHEM] initial value is: 0 (number; means BATTERY_LEVEL_NORMAL)
[2016-09-20 17:05:01] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[2016-09-20 17:05:01] [FHEM] ContactSensorState characteristic for WZ.Fenster:contact
[2016-09-20 17:05:01] [FHEM] initial value is: 1 (number; means CONTACT_NOT_DETECTED)
[2016-09-20 17:05:01] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[2016-09-20 17:05:01] [FHEM] CurrentDoorState characteristic for WZ.Fenster:contact
[2016-09-20 17:05:01] [FHEM] initial value is: 0 (number; means OPEN)
[2016-09-20 17:05:01] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
EDIT: I changed the "expert" attribute to "2_full"
from homebridge-fhem.
the initial values look ok.
do you see the events from the event monitor also in the homebridge console?
from the Sco? from other devices?
please show a list of the fhem device also.
from homebridge-fhem.
when I open a window or a door there is nothing happening in the homebridge console
at the moment I only have those sensors integrated in homebridge. all other devices are switches.
do you want to see how the device is define in my fhem config?
define WZ.Fenster CUL_HM 3D68E9
attr WZ.Fenster IODev hmusb
attr WZ.Fenster actCycle 001:05
attr WZ.Fenster actStatus alive
attr WZ.Fenster alias Fenstersensor Wohnzimmer
attr WZ.Fenster autoReadReg 4_reqStatus
attr WZ.Fenster event-on-change-reading state,battery
attr WZ.Fenster expert 2_defReg+raw
attr WZ.Fenster firmware 1.0
attr WZ.Fenster genericDeviceType contact
attr WZ.Fenster group Zugangssensor
attr WZ.Fenster model HM-SEC-SCo
attr WZ.Fenster peerIDs 00000000,
attr WZ.Fenster room CUL_HM,Wohnzimmer,Homekit
attr WZ.Fenster serialNr MEQ0818607
attr WZ.Fenster subType threeStateSensor
define FileLog_WZ.Fenster FileLog ./log/WZ.Fenster-%Y.log WZ.Fenster
attr FileLog_WZ.Fenster logtype text
attr FileLog_WZ.Fenster room CUL_HM
from homebridge-fhem.
found it. you have defined event-on-change-reading with state,battery. this will suppress events for all other readings. homekit-fhem uses the contact reading. you can add contact to your event-on-change-reading attribute or use homebridgeMapping so that ContactSensorState and CurrentDoorState will use state instead of contact. but contact is preferred.
from homebridge-fhem.
thats it! now its working like a charme. thank you so much!
from homebridge-fhem.
Looks like an update of fhem and homebridge-fhem has fixed it. I'll keep the issue open and close it if I'm certain its fixed in a few days. :) thanks this is working very nicely!
from homebridge-fhem.
Ok so i've actually got it working just fine for some MQTT-DEVICE. updates like a charm.
However, I have some TRX lights that do not! A screen shot below is of the device config. There are no event filters or anything.
The device works in homebridge-fhem. it just that its status is not updated! any ideas?
from homebridge-fhem.
do you see the events in the event monitor? does fhemweb update its icons without reload?
from homebridge-fhem.
fhemweb updates without a refresh.
and the following is in the events monitor
2016-09-28 11:18:08 TRX_LIGHT TRX_AC_002d4f3a03 off
so that is working
from homebridge-fhem.
please show a list of the WEB device.
from homebridge-fhem.
could you be a bit more specific on how to do that? is that in FHEM?
from homebridge-fhem.
just type
list WEB
in the command box on top of the page or in a telnet connection.
from homebridge-fhem.
that was easy
Internals:
CONNECTS 78
DEF 8083 global
FD 6
NAME WEB
NR 5
NTFY_ORDER 50-WEB
PORT 8083
STATE Initialized
TYPE FHEMWEB
Attributes:
confirmDelete 0
defaultRoom Livingroom
editConfig 1
hiddenroom CUL_FHTTK,FS20,TRX_LIGHT,TRX_ELSE,TRX_WEATHER,DashboardRoom,Plots
longpoll 0
redirectCmds 0
refresh 0
reverseLogs 1
from homebridge-fhem.
longpoll hast to be 1 so that fhemweb will update its icons. but that should not be related.
can you enable the console.log lines in homebridge-fhem index.js for the lines 464,480 and 495 and have a look if you see something on the homebridge console if the events happen in fhem?
from homebridge-fhem.
OK so the plot thickens a little bit. I enabled that debugging and nothing happens in home bridge console when I turn on/off the light. This is despite the fact that the event viewer is logging events as shown below for the device.
I've tried adding attr TRX_AC_002d4f3a03 homebridgeMapping On=state
and attr TRX_AC_002d4f3a03 genericDeviceType switch
but it does not work. Homebridge-fhem is picking up the changing state of my structure called house though, whenever i change the switch. so this is something specific to the TRX_LIGHTS that is not working!!
any ideas? and thanks for the help so far. this software really is awesome!
from homebridge-fhem.
please post a jsonlist2 from the TRX_AC_002d4f3a03 device. it looks like it is not correctly detected and the characteristics just have the default values and no connection to the fhem readings.
from homebridge-fhem.
here you go
{
"Arg":"TRX_AC_002d4f3a03",
"Results": [
{
"Name":"TRX_AC_002d4f3a03",
"PossibleSets":"all_level all_off all_on level:slider,0,1,15 off on on-till on-for-timer",
"PossibleAttrs":"verbose:0,1,2,3,4,5 room group comment:textField-long alias eventMap userReadings:textField-long IODev ignore:1,0 do_not_notify:1,0 repeat event-on-change-reading event-on-update-reading event-aggregator event-min-interval stateFormat:textField-long timestamp-on-change-reading cmdIcon devStateIcon devStateStyle devices devices_map fm_type genericDeviceType:ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long house house_map icon lights lights_map music music_map room_map sortby structexclude webCmd widgetOverride house house_map lights lights_map room_map structexclude userattr",
"Internals": {
"DEF": "AC 002d4f3a03 light",
"NAME": "TRX_AC_002d4f3a03",
"NR": "335",
"STATE": "on",
"TRX_LIGHT_deviceid": "002d4f3a03",
"TRX_LIGHT_devicelog": "light",
"TRX_LIGHT_type": "AC",
"TYPE": "TRX_LIGHT"
},
"Readings": {
"light": { "Value":"on", "Time":"2016-09-13 18:55:20" },
"state": { "Value":"on", "Time":"2016-09-29 11:52:36" }
},
"Attributes": {
"IODev": "d2",
"alias": "Couch Light",
"genericDeviceType": "switch",
"group": "lights",
"homebridgeMapping": "On=state",
"house": "house",
"lights": "livingroom.structure.lights",
"room": "Favourites,Homekit,Livingroom",
"userattr": "house house_map lights lights_map room_map structexclude"
}
} ],
"totalResultsReturned":1
}
from homebridge-fhem.
this looks ok...
please post the console output when starting homebridge. ideally with --debug
from homebridge-fhem.
no problem.
andrew@melvana:~$ homebridge --debug
*** WARNING *** The program 'nodejs' 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=nodejs>
*** WARNING *** The program 'nodejs' 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=nodejs&f=DNSServiceRegister>
[30/09/2016, 18:52:30] Loaded plugin: homebridge-fhem
homebridge API version: 2
[30/09/2016, 18:52:32] Registering platform 'homebridge-fhem.FHEM'
[30/09/2016, 18:52:32] ---
[30/09/2016, 18:52:32] Loaded plugin: homebridge-mpd
[30/09/2016, 18:52:32] Registering accessory 'homebridge-mpd.mpd'
[30/09/2016, 18:52:32] ---
[30/09/2016, 18:52:32] Loaded config.json with 0 accessories and 1 platforms.
[30/09/2016, 18:52:32] ---
[30/09/2016, 18:52:32] Loading 1 platforms...
[30/09/2016, 18:52:32] [FHEM] Initializing FHEM platform...
starting longpoll: http://192.168.1.25:8083/fhem.pl?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1475257953063
[30/09/2016, 18:52:33] [FHEM] Checking genericDeviceType...
[30/09/2016, 18:52:33] [FHEM] executing: http://192.168.1.25:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[30/09/2016, 18:52:33] [FHEM] Fetching FHEM devices...
[30/09/2016, 18:52:33] [FHEM] fetching: http://192.168.1.25:8083/fhem?cmd=jsonlist2%20room=Homekit&XHR=1
Server listening on: http://<ip>:8282
[30/09/2016, 18:52:33] [FHEM] got: 16 results
[30/09/2016, 18:52:33] [FHEM] mappings for BathroomHeat: { CurrentTemperature: { reading: 'measured-temp', minValue: -30 },
StatusLowBattery:
{ reading: 'battery',
values: [ 'ok:BATTERY_LEVEL_NORMAL', '/.*/:BATTERY_LEVEL_LOW' ] },
TargetTemperature:
{ reading: 'desired-temp',
cmd: 'desired-temp',
delay: true,
minValue: 6,
maxValue: 30,
minStep: 0.5 },
'4648454d-0201-686F-6D65-627269646765':
{ reading: 'actuator',
name: 'Actuation',
format: 'UINT8',
unit: 'PERCENTAGE',
maxValue: 100,
minValue: 0,
minStep: 1 },
TargetHeatingCoolingState:
{ reading: 'mode',
values: [ '/^auto/:AUTO', '/^holiday_short/:OFF', '/.*/:HEAT' ],
cmds:
[ 'OFF:mode holiday_short',
'HEAT:mode manual',
'COOL:mode manual',
'AUTO:mode auto' ] } }
[30/09/2016, 18:52:33] [FHEM] BathroomHeat is thermostat
[30/09/2016, 18:52:33] [FHEM] BathroomHeat has
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature [measured-temp]
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery [battery]
[30/09/2016, 18:52:33] [FHEM] TargetTemperature [desired-temp]
[30/09/2016, 18:52:33] [FHEM] Custom Actuation [actuator]
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState [mode]
2016-09-30 18:52:33 caching: BathroomHeat-measured-temp: 19.3
[30/09/2016, 18:52:33] [FHEM] caching: CurrentTemperature: 19.3 (as number; from '19.3')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] value2homekit: { ok: 0 }
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-30 18:52:33 caching: BathroomHeat-battery: ok
[30/09/2016, 18:52:33] [FHEM] BathroomHeat-battery values: value ok mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2016-09-30 18:52:33 caching: BathroomHeat-desired-temp: 13.0
[30/09/2016, 18:52:33] [FHEM] caching: TargetTemperature: 13 (as number; from '13.0')
2016-09-30 18:52:33 caching: BathroomHeat-actuator: 0%
[30/09/2016, 18:52:33] [FHEM] caching: Custom Actuation: 0 (as number; from '0%')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '^auto', to: 3 },
{ re: '^holiday_short', to: 0 },
{ re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT', '3': 'AUTO' }
[30/09/2016, 18:52:33] [FHEM] homekit2cmd: { '0': 'mode holiday_short',
'1': 'mode manual',
'2': 'mode manual',
'3': 'mode auto' }
2016-09-30 18:52:33 caching: BathroomHeat-mode: auto
[30/09/2016, 18:52:33] [FHEM] BathroomHeat-mode values: value auto mapped to 3
[30/09/2016, 18:52:33] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'auto')
[30/09/2016, 18:52:33] [FHEM] mappings for Bedroom1Heat: { CurrentTemperature: { reading: 'measured-temp', minValue: -30 },
StatusLowBattery:
{ reading: 'battery',
values: [ 'ok:BATTERY_LEVEL_NORMAL', '/.*/:BATTERY_LEVEL_LOW' ] },
TargetTemperature:
{ reading: 'desired-temp',
cmd: 'desired-temp',
delay: true,
minValue: 6,
maxValue: 30,
minStep: 0.5 },
'4648454d-0201-686F-6D65-627269646765':
{ reading: 'actuator',
name: 'Actuation',
format: 'UINT8',
unit: 'PERCENTAGE',
maxValue: 100,
minValue: 0,
minStep: 1 },
TargetHeatingCoolingState:
{ reading: 'mode',
values: [ '/^auto/:AUTO', '/^holiday_short/:OFF', '/.*/:HEAT' ],
cmds:
[ 'OFF:mode holiday_short',
'HEAT:mode manual',
'COOL:mode manual',
'AUTO:mode auto' ] } }
[30/09/2016, 18:52:33] [FHEM] Bedroom1Heat is thermostat
[30/09/2016, 18:52:33] [FHEM] Bedroom1Heat has
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature [measured-temp]
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery [battery]
[30/09/2016, 18:52:33] [FHEM] TargetTemperature [desired-temp]
[30/09/2016, 18:52:33] [FHEM] Custom Actuation [actuator]
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState [mode]
2016-09-30 18:52:33 caching: Bedroom1Heat-measured-temp: 18.3
[30/09/2016, 18:52:33] [FHEM] caching: CurrentTemperature: 18.3 (as number; from '18.3')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] value2homekit: { ok: 0 }
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-30 18:52:33 caching: Bedroom1Heat-battery: ok
[30/09/2016, 18:52:33] [FHEM] Bedroom1Heat-battery values: value ok mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2016-09-30 18:52:33 caching: Bedroom1Heat-desired-temp: 10.0
[30/09/2016, 18:52:33] [FHEM] caching: TargetTemperature: 10 (as number; from '10.0')
2016-09-30 18:52:33 caching: Bedroom1Heat-actuator: 0%
[30/09/2016, 18:52:33] [FHEM] caching: Custom Actuation: 0 (as number; from '0%')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '^auto', to: 3 },
{ re: '^holiday_short', to: 0 },
{ re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT', '3': 'AUTO' }
[30/09/2016, 18:52:33] [FHEM] homekit2cmd: { '0': 'mode holiday_short',
'1': 'mode manual',
'2': 'mode manual',
'3': 'mode auto' }
2016-09-30 18:52:33 caching: Bedroom1Heat-mode: auto
[30/09/2016, 18:52:33] [FHEM] Bedroom1Heat-mode values: value auto mapped to 3
[30/09/2016, 18:52:33] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'auto')
[30/09/2016, 18:52:33] [FHEM] mappings for Bedroom2Heat: { CurrentTemperature: { reading: 'measured-temp', minValue: -30 },
StatusLowBattery:
{ reading: 'battery',
values: [ 'ok:BATTERY_LEVEL_NORMAL', '/.*/:BATTERY_LEVEL_LOW' ] },
TargetTemperature:
{ reading: 'desired-temp',
cmd: 'desired-temp',
delay: true,
minValue: 6,
maxValue: 30,
minStep: 0.5 },
'4648454d-0201-686F-6D65-627269646765':
{ reading: 'actuator',
name: 'Actuation',
format: 'UINT8',
unit: 'PERCENTAGE',
maxValue: 100,
minValue: 0,
minStep: 1 },
TargetHeatingCoolingState:
{ reading: 'mode',
values: [ '/^auto/:AUTO', '/^holiday_short/:OFF', '/.*/:HEAT' ],
cmds:
[ 'OFF:mode holiday_short',
'HEAT:mode manual',
'COOL:mode manual',
'AUTO:mode auto' ] } }
[30/09/2016, 18:52:33] [FHEM] Bedroom2Heat is thermostat
[30/09/2016, 18:52:33] [FHEM] Bedroom2Heat has
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature [measured-temp]
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery [battery]
[30/09/2016, 18:52:33] [FHEM] TargetTemperature [desired-temp]
[30/09/2016, 18:52:33] [FHEM] Custom Actuation [actuator]
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState [mode]
2016-09-30 18:52:33 caching: Bedroom2Heat-measured-temp: 19.4
[30/09/2016, 18:52:33] [FHEM] caching: CurrentTemperature: 19.4 (as number; from '19.4')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] value2homekit: { ok: 0 }
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-30 18:52:33 caching: Bedroom2Heat-battery: low
[30/09/2016, 18:52:33] [FHEM] Bedroom2Heat-battery values: value low mapped to 1
[30/09/2016, 18:52:33] [FHEM] caching: StatusLowBattery: 1 (as number; means BATTERY_LEVEL_LOW; from 'low')
2016-09-30 18:52:33 caching: Bedroom2Heat-desired-temp: 21.0
[30/09/2016, 18:52:33] [FHEM] caching: TargetTemperature: 21 (as number; from '21.0')
2016-09-30 18:52:33 caching: Bedroom2Heat-actuator: 0%
[30/09/2016, 18:52:33] [FHEM] caching: Custom Actuation: 0 (as number; from '0%')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '^auto', to: 3 },
{ re: '^holiday_short', to: 0 },
{ re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT', '3': 'AUTO' }
[30/09/2016, 18:52:33] [FHEM] homekit2cmd: { '0': 'mode holiday_short',
'1': 'mode manual',
'2': 'mode manual',
'3': 'mode auto' }
2016-09-30 18:52:33 caching: Bedroom2Heat-mode: auto
[30/09/2016, 18:52:33] [FHEM] Bedroom2Heat-mode values: value auto mapped to 3
[30/09/2016, 18:52:33] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'auto')
[30/09/2016, 18:52:33] [FHEM] mappings for KitchenHeat: { CurrentTemperature: { reading: 'measured-temp', minValue: -30 },
StatusLowBattery:
{ reading: 'battery',
values: [ 'ok:BATTERY_LEVEL_NORMAL', '/.*/:BATTERY_LEVEL_LOW' ] },
TargetTemperature:
{ reading: 'desired-temp',
cmd: 'desired-temp',
delay: true,
minValue: 6,
maxValue: 30,
minStep: 0.5 },
'4648454d-0201-686F-6D65-627269646765':
{ reading: 'actuator',
name: 'Actuation',
format: 'UINT8',
unit: 'PERCENTAGE',
maxValue: 100,
minValue: 0,
minStep: 1 },
TargetHeatingCoolingState:
{ reading: 'mode',
values: [ '/^auto/:AUTO', '/^holiday_short/:OFF', '/.*/:HEAT' ],
cmds:
[ 'OFF:mode holiday_short',
'HEAT:mode manual',
'COOL:mode manual',
'AUTO:mode auto' ] } }
[30/09/2016, 18:52:33] [FHEM] KitchenHeat is thermostat
[30/09/2016, 18:52:33] [FHEM] KitchenHeat has
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature [measured-temp]
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery [battery]
[30/09/2016, 18:52:33] [FHEM] TargetTemperature [desired-temp]
[30/09/2016, 18:52:33] [FHEM] Custom Actuation [actuator]
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState [mode]
2016-09-30 18:52:33 caching: KitchenHeat-measured-temp: 20.2
[30/09/2016, 18:52:33] [FHEM] caching: CurrentTemperature: 20.2 (as number; from '20.2')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] value2homekit: { ok: 0 }
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-30 18:52:33 caching: KitchenHeat-battery: ok
[30/09/2016, 18:52:33] [FHEM] KitchenHeat-battery values: value ok mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2016-09-30 18:52:33 caching: KitchenHeat-desired-temp: 6.0
[30/09/2016, 18:52:33] [FHEM] caching: TargetTemperature: 6 (as number; from '6.0')
2016-09-30 18:52:33 caching: KitchenHeat-actuator: 0%
[30/09/2016, 18:52:33] [FHEM] caching: Custom Actuation: 0 (as number; from '0%')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '^auto', to: 3 },
{ re: '^holiday_short', to: 0 },
{ re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT', '3': 'AUTO' }
[30/09/2016, 18:52:33] [FHEM] homekit2cmd: { '0': 'mode holiday_short',
'1': 'mode manual',
'2': 'mode manual',
'3': 'mode auto' }
2016-09-30 18:52:33 caching: KitchenHeat-mode: auto
[30/09/2016, 18:52:33] [FHEM] KitchenHeat-mode values: value auto mapped to 3
[30/09/2016, 18:52:33] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'auto')
[30/09/2016, 18:52:33] [FHEM] mappings for LivingroomHeat: { CurrentTemperature: { reading: 'measured-temp', minValue: -30 },
StatusLowBattery:
{ reading: 'battery',
values: [ 'ok:BATTERY_LEVEL_NORMAL', '/.*/:BATTERY_LEVEL_LOW' ] },
TargetTemperature:
{ reading: 'desired-temp',
cmd: 'desired-temp',
delay: true,
minValue: 6,
maxValue: 30,
minStep: 0.5 },
'4648454d-0201-686F-6D65-627269646765':
{ reading: 'actuator',
name: 'Actuation',
format: 'UINT8',
unit: 'PERCENTAGE',
maxValue: 100,
minValue: 0,
minStep: 1 },
TargetHeatingCoolingState:
{ reading: 'mode',
values: [ '/^auto/:AUTO', '/^holiday_short/:OFF', '/.*/:HEAT' ],
cmds:
[ 'OFF:mode holiday_short',
'HEAT:mode manual',
'COOL:mode manual',
'AUTO:mode auto' ] } }
[30/09/2016, 18:52:33] [FHEM] LivingroomHeat is thermostat
[30/09/2016, 18:52:33] [FHEM] LivingroomHeat has
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature [measured-temp]
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery [battery]
[30/09/2016, 18:52:33] [FHEM] TargetTemperature [desired-temp]
[30/09/2016, 18:52:33] [FHEM] Custom Actuation [actuator]
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState [mode]
2016-09-30 18:52:33 caching: LivingroomHeat-measured-temp: 19.9
[30/09/2016, 18:52:33] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] value2homekit: { ok: 0 }
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'BATTERY_LEVEL_NORMAL', '1': 'BATTERY_LEVEL_LOW' }
2016-09-30 18:52:33 caching: LivingroomHeat-battery: ok
[30/09/2016, 18:52:33] [FHEM] LivingroomHeat-battery values: value ok mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: StatusLowBattery: 0 (as number; means BATTERY_LEVEL_NORMAL; from 'ok')
2016-09-30 18:52:33 caching: LivingroomHeat-desired-temp: 14.0
[30/09/2016, 18:52:33] [FHEM] caching: TargetTemperature: 14 (as number; from '14.0')
2016-09-30 18:52:33 caching: LivingroomHeat-actuator: 0%
[30/09/2016, 18:52:33] [FHEM] caching: Custom Actuation: 0 (as number; from '0%')
[30/09/2016, 18:52:33] [FHEM] value2homekit_re: [ { re: '^auto', to: 3 },
{ re: '^holiday_short', to: 0 },
{ re: '.*', to: 1 } ]
[30/09/2016, 18:52:33] [FHEM] homekit2name: { '0': 'OFF', '1': 'HEAT', '3': 'AUTO' }
[30/09/2016, 18:52:33] [FHEM] homekit2cmd: { '0': 'mode holiday_short',
'1': 'mode manual',
'2': 'mode manual',
'3': 'mode auto' }
2016-09-30 18:52:33 caching: LivingroomHeat-mode: auto
[30/09/2016, 18:52:33] [FHEM] LivingroomHeat-mode values: value auto mapped to 3
[30/09/2016, 18:52:33] [FHEM] caching: TargetHeatingCoolingState: 3 (as number; means AUTO; from 'auto')
[30/09/2016, 18:52:33] [FHEM] homebridgeMapping: On=state
[30/09/2016, 18:52:33] [FHEM] mappings for TRX_AC_002d4f3a03: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] TRX_AC_002d4f3a03 is switch
[30/09/2016, 18:52:33] [FHEM] TRX_AC_002d4f3a03 has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: TRX_AC_002d4f3a03-state: off
[30/09/2016, 18:52:33] [FHEM] TRX_AC_002d4f3a03-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] mappings for bathroomlamp: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] bathroomlamp is switch
[30/09/2016, 18:52:33] [FHEM] bathroomlamp has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: bathroomlamp-state: on
[30/09/2016, 18:52:33] [FHEM] bathroomlamp-state valueOn/valueOff: value on mapped to 1
[30/09/2016, 18:52:33] [FHEM] caching: On: true (as boolean; from 'on')
[30/09/2016, 18:52:33] [FHEM] mappings for bathroomstereo: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] bathroomstereo is switch
[30/09/2016, 18:52:33] [FHEM] bathroomstereo has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: bathroomstereo-state: off
[30/09/2016, 18:52:33] [FHEM] bathroomstereo-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] mappings for counterlights: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] counterlights is switch
[30/09/2016, 18:52:33] [FHEM] counterlights has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: counterlights-state: off
[30/09/2016, 18:52:33] [FHEM] counterlights-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] mappings for house: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] house is switch
[30/09/2016, 18:52:33] [FHEM] house has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: house-state: off
[30/09/2016, 18:52:33] [FHEM] house-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] mappings for kitchenlamp: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] kitchenlamp is switch
[30/09/2016, 18:52:33] [FHEM] kitchenlamp has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: kitchenlamp-state: off
[30/09/2016, 18:52:33] [FHEM] kitchenlamp-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] homebridgeMapping: On=switch
[30/09/2016, 18:52:33] [FHEM] mappings for mqtt_sonoff1: { On: { reading: 'switch', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff1 is switch
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff1 has
[30/09/2016, 18:52:33] [FHEM] On [switch;on,off]
2016-09-30 18:52:33 caching: mqtt_sonoff1-switch: on
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff1-switch valueOn/valueOff: value on mapped to 1
[30/09/2016, 18:52:33] [FHEM] caching: On: true (as boolean; from 'on')
[30/09/2016, 18:52:33] [FHEM] homebridgeMapping: On=switch
[30/09/2016, 18:52:33] [FHEM] mappings for mqtt_sonoff2: { On: { reading: 'switch', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff2 is switch
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff2 has
[30/09/2016, 18:52:33] [FHEM] On [switch;on,off]
2016-09-30 18:52:33 caching: mqtt_sonoff2-switch: off
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff2-switch valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] homebridgeMapping: On=switch
[30/09/2016, 18:52:33] [FHEM] mappings for mqtt_sonoff3: { On: { reading: 'switch', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff3 is switch
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff3 has
[30/09/2016, 18:52:33] [FHEM] On [switch;on,off]
2016-09-30 18:52:33 caching: mqtt_sonoff3-switch: off
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff3-switch valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] homebridgeMapping: On=switch
[30/09/2016, 18:52:33] [FHEM] mappings for mqtt_sonoff4: { On: { reading: 'switch', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff4 is switch
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff4 has
[30/09/2016, 18:52:33] [FHEM] On [switch;on,off]
2016-09-30 18:52:33 caching: mqtt_sonoff4-switch: off
[30/09/2016, 18:52:33] [FHEM] mqtt_sonoff4-switch valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] mappings for tvhifi: { On: { reading: 'state', valueOff: 'off', cmdOn: 'on', cmdOff: 'off' } }
[30/09/2016, 18:52:33] [FHEM] tvhifi is switch
[30/09/2016, 18:52:33] [FHEM] tvhifi has
[30/09/2016, 18:52:33] [FHEM] On [state;on,off]
2016-09-30 18:52:33 caching: tvhifi-state: off
[30/09/2016, 18:52:33] [FHEM] tvhifi-state valueOn/valueOff: value off mapped to 0
[30/09/2016, 18:52:33] [FHEM] caching: On: false (as boolean; from 'off')
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'BathroomHeat'...
[30/09/2016, 18:52:33] [FHEM] creating services for BathroomHeat
[30/09/2016, 18:52:33] [FHEM] information service for BathroomHeat
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for BathroomHeat
[30/09/2016, 18:52:33] [FHEM] Thermostat service for BathroomHeat
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature characteristic for BathroomHeat:measured-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 19.3 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: -30,
maxValue: 100,
minStep: 0.1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery characteristic for BathroomHeat:battery
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number; means BATTERY_LEVEL_NORMAL)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetTemperature characteristic for BathroomHeat:desired-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 13 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: 6,
maxValue: 30,
minStep: 0.5,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Custom Actuation characteristic for BathroomHeat:actuator
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: 'percentage',
minValue: 0,
maxValue: 100,
minStep: 1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState characteristic for BathroomHeat:mode
[30/09/2016, 18:52:33] [FHEM] initial value is: 3 (number; means AUTO)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'Bedroom1Heat'...
[30/09/2016, 18:52:33] [FHEM] creating services for Bedroom1Heat
[30/09/2016, 18:52:33] [FHEM] information service for Bedroom1Heat
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for Bedroom1Heat
[30/09/2016, 18:52:33] [FHEM] Thermostat service for Bedroom1Heat
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature characteristic for Bedroom1Heat:measured-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 18.3 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: -30,
maxValue: 100,
minStep: 0.1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery characteristic for Bedroom1Heat:battery
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number; means BATTERY_LEVEL_NORMAL)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetTemperature characteristic for Bedroom1Heat:desired-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 10 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: 6,
maxValue: 30,
minStep: 0.5,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Custom Actuation characteristic for Bedroom1Heat:actuator
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: 'percentage',
minValue: 0,
maxValue: 100,
minStep: 1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState characteristic for Bedroom1Heat:mode
[30/09/2016, 18:52:33] [FHEM] initial value is: 3 (number; means AUTO)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'Bedroom2Heat'...
[30/09/2016, 18:52:33] [FHEM] creating services for Bedroom2Heat
[30/09/2016, 18:52:33] [FHEM] information service for Bedroom2Heat
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for Bedroom2Heat
[30/09/2016, 18:52:33] [FHEM] Thermostat service for Bedroom2Heat
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature characteristic for Bedroom2Heat:measured-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 19.4 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: -30,
maxValue: 100,
minStep: 0.1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery characteristic for Bedroom2Heat:battery
[30/09/2016, 18:52:33] [FHEM] initial value is: 1 (number; means BATTERY_LEVEL_LOW)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetTemperature characteristic for Bedroom2Heat:desired-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 21 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: 6,
maxValue: 30,
minStep: 0.5,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Custom Actuation characteristic for Bedroom2Heat:actuator
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: 'percentage',
minValue: 0,
maxValue: 100,
minStep: 1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState characteristic for Bedroom2Heat:mode
[30/09/2016, 18:52:33] [FHEM] initial value is: 3 (number; means AUTO)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'KitchenHeat'...
[30/09/2016, 18:52:33] [FHEM] creating services for KitchenHeat
[30/09/2016, 18:52:33] [FHEM] information service for KitchenHeat
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for KitchenHeat
[30/09/2016, 18:52:33] [FHEM] Thermostat service for KitchenHeat
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature characteristic for KitchenHeat:measured-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 20.2 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: -30,
maxValue: 100,
minStep: 0.1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery characteristic for KitchenHeat:battery
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number; means BATTERY_LEVEL_NORMAL)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetTemperature characteristic for KitchenHeat:desired-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 6 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: 6,
maxValue: 30,
minStep: 0.5,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Custom Actuation characteristic for KitchenHeat:actuator
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: 'percentage',
minValue: 0,
maxValue: 100,
minStep: 1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState characteristic for KitchenHeat:mode
[30/09/2016, 18:52:33] [FHEM] initial value is: 3 (number; means AUTO)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'LivingroomHeat'...
[30/09/2016, 18:52:33] [FHEM] creating services for LivingroomHeat
[30/09/2016, 18:52:33] [FHEM] information service for LivingroomHeat
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for LivingroomHeat
[30/09/2016, 18:52:33] [FHEM] Thermostat service for LivingroomHeat
[30/09/2016, 18:52:33] [FHEM] CurrentTemperature characteristic for LivingroomHeat:measured-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 19.9 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: -30,
maxValue: 100,
minStep: 0.1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] StatusLowBattery characteristic for LivingroomHeat:battery
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number; means BATTERY_LEVEL_NORMAL)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetTemperature characteristic for LivingroomHeat:desired-temp
[30/09/2016, 18:52:33] [FHEM] initial value is: 14 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'float',
unit: 'celsius',
minValue: 6,
maxValue: 30,
minStep: 0.5,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Custom Actuation characteristic for LivingroomHeat:actuator
[30/09/2016, 18:52:33] [FHEM] initial value is: 0 (number)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: 'percentage',
minValue: 0,
maxValue: 100,
minStep: 1,
perms: [ 'pr', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] TargetHeatingCoolingState characteristic for LivingroomHeat:mode
[30/09/2016, 18:52:33] [FHEM] initial value is: 3 (number; means AUTO)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'uint8',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'TRX_AC_002d4f3a03'...
[30/09/2016, 18:52:33] [FHEM] creating services for TRX_AC_002d4f3a03
[30/09/2016, 18:52:33] [FHEM] information service for TRX_AC_002d4f3a03
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for TRX_AC_002d4f3a03
[30/09/2016, 18:52:33] [FHEM] Switch service for TRX_AC_002d4f3a03
[30/09/2016, 18:52:33] [FHEM] On characteristic for TRX_AC_002d4f3a03:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'bathroomlamp'...
[30/09/2016, 18:52:33] [FHEM] creating services for bathroomlamp
[30/09/2016, 18:52:33] [FHEM] information service for bathroomlamp
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for bathroomlamp
[30/09/2016, 18:52:33] [FHEM] Switch service for bathroomlamp
[30/09/2016, 18:52:33] [FHEM] On characteristic for bathroomlamp:state
[30/09/2016, 18:52:33] [FHEM] initial value is: true (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'bathroomstereo'...
[30/09/2016, 18:52:33] [FHEM] creating services for bathroomstereo
[30/09/2016, 18:52:33] [FHEM] information service for bathroomstereo
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for bathroomstereo
[30/09/2016, 18:52:33] [FHEM] Switch service for bathroomstereo
[30/09/2016, 18:52:33] [FHEM] On characteristic for bathroomstereo:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'counterlights'...
[30/09/2016, 18:52:33] [FHEM] creating services for counterlights
[30/09/2016, 18:52:33] [FHEM] information service for counterlights
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for counterlights
[30/09/2016, 18:52:33] [FHEM] Switch service for counterlights
[30/09/2016, 18:52:33] [FHEM] On characteristic for counterlights:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'house'...
[30/09/2016, 18:52:33] [FHEM] creating services for house
[30/09/2016, 18:52:33] [FHEM] information service for house
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for house
[30/09/2016, 18:52:33] [FHEM] Switch service for house
[30/09/2016, 18:52:33] [FHEM] On characteristic for house:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'kitchenlamp'...
[30/09/2016, 18:52:33] [FHEM] creating services for kitchenlamp
[30/09/2016, 18:52:33] [FHEM] information service for kitchenlamp
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for kitchenlamp
[30/09/2016, 18:52:33] [FHEM] Switch service for kitchenlamp
[30/09/2016, 18:52:33] [FHEM] On characteristic for kitchenlamp:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'mqtt_sonoff1'...
[30/09/2016, 18:52:33] [FHEM] creating services for mqtt_sonoff1
[30/09/2016, 18:52:33] [FHEM] information service for mqtt_sonoff1
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for mqtt_sonoff1
[30/09/2016, 18:52:33] [FHEM] Switch service for mqtt_sonoff1
[30/09/2016, 18:52:33] [FHEM] On characteristic for mqtt_sonoff1:switch
[30/09/2016, 18:52:33] [FHEM] initial value is: true (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'mqtt_sonoff2'...
[30/09/2016, 18:52:33] [FHEM] creating services for mqtt_sonoff2
[30/09/2016, 18:52:33] [FHEM] information service for mqtt_sonoff2
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for mqtt_sonoff2
[30/09/2016, 18:52:33] [FHEM] Switch service for mqtt_sonoff2
[30/09/2016, 18:52:33] [FHEM] On characteristic for mqtt_sonoff2:switch
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'mqtt_sonoff3'...
[30/09/2016, 18:52:33] [FHEM] creating services for mqtt_sonoff3
[30/09/2016, 18:52:33] [FHEM] information service for mqtt_sonoff3
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for mqtt_sonoff3
[30/09/2016, 18:52:33] [FHEM] Switch service for mqtt_sonoff3
[30/09/2016, 18:52:33] [FHEM] On characteristic for mqtt_sonoff3:switch
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'mqtt_sonoff4'...
[30/09/2016, 18:52:33] [FHEM] creating services for mqtt_sonoff4
[30/09/2016, 18:52:33] [FHEM] information service for mqtt_sonoff4
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for mqtt_sonoff4
[30/09/2016, 18:52:33] [FHEM] Switch service for mqtt_sonoff4
[30/09/2016, 18:52:33] [FHEM] On characteristic for mqtt_sonoff4:switch
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
[30/09/2016, 18:52:33] [FHEM] Initializing platform accessory 'tvhifi'...
[30/09/2016, 18:52:33] [FHEM] creating services for tvhifi
[30/09/2016, 18:52:33] [FHEM] information service for tvhifi
[30/09/2016, 18:52:33] [FHEM] manufacturer, model and serial number characteristics for tvhifi
[30/09/2016, 18:52:33] [FHEM] Switch service for tvhifi
[30/09/2016, 18:52:33] [FHEM] On characteristic for tvhifi:state
[30/09/2016, 18:52:33] [FHEM] initial value is: false (boolean)
[30/09/2016, 18:52:33] [FHEM] props: { format: 'bool',
unit: null,
minValue: null,
maxValue: null,
minStep: null,
perms: [ 'pr', 'pw', 'ev' ] }
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
[30/09/2016, 18:52:33] Homebridge is running on port 51826.
from homebridge-fhem.
i have no idea at the moment.
with the enabled log messages you do see the events from the mqtt devices on the homebridge console but not from the trx device. right?
do you see anything if you use
setreading TRX_AC_002d4f3a03 state off
or
setreading TRX_AC_002d4f3a03 state on
respectively in fhem ?
from homebridge-fhem.
ok.. getting somewhere... those command produce output in homebridge debug...
[01/10/2016, 12:39:43] Homebridge is running on port 51826.
2016-10-01 12:39:54 caching: TRX_AC_002d4f3a03-state: off
[01/10/2016, 12:39:54] [FHEM] TRX_AC_002d4f3a03-state valueOn/valueOff: value off mapped to 0
[01/10/2016, 12:39:54] [FHEM] caching: On: false (as boolean; from 'off')
2016-10-01 12:40:05 caching: TRX_AC_002d4f3a03-state: on
[01/10/2016, 12:40:05] [FHEM] TRX_AC_002d4f3a03-state valueOn/valueOff: value on mapped to 1
[01/10/2016, 12:40:05] [FHEM] caching: On: true (as boolean; from 'on')
2016-10-01 12:41:12 caching: TRX_AC_002d4f3a03-state: off
[01/10/2016, 12:41:12] [FHEM] TRX_AC_002d4f3a03-state valueOn/valueOff: value off mapped to 0
[01/10/2016, 12:41:12] [FHEM] caching: On: false (as boolean; from 'off')
2016-10-01 12:41:17 caching: TRX_AC_002d4f3a03-state: on
[01/10/2016, 12:41:17] [FHEM] TRX_AC_002d4f3a03-state valueOn/valueOff: value on mapped to 1
[01/10/2016, 12:41:17] [FHEM] caching: On: true (as boolean; from 'on')
but they do not change the light on/off
does this mean there is a bug in this device in fhem... seems like the on/off is not generating the right events / reading updates..
from homebridge-fhem.
if setreading works then the homebridge side and the communication from fhem woks.
there is something strange with the trx device. but i have no idea what.
could you please try to remove line 526 in 45_TRX.pm? then restart fhem. does it make a difference?
from homebridge-fhem.
ok tried that. no difference.
from homebridge-fhem.
hmmm. then i have no idea whats wrong. if the events are in the event viewer and fhemweb ist automatically updating its icons and setreading works to update the value in homekit then it should just work...
with the homebridge changes from above that enable more logging do you see the other events? only the ones from the trx device are missing?
from homebridge-fhem.
that is correct. events for structure, my custom MQTT switches all work fine. just TRX...
from homebridge-fhem.
do you also see all of them in the hombridge console output?
from homebridge-fhem.
yes. if i toggle any of them (except TRX...), i get output in home bridge console. Thats the slightly weird thing... if the TRX_switch is part of a structure, then it triggers the structure change and home bridge-fhem picks that up! but not the actual event / change of the switch state. The state of my thermostats is propagated to home bridge...) just not the TRX switches...
from homebridge-fhem.
this is very strange. is there any change if you remove the trx device from the structure?
from homebridge-fhem.
nope removed everything. created new device with nothing. added homekit room. works... home bridge-fhem to fhem... no alerts back to fhem...
wonder if its worth getting the fhem guys to take a look. seems like some events are not working correctly for these devices...
from homebridge-fhem.
sorry but i have no idea what the problem is. as i don't have a trx i can't help you much with debugging.
maybe you can try a readingsProxy in front of the trx device.
from homebridge-fhem.
ok. i've submitted an issue on fhem forum! I think there is something up with fhem. even using a freshly update fhem on the rPi which directly interfaces with the RFXCOM device, events are not propagated to homebridge-fhem!
from homebridge-fhem.
Can you try something for me. I've tried creating a dummy switch and it is also not working. These are the defines.. I started simple and then added things, but in theory it should work just like a switch, except that it does not.
define bathroomlampdummy dummy
attr bathroomlampdummy genericDeviceType switch
attr bathroomlampdummy homebridgeMapping On=switch
attr bathroomlampdummy room Bathroom,Homekit
attr bathroomlampdummy setList on off
from homebridge-fhem.
your switch is probably not working because your switch has no switch reading. you have to use state or readingList switch to configure the dummy to use the switch reading. you should also set the switch to on or off at least once.
for a simple dummy switch you just need
define switch dummy
attr switch setList on off
set switch off
after that you can start homebridge and if you change the switch state in fhem with set switch on or set switch off this will be visible in homekit.
from homebridge-fhem.
ok so that fixed it. setting up two notifies and a dummy works! bit of a long winded way of getting TRX _LIGHT to work!
from homebridge-fhem.
just reopen if there is something to do in homebridge-fhem.
from homebridge-fhem.
hi justme,
i'm experiencing similar issues here.
I have fhem and homebridge running on a RasPi.
In fhem i use the "pilight" module to control some radio controlled sockets.
Like sticilface, the status is not updating accordingly. When turning the sockets on or off through iOS Home App, everything works. But when closing the app or turning them on / off through fhem the status is not updated / reported to homebridge.
Funny thing: when using a dummy switch, this dummy switch is working perfectly fine and the status is updated correctly. i can even turn the socket on / off through fhem and i can immediately see the correct status in Home app.
Any ideas?
Thanks!
from homebridge-fhem.
check in the event monitor if there are events and check in the device detail view in the browser if the readings update automatically if you with the device in a second window.
if not -> it is a bug in the device module. it probably uses direct access to fhem internals instead of the readings update functions.
if the readings in the detail window do update automatically without page reload -> we have to dig deeper.
from homebridge-fhem.
i never really got to the bottom of this. just kind of left it, but it is still an issue..
from homebridge-fhem.
very good way of troubleshooting. thank you very much for teaching me.
yes, i could see the events in the event monitor. But the status did not change in device detail view. so you assumption seems to be right. the module itself seems to misbehave.
but good news is, with this explanation, i now understood what @sticilface meant with the dummy and two notifies.
i managed to do the same and now have a working config. this is more a workaround than a fix, but i'm happy with it!
@justme-1968 thank you very much for your help and also for homebridge-fhem! :)
from homebridge-fhem.
I've come back to home bridge-fhem after a detour with alexa that i've got working. luckily with alexa it is all one way so the state does not get updated. @justme-1968 given all the chat that we've had, would you be able to sum the issue up to maybe raise to the fhem team. I think our conclusion is that there is an underlying issue with the fhem module? would you agree? maybe we can raise it with them on the forum?
from homebridge-fhem.
there is a know problem with the TRX module. but as far as i know it is currently unmaintained.
do you have an account in the fhem forum? then it would be best if you could post your problem there.
by the way: if you use alexa-fhem then you can ask alexa about the state. so it is not one way only :)
from homebridge-fhem.
I think i've got to the bottom of it. The cached value is always off
from homebridge-fhem.
please show the homebridgeMaping for the device.
it looks like the event data is not parsed correctly or the mapping is wrong
from homebridge-fhem.
Related Issues (20)
- Plugin slows down Homebridge 1.3 HOT 1
- warning from the characteristic 'Hue' & 'on' HOT 5
- warning from the characteristic 'Saturation' HOT 17
- Installation procedure failure (version 0.5.29) HOT 2
- Configuration gets lost after docker container restart HOT 7
- Homebridge-fhem Problem mit fhem Zugriff. HOT 4
- No reconnect after FHEM Server restart HOT 2
- homebridge-fhem with Homebridge 1.3.x does not work (for me) HOT 4
- Thermostat's dont't work anymore HOT 3
- longpoll error HOT 13
- No response with Mac OS Monterey HOT 1
- Status der Geräte updated nach einiger Zeit nicht mehr HOT 2
- This plugin slows down Homebridge. The read handler for the characteristic 'Current Relative Humidity' was slow to respond HOT 1
- Homebridge sometimes does not start with homebridge-fhem plugin active HOT 8
- Plugin settings in Homebridge UI overwrite manually created configuration HOT 3
- Option to reduce log output HOT 1
- Device state update is not working HOT 14
- For ProgrammableSwitchEvent the nocache=1 dosent work HOT 6
- History Type Energy not working HOT 1
- HMCCU-Geräte werden bei best. Konstellationen vergessen und später als neue Geräte wieder hinzugefügt HOT 1
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.
from homebridge-fhem.