Fibaro is not able to get FHEM acting

Begonnen von emnagel, 08 März 2014, 21:27:52

Vorheriges Thema - Nächstes Thema

emnagel

Hi,

I am trying to build a virtual device in Fibaro HC Lite connecting to FHEM, but on the FHEM system I do not see any response / action.

When I use http://10.0.0.1:8083/fhem?cmd.Lamp=set%20lamp%20on direct in the browser the lamp is turned on directly. But once the code is in a Fibaro virtual device there is no response and no line in the log file of FHEM. Doing the same direct on a HTTP server I do see a GET in the access.log. For me this means the logic from Fibaro is working.

Any clues how to fix?

thx in advance,
Erik

micomat

Hi,

is the set lamp on command working from the fhem-command-line?

Markus
Synology DS218+ with fhem+iobroker in docker, 2x RasPi w. ser2net, CUL433+868, IT, EGPM2LAN, THZ/LWZ, FB_Callmonitor, HMS100TF, Homematic, 2x TX3-TH, Pushover, USB-IR-SML-Head, SONOS, GHoma, MBus, KLF200

rudolfkoenig

Is the FHEMWEB instance defined with global
Set the verbose level of the FHEMWEB instance to 5, and check the FHEM logfile.
Can you tell me the point in switching ZWave lamps from Fibaro HC Lite via FHEM?

emnagel

2014.03.09 22:20:01 4: Connection accepted from FHEMWEB:10.0.0.x:43390
2014.03.09 22:20:01 4: Connection closed for FHEMWEB:10.0.0.x:43390


The set command in command-line is working.

The point of swithing the light is because FS20 is not supported by Fibaro and all my other devices (some light and heating) are handled in this system.

cheers, Erik

emnagel

Solved:

2014.03.09 22:31:04 4: Connection accepted from FHEMWEB:10.0.0.63:44172
2014.03.09 22:31:04 4: HTTP FHEMWEB:10.0.0.x:44172 GET /fhem?cmd.Lamp=set%20lamp%20on
2014.03.09 22:31:04 5: Cmd: >set lamp on<
2014.03.09 22:31:04 3: FS20 set lamp on
2014.03.09 22:31:04 5: CUL_0 sending F2a046011
2014.03.09 22:31:04 5: SW: F2a046011
2014.03.09 22:31:04 5: Triggering lamp (1 changes)
2014.03.09 22:31:04 5: Notify loop for lamp on
2014.03.09 22:31:04 4: Connection closed for FHEMWEB:10.0.0.x:44172


Added HTTP/1.10x0D0x0A0x0D0x0A to the string and it is working..