attr alexa stateFormat alexaFHEM
attr alexa devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
root@demucvmkp01con:/docker/has# docker logs has_alexa-fhem_1
[2019-1-4 00:00:04] using /root/.alexa/config.json
[2019-1-4 00:00:04] ---
[2019-1-4 00:00:04] this is alexa-fhem 0.4.7
[2019-1-4 00:00:04] Fetching FHEM devices...
[2019-1-4 00:00:04] [FHEM] starting longpoll: http://fhem:9093/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1546560004730
[2019-1-4 00:00:04] Server listening on: http://:::3000
[2019-1-4 00:00:04] requesting messaging token
[2019-1-4 00:00:04] [FHEM] Checking devices and attributes...
[2019-1-4 00:00:04] [FHEM] executing: http://fhem:9093/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2019-1-4 00:00:04] [FHEM] executing: http://fhem:9093/fhem?cmd=jsonlist2%20TYPE=alexa&XHR=1
[2019-1-4 00:00:04] [FHEM] Fetching FHEM devices...
[2019-1-4 00:00:04] [FHEM] fetching: http://fhem:9093/fhem?cmd=jsonlist2%20room=Alexa&XHR=1
[2019-1-4 00:00:04] [FHEM] alexa device is Alexa
[2019-1-4 00:00:04] [FHEM] Alexa is switch
[2019-1-4 00:00:04] [FHEM] Alexa has
[2019-1-4 00:00:04] [FHEM] homebridgeMapping: #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
[2019-1-4 00:00:04] [FHEM] executing: http://fhem:9093/fhem?cmd=%7B$defs%7BAlexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;%7B$defs%7BAlexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20=%20%220.4.7%22%7D;%7B$defs%7BAlexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-4 00:00:04] [FHEM] executing: http://fhem:9093/fhem?cmd=%7B$defs%7BAlexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;list%20Alexa%20.eventToken;%7B$defs%7BAlexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-4 00:00:04] [FHEM] got: 6 results
[2019-1-4 00:00:04] [FHEM] HM_LC_BALC_SunBlind is blind
[2019-1-4 00:00:04] [FHEM] HM_LC_BALC_SunBlind has
[2019-1-4 00:00:04] [FHEM] PositionState [direction]
[2019-1-4 00:00:04] [FHEM] CurrentPosition [pct]
[2019-1-4 00:00:04] [FHEM] TargetPosition [pct]
[2019-1-4 00:00:04] [FHEM] { reading: 'direction',
values:
[ '/^opening/:INCREASING',
'/^closing/:DECREASING',
'/.*/:STOPPED' ],
device: 'HM_LC_BALC_SunBlind',
informId: 'HM_LC_BALC_SunBlind-direction',
characteristic_type: 'PositionState',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: {},
value2homekit_re:
[ { re: '^opening', to: 'INCREASING' },
{ re: '^closing', to: 'DECREASING' },
{ re: '.*', to: 'STOPPED' } ] }
2019-01-04 00:00:04 caching: HM_LC_BALC_SunBlind-direction: stop
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
device: 'HM_LC_BALC_SunBlind',
informId: 'HM_LC_BALC_SunBlind-pct',
characteristic_type: 'CurrentPosition',
log:
{ [Function: bound ]
2019-01-04 00:00:04 caching: HM_LC_BALC_SunBlind-pct: 0
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
cmd: 'pct',
delay: true,
device: 'HM_LC_BALC_SunBlind',
informId: 'HM_LC_BALC_SunBlind-pct',
characteristic_type: 'TargetPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] HM_LC_BR_Shutter is blind
[2019-1-4 00:00:04] [FHEM] HM_LC_BR_Shutter has
[2019-1-4 00:00:04] [FHEM] PositionState [direction]
[2019-1-4 00:00:04] [FHEM] CurrentPosition [pct]
[2019-1-4 00:00:04] [FHEM] TargetPosition [pct]
[2019-1-4 00:00:04] [FHEM] { reading: 'direction',
values:
[ '/^opening/:INCREASING',
'/^closing/:DECREASING',
'/.*/:STOPPED' ],
device: 'HM_LC_BR_Shutter',
informId: 'HM_LC_BR_Shutter-direction',
characteristic_type: 'PositionState',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: {},
value2homekit_re:
[ { re: '^opening', to: 'INCREASING' },
{ re: '^closing', to: 'DECREASING' },
{ re: '.*', to: 'STOPPED' } ] }
2019-01-04 00:00:04 caching: HM_LC_BR_Shutter-direction: stop
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
device: 'HM_LC_BR_Shutter',
informId: 'HM_LC_BR_Shutter-pct',
characteristic_type: 'CurrentPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: HM_LC_BR_Shutter-pct: 40
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
cmd: 'pct',
delay: true,
device: 'HM_LC_BR_Shutter',
informId: 'HM_LC_BR_Shutter-pct',
characteristic_type: 'TargetPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] HM_LC_LR_ShutterWest is blind
[2019-1-4 00:00:04] [FHEM] HM_LC_LR_ShutterWest has
[2019-1-4 00:00:04] [FHEM] PositionState [direction]
[2019-1-4 00:00:04] [FHEM] CurrentPosition [pct]
[2019-1-4 00:00:04] [FHEM] TargetPosition [pct]
[2019-1-4 00:00:04] [FHEM] { reading: 'direction',
values:
[ '/^opening/:INCREASING',
'/^closing/:DECREASING',
'/.*/:STOPPED' ],
device: 'HM_LC_LR_ShutterWest',
informId: 'HM_LC_LR_ShutterWest-direction',
characteristic_type: 'PositionState',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: {},
value2homekit_re:
[ { re: '^opening', to: 'INCREASING' },
{ re: '^closing', to: 'DECREASING' },
{ re: '.*', to: 'STOPPED' } ] }
2019-01-04 00:00:04 caching: HM_LC_LR_ShutterWest-direction: stop
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
device: 'HM_LC_LR_ShutterWest',
informId: 'HM_LC_LR_ShutterWest-pct',
characteristic_type: 'CurrentPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: HM_LC_LR_ShutterWest-pct: 40
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
cmd: 'pct',
delay: true,
device: 'HM_LC_LR_ShutterWest',
informId: 'HM_LC_LR_ShutterWest-pct',
characteristic_type: 'TargetPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] homebridgeMapping: clear CurrentPosition=pct TargetPosition=CurrentPosition,cmd=pct
[2019-1-4 00:00:04] [FHEM] HmIP_BROLL_LR_ShutterSouth is blind
[2019-1-4 00:00:04] [FHEM] HmIP_BROLL_LR_ShutterSouth has
[2019-1-4 00:00:04] [FHEM] CurrentPosition [pct]
[2019-1-4 00:00:04] [FHEM] TargetPosition [pct]
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
device: 'HmIP_BROLL_LR_ShutterSouth',
informId: 'HmIP_BROLL_LR_ShutterSouth-pct',
characteristic_type: 'CurrentPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: HmIP_BROLL_LR_ShutterSouth-pct: 40
[2019-1-4 00:00:04] [FHEM] { reading: 'pct',
cmd: 'pct',
device: 'HmIP_BROLL_LR_ShutterSouth',
informId: 'HmIP_BROLL_LR_ShutterSouth-pct',
characteristic_type: 'TargetPosition',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] homebridgeMapping: StatusActive=Activity,values=/^alive/:1;/^dead/:0 CurrentTemperature=temperature,minValue=-30,subtype=Outdoor HumiditySensor=humidity,minValue=0,subtype=Outdoor CurrentAmbientLightLevel=luminosity,factor=1,subtype=Outdoor
[2019-1-4 00:00:04] [FHEM] WeatherStation is thermometer
[2019-1-4 00:00:04] [FHEM] WeatherStation has
[2019-1-4 00:00:04] [FHEM] Custom Energy [energy]
[2019-1-4 00:00:04] [FHEM] CurrentAmbientLightLevel [luminosity]
[2019-1-4 00:00:04] [FHEM] CurrentTemperature [temperature]
[2019-1-4 00:00:04] [FHEM] CurrentRelativeHumidity [humidity]
[2019-1-4 00:00:04] [FHEM] Custom AirPressure [pressure]
[2019-1-4 00:00:04] [FHEM] StatusActive [Activity]
[2019-1-4 00:00:04] [FHEM] HumiditySensor [humidity]
[2019-1-4 00:00:04] [FHEM] { name: 'Energy',
reading: 'energy',
format: 'FLOAT',
factor: 1,
device: 'WeatherStation',
informId: 'WeatherStation-energy',
characteristic_type: 'E863F10C-079E-48FF-8F27-9C2605A29F52',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: WeatherStation-energy: 5729.06805553911
[2019-1-4 00:00:04] [FHEM] caching: Custom Energy: 5729.06805553911 (as number; from '5729.06805553911')
[2019-1-4 00:00:04] [FHEM] { reading: 'luminosity',
minValue: 0,
factor: '1',
subtype: 'Outdoor',
device: 'WeatherStation',
informId: 'WeatherStation-luminosity',
characteristic_type: 'CurrentAmbientLightLevel',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: WeatherStation-luminosity: 0.0
[2019-1-4 00:00:04] [FHEM] { reading: 'temperature',
minValue: -30,
subtype: 'Outdoor',
device: 'WeatherStation',
informId: 'WeatherStation-temperature',
characteristic_type: 'CurrentTemperature',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: WeatherStation-temperature: 5.9
[2019-1-4 00:00:04] [FHEM] { reading: 'humidity',
device: 'WeatherStation',
informId: 'WeatherStation-humidity',
characteristic_type: 'CurrentRelativeHumidity',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: WeatherStation-humidity: 55
[2019-1-4 00:00:04] [FHEM] { name: 'AirPressure',
reading: 'pressure',
format: 'UINT16',
factor: 1,
device: 'WeatherStation',
informId: 'WeatherStation-pressure',
characteristic_type: 'E863F10F-079E-48FF-8F27-9C2605A29F52',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
2019-01-04 00:00:04 caching: WeatherStation-pressure: 1019.5
[2019-1-4 00:00:04] [FHEM] caching: Custom AirPressure: 1020 (as number; from '1019.5')
[2019-1-4 00:00:04] [FHEM] { reading: 'Activity',
values: [ '/^alive/:1', '/^dead/:0' ],
device: 'WeatherStation',
informId: 'WeatherStation-Activity',
characteristic_type: 'StatusActive',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: {},
value2homekit_re: [ { re: '^alive', to: '1' }, { re: '^dead', to: '0' } ] }
2019-01-04 00:00:04 caching: WeatherStation-Activity: dead
[2019-1-4 00:00:04] [FHEM] { reading: 'humidity',
minValue: 0,
subtype: 'Outdoor',
device: 'WeatherStation',
informId: 'WeatherStation-humidity',
characteristic_type: 'HumiditySensor',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' } }
[2019-1-4 00:00:04] [FHEM] homebridgeMapping: SecuritySystemCurrentState=state,values=/home|awoken/:0;;absent:1;;/asleep|gotosleep/:2;;gone:3 SecuritySystemTargetState=SecuritySystemCurrentState,cmds=0:state+home;;1:state+absent;;2:state+gotosleep;;3:state+gone,delay=1
[2019-1-4 00:00:04] [FHEM] rr_Julian is security
[2019-1-4 00:00:04] [FHEM] rr_Julian has
[2019-1-4 00:00:04] [FHEM] OccupancyDetected [presence]
[2019-1-4 00:00:04] [FHEM] SecuritySystemCurrentState [state]
[2019-1-4 00:00:04] [FHEM] SecuritySystemTargetState [state]
[2019-1-4 00:00:04] [FHEM] { reading: 'presence',
values: [ 'present:OCCUPANCY_DETECTED', '/.*/:OCCUPANCY_NOT_DETECTED' ],
device: 'rr_Julian',
informId: 'rr_Julian-presence',
characteristic_type: 'OccupancyDetected',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: { present: 'OCCUPANCY_DETECTED' },
value2homekit_re: [ { re: '.*', to: 'OCCUPANCY_NOT_DETECTED' } ] }
2019-01-04 00:00:04 caching: rr_Julian-presence: present
[2019-1-4 00:00:04] [FHEM] { reading: 'state',
values:
[ '/home|awoken/:0',
'',
'absent:1',
'',
'/asleep|gotosleep/:2',
'',
'gone:3' ],
device: 'rr_Julian',
informId: 'rr_Julian-state',
characteristic_type: 'SecuritySystemCurrentState',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: { '': '', absent: '1', gone: '3' },
value2homekit_re:
[ { re: 'home|awoken', to: '0' },
{ re: 'asleep|gotosleep', to: '2' } ] }
2019-01-04 00:00:04 caching: rr_Julian-state: home
[2019-1-4 00:00:04] [FHEM] { reading: 'state',
values:
[ '/home|awoken/:0',
'',
'absent:1',
'',
'/asleep|gotosleep/:2',
'',
'gone:3' ],
cmds:
[ '0:state+home',
'',
'1:state+absent',
'',
'2:state+gotosleep',
'',
'3:state+gone' ],
delay: 1,
device: 'rr_Julian',
informId: 'rr_Julian-state',
characteristic_type: 'SecuritySystemTargetState',
log:
{ [Function: bound ]
debug: [Function],
info: [Function],
warn: [Function],
error: [Function],
log: [Function],
prefix: 'FHEM' },
value2homekit: { '': '', absent: '1', gone: '3' },
value2homekit_re:
[ { re: 'home|awoken', to: '0' },
{ re: 'asleep|gotosleep', to: '2' } ],
homekit2cmd:
{ '0': 'state home',
'1': 'state absent',
'2': 'state gotosleep',
'3': 'state gone',
'': '' },
homekit2cmd_re: [] }
[2019-1-4 00:00:05] got messaging token
[2019-1-4 00:00:05] refreshing token
[2019-1-4 00:00:05] failed to refresh token: unauthorized_client: 'Not authorized for requested operation'
[2019-1-4 00:00:48] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:50] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:50] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:50] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:51] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:51] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from fd00:5:7:7::7
[2019-1-4 00:00:51] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from fd00:5:7:7::7
[2019-1-4 00:00:51] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from fd00:5:7:7::7
[2019-1-4 00:00:51] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from fd00:5:7:7::7
[2019-1-4 00:00:52] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:52] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:52] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
[2019-1-4 00:00:52] ERROR: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Server.processBody (/usr/lib/node_modules/alexa-fhem/lib/server.js:136:26)
at Server.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:148:33)
at emitNone (events.js:106:13)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9) from ::ffff:172.27.0.7
root@demucvmkp01con:/docker/has#
{
"alexa": {
"port": 3000,
"name": "Alexa",
"ssl": false,
"keyFile": "/certs/alexa-fhem.key",
"certFile": "/certs/alexa-fhem.crt",
"nat-pmp": "",
"nat-upnp": false,
"applicationId": "amzn1.ask.skill.XXXXXXXXXX",
"oauthClientID": "amzn1.application-oa2-client.YYYYYYYYY",
"permissions": {
"amzn1.ask.skill.XXXXXXXXXX": {
"client_id": "amzn1.application-oa2-client.YYYYYYYYY",
"client_secret": "ZZZZZZZZZZZZZZZZZZZZZZZZZZ"
}
}
},
"connections": [
{
"name": "FHEM",
"server": "fhem",
"port": "9093",
"webname": "fhem",
"auth": {
"user": "123",
"pass": "123"
},
"filter": "room=Alexa"
}
]
}
Zitat von: justme1968 am 04 Januar 2019, 11:35:54
@Loredo: da war noch experimenteller code für das messaging api drin. das hat amazon inzwischen aber gecancelt.
update ist draussen.
Zitat von: justme1968 am 08 Januar 2019, 18:17:06
alles gut. legacy ist bald erledigt :)
Zitat von: justme1968 am 08 Januar 2019, 18:17:06
für die fälle bei denen weder der lokale noch der remote start über das modul geht wäre es schön deine alternative zu dokumentieren. aber wirklich nur als fallback.
2019.01.10 12:59:31 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:59:10 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:58:48 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:58:27 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg019.01.10 12:59:53 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:59:31 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:59:10 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:58:48 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:58:27 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:58:20 2: Stereoanlage: second attempt to read timed out, this is an unrecoverable error.
2019.01.10 12:58:20 1: Stereoanlage: Can't connect to 192.168.XXX.XXX:XX: Connection timed out
2019.01.10 12:58:17 2: Stereoanlage: first attempt to read timed out, trying to close and open the device.
2019.01.10 12:58:06 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:57:44 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:57:18 2: AttrTemplates: got 35 entries
2019.01.10 12:57:18 1: Stereoanlage: Can't connect to 192.168.XXX.XXX:XX: 192.168.XXX.XXX: No route to host
2019.01.10 12:57:18 1: Stereoanlage: Can't connect to 192.168.XXX.XXX:XX: Illegal seek
2019.01.10 12:57:17 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:57:16 0: Server started with 222 defined entities (fhem.pl:18111/2019-01-01 perl:5.024001 os:linux user:fhem pid:1991)
2019.01.10 12:57:16 0: Featurelevel: 5.9
2019.01.10 12:57:16 1: usb create end
2019.01.10 12:57:09 1: usb create starting
2019.01.10 12:57:08 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/31_HUEDevice.pm line 1261.
2019.01.10 12:57:08 2: Bad_WEEKPROFILE(assignDev): device BA_Wandthermostat not supported or defined
2019.01.10 12:57:08 1: Including ./log/fhem.save
2019.01.10 12:57:08 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:57:08 2: MyAlexa: created default configfile: ./alexa-fhem.cfg
2019.01.10 12:57:07 2: EGPM2LAN Powerstate: 0,0,0,0
2019.01.10 12:57:02 1: Including fhem.cfg
2019.01.10 12:52:32 0: SONOS0: Das Lauschen auf der Schnittstelle wurde beendet. Prozess endet nun auch...
'(HUEDevice_devStateIcon($name),"toggle")' is an unknown bound type in regex; marked by <-- HERE in m/\b{(HUEDevice_devStateIcon($name),"toggle") <-- HERE }:([^ ]*)/ at ./FHEM/01_FHEMWEB.pm line 1769.
2019.01.10 12:41:39 2: MyAlexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.10 12:39:07 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:39:07 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:39:02 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:39:02 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:39:02 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:58 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:54 2: harmonyhub: disconnect
2019.01.10 12:38:54 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:50 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:46 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/lights: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:42 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/lights: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:38 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:34 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:30 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:26 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:21 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
2019.01.10 12:38:21 1: HUEBridge_HTTP_Request http://192.168.XXX.XXX/api/07d74638e634312ffe0e26c1d2bf5e3f/sensors/12: Can't connect to http://192.168.XXX.XXX:80
attr MyAlexa room Wohnzimmer
attr MyAlexa group Systeme
attr MyAlexa stateFormat alexaFHEM
attr MyAlexa devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stopZitat von: gvzdus am 10 Januar 2019, 16:33:05
Ich weiß nicht: Auf der Kommandozeile fühlst Du Dich nicht so wohl, oder?
Zitat von: gvzdus am 10 Januar 2019, 16:33:05
Ändern sich denn tatsächlich mit jedem neuen Schlüssel die ersten 5-6-Zeichen bis zum "-"?
ps -ef | egrep '(alexa|ssh)'
root 498 1 0 16:21 ? 00:00:00 /usr/sbin/sshd -D
root 573 498 0 16:21 ? 00:00:00 sshd: pi [priv]
pi 615 573 0 16:21 ? 00:00:00 sshd: pi@pts/0
fhem 650 594 0 16:21 ? 00:00:03 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
fhem 681 650 0 16:21 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:3000 -oServerAliveInterval=90 -p 58824 fhem-va.fhem.de
pi 742 618 0 16:55 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)[2019-1-12 19:42:50] Server listening on: http://127.0.0.1:39363 for proxy connections
[2019-1-12 19:42:50] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":39363},"connections":[{"webname":"fhem","uid":1000,"name":"FHEM","filter":"alexaName=..*","server":"127.0.0.1","port":"8083"}]}
[2019-1-12 19:42:50] [FHEM] longpoll error: Error: self signed certificate, retry in: 5000msec
(node:6166) UnhandledPromiseRejectionWarning: ReferenceError: reject is not defined
at runAutoconfig (/usr/lib/node_modules/alexa-fhem/lib/user.js:310:7)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
(node:6166) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:6166) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Zitat von: justme1968 am 12 Januar 2019, 19:55:54
wenn dein fhem mit user/password gesichert ist musst du alexaFHEM-auth setzen.
[2019-1-12 20:05:44] BearerToken '' read from alexa
[2019-1-12 20:05:44] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.(node:8140) UnhandledPromiseRejectionWarning: ReferenceError: reject is not defined
at runAutoconfig (/usr/lib/node_modules/alexa-fhem/lib/user.js:310:7)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
(node:8140) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8140) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
root@Fhem:/home/fhem# sudo npm update -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.6
updated 1 package in 2.97s[2019-1-12 20:34:08] SSH: Host key verification failed.
[2019-1-12 20:34:08] Reading alexaFHEM.ProxyConnection set to running, stderr=Host key verification failed.
[2019-1-12 20:34:08] SSH: exited with 255 - will restart in 69.71043786559359 seconds
[2019-1-12 20:34:08] Reading alexaFHEM.ProxyConnection set to stopped, Terminated with 255, ssh will restart at 20:35:18
Zitat von: justme1968 am 12 Januar 2019, 20:44:48
gut. das sind mindestens zwei schritte weiter
georg schaut gleich nach deinem tunnel.
Zitat von: gvzdus am 12 Januar 2019, 20:54:53
Moin Spezialtrick! Also, Du bist mir voraus, die 0.5.6 haben :-) Egal.
Dem Forum wollen wir nicht das Problem vorenthalten, aber statt Ping-Pong kontaktiere mich doch bitte unter gvz-fhem@garnix.de, logge Dich bitte auf der Kiste ein mit
sudo -u fhem bash
und gebe mal per Hand ein:
ssh -p 58824 fhem-va.fhem.de status
Kommt da auch die Hostkey-Warnung?
2019.01.12 21:10:09 2: alexa: created default configfile: /volume1/@appstore/fhem/fhem-5.6/alexa-fhem.cfg
2019.01.12 21:10:10 2: alexa: alexa-fhem does not exist: Zitat von: justme1968 am 12 Januar 2019, 21:25:01
das alexa-fhem executable muss einfach nur im pfad sein. egal wo.
wenn das nicht geht kannst du das alexaFHEM-cmd attribut setzen.
es könnte sein das der @ im pfad noch maskiert werden muss. musst du probieren.
ich weiss nicht wo das synolgy node/npm die binares hin installiert.
oder einfach ein symlink von nach /usr/local/bin
so lange alexa-fhem nicht gefunden wird wird auch nichts gestartet und es gibt kein log.
/opt/bin:/opt/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/binsudo ln -s /volume1/@appstore/Node.js_v8/usr/local/bin/alexa-fhem /usr/bin/alexa-fhemsudo ln -s /volume1/@appstore/Node.js_v8/usr/local/lib/node_modules/ /usr/lib/node_modules2019.01.12 21:30:02 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1213.
2019.01.12 21:30:02 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1215
Zitat von: gvzdus am 12 Januar 2019, 21:56:38
Hast Du meinen Skill FHEMlazy gelöscht? Und auch die Geräte, die dazu gehören, rausgeworfen?
Vielleicht sucht er sie bevorzugt noch unter FHEMlazy, aber den hast Du abgeklemmt....
Zitat von: justme1968 am 12 Januar 2019, 21:57:08
gibt dein echo einen fehler?
siehst du events wenn du eine gerätesuche startest?
siehst du im log das events von amazon kommen wenn du bedienst ?
sudo -u fhem /bin/bash
/usr/bin/alexa-fhem -c /opt/fhem/alexa-fhem.cfg -A
Zitat von: DanielK am 13 Januar 2019, 01:49:40
Hallo und herzlichen Dank für die tolle Arbeit.
Ich habe jedoch ein Problem, dass bei mir nach dem Anlegen des Alexa-Devices sämtliche Readings nach einem 'shutdown restart' verschwinden.
Ich habe z. B. ein Dummy in der ich eine Weckzeit per setList eingebe, nachdem ich das ALexa-Device defined habe und dann einen 'shutdown restart' mache,
ist die eingestellte Zeit weg.
Ist dieses Problem bekannt? Sobald ich das Device lösche, macht FHEM wieder alles richtig.
Danke & Gruß
Daniel
Zitat von: Nexium am 13 Januar 2019, 07:54:01
Hallo,
kann das ganze denn nun schon jeder Installieren?
Gruß Dominik
Zitat von: Esjay am 13 Januar 2019, 09:00:12
Hast du nach dem define auf Save geklickt? Wäre ein klassiker wenn nicht.
Kurz gesagt ja. Einfach das richtige Wiki durcharbeiten, und dann bist du in 5 Minuten durch.
Grüße
Internals:
FD 24
LAST_START 2019-01-13 08:58:47
LAST_STOP 2019-01-13 08:58:47
NAME alexa
NOTIFYDEV global
NR 330
NTFY_ORDER 50-alexa
PID 1062
STARTS 2
STATE active
TYPE alexa
currentlogfile ./log/alexa-2019-01-13.log
logfile ./log/alexa-%Y-%m-%d.log
READINGS:
2019-01-13 08:58:47 alexaFHEM running /usr/local/bin/alexa-fhem
Attributes:
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log ./log/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nachtZitatwenn dein fhem mit user/password gesichert ist musst du alexaFHEM-auth setzen.
sudo -u fhem bash
cd
/usr/local/bin/alexa-fhem -c ~/alexa-fhem.cfg -A
/usr/bin/alexa-fhem -c ~/alexa-fhem.cfg -A
Zitat von: Esjay am 13 Januar 2019, 09:00:12
Hast du nach dem define auf Save geklickt? Wäre ein klassiker wenn nicht.
Grüße
Zitat von: justme1968 am 13 Januar 2019, 10:12:08Bin zur Zeit unterwegs, werde heute nachmittag mal weiter testen und das Log durchforsten.
@DanielK: von so einem problem habe ich noch nie gehört...
steht irgendetwas im fhem log?
ist am letzen reading das gesichert wird irgendetwas auffällig?
[2019-1-13 11:38:53] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547375933312
[2019-1-13 11:38:53] [FHEM] Checking devices and attributes...
[2019-1-13 11:38:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2019-1-13 11:38:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=alexa&XHR=1
[2019-1-13 11:38:53] [FHEM] Fetching FHEM devices...
[2019-1-13 11:38:53] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-1-13 11:38:53] [FHEM] longpoll ended, reconnect in: 14700msec
[2019-1-13 11:38:54] [FHEM] There was a problem connecting to FHEM (https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1).
[2019-1-13 11:38:54] [FHEM] 401: Authorization Required
[2019-1-13 11:38:54] [FHEM] There was a problem connecting to FHEM (https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=alexa&XHR=1).
[2019-1-13 11:38:54] [FHEM] 401: Authorization Required
[2019-1-13 11:38:54] [FHEM] There was a problem connecting to FHEM
[2019-1-13 11:38:54] [FHEM] 401: Authorization Required[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 12:08:53] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[2019-1-13 12:08:53] SSH: Host key verification failed.
[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to running, stderr=Host key verification failed.
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20stderr=Host%20key%20verification%20failed.%0D%0A;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 12:08:53] SSH: exited with 255 - will restart in 107.94522439533938 seconds
[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to stopped, Terminated with 255, ssh will restart at 12:10:41
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20stopped,%20Terminated%20with%20255,%20ssh%20will%20restart%20at%2012:10:41;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
Zitat von: roman1528 am 13 Januar 2019, 12:09:56Der Key liegt im Verzeichnis '/opt/fhem/.SSH
Okay cool. Danke.
Habe es aber hinbekommen. Also Auth am Server läuft schon mal.
Jetzt spackt SSH rum.....Code Auswählen[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 12:08:53] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[2019-1-13 12:08:53] SSH: Host key verification failed.
[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to running, stderr=Host key verification failed.
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20stderr=Host%20key%20verification%20failed.%0D%0A;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 12:08:53] SSH: exited with 255 - will restart in 107.94522439533938 seconds
[2019-1-13 12:08:53] Reading alexaFHEM.ProxyConnection set to stopped, Terminated with 255, ssh will restart at 12:10:41
[2019-1-13 12:08:53] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20stopped,%20Terminated%20with%20255,%20ssh%20will%20restart%20at%2012:10:41;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
EDIT: Wo wird denn der generierte SSH-Key gespeichert? dann haue ich den auch nochmal raus und mache nen clean install von alexa.
Zitat von: DanielK am 13 Januar 2019, 12:44:09
Der Key liegt im Verzeichnis '/opt/fhem/.SSH
Gruß Daniel
Gesendet von meinem SM-N950F mit Tapatalk
2019.01.13 13:55:01 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1213.
2019.01.13 13:55:01 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1215.[13.1.2019, 13:54:41] 39_alexa.pm is new version: 324
[13.1.2019, 13:54:41] SSH proxy configuration set up done
[13.1.2019, 13:54:41] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[13.1.2019, 13:54:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_131022457062243&XHR=1
[13.1.2019, 13:54:41] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[13.1.2019, 13:54:41] BearerToken 'xxxxxxxxxxxxxxxxxxxxxxxxx' read from alexa
[13.1.2019, 13:54:42] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[13.1.2019, 13:54:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20SSH%20connected;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_131022457062243&XHR=1
[13.1.2019, 13:54:42] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.pi@raspberrypi:~ $ sudo npm update -g alexa-fhem
(node:761) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Zitat von: roman1528 am 13 Januar 2019, 12:50:38
Danke.
Dann wird bei mir wohl kein Key generiert. Denn der Ordner ist leer.
Edit: Habe alexa-fhem manuell über die Konsole gestartet und eingerichtet. Key's wurden generiert und so weiter. Modul scheint also eingerichtet zu sein. Geräte werden in Alexa gefunden. Jetzt geht's ans testen.
Trotzdem Danke^^
jay@ubuntu:/usr/bin/alexa-fhem$ node --version
v8.15.02019.01.13 13:28:26 2: AlexaFhem: alexa-fhem does not exist: Zitat von: Niko1987 am 13 Januar 2019, 14:16:15
Hallo zusammen,
wie kann man alexa-fhem denn über ssh starten?
Ich hab das gefühl das mein alexa-fhem an den falschen Pfad installiert wurde.
Hab diese Node installiert.Code Auswählenjay@ubuntu:/usr/bin/alexa-fhem$ node --version
v8.15.0
Leider startet das Modul nicht.Code Auswählen2019.01.13 13:28:26 2: AlexaFhem: alexa-fhem does not exist:
Vielleicht kann mir jemand helfen.
Vielen Dank
GRuß
Flo
stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stopZitat von: desmoloch am 13 Januar 2019, 14:10:44
Leider schmiert bei mir nach einiger Zeit der ssh Prozess ab. Im fhem Log als auch im Alexa Log kann ich dazu nichts finden.
Wo kann ich noch schauen?
Ein restart fixt wieder alles.
Gruß
[2019-1-13 14:23:28] SSH: Your public key is not known, please register first
[2019-1-13 14:23:28] SSH: exited with 255 - will restart in 58.17426411720973 seconds[2019-1-13 14:34:46] SSH: Connection to fhem-va.fhem.de closed by remote host.root@fhem_va:~# w
14:05:57 up 15 days, 19:02, 1 user, load average: 0.00, 0.00, 0.00
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
gvz pts/0 2a02:908:210:3ca Sat18 0.00s 0.01s 0.00s sshd: gvz [priv]
Zitat von: justme1968 am 13 Januar 2019, 15:35:15
bitte test mal mit der version die ich eben gepostet habe.
[13.1.2019, 16:25:08] BearerToken '*********2B2A256' read from alexa
[13.1.2019, 16:25:08] [FHEM] got .eventToken
[13.1.2019, 16:25:08] refreshing token
[13.1.2019, 16:25:09] got fresh token
[13.1.2019, 16:25:38] Received Directive: {"directive":{"header":{"namespace":"Alexa.Discovery","name":"Discover","payloadVersion":"3","messageId":"31097799-0921-4a8f-8248-18eda6f16638"},"payload":{"scope":{"type":"BearerToken","token":"*********7CE2E292B2A256"}}}}
[13.1.2019, 16:25:38] found 0 device(s)
response :{"event":{"header":{"namespace":"Alexa.Discovery","name":"Discover.Response","payloadVersion":"3","messageId":"da56363f-e165-48f6-8d87-e61bf6a737d5"},"payload":{"endpoints":[]}}}
Zitat@Teccno: tippe mal: keinen alexaNamen für die devices vergebenFalsch getippt! Das isses nich'! ;-)
ZitatIns Alexa-FHEM-Log?ja.
Zitat von: justme1968 am 13 Januar 2019, 16:40:58
alexaRoom ist für den smart home skill nicht relevant.
schau ins log on der filter und die frage passen und ob dort sonst noch etwas steht
Zitat von: justme1968 am 13 Januar 2019, 16:57:12
weil es im api nicht vorgesehen ist.
dafür sind die gruppen in der alexa app.
Zitat von: 0ni am 13 Januar 2019, 14:09:31Push
Hallo zusammen,
ich habe gerade mal die Anleitung durchgearbeitet und da scheint was nicht zu klappen.
alexaFHEM.skillRegKey crypt:... wird nicht angezeigt.
Im FHEM - Log sehe ich folgendes :Code Auswählen2019.01.13 13:55:01 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1213.
2019.01.13 13:55:01 1: PERL WARNING: Use of uninitialized value $encoded in pattern match (m//) at ./FHEM/39_alexa.pm line 1215.
Im Alexa Log sehe ich am Ende :Code Auswählen[13.1.2019, 13:54:41] 39_alexa.pm is new version: 324
[13.1.2019, 13:54:41] SSH proxy configuration set up done
[13.1.2019, 13:54:41] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[13.1.2019, 13:54:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_131022457062243&XHR=1
[13.1.2019, 13:54:41] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[13.1.2019, 13:54:41] BearerToken 'xxxxxxxxxxxxxxxxxxxxxxxxx' read from alexa
[13.1.2019, 13:54:42] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[13.1.2019, 13:54:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20SSH%20connected;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_131022457062243&XHR=1
[13.1.2019, 13:54:42] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.
Nachtrag: wenn ich in der Konsole ein Update machen will oder versuchen will kommt folgendes :Code Auswählenpi@raspberrypi:~ $ sudo npm update -g alexa-fhem
(node:761) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Beste Grüße
Zitat von: justme1968 am 13 Januar 2019, 16:57:12
weil es im api nicht vorgesehen ist.
dafür sind die gruppen in der alexa app.
Zitatdu kommst leider um das setzen von genericDeviceType und homebridgeMapping nicht rumDer Aufwand bei lediglich drei Temp-Sensoren hielt sich in Grenzen. ;)
Zitat von: justme1968 am 13 Januar 2019, 16:59:39
nein.
es gibt kein api dafür.
Zitat von: Spezialtrick am 13 Januar 2019, 17:17:39
Schade. :(
Ich habe da noch eine paare kleinere Fragen. In meiner gesamten Wohnung hängen Temperatur/Feuchtigkeitssensoren hängen. Über Alexa wird mir jedoch nur die Temperatur angezeigt. Lässt sich die Feuchtigkeit auch übermitteln?
Mein Echo antwortet mir auf die Frage ,,Wie ist die Temperatur im Wohnzimmer" brav mit der aktuellen Temperatur. Die Frage ,,Wie warm ist es im Wohnzimmer" wird leider nicht unterstützt. Kann man diese leicht abgewandelten Fragen irgendwie einpflegen?
Zitat von: 0ni am 13 Januar 2019, 16:58:49
Push
Gesendet von meinem SM-G950F mit Tapatalk
[2019-1-13 18:02:36] using ./alexa-fhem.cfg
[2019-1-13 18:02:36] _loadConfig: Config parsed completely.
[2019-1-13 18:02:36] this is alexa-fhem 0.5.7
[2019-1-13 18:02:36] Fetching FHEM devices...
[2019-1-13 18:02:36] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547398956781
[2019-1-13 18:02:36] Server listening on: https://:::3000 for direct connections
[2019-1-13 18:02:36] Server listening on: http://127.0.0.1:35351 for proxy connections
[2019-1-13 18:02:36] Passed config: {"alexa":{"ssh":"/usr/bin/ssh","keyFile":"/opt/fhem/key.pem","applicationId":["amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"],"name":"Alexa TEST","permissions":{"<skill-id>":{"client_id":"xyz","client_secret":"123"}},"publicSkill":true,"certFile":"/opt/fhem/cert.pem","oauthClientID":["amzn1.application-oa2-client.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"],"port":3000},"connections":[{"webname":"fhem","port":"8083","name":"FHEM","uid":999,"server":"127.0.0.1","filter":"room=alexa","base_url":"http://127.0.0.1:8083/fhem","auth":{"user":"XXXXXX","pass":"XXXXXX","sendImmediately":false}}],"sshproxy":{"description":"FHEM Connector","ssh":"/usr/bin/ssh","name":"sshproxy","bind-ip":"127.0.0.1","ssl":false,"port":35351}}
[2019-1-13 18:02:36] [FHEM] Checking devices and attributes...
[2019-1-13 18:02:36] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2019-1-13 18:02:36] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=alexa&XHR=1
[2019-1-13 18:02:36] [FHEM] Fetching FHEM devices...
[2019-1-13 18:02:36] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20room=alexa&XHR=1
SSH key seems to exist
Our SSH key is known at the reverse proxy, good!
[2019-1-13 18:02:37] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-1-13 18:02:37] [FHEM] alexa device is alexa
[2019-1-13 18:02:37] [FHEM] homebridgeMapping: #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
[2019-1-13 18:02:37] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;%7B$defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20=%20%220.5.7%22%7D;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 18:02:37] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;get%20alexa%20proxyToken;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 18:02:37] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;list%20alexa%20.eventToken;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 18:02:37] 39_alexa.pm is new version: 324
[2019-1-13 18:02:37] SSH proxy configuration set up done
[2019-1-13 18:02:37] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[2019-1-13 18:02:37] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 18:02:37] [FHEM] got: 0 results
[2019-1-13 18:02:37] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[2019-1-13 18:02:37] BearerToken '1884F4858319056C' read from alexa
[2019-1-13 18:02:37] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[2019-1-13 18:02:37] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20SSH%20connected;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
[2019-1-13 18:02:37] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.SSH key seems to exist
Our SSH key is known at the reverse proxy, good!
[2019-1-13 18:02:37] SSH proxy configuration set up done[2019-1-13 18:02:37] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.Zitat von: roman1528 am 13 Januar 2019, 14:22:35
/usr/local/bin/alexa-fhem -A
jay@ubuntu:~$ /usr/local/bin/alexa-fhem -A
-bash: /usr/local/bin/alexa-fhem: Is a directory
sudo -u fhem bash
ssh -p 58824 fhem-va.fhem.de status
ssh -p 58824 fhem-va.fhem.de unregister
root@raspberrypi:~# npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.7
updated 1 package in 7.144s
Zitat von: gvzdus am 13 Januar 2019, 19:08:39
@Niko1987:
Bei mir kommt beiCode Auswählenroot@raspberrypi:~# npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.7
updated 1 package in 7.144s
Du kannst das jederzeit erneut ausführen, in meinem Fall sagt die Zeile mit "/usr/bin/alexa-fhem", dass es eben dort zu finden ist.
root@ubuntu:~# npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.7
added 59 packages from 64 contributors in 5.833sZitatsudo npm install -g alexa-fhemhabe ich schon erfolgreich durchgeführt.
pi@raspberrypi:~ $ ps -ef | egrep '(alexa|ssh)'
pi 790 1 0 21:32 ? 00:00:03 alexa
root 840 1 0 21:32 ? 00:00:00 /usr/sbin/sshd -D
root 1207 840 0 21:43 ? 00:00:00 sshd: pi [priv]
pi 1216 1207 0 21:43 ? 00:00:00 sshd: pi@pts/0
fhem 1367 1329 0 21:47 ? 00:00:04 node /usr/bin/alexa-fhem -c ./log/alexa-fhem.cfg
pi 1571 1218 0 21:54 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)
Zitatdu musst auf jeden fall den alten autostart deaktivierenViele Grüße
und du solltest je nach skill deine alte config über die automatisch erzeugte kopieren.
Zitat von: raimundl am 12 Januar 2019, 20:28:16
funktioniert!!!
Der Key im Reading ist falsch, jedoch mit get alexa proxyKey erscheint ein popup mit dem richtigen Key!
Noch eine Beobachtung: Ich war Betatester und nach jeder neuen Installation verschwindet mein Testdummy und muss wieder neu angelegt werden.
Nochmals Danke und LG
ZitatIch sollte ja eigentlich nur ein sudo npm update -g alexa-fhem ausführen müssen... und FHEM aktualisieren, das neue 39_alexa.pm-Modul ist der wichtigere Teil.
Zitat von: gvzdus am 13 Januar 2019, 22:59:57
Außerdem, 0.5.2. ist so was von vorgestern - wir sind bei 0.5.7
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'alexa-fhem' ]
2 info using npm@6.5.0
3 info using node@v11.6.0
4 verbose npm-session 95367bf5f42f1b63
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/alexa-fhem 282ms (from cache)
8 silly pacote tag manifest for alexa-fhem@latest fetched in 295ms
9 timing stage:loadCurrentTree Completed in 425ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 3ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule alexa-fhem@0.5.7 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/chalk 66ms (from cache)
18 silly pacote range manifest for chalk@^1.1.1 fetched in 73ms
19 silly resolveWithNewModule chalk@1.1.3 checking installable status
20 http fetch GET 304 https://registry.npmjs.org/commander 149ms (from cache)
21 silly pacote version manifest for commander@2.8.1 fetched in 153ms
22 silly resolveWithNewModule commander@2.8.1 checking installable status
23 http fetch GET 304 https://registry.npmjs.org/readline-sync 155ms (from cache)
24 silly pacote range manifest for readline-sync@^1.4.9 fetched in 157ms
25 silly resolveWithNewModule readline-sync@1.4.9 checking installable status
26 http fetch GET 304 https://registry.npmjs.org/request 158ms (from cache)
27 silly pacote range manifest for request@^2.88.0 fetched in 160ms
28 silly resolveWithNewModule request@2.88.0 checking installable status
29 http fetch GET 304 https://registry.npmjs.org/escape-string-regexp 69ms (from cache)
30 silly pacote range manifest for escape-string-regexp@^1.0.2 fetched in 70ms
31 silly resolveWithNewModule escape-string-regexp@1.0.5 checking installable status
32 http fetch GET 304 https://registry.npmjs.org/strip-ansi 82ms (from cache)
33 silly pacote range manifest for strip-ansi@^3.0.0 fetched in 89ms
34 silly resolveWithNewModule strip-ansi@3.0.1 checking installable status
35 http fetch GET 304 https://registry.npmjs.org/has-ansi 107ms (from cache)
36 silly pacote range manifest for has-ansi@^2.0.0 fetched in 108ms
37 silly resolveWithNewModule has-ansi@2.0.0 checking installable status
38 http fetch GET 304 https://registry.npmjs.org/ansi-styles 119ms (from cache)
39 silly pacote range manifest for ansi-styles@^2.2.1 fetched in 120ms
40 silly resolveWithNewModule ansi-styles@2.2.1 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/supports-color 149ms (from cache)
42 silly fetchPackageMetaData error for supports-color@^2.0.0 Unexpected end of JSON input while parsing near '..."}},"1.1.0":{"name":"'
43 timing stage:rollbackFailedOptional Completed in 1ms
44 timing stage:runTopLevelLifecycles Completed in 757ms
45 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '..."}},"1.1.0":{"name":"'
45 verbose stack at JSON.parse (<anonymous>)
45 verbose stack at parseJson (/usr/local/lib/node_modules/npm/node_modules/json-parse-better-errors/index.js:7:17)
45 verbose stack at consumeBody.call.then.buffer (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/body.js:96:50)
45 verbose stack at process.internalTickCallback (internal/process/next_tick.js:77:7)
46 verbose cwd /home/nuc
47 verbose Linux 4.9.0-6-amd64
48 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "alexa-fhem"
49 verbose node v11.6.0
50 verbose npm v6.5.0
51 error Unexpected end of JSON input while parsing near '..."}},"1.1.0":{"name":"'
52 verbose exit [ 1, true ] [1/14/2019, 6:43:01 AM] client not authorized: {"error_index":"3AKxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxMJ0qpfbJfnxDX5A==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:43:01 AM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"6997axxxxxxxxxxxxxxxxxxe8"},"payload":{}}
2019-01-14 06:43:07 caching: TempSchlafzimmer-temperature: 21.4
2019-01-14 06:43:07 caching: TempSchlafzimmer-humidity: 53
2019-01-14 06:48:57 caching: TempWohnzimmer-temperature: 22.8
2019-01-14 06:49:00 caching: TempArbeitszimmer-humidity: 46
[1/14/2019, 6:53:00 AM] client not authorized: {"error_index":"pNxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxtAg==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:53:00 AM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"2bxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd351"},"payload":{}}
2019-01-14 06:54:57 caching: TempBadezimmer-temperature: 24
2019-01-14 06:54:57 caching: TempBadezimmer-humidity: 49
2019-01-14 06:54:57 caching: TempArbeitszimmer-temperature: 21.9
2019-01-14 06:55:06 caching: TempSchlafzimmer-humidity: 52
2019-01-14 07:00:56 caching: TempBadezimmer-temperature: 24.2
2019-01-14 07:00:56 caching: TempBadezimmer-humidity: 50
2019-01-14 07:01:11 caching: TempGaesteWC-temperature: 21.5
2019-01-14 07:06:55 caching: TempArbeitszimmer-temperature: 21.8
2019-01-14 07:07:01 caching: TempGaesteWC-humidity: 48
Zitat von: gvzdus am 14 Januar 2019, 07:41:17Die Verknüpfung mit FHEMLazy kann ich ausschließen.Der Skill wird unter "Kontoverknüpfung erforderlich" aufgeführt.. Ich habe gestern Abend noch das unregister auf dem Fhem Server durchgeführt,und den Skill anschließend mit neuem Token regestriert. Wenn ich zuhause bin, werde ich nochmal ins Log schauen, und dann können wir, falls die Probleme wieder aufgetreten sind, das volle Debugging gerne einschalten.
Es kommen Requests mit dem falschen BearerToken. Folgende Möglichkeiten halte ich für gut denkbar:
- Du hast noch FHEM-Lazy parallel als Skill verknüpft, oder vielleicht hatte auch Andre Dich mal zum Beta-Test eingeladen?
- Amazon hat irgendwelche Probleme
Die einfachste Abhilfe sollte sein:
- Sicherstellen, dass nur FHEM Connector verknüpft ist
- Verknüpfung bei FHEM-Connector aufheben und sofort neu verknüpfen (Registrierungskey zur Hand haben)
Wenn das nicht hilf, entscheide Dich, ob wir auf der Lambda-Funktion das volle Debugging einschalten für Deine User-ID (Teil 1 Reg.-Schlüssel) aktivieren sollen, dann landet alle Kommunikation für 7 Tage auf der Platte. Ich bräuchte dann Deine User-ID per P-Mail
Zitat von: gvzdus am 14 Januar 2019, 07:49:17
Ja, alles andere wird echt chaotisch und quasi garantiert nicht funktionieren.
Am besten gehst Du den Wiki zu "alexa-fhem" im Abschnitt automatischer Start durch und versuchst zu rekonstruieren, welchen Weg Du gewählt hast.
Zitat von: gvzdus am 14 Januar 2019, 08:15:58
Und bevor Du FHEM Connector verknüpfst, solltest Du die Verknüpfung zu Deinem Entwicklerskill aufheben.
ZitatDanke und sorry, aber ich muss das fragen - wo bzw. wie mache ich das?
pi@raspi-fhem:/opt/fhem $ sudo /bin/bash
root@raspi-fhem:/opt/fhem#
root@raspi-fhem:/opt/fhem# node --version
v8.11.4
root@raspi-fhem:/opt/fhem# sudo npm install -g alexa-fhem
+ alexa-fhem@0.4.4
added 1 package in 3.088s
root@raspi-fhem:/opt/fhem/alexa-fhem# sudo npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.7
added 59 packages in 10.697s
alexaFHEM.ProxyConnection
error, FHEM Web not reachable - -
2019-01-14 09:29:55
[2019-1-14 09:29:53] Reading alexaFHEM.ProxyConnection set to stopping, alexa-fhem terminating
[2019-1-14 09:29:53] using ./alexa-fhem.cfg
[2019-1-14 09:29:53] _loadConfig: Config parsed completely.
[2019-1-14 09:29:53] this is alexa-fhem 0.5.7
[2019-1-14 09:29:53] Fetching FHEM devices...
[2019-1-14 09:29:54] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547454594315
[2019-1-14 09:29:54] Server listening on: http://127.0.0.1:37141 for proxy connections
[2019-1-14 09:29:54] Passed config: {"connections":[{"name":"FHEM","server":"127.0.0.1","uid":999,"webname":"fhem","filter":"alexaName=..*","port":"8083"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":37141}}
[2019-1-14 09:29:54] autoconf: testrequest result is {"success":false,"message":{"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}}
[2019-1-14 09:29:54] FHEM Web not reachable - -
[2019-1-14 09:29:54] Unable to setup SSH proxy configuration
[2019-1-14 09:29:54] [FHEM] Checking devices and attributes...
[2019-1-14 09:29:54] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&XHR=1
[2019-1-14 09:29:54] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=alexa&XHR=1
[2019-1-14 09:29:54] [FHEM] Fetching FHEM devices...
[2019-1-14 09:29:54] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-1-14 09:29:55] [FHEM] alexa device is alexa
---
[2019-1-14 09:29:55] BearerToken '' read from alexa
[2019-1-14 09:29:55] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2019-1-14 09:29:55] Reading alexaFHEM.ProxyConnection set to error, FHEM Web not reachable - -
[2019-1-14 09:29:55] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20error,%20FHEM%20Web%20not%20reachable%20-%20-;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&XHR=1
root@raspi-fhem:/opt/fhem# ps -ef | egrep '(alexa|ssh)'
root 561 1 0 01:00 ? 00:00:00 /usr/sbin/sshd -D
root 3033 561 0 07:51 ? 00:00:00 sshd: pi [priv]
pi 3048 3033 0 07:51 ? 00:00:01 sshd: pi@pts/0
fhem 4565 4418 0 09:29 ? 00:00:02 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx -s
root 4697 3630 0 09:42 pts/0 00:00:00 grep -E (alexa|ssh)
Zitat von: justme1968 am 14 Januar 2019, 09:42:30
das alexaFHEMauth attribut setzen
2019.01.14 09:29:53 3: alexa: alexaFHEM stopped
2019.01.14 09:29:53 3: alexa: alexaFHEM starting
2019.01.14 09:29:53 3: alexa: using logfile: ./log/alexa-2019-01-14.log
2019.01.14 09:29:53 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a chris:xxxxxx -s
connections" : [
{
"filter" : "alexaName=...*",
"server" : "127.0.0.1",
"uid" : 999,
"webname" : "fhem",
"ssl": true,
"port" : "8083",
"name" : "FHEM"
}
],Zitat von: justme1968 am 14 Januar 2019, 09:13:00Hallo @ all,
0.4.4 ist uralt.
alte version am besten löschen
sudo npm remove -g alexa-fhem
Zitat von: gvzdus am 14 Januar 2019, 09:50:04
Workaround:
In /opt/fhem/alexa-fhem.cfg bitte in dem Block:
...
den Wert von ssl entweder abändern auf true, oder neu einfügen. Dann "restart" im Alexa-Device auswählen.
Zitat von: justme1968 am 14 Januar 2019, 09:56:39Also Alexa.pm als Update sperren und fertig oder ist das egal?
niemand muss
wechseln bei dem alles geht und der zufrieden ist.
die neue version ist erst mal hauptsächlich für alle die keinen eigen skill einrichten möchten
Zitat von: gvzdus am 13 Januar 2019, 23:37:19
Besser erst alexa-fhem upgraden - den Restart musst Du ja schon im Rahmen des FHEM-Upgrade danach durchführen.
Eine Restsorge hätte ich jetzt: Fahren dabei (beim FHEM-Restart) auch alexa-fhem und ssh runter - bin aber eigentlich ganz zuversichtlich.
sudo /bin/bashsudp npm remove -g alexa-fhemsudo npm install -g alexa-fhemupdateshutdown restartget MyAlexa proxyKeydefine alexa alexadrwxr-xr-x 16 fhem dialout 4096 Jan 14 11:44 .
drwxr-xr-x 4 root root 4096 Mar 4 2018 ..
drwx------ 2 fhem dialout 4096 Jan 10 01:24 .alexa
drwxr-xr-x 5 fhem dialout 4096 Jan 10 01:16 alexa-fhem
-rw-r--r-- 1 fhem dialout 526 Jan 14 11:44 alexa-fhem.cfg
-rw-r--r-- 1 fhem dialout 411 Jan 10 17:06 alexa-fhem.cfg.previous
-rw-r--r-- 1 fhem dialout 2 Jan 10 01:11 alexa.pid
drwxr-xr-x 2 fhem dialout 4096 Jan 14 11:19 backup
-rw------- 1 fhem dialout 1215 Jan 10 17:16 .bash_history
-rw-r--r-- 1 fhem dialout 273383 Jan 14 11:22 CHANGED
drwx------ 3 fhem dialout 4096 Jan 9 20:14 .config
-rw-r--r-- 1 fhem dialout 39688 Nov 1 12:59 configDB.pm
drwxrwxrwx 41 fhem root 4096 Oct 8 2016 contrib
drwxrwxrwx 3 fhem root 4096 Nov 8 2015 demolog
drwxrwxrwx 4 fhem root 4096 Jul 6 2017 docs
drwxrwxrwx 6 fhem root 24576 Jan 14 11:44 FHEM
-rw-r--r-- 1 fhem dialout 89692 Jan 14 11:51 fhem.cfg
-rw-r--r-- 1 fhem dialout 19987 Nov 1 12:59 fhem.cfg.demo
-rw-rw-rw- 1 fhem root 39041 Jan 8 2017 fhem.cfg_old
-rw-r--r-- 1 fhem dialout 86403 Jan 9 20:14 fhem.cfg_vorfhemlazy
-rw-rw-rw- 1 fhem root 744 Nov 9 2014 fhem_orig.cfg
-rw-r--r-- 1 fhem dialout 152823 Jan 4 23:32 fhem.pl
-rw-r--r-- 1 fhem dialout 0 Jul 23 2016 fronthem.err
drwxrwxrwx 2 fhem root 4096 Jan 14 00:00 log
-rw-r--r-- 1 fhem dialout 39004 Jan 14 11:22 MAINTAINER.txt
drwxr-xr-x 5 fhem dialout 4096 Jan 9 20:15 .npm
-rw-rw-rw- 1 fhem root 761 Nov 9 2014 README_DEMO.txt
drwxr-xr-x 7 fhem dialout 4096 Jun 8 2018 restoreDir
drwx------ 2 fhem dialout 4096 Jan 9 20:16 .ssh
drwxr-xr-x 2 fhem dialout 4096 Feb 11 2016 unused
drwxrwxrwx 15 fhem root 4096 Mar 4 2018 wwwdrwxrwxrwx 41 fhem root 4096 Oct 8 2016 contrib
drwxrwxrwx 3 fhem root 4096 Nov 8 2015 demolog
drwxrwxrwx 4 fhem root 4096 Jul 6 2017 docs
drwxrwxrwx 6 fhem root 24576 Jan 14 11:44 FHEM
drwxrwxrwx 2 fhem root 4096 Jan 14 00:00 log
drwxrwxrwx 15 fhem root 4096 Mar 4 2018 www
fhem@Fhem:~$ sudo npm install -g alexa-fhem
/usr/local/bin/alexa-fhem -> /usr/local/lib/node_modules/alexa-fhem/bin/alexa
/usr/local/lib
└── alexa-fhem@0.5.7
fhem@Fhem:~$ ps -ef | egrep '(alexa|ssh)'
root 923 1 0 Jan11 ? 00:00:00 /usr/sbin/sshd -D
root 17985 923 0 13:01 ? 00:00:00 sshd: fhem [priv]
fhem 18018 1 0 07:47 ? 00:00:05 alexa
fhem 18052 17985 0 13:01 ? 00:00:00 sshd: fhem@notty
root 19255 923 0 13:24 ? 00:00:00 sshd: fhem [priv]
fhem 19306 19255 0 13:24 ? 00:00:00 sshd: fhem@notty
root 20909 923 0 13:53 ? 00:00:00 sshd: fhem [priv]
fhem 20960 20909 0 13:53 ? 00:00:00 sshd: fhem@pts/0
fhem 21025 20961 0 13:54 pts/0 00:00:00 grep -E (alexa|ssh)Internals:
CFGFN
FD 21
LAST_START 2019-01-14 13:12:26
LAST_STOP 2019-01-14 13:12:26
NAME alexa
NOTIFYDEV global
NR 966
NTFY_ORDER 50-alexa
PID 18679
STARTS 7
STATE running /usr/local/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.7
currentlogfile ./log/alexa-2019-01-14.log
logfile ./log/alexa-%Y-%m-%d.log
READINGS:
2019-01-14 13:12:26 alexaFHEM running /usr/local/bin/alexa-fhem[14.1.2019, 14:10:31] Passed config: {"connections":[{"port":"8083","server":"127.0.0.1","name":"FHEM","uid":1000,"ssl":true,"filter":"alexaName=..*","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":44115}}
[14.1.2019, 14:10:31] Server listening on: http://127.0.0.1:44115 for proxy connections
[14.1.2019, 14:10:31] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547471431468
[14.1.2019, 14:10:31] Fetching FHEM devices...
[14.1.2019, 14:10:31] this is alexa-fhem 0.5.7
[14.1.2019, 14:10:31] _loadConfig: Config parsed completely.2019.01.14 15:32:02 1: Error: >ALEXA< has no TYPE, but following keys: >active<
2019.01.14 15:32:02 1: Error: >ALEXA< has no TYPE, but following keys: >active<
2019.01.14 15:32:02 1: Error: >ALEXA< has no TYPE, but following keys: >active<
2019.01.14 15:31:54 0: Server started with 510 defined entities (fhem.pl:18111/2019-01-01 perl:5.026001 os:linux user:fhem pid:27385)
2019.01.14 15:31:54 0: Featurelevel: 9.9
2019.01.14 15:31:52 3: alexa: using logfile: ./log/alexa-2019-01-14.log
2019.01.14 15:31:52 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a userxxx:paswortxxx
2019.01.14 15:31:52 3: alexa: alexaFHEM starting
2019.01.14 15:31:41 1: Including ./log/fhem.save[2019-1-14 17:27:19] reloading http://localhost:8083/fhem
[2019-1-14 17:27:19] removing Drucker from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing FensterLampe from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing HUEDevice14 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing HUEDevice16 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing HUEDevice19 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing HUEDevice7 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing HUEGroup4 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing MAX_191dab from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing MAX_191db5 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing MAX_191e95 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing MAX_191f54 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing MAX_192f92 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing QNAP from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing Schreibtisch from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing Status_Guest_WLAN_Unifi from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing USBLadestation from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing XboxController from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing hueBridge1_HUEDevice10 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing hueBridge1_HUEDevice8 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing hueBridge1_HUEDevice9 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing hueBridge1_HUEGroup14 from http://localhost:8083/fhem
[2019-1-14 17:27:19] removing hueBridge1_HUEGroup5 from http://localhost:8083/fhem
[2019-1-14 17:27:19] [FHEM] Fetching FHEM devices...
[2019-1-14 17:27:19] [FHEM] fetching: http://localhost:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_XXX
[2019-1-14 17:27:20] [FHEM] got: 24 results
...
[2019-1-14 17:27:20] [FHEM] FensterLampe is light
[2019-1-14 17:27:20] [FHEM] FensterLampe has
[2019-1-14 17:27:20] [FHEM] On [state;on,off]
...
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup14 is light
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup14 has
[2019-1-14 17:27:20] [FHEM] On [onoff;on,off]
[2019-1-14 17:27:20] [FHEM] Brightness [bri]
[2019-1-14 17:27:20] [FHEM] Hue [hue;hue;0-65535]
[2019-1-14 17:27:20] [FHEM] Saturation [sat;sat;0-254]
[2019-1-14 17:27:20] [FHEM] Custom Color Temperature [ct]
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup14-ct not a number: undefined
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup5 is light
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup5 has
[2019-1-14 17:27:20] [FHEM] On [onoff;on,off]
[2019-1-14 17:27:20] [FHEM] Brightness [bri]
[2019-1-14 17:27:20] [FHEM] Hue [hue;hue;0-65535]
[2019-1-14 17:27:20] [FHEM] Saturation [sat;sat;0-254]
[2019-1-14 17:27:20] [FHEM] Custom Color Temperature [ct]
[2019-1-14 17:27:20] [FHEM] hueBridge1_HUEGroup5-ct not a number: undefined
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
[2019-1-14 17:27:20] no event token available
Zitat von: justme1968 am 14 Januar 2019, 17:42:28
- wenn es nur um ein einzelnes device geht solltest du beim reload noch dessen namen angeben.
Zitat von: justme1968 am 14 Januar 2019, 17:42:28
- die token meldung bezieht sich auf den versuch ein event an amzon zu senden um die devices zu aktualisieren.
aus irgendeinem grund hat alexa-fhem das token nicht. es sollte im reading .eventToken deines alexa device stecken.
wenn es nicht da ist: die skill verknüpfung löschen und neu verknüpfen.
du sollest eine meldung sehen das alexa-fhem ein token bekommen hat und es sollte dann im reading stehen
[2019-1-14 17:51:49] got event token
[2019-1-14 18:04:26] posting skill event
[2019-1-14 18:04:26] posted skill event: 202: [2019-1-14 18:03:28] reloading FensterLampe from http://localhost:8083/fhem
[2019-1-14 18:03:28] removing FensterLampe from http://localhost:8083/fhem
[2019-1-14 18:03:28] [FHEM] Fetching FHEM devices...
[2019-1-14 18:03:28] [FHEM] fetching: http://localhost:8083/fhem?cmd=jsonlist2%20NAME=FensterLampe&fwcsrf=csrf_XXXX
[2019-1-14 18:03:28] [FHEM] got: 1 results
[2019-1-14 18:03:28] [FHEM] FensterLampe is light
[2019-1-14 18:03:28] [FHEM] FensterLampe has
[2019-1-14 18:03:28] [FHEM] On [state;on,off]
[2019-1-14 18:03:28] posting skill event
[2019-1-14 18:03:28] posted skill event: 202: Zitat von: gvzdus am 14 Januar 2019, 07:41:17
Es kommen Requests mit dem falschen BearerToken. Folgende Möglichkeiten halte ich für gut denkbar:
- Du hast noch FHEM-Lazy parallel als Skill verknüpft, oder vielleicht hatte auch Andre Dich mal zum Beta-Test eingeladen?
- Amazon hat irgendwelche Probleme
Die einfachste Abhilfe sollte sein:
- Sicherstellen, dass nur FHEM Connector verknüpft ist
- Verknüpfung bei FHEM-Connector aufheben und sofort neu verknüpfen (Registrierungskey zur Hand haben)
Wenn das nicht hilf, entscheide Dich, ob wir auf der Lambda-Funktion das volle Debugging einschalten für Deine User-ID (Teil 1 Reg.-Schlüssel) aktivieren sollen, dann landet alle Kommunikation für 7 Tage auf der Platte. Ich bräuchte dann Deine User-ID per P-Mail
1/14/2019, 6:07:56 PM] 39_alexa.pm is new version: 324
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=set%20alexa%20proxyToken%201xxxxxxxxxxxxx3A1&fwcsrf=csrf_20xxxxxxxxxxx22&XHR=1
[1/14/2019, 6:07:57 PM] BearerToken 'xxxxxxxxxxxxx' read from alexa
[1/14/2019, 6:07:57 PM] [FHEM] got .eventToken
[1/14/2019, 6:07:57 PM] refreshing token
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=set%20alexa%20proxyKey%201xxxxxxxxxxxxxxxxxxxxxx3A1&fwcsrf=csrf_2050xxxxxxxxxxxxxxx&XHR=1
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=%7B%20FW_directNotify(%22%23FHEMWEB%3AWEB%22%2C%20%22location.reload('true')%22%2C%20%22%22)%20%7D&fwcsrf=csrf_20xxxxxxxxx2&XHR=1
[1/14/2019, 6:07:57 PM] SSH proxy configuration set up done
[1/14/2019, 6:07:57 PM] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[1/14/2019, 6:07:57 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_20xxxxxxxxxxx2&XHR=1
[1/14/2019, 6:07:57 PM] SSH setup completed with new bearer token
[1/14/2019, 6:07:57 PM] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[1/14/2019, 6:07:57 PM] got fresh token
[1/14/2019, 6:07:58 PM] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[1/14/2019, 6:07:58 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20SSH%20connected;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_20xxxxxxxxxxxxx2&XHR=1
[1/14/2019, 6:07:58 PM] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.
[1/14/2019, 6:08:00 PM] client not authorized: {"error_index":"yxxxxxxxxxxxxxxxxxxxxxxxckqQKa5TrA==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:08:00 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"b3xxxxxxxxxxxa1ab6c"},"payload":{}}
[1/14/2019, 6:08:02 PM] client not authorized: {"error_index":"wQLxxxxxxxxxxxxxxxxxxxxxxxizjbUOpVXA==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:08:02 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"23xxxxxxxf9e25"},"payload":{}}
[1/14/2019, 6:08:29 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"9cxxxxxxxxxxb05"},"payload":{}}
[1/14/2019, 6:12:42 PM] Received Directive: {"directive":{"header":{"namespace":"Alexa.Discovery","name":"Discover","payloadVersion":"3","messageId":"7a704d14-f5ec-455d-9c49-8a814836db4f"},"payload":{"scope":{"type":"BearerToken","token":"1xxxxxxxxxxxxxxxxxxxxxxx"}}}}
[1/14/2019, 6:12:42 PM] found 19 device(s)
response :{"event":{"header":{"namespace":"Alexa.Discovery","name":"Discover.Response","payloadVersion":"3","messageId":"6fxxxxxxxxxxxxxa6"},"payload":{"endpoints":[{"endpointId":"Ambilight","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"ambilight","description":"n: Ambilight, r: hidden,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Ambilight"}},{"endpointId":"Fernseher","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"fernseher","description":"n: Fernseher, r: homekit,wohnzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Fernseher"}},{"endpointId":"GuteNachtAlexa","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"gutenacht","description":"n: GuteNachtAlexa, r: dummys,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"GuteNachtAlexa"}},{"endpointId":"HUEDevice12","manufacturerName":"FHEMHUEDevice","modelName":"FHEMPlug 01","version":"<unknown>","friendlyName":"terrarium","description":"n: HUEDevice12, r: homekit,spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"HUEDevice12"}},{"endpointId":"HUEDevice9","manufacturerName":"FHEMHUEDevice","modelName":"FHEMLWB010","version":"<unknown>","friendlyName":"nachttisch katha","description":"n: HUEDevice9, r: schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["LIGHT"],"cookie":{"device":"HUEDevice9"}},{"endpointId":"Heimkino","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"heimkino","description":"n: Heimkino, r: spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Heimkino"}},{"endpointId":"00:17:88:01:00:64:4d:05-0f","manufacturerName":"FHEMHUEDevice","modelName":"FHEMLWB001","version":"<unknown>","friendlyName":"nachttisch stephan","description":"n: Hue_HUEDevice7, r: schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["LIGHT"],"cookie":{"device":"Hue_HUEDevice7"}},{"endpointId":"MAX_007fbb","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung arbeitszimmer","description":"n: MAX_007fbb, r: arbeitszimmer,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_007fbb"}},{"endpointId":"MAX_0764eb","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung schlafzimmer","description":"n: MAX_0764eb, r: homekit,schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_0764eb"}},{"endpointId":"MAX_07a38e","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung spielzimmer","description":"n: MAX_07a38e, r: kinderzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_07a38e"}},{"endpointId":"Maxtemp","manufacturerName":"FHEMreadingsProxy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"dachboden","description":"n: Maxtemp, r: spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"Maxtemp"}},{"endpointId":"IT_00000F0FFF_0F_F0","manufacturerName":"FHEMIT","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"schuhschrank","description":"n: Schuhschrank, r: flur,steckdosen,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Schuhschrank"}},{"endpointId":"StaubsaugerEG","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"staubsauger erdgeschoss","description":"n: StaubsaugerEG, r: erdgeschoss","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"StaubsaugerEG"}},{"endpointId":"StaubsaugerOG","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"staubsauger obergeschoss","description":"n: StaubsaugerOG, r: obergeschoss","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"StaubsaugerOG"}},{"endpointId":"TempArbeitszimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur arbeitszimmer","description":"n: TempArbeitszimmer, r: arbeitszimmer,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempArbeitszimmer"}},{"endpointId":"TempBadezimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur badezimmer","description":"n: TempBadezimmer, r: bad,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempBadezimmer"}},{"endpointId":"TempGaesteWC","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur gaestebad","description":"n: TempGaesteWC, r: gaestewc,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempGaesteWC"}},{"endpointId":"TempSchlafzimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur schlafzimmer","description":"n: TempSchlafzimmer, r: homekit,schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempSchlafzimmer"}},{"endpointId":"TempWohnzimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur wohnzimmer","description":"n: TempWohnzimmer, r: alexa,homekit,wohnzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempWohnzimmer"}}]}}}
2019-01-14 18:12:56 caching: TempArbeitszimmer-temperature: 22.4
2019-01-14 18:12:56 caching: TempWohnzimmer-temperature: 23.6
2019-01-14 18:13:01 caching: TempSchlafzimmer-temperature: 21.5
[14.1.2019, 18:50:25] using ./alexa-fhem.cfg
[14.1.2019, 18:50:25] _loadConfig: Config parsed completely.
[14.1.2019, 18:50:25] this is alexa-fhem 0.5.7
[14.1.2019, 18:50:25] Fetching FHEM devices...
[14.1.2019, 18:50:26] [FHEM] starting longpoll: http://127.0.0.1:undefined/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547488226079
[14.1.2019, 18:50:26] Server listening on: http://127.0.0.1:39795 for proxy connections
[14.1.2019, 18:50:26] Passed config: {"connections":[{"uid":999,"server":"127.0.0.1","name":"FHEM","filter":"alexaName=..*"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":39795}}
[14.1.2019, 18:50:26] [FHEM] longpoll error: Error: connect ECONNREFUSED 127.0.0.1:80, retry in: 5000msec
[14.1.2019, 18:50:26] autoconf: testrequest result is {"success":false,"message":{"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":80}}
[14.1.2019, 18:50:26] FHEM Web not reachable - -
[14.1.2019, 18:50:26] Unable to setup SSH proxy configuration
[14.1.2019, 18:50:27] Reading alexaFHEM.ProxyConnection set to error, FHEM Web not reachable - -
[14.1.2019, 18:50:31] [FHEM] starting longpoll: http://127.0.0.1:undefined/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547488231184
[14.1.2019, 18:50:31] [FHEM] longpoll error: Error: connect ECONNREFUSED 127.0.0.1:80, retry in: 10000msec
Zitat von: justme1968 am 14 Januar 2019, 19:01:11
wenn das config file über das alexa modul erzeugt wird kommt es aus dem WEB in fhem device.
Zitat von: justme1968 am 14 Januar 2019, 19:01:11
die frage ist warum hast du ein config file ohne port?
Zitat von: justme1968 am 14 Januar 2019, 17:34:37
1. ja. ist bekannt. das device dynamisch temporary angelegt wenn alexa-fhem läuft und sonst beendet. deshalb lassen sich keine attribute setzen und das device wird auch nicht gespeichert.
2. dann solltest du mal im log schauen woran es liegt. es soll automatisch gestartet werden.
[2019-1-14 19:46:21] [FHEM] FLUR.licht_vorn is switch
[2019-1-14 19:46:21] [FHEM] FLUR.licht_vorn has
[2019-1-14 19:46:21] [FHEM] FirmwareRevision [D-firmware]
[2019-1-14 19:46:21] [FHEM] On [state;on,off]
2019-01-14 19:46:21 caching: FLUR.licht_vorn-D-firmware: 2.3
2019-01-14 19:46:21 caching: FLUR.licht_vorn-state: off
[2019-1-14 19:46:21] [FHEM] homebridgeMapping: LockCurrentState=state,values=on:UNSECURED;released:SECURED,default=UNKNOWN \ LockTargetState=state,values=on:UNSECURED;released:SECURED,default=UNKNOWN,cmds=SECURED:off;UNSECURED:on \ LockManagementAutoSecureTimeout=1 \ LockMechanismLastKnownAction=state,values=on:unsecuredRemotely;on:securedWithAutomaticSecureTimeout
/usr/lib/node_modules/alexa-fhem/lib/fhem.js:948
if( match === undefined || match.length < 4 || !match[3] ) {
^
TypeError: Cannot read property 'length' of null
at FHEMDevice.fromHomebridgeMapping (/usr/lib/node_modules/alexa-fhem/lib/fhem.js:948:40)
at new FHEMDevice (/usr/lib/node_modules/alexa-fhem/lib/fhem.js:2394:8)
at FHEM.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/fhem.js:846:39)
at Array.map (<anonymous>)
at FHEM.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/fhem.js:843:31)
at Request.self.callback (/usr/lib/node_modules/alexa-fhem/node_modules/request/request.js:185:22)
at Request.emit (events.js:188:13)
at Request.<anonymous> (/usr/lib/node_modules/alexa-fhem/node_modules/request/request.js:1161:10)
at Request.emit (events.js:188:13)
at Gunzip.<anonymous> (/usr/lib/node_modules/alexa-fhem/node_modules/request/request.js:1083:12)Internals:
CFGFN
FD 24
LAST_START 2019-01-14 18:54:28
LAST_STOP 2019-01-14 18:54:28
NAME alexa
NOTIFYDEV global
NR 140
NTFY_ORDER 50-alexa
PID 3622
STARTS 4
STATE running /usr/local/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.7
currentlogfile ./log/alexa-2019-01-14.log
logfile ./log/alexa-%Y-%m-%d.log
READINGS:
2019-01-14 18:54:28 alexaFHEM running /usr/local/bin/alexa-fhem
2019-01-14 18:54:33 alexaFHEM.ProxyConnection running, SSH connected
2019-01-14 18:45:58 alexaFHEM.bearerToken crypt:710002575679270100700850700a0850
Attributes:
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log ./log/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nacht
stateFormat alexaFHEM2019.01.14 18:45:49 2: alexa: created default configfile: ./alexa-fhem.cfg
2019.01.14 18:45:50 3: alexa: alexaFHEM starting
2019.01.14 18:45:50 3: alexa: using logfile: ./log/alexa-2019-01-14.log
2019.01.14 18:45:50 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.14 18:45:50 3: alexa: read: end of file reached while sysread
2019.01.14 18:45:50 3: alexa: alexaFHEM stopped
2019.01.14 18:45:50 3: alexa: alexaFHEM starting
2019.01.14 18:45:50 3: alexa: using logfile: ./log/alexa-2019-01-14.log
2019.01.14 18:45:50 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.14 18:45:58 3: alexa: read: end of file reached while sysread
2019.01.14 18:45:58 3: alexa: alexaFHEM stopped
2019.01.14 18:46:18 3: alexa: alexaFHEM starting
2019.01.14 18:46:18 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.14 18:46:18 3: alexa: using logfile: ./log/alexa-2019-01-14.log
2019.01.14 18:46:43 2: AttrTemplates: got 45 entries
2019.01.14 18:54:28 3: alexa: read: end of file reached while sysread
2019.01.14 18:54:28 3: alexa: alexaFHEM stopped
2019.01.14 18:54:28 3: alexa: alexaFHEM starting
2019.01.14 18:54:28 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.01.14 18:54:28 3: alexa: using logfile: ./log/alexa-2019-01-14.logroot@raspberrypi:/home/pi# ps -ef | egrep '(alexa|ssh)'
root 512 1 0 18:38 ? 00:00:00 /usr/sbin/sshd -D
root 551 512 0 18:39 ? 00:00:00 sshd: pi [priv]
pi 566 551 0 18:39 ? 00:00:00 sshd: pi@pts/0
fhem 3584 3550 1 18:46 ? 00:00:03 node /usr/local/bin/alexa-fhem - c ./alexa-fhem.cfg
fhem 3595 3584 0 18:46 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:4 0603 -oServerAliveInterval=90 -p 58824 fhem-va.fhem.de
root 3601 594 0 18:49 pts/0 00:00:00 grep -E (alexa|ssh)
Zitat von: justme1968 am 14 Januar 2019, 19:17:03
@betateilchen: eine bessere suche nach einem fhemweb device steht noch auf der liste.
@webs = devspec2array("TYPE=FHEMWEB");
foreach (@webs) {
if ( !InternalVal( $_, 'TEMPORARY', undef ) ) {
$FW_wname = InternalVal( $_, 'NAME', '' );
last;
}
}
Zitat von: gvzdus am 14 Januar 2019, 19:48:43
@det: Ich glaube, nach Warteliste bist Du definitiv als nächster dran.
Was mir auffällt:
Nach der Kommandozeile für alexa hast Du kein SSL-FHEMWEB (kein "-s" angegeben). Nach der "Passed config"-Zeile schon. Das garantiert mit Version 0.5.7 (und früher) schon mal Inkonsistenzen zwischen SSH-Anteil und alexa-fhem. Wenn Du alexa-fhem.cfg und Realität näher aneinander ran bringst, kommt Du vermutlich weiter.
Alternativ wäre konkret aus dem alexa-Logfile der Abschnitt ab "passed config" hilfreich, bis zu dem Moment, wo er "scheinbar" aufgibt (wird demnächst besser geloggt werden).
devspec2array('TYPE=FHEMWEB:FILTER=TEMPORARY!=1') )[14.1.2019, 18:45:52] using ./alexa-fhem.cfg
[14.1.2019, 18:45:52] _loadConfig: Config parsed completely.
[14.1.2019, 18:45:52] this is alexa-fhem 0.5.7
[14.1.2019, 18:45:52] Fetching FHEM devices...
[14.1.2019, 18:45:53] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1547491553455
[14.1.2019, 18:45:53] Server listening on: http://127.0.0.1:43055 for proxy connections
Creating directory /opt/fhem/.alexa
[14.1.2019, 18:45:53] Passed config: {"connections":[{"name":"FHEM","webname":"fhem","uid":999,"port":"8083","filter":"alexaName=..*","server":"127.0.0.1"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","bind-ip":"127.0.0.1","port":43055}}
[14.1.2019, 18:45:53] [FHEM] Checking devices and attributes...
[14.1.2019, 18:45:53] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22,%22userattr%22,%22%22)%7D&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:53] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE=alexa&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:53] [FHEM] Fetching FHEM devices...
[14.1.2019, 18:45:53] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_115238495440766&XHR=1
No SSH public key found, we have to generate one.
Generating public/private rsa key pair.
Created directory '/opt/fhem/.ssh'.
Your identification has been saved in /opt/fhem/.ssh/id_rsa.
Your public key has been saved in /opt/fhem/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx1jE fhem@raspberrypi
The key's randomart image is:
+---[RSA 2048]----+
|.o... . .o+E+ |
|.o.o . +.o=ooo. |
|. + = . o... o. |
| = + . o.. o . |
|o o o ..S.+ .. |
|. . o...o= . |
|. ... O o |
| . .. o o |
| .. |
+----[SHA256]-----+
[14.1.2019, 18:45:58] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:58] 39_alexa.pm is new version: 324
[14.1.2019, 18:45:58] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20FHEM.Alexa&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:58] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%20addToAttrList(%20%22homebridgeMapping:textField-long%22%20)%20%7D&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:58] [FHEM] homebridgeMapping attribute created.
[14.1.2019, 18:45:58] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BaddToAttrList(%20%22genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock,scene%22%20)%20%7D&fwcsrf=csrf_115238495440766&XHR=1
[14.1.2019, 18:45:58] [FHEM] got: 0 results
[14.1.2019, 18:45:58] [FHEM] alexa device is alexa
[14.1.2019, 18:45:58] [FHEM] homebridgeMapping: #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozentnpm install -g alexa-fhem@0.5.7Internals:
CFGFN FHEM/fhem_WOHN_SCHLAF.cfg
NAME Fernseher
NR 274
STATE on
TYPE dummy
READINGS:
2019-01-14 21:06:34 state on
Attributes:
DbLogExclude .*
alexaRoom Wohnzimmer
genericDeviceType switch
icon it_television
room Alexa,Homekit
setList on off
webCmd on:offZitatAndre hat gerade 0.5.8 released und ist für nichts verantwortlich :-)
sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregisterset restart gemacht
# npm install -g alexa-fhem
(node:22482) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
{
"connections": [{
"port": "8083",
"server": "127.0.0.1",
"name": "FHEM",
"uid": 1000,
"ssl": true,
"filter": "alexaName=..*",
"webname": "fhem"
}],
"sshproxy": {
"ssh": "/usr/bin/ssh",
"description": "FHEM Connector",
"bind-ip": "127.0.0.1",
"port": 44115
}
}Zitat von: Kusselin am 14 Januar 2019, 22:20:33
Ha justme..deshalb frage ich doch hier im Board... seit..vor lauter aufregung mach ich noch _ und Großbuchstaben??? Ist richtig wenn man alles klein schreibt und mit Leerzeichen..richtig?
Gruss
Zitat von: gvzdus am 14 Januar 2019, 22:10:33:D :D :D geht - keys sind da => Rotwein und morgen weiter! Danke und gute Nacht!
@det : Bier ist schon länger offen, aber noch kann ich schreiben (Merkt man ja immer erst viel zu spät, wann es nicht mehr geht, rückwirkend betrachtet).
Zur Sache: Die config.json (neu: ~/alexa-fhem.cfg) "sticht" die Kommandozeile. Und der Config, die gezogen wird und in "Passed config" ausgegeben wird, steht, formatiert:Code Auswählen{
"connections": [{
"port": "8083",
"server": "127.0.0.1",
"name": "FHEM",
"uid": 1000,
"ssl": true,
"filter": "alexaName=..*",
"webname": "fhem"
}],
"sshproxy": {
"ssh": "/usr/bin/ssh",
"description": "FHEM Connector",
"bind-ip": "127.0.0.1",
"port": 44115
}
}
connections ist die Verbindung zu FHEMWEB, und wenn da in der Config "ssl: true" steht, wird er es "immer" mit SSL versuchen. Vermutlich bist Du glücklich, wenn das "ssl" auf false steht oder gelöscht wurde. Dann bliebe noch die Frage: "Wie kam es dahin"?
Zitat von: MadMax-FHEM am 14 Januar 2019, 22:16:21
Nach dem Vergeben der Attribute ein reload von alexa durchgeführt?
Gruß, Joachim
[2019-1-15 06:44:48] <<<< [ssh] {"directive":{"header":{"namespace":"Alexa.ThermostatController","name":"SetTargetTemperature","payloadVersion":"3"
,"messageId":"4e67d0f6-28f6-46c9-a705-636d84e5f8c6","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"13DA00-AAAAAAAAAAAAAAAAA"},"endpointId":"MAX_14694d","cookie":{"device":"ug_buero_t1"}},"payload":{"targetSetpoint":{"value":15,"scale":"CELSIUS"}}}}
Zitat von: mark79 am 15 Januar 2019, 09:43:01Über Routinen lassen sich quasi als Umweg eigene Kommandos anlegen (statt einen Customer Skill zu nutzen).
Was genau macht ihr mit den Routinen, habt ihr ein paar Beispiele? Ich habe gesehen, das im alexa Device "gutenMorgen" unter fhemIntents eingetragen ist. Nur wie nutzt man das?
Wenn ich Alexa einen guten morgen wünsche und im Event monitor schaue, taucht das dort nichts auf.
Oder ist das nur dafür gedacht um in der Alexa APP, aus vorhandenen Geräten eine Routine zu basteln?
So läufts echt prima und schaltet gefühlt viel schneller als ha-bridge. :)
Zitat von: Kusselin am 15 Januar 2019, 10:14:12Im Prinzip so wie oben beschrieben ;-)
Hallo balli1187,
wie würde denn solch ein Kommando aussehen wenn man sich die geburtstage ansagen lassen wollte?
Gruss
Internals:
IODev myBroker
NAME AZ.BUERO
NR 91
STATE OFF
TYPE MQTT_DEVICE
retain *:1
Helper:
DBLOG:
ENERGY_Power:
logdb:
TIME 1547544690.46999
VALUE 0
ENERGY_Today:
logdb:
TIME 1547543663.94601
VALUE 0.005
ENERGY_Voltage:
logdb:
TIME 1547544674.42888
VALUE 0
LIGHT:
logdb:
TIME 1547544688.33909
VALUE OFF
state:
logdb:
TIME 1547544688.30246
VALUE OFF
READINGS:
2019-01-15 10:31:30 ENERGY {"Time":"2019-01-15T10:31:28","ENERGY":{"Total":0.095,"Yesterday":0.026,"Today":0.005,"Power":0,"Factor":0.00,"Voltage":0,"Current":0.088}}
2019-01-10 07:35:26 ENERGY_ApparentPower 0
2019-01-15 10:31:30 ENERGY_Power 0
2019-01-10 07:35:26 ENERGY_ReactivePower 0
2019-01-15 10:31:30 ENERGY_Today 0.005
2019-01-15 10:31:30 ENERGY_Voltage 0
2019-01-15 10:31:30 ENERGY_Yesterday 0.026
2019-01-10 07:40:35 INFO2 {"WebServerMode":"Admin","Hostname":"sonoff_pow_c-5389","IPAddress":"192.168.2.20"}
2019-01-15 10:31:28 LIGHT OFF
2019-01-15 09:24:08 LWT Online
2019-01-15 10:31:28 state OFF
2019-01-15 10:31:30 transmission-state incoming publish received
message_ids:
publishSets:
:
topic cmnd/sonoff_pow_c/POWER
values:
ON
OFF
sets:
OFF
ON
subscribe:
tele/sonoff_pow_c/SENSOR
tele/sonoff_pow_c/INFO2
cmnd/sonoff_pow_c/POWER
tele/sonoff_pow_c/LWT
stat/sonoff_pow_c/POWER
subscribeExpr:
^tele\/sonoff_pow_c\/SENSOR$
^tele\/sonoff_pow_c\/INFO2$
^cmnd\/sonoff_pow_c\/POWER$
^tele\/sonoff_pow_c\/LWT$
^stat\/sonoff_pow_c\/POWER$
subscribeQos:
cmnd/sonoff_pow_c/POWER 0
stat/sonoff_pow_c/POWER 0
tele/sonoff_pow_c/INFO2 0
tele/sonoff_pow_c/LWT 0
tele/sonoff_pow_c/SENSOR 0
subscribeReadings:
cmnd/sonoff_pow_c/POWER:
cmd
name LIGHT
stat/sonoff_pow_c/POWER:
cmd
name state
tele/sonoff_pow_c/INFO2:
cmd
name INFO2
tele/sonoff_pow_c/LWT:
cmd
name LWT
tele/sonoff_pow_c/SENSOR:
cmd
name ENERGY
Attributes:
DbLogExclude transmission-state,ENERGY
IODev myBroker
alexaName Büro
alias Büro
devStateIcon ON:rc_GREEN:OFF OFF:rc_RED:ON
event-on-change-reading .*
genericDeviceType switch
group Strom
homebridgeMapping On=state,cmdOn=ON,cmdOff=OFF
publishSet ON OFF cmnd/sonoff_pow_c/POWER
retain 1
room zzz_ha-bridge,Buero,ZZZ_System->MQTT,Wohnung
stateFormat state
subscribeReading_ENERGY tele/sonoff_pow_c/SENSOR
subscribeReading_INFO2 tele/sonoff_pow_c/INFO2
subscribeReading_LIGHT cmnd/sonoff_pow_c/POWER
subscribeReading_LWT tele/sonoff_pow_c/LWT
subscribeReading_state stat/sonoff_pow_c/POWER
[15.1.2019, 10:34:00] [FHEM] caching: On: 1 (as number; from 'OFF')
HOWTO for public FHEM Connector skill: FHEM_Connector
HOWTO for privte skills: alexa-fhem/usr/local/lib/node_modules/alexa-fhem/lib/user.js:70
(async () => {
^
SyntaxError: Unexpected token (
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:549:28)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:11:29)
/usr/local/lib/node_modules/alexa-fhem/lib/user.js:70
(async () => {
^Zitat von: justme1968 am 15 Januar 2019, 10:48:38
bist du sicher mit den links? bei mir zeigen die auf zwei unterschiedliche artikel
39_alexa.pm 18257 2019-01-14 19:57:18Z justme1968
Zitat von: Esjay am 14 Januar 2019, 18:20:10Code Auswählen1/14/2019, 6:07:56 PM] 39_alexa.pm is new version: 324
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=set%20alexa%20proxyToken%201xxxxxxxxxxxxx3A1&fwcsrf=csrf_20xxxxxxxxxxx22&XHR=1
[1/14/2019, 6:07:57 PM] BearerToken 'xxxxxxxxxxxxx' read from alexa
[1/14/2019, 6:07:57 PM] [FHEM] got .eventToken
[1/14/2019, 6:07:57 PM] refreshing token
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=set%20alexa%20proxyKey%201xxxxxxxxxxxxxxxxxxxxxx3A1&fwcsrf=csrf_2050xxxxxxxxxxxxxxx&XHR=1
[1/14/2019, 6:07:57 PM] executing: http://localhost:8083/fhem?cmd=%7B%20FW_directNotify(%22%23FHEMWEB%3AWEB%22%2C%20%22location.reload('true')%22%2C%20%22%22)%20%7D&fwcsrf=csrf_20xxxxxxxxx2&XHR=1
[1/14/2019, 6:07:57 PM] SSH proxy configuration set up done
[1/14/2019, 6:07:57 PM] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[1/14/2019, 6:07:57 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20starting,%20starting%20SSH;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_20xxxxxxxxxxx2&XHR=1
[1/14/2019, 6:07:57 PM] SSH setup completed with new bearer token
[1/14/2019, 6:07:57 PM] SSH: Pseudo-terminal will not be allocated because stdin is not a terminal.
[1/14/2019, 6:07:57 PM] got fresh token
[1/14/2019, 6:07:58 PM] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[1/14/2019, 6:07:58 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%201;;undef%7D;setreading%20alexa%20alexaFHEM.ProxyConnection%20running,%20SSH%20connected;%7B$defs%7Balexa%7D-%3E%7B%22active%22%7D%20=%200;;undef%7D&fwcsrf=csrf_20xxxxxxxxxxxxx2&XHR=1
[1/14/2019, 6:07:58 PM] SSH: Welcome at the reverse proxy!
This pseudoshell does not react to any input - do not get irritated.
[1/14/2019, 6:08:00 PM] client not authorized: {"error_index":"yxxxxxxxxxxxxxxxxxxxxxxxckqQKa5TrA==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:08:00 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"b3xxxxxxxxxxxa1ab6c"},"payload":{}}
[1/14/2019, 6:08:02 PM] client not authorized: {"error_index":"wQLxxxxxxxxxxxxxxxxxxxxxxxizjbUOpVXA==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/14/2019, 6:08:02 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"23xxxxxxxf9e25"},"payload":{}}
[1/14/2019, 6:08:29 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
response :{"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"9cxxxxxxxxxxb05"},"payload":{}}
[1/14/2019, 6:12:42 PM] Received Directive: {"directive":{"header":{"namespace":"Alexa.Discovery","name":"Discover","payloadVersion":"3","messageId":"7a704d14-f5ec-455d-9c49-8a814836db4f"},"payload":{"scope":{"type":"BearerToken","token":"1xxxxxxxxxxxxxxxxxxxxxxx"}}}}
[1/14/2019, 6:12:42 PM] found 19 device(s)
response :{"event":{"header":{"namespace":"Alexa.Discovery","name":"Discover.Response","payloadVersion":"3","messageId":"6fxxxxxxxxxxxxxa6"},"payload":{"endpoints":[{"endpointId":"Ambilight","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"ambilight","description":"n: Ambilight, r: hidden,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Ambilight"}},{"endpointId":"Fernseher","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"fernseher","description":"n: Fernseher, r: homekit,wohnzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Fernseher"}},{"endpointId":"GuteNachtAlexa","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"gutenacht","description":"n: GuteNachtAlexa, r: dummys,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"GuteNachtAlexa"}},{"endpointId":"HUEDevice12","manufacturerName":"FHEMHUEDevice","modelName":"FHEMPlug 01","version":"<unknown>","friendlyName":"terrarium","description":"n: HUEDevice12, r: homekit,spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"HUEDevice12"}},{"endpointId":"HUEDevice9","manufacturerName":"FHEMHUEDevice","modelName":"FHEMLWB010","version":"<unknown>","friendlyName":"nachttisch katha","description":"n: HUEDevice9, r: schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["LIGHT"],"cookie":{"device":"HUEDevice9"}},{"endpointId":"Heimkino","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"heimkino","description":"n: Heimkino, r: spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Heimkino"}},{"endpointId":"00:17:88:01:00:64:4d:05-0f","manufacturerName":"FHEMHUEDevice","modelName":"FHEMLWB001","version":"<unknown>","friendlyName":"nachttisch stephan","description":"n: Hue_HUEDevice7, r: schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["LIGHT"],"cookie":{"device":"Hue_HUEDevice7"}},{"endpointId":"MAX_007fbb","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung arbeitszimmer","description":"n: MAX_007fbb, r: arbeitszimmer,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_007fbb"}},{"endpointId":"MAX_0764eb","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung schlafzimmer","description":"n: MAX_0764eb, r: homekit,schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_0764eb"}},{"endpointId":"MAX_07a38e","manufacturerName":"FHEMMAX","modelName":"FHEMHeatingThermostat","version":"<unknown>","friendlyName":"heizung spielzimmer","description":"n: MAX_07a38e, r: kinderzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"},{"name":"thermostatMode"}],"configuration":{"supportsScheduling":false,"supportedModes":["CUSTOM","HEAT","ECO","AUTO"]},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"MAX_07a38e"}},{"endpointId":"Maxtemp","manufacturerName":"FHEMreadingsProxy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"dachboden","description":"n: Maxtemp, r: spielzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"Maxtemp"}},{"endpointId":"IT_00000F0FFF_0F_F0","manufacturerName":"FHEMIT","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"schuhschrank","description":"n: Schuhschrank, r: flur,steckdosen,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Schuhschrank"}},{"endpointId":"StaubsaugerEG","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"staubsauger erdgeschoss","description":"n: StaubsaugerEG, r: erdgeschoss","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"StaubsaugerEG"}},{"endpointId":"StaubsaugerOG","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"staubsauger obergeschoss","description":"n: StaubsaugerOG, r: obergeschoss","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"StaubsaugerOG"}},{"endpointId":"TempArbeitszimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur arbeitszimmer","description":"n: TempArbeitszimmer, r: arbeitszimmer,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempArbeitszimmer"}},{"endpointId":"TempBadezimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur badezimmer","description":"n: TempBadezimmer, r: bad,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempBadezimmer"}},{"endpointId":"TempGaesteWC","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur gaestebad","description":"n: TempGaesteWC, r: gaestewc,homekit,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempGaesteWC"}},{"endpointId":"TempSchlafzimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur schlafzimmer","description":"n: TempSchlafzimmer, r: homekit,schlafzimmer,alexa","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempSchlafzimmer"}},{"endpointId":"TempWohnzimmer","manufacturerName":"FHEMLaCrosse","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"temperatur wohnzimmer","description":"n: TempWohnzimmer, r: alexa,homekit,wohnzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"TempWohnzimmer"}}]}}}
2019-01-14 18:12:56 caching: TempArbeitszimmer-temperature: 22.4
2019-01-14 18:12:56 caching: TempWohnzimmer-temperature: 23.6
2019-01-14 18:13:01 caching: TempSchlafzimmer-temperature: 21.5
Leider hat sich an dem Problem nichts geändert. Es geht hin und her!
Die Mailadresse, von der aus du die Fhemlazy Einladung verschickt hast?
Grüße
Zitat von: gvzdus am 15 Januar 2019, 10:39:20
Hi, sorry, bitte nicht hier.
Andre und ich schauen bei jedem Posting hier im Thread hektisch nach, ob wir was verbessern müssen.
Da sind Postings wie Deins "Fehlalarme".
39_alexa.pm 18257 2019-01-14 19:57:18Z justme1968[1/15/2019, 3:50:46 PM] BearerToken '...D5CF9' read from alexa
[1/15/2019, 3:50:46 PM] [FHEM] got .eventToken
[1/15/2019, 3:50:46 PM] refreshing token
[1/15/2019, 3:50:46 PM] 39_alexa.pm is new version: true
[1/15/2019, 3:50:46 PM] sshautoconf: completed successfully
[1/15/2019, 3:50:46 PM] *** SSH: proxy configuration set up done
[1/15/2019, 3:50:46 PM] Reading alexaFHEM.ProxyConnection set to starting, starting SSH
[1/15/2019, 3:50:46 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%2C%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_327686427377525&XHR=1
[1/15/2019, 3:50:47 PM] got fresh token
[1/15/2019, 3:50:47 PM] Reading alexaFHEM.ProxyConnection set to running, SSH connected
[1/15/2019, 3:50:47 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%2C%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_327686427377525&XHR=1
[1/15/2019, 3:50:47 PM] *** SSH: proxy connection established
[1/15/2019, 3:50:47 PM] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
[1/15/2019, 3:51:36 PM] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"4a99fc28-494c-4f17-98e3-c310718b396a","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1XXXXX-XXXXXXXXXXXX616B"},"endpointId":"TempBadezimmer","cookie":{"device":"TempBadezimmer"}},"payload":{}}}
[1/15/2019, 3:51:36 PM] client not authorized: {"error_index":"eSiKbi04cgTVXWR-mXmY2QAAAAAAAAAB5_coxsb3rMHjdCe5ZbP8VEgyFT2PPwGjGuiUx3dRGiqdfCi_Ln1PvXZJOIZ8qBWf8CQpGFYWRa4NeZMkQBo9c4IhEK5y5GeuNg1g0YEiNxr3yn49qxf-JfqH6tVt5p7zqJix8VVd8yGAwAt7WH6s_xvtes1pPb3fRnfb84YVUsrqM91XY-fZx7aSDIg3mp_lI_v5IIHtD4Cp3KCRwsR1Uw==","error_description":"The request has an invalid parameter : access_token","error":"invalid_token"}
[1/15/2019, 3:51:36 PM] ERROR: InvalidAccessTokenError from 127.0.0.1
[1/15/2019, 3:51:36 PM] <<<< [ssh] {"header":{"namespace":"Alexa.ConnectedHome.Control","name":"InvalidAccessTokenError","payloadVersion":"2","messageId":"c8dc5aab-2f37-4af3-a3a4-04d2b6d18156"},"payload":{}}sudo -u fhem ssh -p 58824 fhem-va.fhem.de statusRegistered.
Registered on 2019-01-15T14:30:40Z.2019-01-15 14:30:40 INFO Server:130 - Authenticated Session: /79.236.56.205:44320 with PublicKeyHC 13XXXX
2019-01-15 14:30:40 INFO Server:130 - Authenticated Session: /79.236.56.205:44320 with PublicKeyHC 13XXXX
2019-01-15 14:30:40 INFO ServerUserAuthService:322 - Session fhem@/79.236.56.205:44320 authenticated
2019-01-15 14:30:40 INFO ControlCommand:116 - Request register keyhash=84b614e50d9a1684c1XXXXXXXXXXXX768530cc3e from ServerSessionImpl[fhem@/79.236.56.205:44320] answered with out=Registered. Your key to activate the FHEMlazy skill with Alexa etc. is:\n\n\n XXXXXX-...\n\nNote it down NOW!\nThere is no way to get it again apart from registrating yourself again!\n\nYour are now set up to create the reverse-tunnel to your computer with\n\nssh -p 58824 -R 1234:localhost:3000 fhem-va.fhem.de\n\n(assuming that alexa-fhem is running on localhost:3000)\n, err=
2019-01-15 14:33:13 INFO ControlCommand:116 - Request status from ServerSessionImpl[fhem@/79.236.56.205:45000] answered with out=Registered.\nRegistered on 2019-01-15T14:30:40Z.\n, err=
2019-01-15 14:35:51 INFO ControlCommand:116 - Request status from ServerSessionImpl[fhem@/79.236.56.205:46104] answered with out=Registered.\nRegistered on 2019-01-15T14:30:40Z.\n, err=
2019-01-15 14:36:22 INFO ControlCommand:116 - Request status from ServerSessionImpl[fhem@/79.236.56.205:46218] answered with out=Registered.\nRegistered on 2019-01-15T14:30:40Z.\n, err=
2019-01-15 14:50:46 INFO ControlCommand:116 - Request status from ServerSessionImpl[fhem@/79.236.56.205:50968] answered with out=Registered.\nRegistered on 2019-01-15T14:30:40Z.\n, err=
2019-01-15 14:56:54 INFO ControlCommand:116 - Request status from ServerSessionImpl[fhem@/79.236.56.205:52824] answered with out=Registered.\nRegistered on 2019-01-15T14:30:40Z.\n, err=
Zitat von: justme1968 am 14 Januar 2019, 17:34:37
1. ja. ist bekannt. das device dynamisch temporary angelegt wenn alexa-fhem läuft und sonst beendet. deshalb lassen sich keine attribute setzen und das device wird auch nicht gespeichert.
2. dann solltest du mal im log schauen woran es liegt. es soll automatisch gestartet werden.
Zitat von: justme1968 am 16 Januar 2019, 10:37:55
der fhem port wird doch automatisch aus deinem laufendem fhem ausgelesen.
falls das aus irgendeinem grund nicht passt editierst du das config file per edit files oder von hand und sagst ein mal start.
130E36-
131C16-
131CF4-
1336F8-
13B3D8-
141489-Zitat von: Loki am 16 Januar 2019, 10:43:16
Meine Instanz läuft über 2 Ports. Einer für ein lokalen Zugriff ohne Login und ein anderer für den externen Zugriff mit Login und eingeschränkten Rechten. Bei der Installation wurde der zweite Port in die conf übernommen.
Zitat von: balli1187 am 15 Januar 2019, 08:33:28
Moin,
Ich habe gestern von einer recht alten Version (0.4.4) auf diese neue Version geupdated. Alles läuft aktuell und funktioniert. HERZLICHEN DANK an die Entwickler.
Dennoch zwei Fragen:
- wie wäre das richtige Vorgehen, wenn ich von meinem eigenen (Entwickler)Skill auf den offiziellen Skill wechseln möchte? Würde was dagegen sprechen?
- das attr room lässt sich für das log nicht setzen. Soweit ich gelesen hab, ist das mehr oder weniger beabsichtigt. Ließe sich das ändern? Meine ordnungszwang hat was gegen das ,,unsorted" ;-)
set alexa stopsudo npm update -g alexa-fhemZitat von: gvzdus am 16 Januar 2019, 19:59:01Danke für die Antwort.
@balli1187: Der Vorteil des Entwickler-Skills ist, dass Du an allen Ecken basteln kannst wie Du möchtest. Und, dass Du Dir theoretisch eine sicherere Lösung schaffen kannst, ohne Dritte wie den Verein, Andre & mich ins Spiel zu bringen.
Den Vorteil der FHEM-Connector-Lösung sehe ich darin:
- Keine Gedanken mehr über den offenen Port
- Flotter, weil typischerweise die Lambda-Funktion "noch da ist" (sogenannte Cold-Start-Thematik) und die Authentifizierung nur in eine Richtung verläuft
- "Politisches Gewicht" ggü. Amazon
Zitat von: justme1968 am 17 Januar 2019, 11:45:06
ja. das ist gewollt.
ab heute hast das device überhaupt keinen raum mehr und ist nicht sichtbar.
zugriff nur über den link oben auf der alexa detail Seite.
[2019-1-17 11:36:02] BearerToken '...1B2C2' read from alexa
2019-01-17 11:36:02 caching: sz_Wandthermostat-temperature: 18.0
2019-01-17 11:36:02 caching: sz_Wandthermostat-mode: auto
2019-01-17 11:36:02 caching: sz_Wandthermostat-desiredTemperature: 12.0
2019-01-17 11:36:02 caching: sz_Wandthermostat-firmware: 1.0
2019-01-17 11:36:02 caching: sz_Wandthermostat-battery: ok
[2019-1-17 11:36:02] [FHEM] CurrentHeatingCoolingState [undefined]
[2019-1-17 11:36:02] [FHEM] CurrentTemperature [temperature]
[2019-1-17 11:36:02] [FHEM] TargetHeatingCoolingState [mode]
[2019-1-17 11:36:02] [FHEM] TargetTemperature [desiredTemperature]
[2019-1-17 11:36:02] [FHEM] FirmwareRevision [firmware]
[2019-1-17 11:36:02] [FHEM] StatusLowBattery [battery]
Zitat von: Esjay am 16 Januar 2019, 20:16:04Das Wiki bin ich ja soweit durchgegangen, um auf die aktuelle Version zu kommen. Ich habe mich nur noch nicht getraut die Verbindung mit dem Connector herzustellen, weil ich nicht wusste ob sich das mit der alten installation in die Quere kommt.
Lösch den alten Ordner alexa-fhem,lösch deine alte config ( oder auch nicht), mach den autostart der alten Version rückgängig, schließe deinen aws account, schick Amazon ne Mail mit der Bitte deinen dev account zu löschen, und geh dann das Wiki durch.
Grüße
ZitatLightScene Devices aus FHEM (ab alexa-fhem version 0.5.8 )
werden mit genericDeviceType scene als Szenen eingebunden
über alexaRoom kann der name um einen Ort ergänzt werden
Szenen aus einer LightScene lassen sich nur einschalten
Wichtig: Ein Skill darf nur 12 Szenen automatisch erkennen und einbinden.
[2019-1-17 14:14:52] [FHEM] wz_szene is scene
[2019-1-17 14:14:52] [FHEM] wz_szene has
[2019-1-17 14:14:52] [FHEM] On [undefined;scene,undefined]
2019-01-17 14:14:52 caching: wz_szene-state: abwesendZitat von: justme1968 am 17 Januar 2019, 15:35:42Ja da gibts 7 Szenen drin:
@binford6000: und hast du in der LightScene auch schon etwas abgespeichert?
Internals:
DEF wz_kugel_licht wz_kugel2_licht wz_stehlampe_licht wz_strasse_licht wz_treppe_licht wz_vase_licht wz_vase_licht
HAS_DataDumper 1
HAS_JSON 1
NAME wz_szene
NR 133
NTFY_ORDER 50-wz_szene
STATE abwesend
TYPE LightScene
mayBeVisible 1
CONTENT:
wz_kugel2_licht 1
wz_kugel_licht 1
wz_stehlampe_licht 1
wz_strasse_licht 1
wz_treppe_licht 1
wz_vase_licht 1
OLDREADINGS:
2019-01-17 15:01:32 state anwesend_alle
READINGS:
2019-01-17 15:21:59 state abwesend
SCENES:
abwesend:
Steckdose1 off
wz_vase_licht off
wz_kugel2_licht:
icon light_light_dim_00
state off
wz_kugel_licht:
icon light_light_dim_00
state off
wz_stehlampe_licht:
icon light_light_dim_00
state off
wz_strasse_licht:
icon light_light_dim_00
state off
wz_treppe_licht:
icon light_light_dim_00
state off
anwesend:
Steckdose1 on
wz_vase_licht on
wz_kugel2_licht:
icon dim12%
state bri 24 : xy 1,1
wz_kugel_licht:
icon light_light_dim_00
state off
wz_stehlampe_licht:
icon dim56%
state bri 153
wz_strasse_licht:
icon light_light_dim_00
state off
wz_treppe_licht:
icon light_light_dim_00
state off
anwesend_alle:
Steckdose1 on
wz_vase_licht on
wz_kugel2_licht:
icon dim12%
state bri 24 : xy 0.622313,0.330581
wz_kugel_licht:
icon dim75%
state bri 200 : hue 14592 : sat 143
wz_stehlampe_licht:
icon dim56%
state bri 153
wz_strasse_licht:
icon dim43%
state bri 115 : hue 14592 : sat 143
wz_treppe_licht:
icon dim75%
state bri 200 : hue 14592 : sat 143
anwesend_alle_farbe:
wz_vase_licht off
wz_kugel2_licht:
icon dim12%
state bri 24 : xy 0.622313,0.330581
wz_kugel_licht:
icon light_light_dim_100@red
state bri 254 : hue 14592 : sat 143
wz_stehlampe_licht:
icon dim56%
state bri 153
wz_strasse_licht:
icon dim68%
state bri 194 : hue 14592 : sat 143
wz_treppe_licht:
icon light_light_dim_100@red
state bri 254 : hue 7268 : sat 183
kino:
Steckdose1 on
wz_vase_licht on
wz_kugel2_licht:
icon light_light_dim_00
state off
wz_kugel_licht:
icon dim37%
state bri 90 : ct 365
wz_stehlampe_licht:
icon dim12%
state bri 24
wz_strasse_licht:
icon dim12%
state bri 24 : ct 365
wz_treppe_licht:
icon dim12%
state bri 24 : ct 365
panik:
wz_vase_licht off
wz_kugel2_licht:
icon light_light_dim_100@red
state bri 254 : xy 0.622298,0.330566
wz_kugel_licht:
icon light_light_dim_100@red
state bri 254 : ct 365
wz_stehlampe_licht:
icon light_light_dim_100@red
state bri 254
wz_strasse_licht:
icon light_light_dim_100@red
state bri 254 : ct 365
wz_treppe_licht:
icon light_light_dim_100@red
state bri 254 : ct 365
schlafen:
Steckdose1 off
wz_vase_licht off
wz_kugel2_licht:
icon dim12%
state bri 24 : xy 0.622283,0.330566
wz_kugel_licht:
icon light_light_dim_00
state off
wz_stehlampe_licht:
icon light_light_dim_00
state off
wz_strasse_licht:
icon light_light_dim_00
state off
wz_treppe_licht:
icon light_light_dim_00
state off
devices:
wz_kugel2_licht
wz_kugel_licht
wz_stehlampe_licht
wz_strasse_licht
wz_treppe_licht
wz_vase_licht
Attributes:
alexaName living
alexaRoom Wohnzimmer
async_delay 0.25
genericDeviceType scene
group Lichtszenen
icon audio_eq
oldreadings state
room 20_Licht
webCmd sceneAlexa, aktiviere Szene anwesend wohnzimmer...
Alexa, schalte anwesend wohnzimmer ein...[2019-1-17 16:36:23] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20wz_szene%20scene%2Banwesend&fwcsrf=csrf_213722044830349&XHR=1Zitat von: meier81 am 17 Januar 2019, 19:40:49Klingt nach einem älteren Modul, da hatte ich auch Probleme mit. Welche Version nutzt Du denn?
Erstmal vorneweg: Echt super Arbeit das Modul, ganz einfache Installation und funktioniert super.
Mit ist allerdings heute aufgefallen das ich über eine ganz blöde Konstellation gestolpert bin. Modul ist installiert und läuft einwandfrei. Habe dann eine Kleinigkeit direkt in der fhem.cfg geändert und dann anschließend mit dem Button "Save fhem.cfg" gespeichert (mache ich öfters mal bei kleinen Änderungen). Dann viel mir auf das mir links im Menü mit dem "Save config" Button angezeigt wird es gäbe eine ungespeicherte Änderung, und nun ist das Alexa-Modul verschwunden.
Bin dann natürlich nicht auf speichern sondern habe ein "rereadcfg" gemacht, dann war die Konfiguration wieder da.
Kann das von euch jemand reproduzieren bzw. sich mal den Fehler anschauen?
Gruß Markus
Internals:
CHANGED
DEF 06
IODev myJeeLink
LASTInputDev myJeeLink
LaCrosse_lastRcv 2019-01-17 20:03:15
MSGCNT 1866
NAME LaCrosse_06
NR 114
STATE T: 24.5
TYPE LaCrosse
addr 06
battery_new 0
corr1 0
corr2 0
myJeeLink_MSGCNT 1866
myJeeLink_RAWMSG OK 9 6 1 4 221 106
myJeeLink_TIME 2019-01-17 20:03:15
previousH 106
previousT 24.5
sensorType 0=T(H)
Helper:
DBLOG:
state:
myDbLog:
TIME 1547751374.61485
VALUE T
temperature:
myDbLog:
TIME 1547751682.18364
VALUE 24.5
READINGS:
2019-01-17 20:03:15 battery ok
2018-12-06 21:19:20 dewpoint 23.8
2018-12-06 21:19:20 humidity 98
2019-01-17 19:56:14 state T: 24.5
2019-01-17 20:03:15 temperature 24.5
2018-10-22 01:07:48 temperature0 23.3
Attributes:
IODev myJeeLink
alexaName Temperatur
alexaRoom Wohnzimmer
alias Wohnzimmer
event-min-interval humidity:300,state:300,temperature:300
event-on-change-reading battery
event-on-update-reading humidity,state,temperature
genericDeviceType thermometer
group Aktuelle Werte
icon scene_livingroom
temperatur
n: LaCrosse_06, r: wohnzimmer
Zitat von: justme1968 am 17 Januar 2019, 20:07:08
@meier81: bitte versuch das mal nachzustellen. ich wüsste nicht wie das alexa device ohne delete im laufenden betrieb verschwinden sollte.
Zitat...dann "Edit files", dann "fhem.cfg", dann "Save fhem.cfg",...
Zitat von: binford6000 am 18 Januar 2019, 07:32:02Moin
Hallo Markus,
- und sorry fürs OT -, wenn du die fhem.cfg in Ruhe lässt und alle Änderungen in FHEMWEB
machst (DEF oder RAW), ersparst du dir jede Menge Ärger! Hab ich auch früher gemacht und bin bekehrt worden!
Nur mal so als freundlicher Hinweis ;)
VG Sebastian
2019-01-18 11:40:57 caching: st_Balkontuer-state: closed
2019-01-18 11:40:57 caching: st_Balkontuer-firmware: 1.3
2019-01-18 11:40:57 caching: st_Balkontuer-battery: ok
[2019-1-18 11:40:57] [FHEM] CurrentDoorState [state]
[2019-1-18 11:40:57] [FHEM] ContactSensorState [state]
[2019-1-18 11:40:57] [FHEM] FirmwareRevision [firmware]
[2019-1-18 11:40:57] [FHEM] StatusLowBattery [battery]
[2019-1-18 11:40:57] [FHEM] st_Balkontuer has
[2019-1-18 11:40:57] [FHEM] st_Balkontuer is ContactSensor
[2019-1-18 11:40:57] [FHEM] homebridgeMapping: ContactSensorState=state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTED
Zitat von: justme1968 am 18 Januar 2019, 11:50:28
was geht steht im wiki.
batterien gehen aktuell nur mit custom.
Zitat
elektrische Türschlösser
genericDeviceType: lock
Thermostate
Über genericDeviceType thermometer
...
[2019-1-18 11:40:57] [FHEM] CurrentHeatingCoolingState [undefined]
[2019-1-18 11:40:57] [FHEM] CurrentTemperature [temperature]
[2019-1-18 11:40:57] [FHEM] TargetHeatingCoolingState [mode]
2019-01-18 12:13:53 caching: HM_Haustuerschloss-state: locked
2019-01-18 12:13:53 caching: HM_Haustuerschloss-battery: ok
[2019-1-18 12:13:53] [FHEM] LockTargetState [state]
[2019-1-18 12:13:53] [FHEM] LockCurrentState [state]
[2019-1-18 12:13:53] [FHEM] TargetDoorState []
[2019-1-18 12:13:53] [FHEM] StatusLowBattery [battery]
[2019-1-18 12:13:53] [FHEM] HM_Haustuerschloss has
[2019-1-18 12:13:53] [FHEM] HM_Haustuerschloss is lock
2019-1-18 12:48:41] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:48:41.919Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"bd1ebdbe-6ac3-475b-9eb6-235a939d9b87","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:48:41] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:50:48] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:50:48.373Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"25b14cea-9857-45ff-a3c0-4cf675596bba","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:50:48] [FHEM] caching: LockCurrentState: 1 (as number; from 'unlocked')
[2019-1-18 12:50:48] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"64817d75-e9dc-4903-8dfa-0c2fe7ffeb45","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
2019-01-18 12:50:45 caching: HM_Haustuerschloss-state: unlocked
[2019-1-18 12:52:34] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:52:34.415Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"24abeeea-20c0-437e-8180-18a82f414ce6","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:52:34] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:52:34] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"70f17098-0b3c-4b31-b7d8-3469e98cdebd","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
2019-01-18 12:52:31 caching: HM_Haustuerschloss-state: locked
[2019-1-18 12:54:44] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:44.559Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"78281718-492f-4f58-bf5e-c1eb44c7d9b2","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:44] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:54:44] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"f6367325-c379-46ba-aba9-c1e0d1bfe0a0","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:41] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:41.568Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"67a042f5-6c09-4f3f-811d-e1fc3768b5b0","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:41] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:54:41] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"2fe8fff6-7ec7-467e-8173-952628e33749","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:35] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:35.535Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"5db2c5fa-f393-4321-a489-45b478881561","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:35] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:54:35] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"f30919ee-84c8-49c1-a4fa-62e3c54e2242","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:32] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:32.531Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"3e65cda4-047a-4d83-b9c8-97d8059d1434","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:32] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:54:32] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"e1b8d370-ef28-4e07-b0c1-f64f1ff266c6","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:29] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:29.517Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"971663ca-ccdc-49ee-ab3c-153ef0be2127","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:29] [FHEM] caching: LockCurrentState: 1 (as number; from 'locked')
[2019-1-18 12:54:29] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"ade3b505-133d-4914-bb5d-46e49805e6c3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
2019-01-18 12:54:26 caching: HM_Haustuerschloss-state: locked
[2019-1-18 12:54:26] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:26.503Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"63b7bdda-acd9-4c64-9baf-8c73c1639fda","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:26] [FHEM] caching: LockCurrentState: 1 (as number; from 'unlocked')
[2019-1-18 12:54:26] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"afae3f84-4309-443f-9b33-8bbf8c3ace98","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:23] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:23.538Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"f8503c2b-ea6d-4f49-8600-2cb8cf2273a5","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:23] [FHEM] caching: LockCurrentState: 1 (as number; from 'unlocked')
[2019-1-18 12:54:23] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"28024652-b0a6-4ab8-b175-aaa01f9933b4","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:20] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-18T11:54:20.499Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"StateReport","payloadVersion":"3","messageId":"66197f4b-6130-4223-8817-61fbc2824db3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-18 12:54:20] [FHEM] caching: LockCurrentState: 1 (as number; from 'unlocked')
[2019-1-18 12:54:20] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa","name":"ReportState","payloadVersion":"3","messageId":"252fc5df-7c75-430d-97fa-02ba6e62ab2b","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss","cookie":{"device":"HM_Haustuerschloss"}},"payload":{}}}
[2019-1-18 12:54:17] <<<< [ssh] null
at process.internalTickCallback (internal/process/next_tick.js:72:19)
at endReadableNT (_stream_readable.js:1129:12)
at IncomingMessage.emit (events.js:188:13)
at Server.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:149:33)
at Server.processBody (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:138:31)
at Server.verifyToken (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:1228:23)
at Server.handler (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:2110:51)
at Server.handleLockController (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:3221:16)
[2019-1-18 12:54:17] ReferenceError: name is not defined
[2019-1-18 12:54:17] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20HM_Haustuerschloss%20lock%20locked&fwcsrf=csrf_258010689120090&XHR=1
[2019-1-18 12:54:17] [FHEM] HM_Haustuerschloss: executing set cmd for LockTargetState with value SECURED
Zitat von: justme1968 am 18 Januar 2019, 13:00:13
schick mir mal ein jsonlist2 vom device
{
"Arg":"HM_Haustuerschloss",
"Results": [
{
"Name":"HM_Haustuerschloss",
"PossibleSets":"Zuschließen:noArg Aufschließen:noArg Öffnen:noArg Sperren:noArg Entsperren:noArg clear config control datapoint defaults:noArg devstate:lock,unlock lock:noArg unlock:noArg toggle:noArg",
"PossibleAttrs":"alias comment:textField-long eventMap:textField-long group room suppressReading userReadings:textField-long verbose:0,1,2,3,4,5 IODev ccuaggregate:textField-long ccucalculate:textField-long ccuflags:multiple-strict,ackState,nochn0,trace ccureadingfilter:textField-long ccureadingformat:name,namelc,address,addresslc,datapoint,datapointlc ccureadingname:textField-long ccureadings:0,1 ccuget:State,Value ccuscaleval ccuSetOnChange ccuverify:0,1,2 disable:0,1 hmstatevals:textField-long statevals substexcl substitute:textField-long statechannel statedatapoint controldatapoint stripnumber peer:textField-long event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading DbLogExclude DbLogInclude alexaName alexaRoom cmdIcon devStateIcon devStateIcon:textField-long devStateStyle genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long icon power-off power-on sortby webCmd webCmdLabel:textField-long webcmdDevice widgetOverride userattr",
"Internals": {
".eventMapCmd": "Zuschließen:noArg Aufschließen:noArg Öffnen:noArg Sperren:noArg Entsperren:noArg",
"DEF": "NEQ0683051",
"NAME": "HM_Haustuerschloss",
"NR": "564",
"STATE": "Batterie: ok<br>Zugeschlossen",
"TYPE": "HMCCUDEV",
"ccuaddr": "NEQ0683051",
"ccudevstate": "active",
"ccuif": "BidCos-RF",
"ccuname": "Haustuerschloss",
"ccutype": "HM-Sec-Key-S",
"channels": "2",
"firmware": "2.5",
"statevals": "devstate|lock|unlock"
},
"Readings": {
"0.LOWBAT": { "Value":"ok", "Time":"2019-01-18 10:44:05" },
"1.INHIBIT": { "Value":"no", "Time":"2019-01-18 10:44:05" },
"1.STATE": { "Value":"locked", "Time":"2019-01-18 12:54:26" },
"1.STATE_UNCERTAIN": { "Value":"0", "Time":"2019-01-18 12:54:26" },
"battery": { "Value":"ok", "Time":"2019-01-07 08:26:20" },
"batteryState": { "Value":"ok", "Time":"2019-01-18 10:44:05" },
"control": { "Value":"locked", "Time":"2019-01-18 12:54:26" },
"hmstate": { "Value":"locked", "Time":"2019-01-18 12:54:26" },
"state": { "Value":"locked", "Time":"2019-01-18 12:54:26" },
"statedeutsch": { "Value":"Zugeschlossen", "Time":"2019-01-18 12:54:26" }
},
"Attributes": {
"IODev": "HMCCU2",
"alexaName": "Haustür",
"alexaRoom": "Windfang",
"alias": "Haustürschloss",
"ccureadingfilter": "(STATE|LOWBAT|INHIBIT)",
"ccureadingname": "0.(LOWBAT|LOW_BAT):+batteryState",
"eventMap": "/lock:Zuschließen/unlock:Aufschließen/datapoint 1.OPEN true:Öffnen/datapoint 1.INHIBIT true:Sperren/datapoint 1.INHIBIT false:Entsperren",
"genericDeviceType": "lock",
"group": "Haustür",
"hmstatevals": "ERROR!1:clutch_failure,2:motor_aborted",
"room": "Homematic,Erdgeschoss->Windfang,alexa",
"stateFormat": "Batterie: batteryState<br>statedeutsch",
"statedatapoint": "1.STATE",
"statevals": "lock:false,unlock:true",
"substitute": "STATE!(0|false):locked,(1|true):unlocked,2:open;INHIBIT!(0|false):no,(1|true):yes;STATE_UNCERTAIN!(1|true):manual;DIRECTION!0:none,1:up,2:down,3:undefined;ERROR!0:no,1:clutch_failure,2:motor_aborted;LOWBAT!(1|true):low,(0|false):ok",
"userReadings": "statedeutsch {(ReadingsVal($name,\"state\",\"\") eq \"locked\")?\"Zugeschlossen\":\"Aufgeschlossen\"}",
"webCmd": "Zuschließen:Aufschließen:Öffnen"
}
} ],
"totalResultsReturned":1
}
Zitatdu kommst leider um das setzen von genericDeviceType und homebridgeMapping nicht rum
Sonoff8_Temp genericDeviceType thermometer
attr Sonoff8_Temp homebridgeMapping CurrentTemperature=sonoff8-si7021-temperatureattr Sonoff_S26_4 genericDeviceType outlet
attr Sonoff_S26_4 homebridgeMapping On=state2019.01.18 14:31:36 3: FHEMWEB WEB CSRF error: csrf_231414032366876 ne csrf_153906432030333 for client WEB_192.168.1.28_62962 / command jsonlist2 Sonoff_S26_4 STATE. For details see the csrfToken FHEMWEB attribute.
Zitat von: justme1968 am 18 Januar 2019, 14:24:26
@doman75: die fehlende rückmeldung beim schalten in der app habe ich eben behoben. die falsche status abfrage schaue ich mir noch an.
Zitat von: justme1968 am 18 Januar 2019, 16:07:19Hallo Andre,
es gibt eine neue alexa-fhem version 0.5.10. installation und update wie im wiki beschrieben.
was sich geändert hat steht im ersten beitrag dieses threads: https://forum.fhem.de/index.php/topic,95272.msg880923.html#msg880923 (https://forum.fhem.de/index.php/topic,95272.msg880923.html#msg880923) ganz unten.
[2019-1-18 17:58:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20wz_szene%20scene%2Banwesend&fwcsrf=csrf_213722044830349&XHR=1Zitat von: gvzdus am 18 Januar 2019, 16:32:14
Andre meint den FHEM-Connector-Wiki: https://wiki.fhem.de/wiki/FHEM_Connector
Zitat
root werden
Logge Dich auf dem System ein. Da offizielle Software (nodejs etc.) installiert wird, muss Du root werden
sudo /bin/bash
Zitat von: justme1968 am 18 Januar 2019, 18:27:04
nein. muss es nicht. das ist noch irgend ein altes überbleibsel.
hab es entfernt.
Zitat von: justme1968 am 18 Januar 2019, 18:16:51
ja.ja. ich habs verbaselt.
es gibt seit eben eine 0.5.11 und er es tatsächlich repariert ist
attr global userattr genericDeviceType:switch,outlet,light,blind,scene,speaker,thermostat Zitat von: justme1968 am 18 Januar 2019, 15:57:44
@doman75: im nächsten update (info kommt gleich) sollte beides repariert sein.
wichtig: du steuerst dein schloss per hmccu. die liefert andere readings und werte als native hm devices.
deshalb geht normalerweise keines deiner devices automatisch sondern du brauchst fast immer ein homebridgeMapping.
Zitat von: Nexium am 19 Januar 2019, 09:02:11
Hallo,
hatte es jetzt schon zwei mal das mein alexa "Gerät" einfach verschunden war und ich es mit define alexa alexa erst wieder anlegen musste danach war es sofort wieder da und verbunden.
Wie komm ich denn Aktuell an den Log über FHEM ran?
Zitat von: justme1968 am 18 Januar 2019, 15:57:44
@doman75: im nächsten update (info kommt gleich) sollte beides repariert sein.
wichtig: du steuerst dein schloss per hmccu. die liefert andere readings und werte als native hm devices.
2019-1-19 09:27:18] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.LockController","name":"lockState","value":"UNLOCKED","timeOfSample":"2019-01-19T08:27:18.554Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"9b3c5357-de88-46e9-97b3-bfe1ea5d4875","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"12E9CA-5FB1B3EE6F91B2C2"},"endpointId":"HM_Haustuerschloss"},"payload":{}}}
[2019-1-19 09:27:18] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20HM_Haustuerschloss%20lock%20unlocked&fwcsrf=csrf_419942826549317&XHR=1Zitat von: binford6000 am 19 Januar 2019, 09:11:59
In dem du in der Deviceoverview auf "Logfile" klickst, direkt über dem set Befehl ;)
VG Sebastian
Zitat von: justme1968 am 19 Januar 2019, 10:03:54
@Nexium: wann genau ist etwas verschwunden? verwendest du rereadcfg?
2019.01.18 21:36:28 1: Including ./log/fhem.save
2019.01.18 21:36:28 2: alexa: alexaFHEM deleted
2019.01.19 10:39:34 1: Including ./log/fhem.save
2019.01.19 10:39:35 2: alexa: alexaFHEM deleted
Zitat von: Nexium am 19 Januar 2019, 10:37:14
so wie man es eigentlich nicht machen soll ::)
Edit files dann auf fhem.cfg
PS: Hab es grad nochmal getestet, selbst wenn ich nur ein # hinzufüge ohne dabei irgendwo einzugreifen passiert das.Code Auswählen2019.01.19 10:39:34 1: Including ./log/fhem.save
2019.01.19 10:39:35 2: alexa: alexaFHEM deleted
Zitat von: MadMax-FHEM am 19 Januar 2019, 10:44:19
Danach erfolgt (automatisch) rereadconfig ;)
Gruß, Joachim
Zitat von: justme1968 am 19 Januar 2019, 10:46:57
nein. so soll man es nicht machen.
es gibt keinen grund die fhem cfg von hand zu editieren. und schon garnicht bei laufendem fhem.
Zitat von: justme1968 am 19 Januar 2019, 10:51:28
nein. es ist genau umgekehrt.
und fhem bietet die option im normal zustand nicht! da ist das bearbeiten der config deaktiviert.
nochmal: es gibt keinen grund die config von hand zu bearbeiten!
ZitatDas mag für Profis wie dich zustimmen aber für Anfänger wie mich ist es oft leichter die cfg so zu bearbeiten.
Zitat von: binford6000 am 19 Januar 2019, 10:55:20
Falsch! Bei DEF oder RAW gibts sogar noch einen Syntax-Check. Sehr Anfängerfreundlich ;)
VG Sebastian
Zitat von: justme1968 am 19 Januar 2019, 11:04:13
es ist nicht beabsichtig. lässt sich aber leider nicht ändern da ich das rereadcfg nicht beeinflussen kann. es tritt auch nicht immer auf.
service FHEM stopZitat von: balli1187 am 19 Januar 2019, 12:28:27
Genau das passiert halt nicht, sondern es wird perCode Auswählenservice FHEM stop
Gestoppt.
Gesendet von iPhone mit Tapatalk
Zitat von: Teccno am 19 Januar 2019, 15:14:14
Du meinst doch nicht den Eintrag im Connector-Wiki, der da lautet "dummys müssen setList mit on und off haben", oder? Denn mit der pauschalen Aussage klärt sich meine Frage nämlich leider gar nicht.
Welches Wiki?
Zitat von: https://wiki.fhem.de/wiki/FHEM_Connector
Geräte, die sich ein- und ausschalten lassen:
Automatisch: Müssen set on und set off Kommandos haben
dummys müssen setList mit on und off haben
Über genericDeviceType switch bzw. light kann bestimmt werden ob es in alexa als Schalter oder Licht behandelt wird.
Zitat von: https://wiki.fhem.de/wiki/Alexa-Fhem
Ob Dummy oder nicht, wichtig sind die drei fett gedruckten Zeilen
define Alexa.Party dummy
attr Alexa.Party alexaName party
attr Alexa.Party alexaRoom alexaroom
attr Alexa.Party genericDeviceType switch
attr Alexa.Party group AlexaGeräte
attr Alexa.Party room AlexaRoom
attr Alexa.Party setList on off
homebridgeMapping CurrentTemperature=temperature,minValue=-30,subtype=innen
CurrentTemperature=temperature2,minValue=-30,subtype=KatzenhauseInternals:
DEF 20
FUUID 5c42f8e1-f33f-c32d-8dd6-f6a0aacccabc586a
IODev myJeeLink
LASTInputDev myJeeLink
LaCrosse_lastRcv 2019-01-21 17:48:30
MSGCNT 1093
NAME LaCrosse_20
NR 97
STATE 21.3 / 0
TYPE LaCrosse
addr 20
battery_new 0
corr1 0
corr2 0
myJeeLink_MSGCNT 1093
myJeeLink_RAWMSG OK 9 32 1 4 189 106
myJeeLink_TIME 2019-01-21 17:48:30
previousH 106
previousH2 125
previousT 21.3
previousT2 0
sensorType 0=T(H)
READINGS:
2019-01-21 17:48:30 battery ok
2019-01-21 17:48:30 state T: 21.3
2019-01-21 17:48:30 temperature 21.3
2019-01-21 17:48:17 temperature2 0
Attributes:
IODev myJeeLink
alexaName Schlafzimmer
alias Schlafzimmer / Katzenhaus
fhem_widget_channels [{"allowed_values":[],"locations":["WIDGET"]}]
genericDeviceType thermometer
homebridgeMapping CurrentTemperature=temperature,minValue=-30,subtype=innen
CurrentTemperature=temperature2,minValue=-30,subtype=Katzenhause
icon scene_sleeping
readingsSupervision 180,low,temperature,temperature2,battery
room Homekit,LaCrosse
stateFormat temperature / temperature2Zitat von: justme1968 am 21 Januar 2019, 18:06:41
alexa kann nur eine temperatur pro gerät
d.h. du musst dir einen dummy anlagen (ebenfalls als thermometer) und dort das mapping auf die zweite temperatur im original sensor zeigen lassen.
Zitat von: Esjay am 22 Januar 2019, 09:39:20Das wäre ziemlich cool.
Guten Morgen,
ich habe mal eine Frage zu dem Alexa.ChannelController.
https://developer.amazon.com/docs/device-apis/alexa-channelcontroller.html
Hier wird meinem Verständniss nach dargelegt, dass ein Kanalwechsel mit Alexa auf deutsch funktioniert Wenn ich das richtig sehe wird das unter Entertainment Device geführt.
https://developer.amazon.com/docs/smarthome/develop-smart-home-skills-in-multiple-languages.html
Hier wird allerdings geschrieben, dass das Entertainment Device in Deutschland noch nicht funktioniert.
Gibt es hier schon Pläne das zu integrieren, oder ist es seitens Amazon nur in Planung und noch nicht freigegeben?
Grüße
Zitat von: justme1968 am 22 Januar 2019, 16:40:56
@Esjay: seit eben gibt es version 0.5.13 mit Channel-, Input- und PlaybackController.
im prinzip geht alles drei, aber das ganze ist auf alexa seite aber etwas hakelig. das liegt vor allem daran das alexa versucht intelligent zu sein und versucht die meisten der kommandos auf das aktuelle gerät anzuwenden. auch namen wie 'media' gehen nur manchmal weil alexa denkt man wolle ganz allgemein etwas abspielen.
dafür kann man wenn alles klappt den geräte namen an dem zweiten kommando weg lassen.
ChannelController:reading=channel,cmd=channel{
"Arg":"FormularF1",
"Results": [
{
"Name":"FormularF1",
"PossibleSets":"toggle:noArg on:noArg off:noArg volume:slider,0,1,100 volumeUp:noArg volumeDown:noArg msg remoteControl channelUp:noArg channelDown:noArg play:noArg pause:noArg stop:noArg record:noArg showText downmix:on,off channel:Das_Erste_HD,ZDF_HD,RTL_HD,SAT.1_HD,ProSieben_HD,VOX_HD,kabel_eins_HD,SPORT1_HD,RTLII_HD,DMAX_HD,Sky_Cinema_HD,Sky_Cinema_+1_HD,Sky_Cinema_+24_HD,Sky_Cinema_Action_HD,Sky_Cinema_Hits_HD,Sky_Cinema_Family_HD,Sky_1_HD,Sky_Atlantic_HD,13th_Street_HD,SYFY_HD,Sky_Arts_HD,Beate-Uhse.TV_HD,SUPER_RTL_HD,Disney_Cinemagic_HD,Disney_Junior_HD,Discovery_HD,NatGeo_HD,Nat_Geo_Wild_HD,TNT_Comedy_HD,Universal_TV_HD,TNT_Serie_HD,History_HD,Spiegel_Geschichte_HD,E!_Entertainm._HD,TNT_Film_HD,Fox_HD mute:on,off input:tv,radio reboot:noArg restartGui:noArg shutdown:noArg statusRequest:noArg",
"PossibleAttrs":"alias comment:textField-long eventMap:textField-long group room suppressReading userReadings:textField-long verbose:0,1,2,3,4,5 disable:1,0 disabledForIntervals do_not_notify:1,0 https:0,1 http-method:GET,POST http-noshutdown:1,0 disable:0,1 bouquet-tv bouquet-radio timeout remotecontrol:standard,advanced,keyboard lightMode:0,1 ignoreState:0,1 macaddr:textField model wakeupCmd:textField WOL_useUdpBroadcast WOL_port WOL_mode:EW,UDP,BOTH event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading alarmDevice:Actor,Sensor alarmSettings alexaName alexaRoom babbleDevice cmdIcon devStateIcon devStateIcon:textField-long devStateStyle genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long icon msgContactAudio msgContactLight msgContactMail msgContactPush msgContactScreen msgParams msgPriority msgRecipient msgRecipientAudio msgRecipientLight msgRecipientMail msgRecipientPush msgRecipientScreen msgRecipientText msgTitle msgTitleShrt msgType:text,push,mail,screen,light,audio,queue siriName sortby webCmd webCmdLabel:textField-long widgetOverride userattr",
"Internals": {
"CHANGED": "null",
"DEF": "192.168.178.55",
"INTERVAL": "45",
"NAME": "FormularF1",
"NR": "163",
"STATE": "on",
"TYPE": "ENIGMA2",
"URL": "http://192.168.178.55/",
"modelid": "F1"
},
"Readings": {
"acg": { "Value":"6", "Time":"2019-01-22 18:34:23" },
"apid": { "Value":"259", "Time":"2019-01-22 17:52:18" },
"ber": { "Value":"0", "Time":"2019-01-22 18:34:23" },
"channel": { "Value":"RTL_HD", "Time":"2019-01-22 18:02:56" },
"channelList": { "Value":"Das_Erste_HD,ZDF_HD,RTL_HD,SAT.1_HD,ProSieben_HD,VOX_HD,kabel_eins_HD,SPORT1_HD,RTLII_HD,DMAX_HD,Sky_Cinema_HD,Sky_Cinema_+1_HD,Sky_Cinema_+24_HD,Sky_Cinema_Action_HD,Sky_Cinema_Hits_HD,Sky_Cinema_Family_HD,Sky_1_HD,Sky_Atlantic_HD,13th_Street_HD,SYFY_HD,Sky_Arts_HD,Beate-Uhse.TV_HD,SUPER_RTL_HD,Disney_Cinemagic_HD,Disney_Junior_HD,Discovery_HD,NatGeo_HD,Nat_Geo_Wild_HD,TNT_Comedy_HD,Universal_TV_HD,TNT_Serie_HD,History_HD,Spiegel_Geschichte_HD,E!_Entertainm._HD,TNT_Film_HD,Fox_HD", "Time":"2019-01-22 18:23:59" },
"currentMedia": { "Value":"1:0:19:EF10:421:1:C00000:0:0:0:", "Time":"2019-01-22 18:02:56" },
"currentTitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"enigmaversion": { "Value":"2017-07-13", "Time":"2018-01-17 18:50:12" },
"eventcurrenttime": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescription": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescription_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescriptionextended": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescriptionextended_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventname": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventname_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventtitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventtitle_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"fpversion": { "Value":"None", "Time":"2018-01-17 18:50:12" },
"hdd1_capacity": { "Value":"0.9", "Time":"2018-03-02 08:52:46" },
"hdd1_free": { "Value":"0.9", "Time":"2018-03-02 08:52:46" },
"hdd1_model": { "Value":"Generic(Flash Disk)", "Time":"2018-03-02 08:52:46" },
"imageversion": { "Value":"6.0.1", "Time":"2018-01-17 18:50:12" },
"input": { "Value":"tv", "Time":"2019-01-22 17:14:10" },
"inputList": { "Value":"tv,radio", "Time":"2018-01-16 19:34:26" },
"iswidescreen": { "Value":"1", "Time":"2019-01-22 18:02:56" },
"lanmac": { "Value":"0c:8c:8f:00:45:78", "Time":"2018-03-02 08:52:46" },
"model": { "Value":"F1", "Time":"2018-01-17 18:50:12" },
"mute": { "Value":"off", "Time":"2019-01-22 17:14:10" },
"nextTitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"onid": { "Value":"1", "Time":"2019-01-22 17:14:10" },
"pcrpid": { "Value":"255", "Time":"2019-01-22 17:52:18" },
"pmtpid": { "Value":"96", "Time":"2019-01-22 18:02:56" },
"power": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"presence": { "Value":"present", "Time":"2019-01-15 14:29:19" },
"providername": { "Value":"CBC", "Time":"2019-01-22 18:02:56" },
"recordings": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_error": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_finished": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next_counter": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next_counter_hr": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_hr": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_name": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_servicename": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"servicename": { "Value":"RTL HD", "Time":"2019-01-22 18:02:56" },
"servicereference": { "Value":"1:0:19:EF10:421:1:C00000:0:0:0:", "Time":"2019-01-22 18:02:56" },
"servicevideosize": { "Value":"1920x1080", "Time":"2019-01-22 18:02:56" },
"sid": { "Value":"61200", "Time":"2019-01-22 18:02:56" },
"snr": { "Value":"83", "Time":"2019-01-22 18:34:23" },
"snrdb": { "Value":"16.71", "Time":"2019-01-22 18:34:23" },
"state": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"stateAV": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"tsid": { "Value":"1057", "Time":"2019-01-22 18:02:56" },
"tuner_a": { "Value":"BCM7346 (internal) (DVB-S2)", "Time":"2018-01-17 18:50:12" },
"tuner_b": { "Value":"BCM7346 (internal) (DVB-S2)", "Time":"2018-01-17 18:50:12" },
"txtpid": { "Value":"32", "Time":"2019-01-22 17:52:18" },
"videoheight": { "Value":"1080", "Time":"2019-01-22 18:02:56" },
"videowidth": { "Value":"1920", "Time":"2019-01-22 18:02:56" },
"volume": { "Value":"100", "Time":"2019-01-22 17:48:30" },
"vpid": { "Value":"255", "Time":"2019-01-22 17:52:18" },
"webifversion": { "Value":"OWIF 1.2.5", "Time":"2018-01-17 18:50:12" }
},
"Attributes": {
"alexaName": "Test",
"bouquet-radio": "1:7:2:0:0:0:0:0:0:0:FROM BOUQUET \"userbouquet.favourites.radio\" ORDER BY bouquet",
"bouquet-tv": "1:7:1:0:0:0:0:0:0:0:FROM BOUQUET \"userbouquet.favourites.tv\" ORDER BY bouquet",
"devStateIcon": "on:rc_GREEN:off off:rc_YELLOW:on absent:rc_STOP:on",
"genericDeviceType": "media",
"homebridgeMapping": "ChannelController:reading=channel,cmd=channel",
"http-method": "GET",
"icon": "dreambox",
"model": "F1",
"room": "Spielzimmer",
"webCmd": "channel:input"
}
} ],
"totalResultsReturned":1
}[1/22/2019, 6:24:38 PM] [FHEM] FormularF1 is media
[1/22/2019, 6:24:38 PM] [FHEM] FormularF1 has
[1/22/2019, 6:24:38 PM] [FHEM] Custom Volume [volume;cached]
[1/22/2019, 6:24:38 PM] [FHEM] Custom Power [power]
[1/22/2019, 6:24:38 PM] [FHEM] On [state;on,off]
[1/22/2019, 6:24:38 PM] [FHEM] ChannelController [channel]
2019-01-22 18:24:38 caching: FormularF1-volume: 100
[1/22/2019, 6:24:38 PM] [FHEM] caching: Custom Volume: 100 (as number; from '100')
2019-01-22 18:24:38 caching: FormularF1-power: on
[1/22/2019, 6:24:39 PM] [FHEM] FormularF1-power not a number: on
2019-01-22 18:24:39 caching: FormularF1-state: on
2019-01-22 18:24:39 caching: FormularF1-channel: RTL_HDZitatwenn dein gerät nummern will darfst du keine namen sagen und umgekehrt.Ok, danke für die Erläuterung!
Zitatnur bei den nächster/vorheriger kanal kommandos werden sie innerhalb von alexa-fhem genommen um den ziel kanal zu bestimmen.
Zitatam besten schaust du immer in der app was erkannt wurde. und am besten amazon nerven bis sie es reparieren.
Zitat von: justme1968 am 22 Januar 2019, 18:55:31
ach ja: wenn die gerate suche korrekt gelaufen ist taucht in der app ein fernseher neben dem device auf. das passt zwar nicht immer, ist aber besser als OTHER. mehr auswahl gibt es noch nicht.
[22/01/2019, 20:22:56] sshautoconf: *** Error: Your Homedirectory is writable by group/other. This will not work with SSH
[22/01/2019, 20:22:56] sshautoconf: aborted with user homedir writable by group/other ('chmod 755 /opt/fhem' required)
[22/01/2019, 20:22:56] *** SSH: proxy configuration failed: user homedir writable by group/other ('chmod 755 /opt/fhem' required)[22/01/2019, 20:52:53] os.homedir()=/opt/fhem
[22/01/2019, 20:52:53] os.homedir() set to /opt/fhem, but this is not writableZitat von: justme1968 am 22 Januar 2019, 10:39:47
das habe ich weiter oben schon ein paar mal geschrieben:
- es gibt nur eine aktuelle version. das ist die einzige die weiterentwickelt wird.
- es gibt keinen grund für neue installationen die alte version zu installieren.
- eigentlich sollte (fast) jeder im laufe der zeit auf den neuen autostart weg umstellen. auch wenn er den proxy nicht nutzt.
- alle 'alten' features sind weiterhin vorhanden
- das neue alexa-fhem kann genau so wie früher smart home und custom skill gleichzeitig verarbeiten
- es ist 'nur' der offizielle skill als event quelle dazu gekommen
- einfach die passenden config abschnitte zusammen mischen. das muss ein mal von hand gemacht werden.
dann wird jeweils für den proxy und/oder für port 3000 ein listener aufgemacht.
- es gibt eine idee wie wir den proxy auch für custom skills anbieten können.
dann würde auch hier das port forwardig weg fallen wenn man das möchte. das ist aber noch zukunftsmusik.
Zitat- einfach die passenden config abschnitte zusammen mischen. das muss ein mal von hand gemacht werden.
dann wird jeweils für den proxy und/oder für port 3000 ein listener aufgemacht.
Zitat{
"alexa": {
"port": 3000,
"name": "Alexa Custom",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"applicationId": "amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"oauthClientID": "amzn1.application-oa2-client.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"permissions": {"<skill-id>": { "client_id": "xyz", "client_secret": "123"}}
},
"sshproxy" : {
"description" : "FHEM Connector",
"ssh" : "/usr/bin/ssh"
},
"connections": [
{
"name": "FHEM",
"server": "10.0.1.21",
"port": "8083",
"webname": "fhem",
"filter": "alexaName=..*"
}
]
}
Zitat von: justme1968 am 23 Januar 2019, 19:42:05
das ist einfach eine ganz normale config mit sshproxy block für FHEM Connector und alexa block für alles andere das wie bisher über port forwarding läuft.
Zitat von: justme1968 am 23 Januar 2019, 19:42:05
das ist einfach eine ganz normale config mit sshproxy block für FHEM Connector und alexa block für alles andere das wie bisher über port forwarding läuft.
Zitat von: Mathea am 22 Januar 2019, 21:04:05
Hi,
erst einmal danke für die Arbeit am Modul! Ich habe es vor ein paar Tagen installiert und es hat auch fast direkt funktioniert.
Seit ich Vorgestern aber ein Update gemacht habe, bekomme ich die Fehlermeldung, dass das Homedirectory von mehreren Nutzergruppen beschreibbar ist und ich "chmod 755 /opt/fhem" ausführen soll:Code Auswählen[22/01/2019, 20:22:56] sshautoconf: *** Error: Your Homedirectory is writable by group/other. This will not work with SSH
[22/01/2019, 20:22:56] sshautoconf: aborted with user homedir writable by group/other ('chmod 755 /opt/fhem' required)
[22/01/2019, 20:22:56] *** SSH: proxy configuration failed: user homedir writable by group/other ('chmod 755 /opt/fhem' required)
Das habe ich auch getan, aber dann läuft alexa-fhem nicht mehr mit folgender Fehlermeldung im Log:Code Auswählen[22/01/2019, 20:52:53] os.homedir()=/opt/fhem
[22/01/2019, 20:52:53] os.homedir() set to /opt/fhem, but this is not writable
Das scheint mir eine Zwickmühle zu sein.
Leider kenne ich mich mit den Linux Rechtehandling nicht so gut aus. Aber nach meinem Verständnis gehört dem Nutzer unter dem fhem läuft auch der /opt/fhem/ Ordner. Dadurch sollte dieser Nutzer ja auch die Schreibrechte dafür haben. So wie ich das verstanden habe, sollte alexa-fhem ja unter dem selben Nutzer wie fhem laufen und somit die gleichen Schreibrechte in diesem Ordner haben.
Kann mir jemand einen Tipp geben, wie ich es wieder zum Laufen bringe?
Vielen Dank im Voraus!
Mathea
Zitat von: justme1968 am 23 Januar 2019, 20:49:12
ich bin mir nicht sicher ob ich die frage richtig verstehe...
das fhem modul muss hierzu nichts wissen da es keine daten raus schickt.
beim sprechen aktivierst du doch den einen oder den anderen skill. die daten gehen dann an die für den skill jeweils hinterlegte lambda und dann entweder über den proxy oder per port forwarding auf dein alexa-fhem executable.
Zitat von: raimundl am 24 Januar 2019, 09:40:10
Danke, André!
Bitte verzweifle nicht mit mir, nun bin ich aber einen großen Schritt weiter:
Das heißt, dass jedes Gerät das bei "amazon alexa" angelegt ist einen Skill zugeordnet ist.
Heißt das auch nun, dass ich bei "alexa suche meine Geräte" und zwei installierten Skills (fhem-connect und der private) sowie der funktionierenden "config" für beide Wege (Portweiterleiung und Vereinsserver) auf "39_alexa", die Geräte dann doppelt angelegt werden - oder liege ich falsch.
Entschuldige, aber deine Entwicklung ist ein ganz wichtiger Faktor in meiner Hausautomation geworden, der seit Beginn tadellos funktioniert und ich durch Unwissenheit nichts falsch machen will.
Danke und LG
Walter
Zitat von: justme1968 am 23 Januar 2019, 19:42:05
das ist einfach eine ganz normale config mit sshproxy block für FHEM Connector und alexa block für alles andere das wie bisher über port forwarding läuft.
Zitat
{
"alexa": {
"port": 3000,
"name": "Alexa Custom",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"applicationId": "amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"oauthClientID": "amzn1.application-oa2-client.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"permissions": {"<skill-id>": { "client_id": "xyz", "client_secret": "123"}}
},
"sshproxy" : {
"description" : "FHEM Connector",
"ssh" : "/usr/bin/ssh"
},
"connections": [
{
"name": "FHEM",
"server": "10.0.1.21",
"port": "8083",
"webname": "fhem",
"filter": "alexaName=..*"
}
]
}
{
"alexa": {
"port": 8002,
"name": "Alexa FHEM",
"keyFile": "./certs/server-key.pem",
"certFile": "./certs/server-cert.pem",
"nat-upnp": false,
"applicationId": "amzn1.ask.skill...",
"oauthClientID": "amzn1.application-oa2-client..."
},
"sshproxy" : {
"description" : "FHEM Connector",
"ssh" : "/usr/bin/ssh"
},
"connections" : [
{
"name" : "FHEM",
"server" : "10.3.3.40",
"filter" : "alexaName=..*",
"auth": {"user": "...", "pass": "..."},
"ssl": true,
"port" : "8883",
"webname" : "fhem",
"uid" : 999
}
]
}Internals:
FD 32
FUUID 5c44a52d-f33f-0308-c2af-5d240f94a1a6857c
LAST_START 2019-01-24 08:59:16
LAST_STOP 2019-01-24 08:59:06
NAME alexa
NOTIFYDEV global
NR 379
NTFY_ORDER 50-alexa
PID 26376
STARTS 3
STATE running /usr/local/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.13
currentlogfile ./log//alexa-2019-01-24.log
logfile %L/alexa-%Y-%m-%d.log
READINGS:
2019-01-24 08:59:16 alexaFHEM running /usr/local/bin/alexa-fhem
2019-01-24 08:59:22 alexaFHEM.ProxyConnection running; SSH connected
2019-01-15 10:20:07 alexaFHEM.bearerToken crypt:...
2019-01-15 10:20:07 alexaFHEM.skillRegKey crypt:...
2019-01-24 10:42:37 echoId amzn1.ask.device...
2019-01-24 10:42:37 echoRoom wohnzimmer
2019-01-24 10:42:37 intent IntentRequest FHEMperlCodeIntentE
Attributes:
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log %L/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
amzn1.ask.device....=wohnzimmer
fhemIntents #IntentName=<sample utterance>\
{alexaWeckzeit($weckzeit)}=Wecker auf {weckzeit}|wecken um {weckzeit}|weck mich um {weckzeit}|stelle Wecker auf {weckzeit}\
{alexaWeckeraus()}=Wecker Aus\
{alexa_Muell($muell)}=wann wird {muell} abgeholt|wann wird {muell} geleert|wann ist die Abholung von {muell}\
{alexa_goodnight()}=Gute Nacht\
{alexa_goodmorning()}=Guten Morgen\
{alexa_Scene($scene)}={scene} aktivieren|aktiviere {scene}|schalte {scene} ein|schalte {scene} an \
{alexa_tv_programm($programm)}=TV auf {programm}|Fernseher auf {programm}|Sender auf {programm}|Dreambox auf {programm}|Receiver auf {programm}\
{alexa_Sonos($sonos)}=spiele {sonos}
attr alexa group Alexa
icon alexa2
room 90_System->92_Webdevices
stateFormat alexaFHEM"Ich habe Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten.,[2019-1-24 10:42:37] >>>> [srv] {"version":"1.0","session":{"new":true,"sessionId":"amzn1.echo-api.session...application":{"applicationId":"amzn1.ask.skill..."},"user":{"userId":"amzn1.ask.account....","accessToken":"..."}},"context":{"System":{"application":{"applicationId":"amzn1.ask.skill...."},"user":{"userId":"amzn1.ask.account....","accessToken":"..."},"device":{"deviceId":"amzn1.ask.device...","supportedInterfaces":{}},"apiEndpoint":"https://api.eu.amazonalexa.com","apiAccessToken":"..."}},"request":{"type":"IntentRequest","requestId":"amzn1.echo-api.request....","timestamp":"2019-01-24T09:42:35Z","locale":"de-DE","intent":{"name":"FHEMperlCodeIntentE","confirmationStatus":"NONE"}}}
[2019-1-24 10:42:37] accepted new token
[2019-1-24 10:42:37] FHEMperlCodeIntentE
[2019-1-24 10:42:37] Reading intent set to IntentRequest FHEMperlCodeIntentE
[2019-1-24 10:42:37] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20intent%20IntentRequest%20FHEMperlCodeIntentE%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-24 10:42:37] Reading echoId set to amzn1.ask.device...
[2019-1-24 10:42:37] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoId%20amzn1.ask.device...%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-24 10:42:37] Reading echoRoom set to wohnzimmer
[2019-1-24 10:42:37] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoRoom%20wohnzimmer%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] FHEMperlCodeIntentE -> FHEMperlCode
[2019-1-24 10:42:37] <<<< [srv] {"version":"1.0","sessionAttributes":{},"response":{"outputSpeech":{"type":"PlainText","text":"Ich habe Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"},"shouldEndSession":true,"card":{"type":"Simple","title":"FHEMperlCodeIntentE","content":"Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"}}}Zitat von: justme1968 am 22 Januar 2019, 18:55:31
ach ja: wenn die gerate suche korrekt gelaufen ist taucht in der app ein fernseher neben dem device auf. das passt zwar nicht immer, ist aber besser als OTHER. mehr auswahl gibt es noch nicht.
Zitat von: justme1968 am 24 Januar 2019, 19:09:34
es gibt im ersten beitrag eine neue test version für das alexa modul.
hintergrund ist: die drei sprach module (und noch weitere wenn interesse besteht) sollen auf eine gemeinsame infrastruktur was starten/stopen/fhem integration/... angeht umgestellt werden.
wer zeit und lust hat bitte testen.
Zitat von: justme1968 am 24 Januar 2019, 19:17:42
schau dir im log die discovery antwort an. da muss etwas von TV stehen.
{"endpointId":"FormularF1","manufacturerName":"FHEMENIGMA2","modelName":"FHEMF1","version":"<unknown>","friendlyName":"sessel","description":"n: FormularF1, r: spielzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.Speaker","version":"3","properties":{"supported":[{"name":"volume"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.ChannelController","version":"3","properties":{"supported":[{"name":"channel"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["OTHER","TV"],"cookie":{"device":"FormularF1"}},Zitat von: justme1968 am 24 Januar 2019, 19:41:18
@MadMax-FHEM: ja. CoProcess.pm ist schon die gleiche. erst mal alles testen was dir zum starten und stoppen so einfällt :)
got .eventToken
refreshing token
got fresh token
Zitat von: justme1968 am 24 Januar 2019, 20:03:09
doch. bei add sollte etwas im log zu sehen sein. im alexa-fhem log.
Zitat von: justme1968 am 24 Januar 2019, 20:03:09
beim start sollten drei meldungen kommen:Code Auswählengot .eventToken
refreshing token
got fresh token
hast du ein .eventToken reading im alexa device?
alexaFHEM running /usr/local/bin/alexa-fhem 2019-01-24 19:45:00
alexaFHEM.ProxyConnection running; SSH connected 2019-01-24 19:45:05
alexaFHEM.bearerToken crypt:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2019-01-13 18:08:36
alexaFHEM.skillRegKey crypt:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2019-01-13 18:08:36
Zitat von: justme1968 am 24 Januar 2019, 19:41:18
@MadMax-FHEM: ja. CoProcess.pm ist schon die gleiche. erst mal alles testen was dir zum starten und stoppen so einfällt :)
@Esjay: das problem ist das amazon nicht mehreren displayCategories klar kommt und die erste scheinbar auch noch vorfahrt hat.
ich baue es um das nur eine genommen wird.
kannst du mal aus dem mapping volume raus nehmen? zur not zum testen das reading volume mal löschen.
vielleicht ist es für die ersten besser mit einem dummy zu arbeiten und sich langsam vorzuarbeiten.
Zitat von: justme1968 am 24 Januar 2019, 19:07:55
@binford6000: alexa-fhem mit --debug starten und schauen.
...
[2019-1-25 07:48:19] accepted new token
[2019-1-25 07:48:19] { aud: 'amzn1.application-oa2-client...',
user_id: 'amzn1.account...',
iss: 'https://www.amazon.com',
exp: 3441,
app_id: 'amzn1.application...',
iat: 1548398740 }
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] Reading intent set to IntentRequest FHEMperlCodeIntentB
[2019-1-25 07:48:19] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20intent%20IntentRequest%20FHEMperlCodeIntentB%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 07:48:19] Reading echoId set to amzn1.ask.device...
[2019-1-25 07:48:19] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoId%20amzn1.ask.device...%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 07:48:19] Reading echoRoom set to unknown
[2019-1-25 07:48:19] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoRoom%20unknown%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 07:48:19] index: 1
[2019-1-25 07:48:19] characteristic: FHEMperlCode
[2019-1-25 07:48:19] value: undefined
[2019-1-25 07:48:19] type: undefined
[2019-1-25 07:48:19] room: undefined
[2019-1-25 07:48:19] name: undefined
[2019-1-25 07:48:19] device: undefined
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCode
[2019-1-25 07:48:19] FHEMperlCodeIntentB
[2019-1-25 07:48:19] undefined
[2019-1-25 07:48:19] FHEMperlCodeIntentB -> FHEMperlCode
[2019-1-25 07:48:19] <<<< [srv] {"version":"1.0","sessionAttributes":{},"response":{"outputSpeech":{"type":"PlainText","text":"Ich habe Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"},"shouldEndSession":true,"card":{"type":"Simple","title":"FHEMperlCodeIntentB","content":"Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"}}}
ZitatEcho, nächster Kanal auf Fernseher auf vier
Echo, nächster Kanal auf Fernseher
Echo, wechsel auf Fernseher zu Kanal fünf
ZitatAlexa, wechsel auf Fernseher den Kanal zu ZDF
ZitatEcho, einen Kanal vor auf Fernseher
Echo, einen Kanal zurück auf Gerät
defmod TV_Wohnzimmer LGTV_WebOS 192.168.188.20
attr TV_Wohnzimmer alexaName fernseher
attr TV_Wohnzimmer channelGuide 1
attr TV_Wohnzimmer devStateIcon on:10px-kreis-gruen:off off:10px-kreis-rot:on
attr TV_Wohnzimmer event-on-change-reading .*
attr TV_Wohnzimmer group TV_WZ
attr TV_Wohnzimmer homebridgeMapping ChannelController:reading=channel,cmd=channel
attr TV_Wohnzimmer icon it_television
attr TV_Wohnzimmer room Alexacontrol,Homekit,TV->Wohnzimmer
attr TV_Wohnzimmer wakeOnLanMAC E8:5B:5B:80:55:B3
attr TV_Wohnzimmer webCmd on:off:rewind:pause:stop:play:fastForward
setstate TV_Wohnzimmer on
setstate TV_Wohnzimmer 2018-03-19 05:54:39 3D off
setstate TV_Wohnzimmer 2018-03-19 05:54:39 3DMode 2d
setstate TV_Wohnzimmer 2019-01-25 15:32:51 channel 3
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelCurrentEndTime -
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelCurrentStartTime -
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelCurrentTitle -
setstate TV_Wohnzimmer 2019-01-25 15:32:51 channelMedia Satellite Digital TV
setstate TV_Wohnzimmer 2019-01-25 15:32:51 channelName RTL Television
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelNextEndTime -
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelNextStartTime -
setstate TV_Wohnzimmer 2019-01-13 23:32:46 channelNextTitle -
setstate TV_Wohnzimmer 2018-03-19 05:54:41 extInput_AV-1 connect_false
setstate TV_Wohnzimmer 2018-03-19 05:54:41 extInput_AV-2 connect_false
setstate TV_Wohnzimmer 2019-01-08 01:51:30 extInput_HDMI-1 connect_false
setstate TV_Wohnzimmer 2018-03-19 05:54:41 extInput_HDMI-2 connect_false
setstate TV_Wohnzimmer 2018-03-19 05:54:41 extInput_HDMI-3 connect_false
setstate TV_Wohnzimmer 2018-03-19 05:54:41 extInput_Komponente connect_false
setstate TV_Wohnzimmer 2018-03-19 05:54:47 input -
setstate TV_Wohnzimmer 2019-01-25 14:53:31 lastResponse ok
setstate TV_Wohnzimmer 2018-03-19 05:54:47 launchApp TV
setstate TV_Wohnzimmer 2018-03-18 21:27:01 lgKey bb28051b086c710cffa02d019b7d3d2b
setstate TV_Wohnzimmer 2018-03-19 05:54:43 mute off
setstate TV_Wohnzimmer 2019-01-25 14:53:31 pairing paired
setstate TV_Wohnzimmer 2019-01-25 15:32:49 state on
setstate TV_Wohnzimmer 2019-01-25 15:03:35 volume 7hombridgeMapping InputController:reading=<reading>:cmd=<cmd>,values=HDMI+1;HDMI+2;XBOXZitat@binford6000: was hat du denn genau gesagt?
[2019-1-25 16:41:03] >>>> [srv] {"version":"1.0","session":{"new":true,"sessionId":"amzn1.echo-api.session...","application":{"applicationId":"amzn1.ask.skill..."},"user":{"userId":"amzn1.ask.account...","accessToken":".."}},"context":{"System":{"application":{"applicationId":"amzn1.ask.skill...."},"user":{"userId":"amzn1.ask.account...","accessToken":".."},"device":{"deviceId":"amzn1.ask.device...","supportedInterfaces":{}},"apiEndpoint":"https://api.eu.amazonalexa.com","apiAccessToken":".."}},"request":{"type":"IntentRequest","requestId":"amzn1.echo-api.request...","timestamp":"2019-01-25T15:41:03Z","locale":"de-DE","intent":{"name":"FHEMperlCodeIntentH","confirmationStatus":"NONE","slots":{"sonos":{"name":"sonos","value":"filmmusik","resolutions":{"resolutionsPerAuthority":[{"authority":"amzn1.er-authority.echo-sdk.amzn1.ask.skill....FHEM_sonos","status":{"code":"ER_SUCCESS_MATCH"},"values":[{"value":{"name":"Filmmusik","id":"..."}}]}]},"confirmationStatus":"NONE","source":"USER"}}}}}
[2019-1-25 16:41:03] accepted new token
[2019-1-25 16:41:03] { aud: 'amzn1.application-oa2-client...',
user_id: 'amzn1.account...',
iss: 'https://www.amazon.com',
exp: 3582,
app_id: 'amzn1.application...',
iat: 1548430845 }
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] Reading intent set to IntentRequest FHEMperlCodeIntentH
[2019-1-25 16:41:03] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20intent%20IntentRequest%20FHEMperlCodeIntentH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 16:41:03] Reading echoId set to amzn1.ask.device...
[2019-1-25 16:41:03] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoId%20amzn1.ask.device...%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 16:41:03] Reading echoRoom set to wohnzimmer
[2019-1-25 16:41:03] [FHEM] executing: https://10.3.3.40:8883/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20echoRoom%20wohnzimmer%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-25 16:41:03] index: 7
[2019-1-25 16:41:03] characteristic: FHEMperlCode
[2019-1-25 16:41:03] value: undefined
[2019-1-25 16:41:03] type: undefined
[2019-1-25 16:41:03] room: wohnzimmer
[2019-1-25 16:41:03] name: undefined
[2019-1-25 16:41:03] device: undefined
[2019-1-25 16:41:03] { sonos:
{ name: 'sonos',
value: 'filmmusik',
resolutions: { resolutionsPerAuthority: [Array] },
confirmationStatus: 'NONE',
source: 'USER' } }
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCodeIntentH
[2019-1-25 16:41:03] undefined
[2019-1-25 16:41:03] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:03] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCode
[2019-1-25 16:41:04] FHEMperlCodeIntentH
[2019-1-25 16:41:04] undefined
[2019-1-25 16:41:04] FHEMperlCodeIntentH -> FHEMperlCode
[2019-1-25 16:41:04] <<<< [srv] {"version":"1.0","sessionAttributes":{},"response":{"outputSpeech":{"type":"PlainText","text":"Ich habe Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"},"shouldEndSession":true,"card":{"type":"Simple","title":"FHEMperlCodeIntentH","content":"Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten., Ich kann undefined nicht auf undefined schalten. und Ich kann undefined nicht auf undefined schalten. undefined gestellt"}}}
Zitatversuch mal nur 'nächster kanal'. und das am besten nach dem der kanal ein direkt mit dem geräte namen gesetzt wurde.
ZitatEcho, nächster Kanal auf Fernseher auf vier
Echo, nächster Kanal auf Fernseher
Echo, wechsel auf Fernseher zu Kanal fünf
Echo, Fernseher nächster Kanal
Echo, Fernseher lauter/leiser (10er Schritte)
Echo, Fernseher lauter/leiser um fünf
Zitatmit lauter/leiser um .... werden die genannten Werte im Verlauf richtig erkannt (wie auch bei den Sendernamen) aber heraus kommt nur Wirres. um 8 geht auf 18, um 2 erhöht um 4 usw
Zitat von: justme1968 am 26 Januar 2019, 16:49:16
hat irgendjemand probleme mit der CoProcess test version aus dem ersten beitrag?
hat es jemand probiert und hat keine probleme :) ?
SyntaxError: Unexpected token (
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:549:28)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/lib/node_modules/alexa-fhem/lib/server.js:11:29){
"connections" : [
{
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "192.168.178.1",
"webname" : "fhem"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
}
}npm install -g alexa-fhemnpm install -g alexa-fhem{
"alexa": {
"port": 3000,
"name": "Alexa FHEM",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"nat-pmp": "",
"nat-upnp": false,
"applicationId": "amzn1.ask.skill.6b24xxxxxx",
"oauthClientID": "amzn1.application-oa2-client.05d6xxxxxx"
},
"connections": [
{
"name": "FHEM",
"server": "192.168.178.4",
"port": "8083",
"webname": "fhem",
"filter": "room=Alexa"
}
]
}{
"connections" : [
{
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "192.168.178.4",
"webname" : "fhem"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
}
}ZitatLeider habe ich den Faden verloren, weiß keinen Ansatz mehr.
ZitatHaber hier immer wieder gelesen alexaFHEM-auth soll aktiviert werden! Welcher Wert soll dort rein? Die Skill-ID?
sudo apt-get remove nodejs
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y nodejs
sudo npm install npm@latest -gZitatSo habe erst mal nodejs von 6.16 auf 8.15 upgedatet.
define fhemServer npmjs localhostInternals:
CFGFN
DEF localhost
FUUID 5c4d6776-f33f-0308-d911-e1261b62a9ef5b88
HOST localhost
NAME nodejs
NOTIFYDEV global,fhemServer
NR 1586
NTFY_ORDER 50-fhemServer
STATE npm is up to date
TYPE npmjs
VERSION 0.9.0
READINGS:
2019-01-27 09:10:31 nodejsVersion 8.15.0
2019-01-27 09:15:15 outdated fetched done
2019-01-27 09:15:15 state npm is up to date
2019-01-27 09:12:58 update successful
2019-01-27 09:15:15 updatesAvailable 0
helper:
lastSync 2019-01-27
Attributes:
devStateIcon npm.updates.available:security@red npm.is.up.to.date:security@green .*in.progress:system_fhem_reboot@orange errors:message_attention@red
group Alexa-FHEM
icon alexa2
room 90_System->92_Webdevices{
"alexa": {
"port": 3000,
"name": "Alexa FHEM",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"nat-pmp": "",
"nat-upnp": false,
"applicationId": "amzn1.ask.skill.6b24xxxxxx",
"oauthClientID": "amzn1.application-oa2-client.05d6xxxxxx"
},ZitatAlso muss in die alexa-fhem.cfg noch die aus der config.jason rein:
Zitat von: binford6000 am 27 Januar 2019, 11:08:57
Ergänzend zu Joachim:
- Einen Raum für die Geräte wie bei der alten Version wird nicht länger benötigt da der Filter auf alexaName=..* zeigt
- Stattdessen das alexaRoom Attribut benutzen. Siehe auch Wiki
VG Sebastian
#<deviceId>=<room>
amzn1.ask.device.AF...=wohnzimmerZitat- alexaRoom: hat beim fhem Skill (bzw. generell beim Smart Home Skill) KEINE Bedeutung!
"Alexa, aktiviere <scene name> <alexaRoom>" {
"connections" : [
{
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "192.168.178.4",
"webname" : "fhem"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
}
}
Zitat von: binford6000 am 27 Januar 2019, 11:17:13
Nochmal ergänzend zum Thema Room:
Wenn im Attribut echoRooms die deviceID des Echos steht, kann die Angabe des Raums auch weggelassen werden:Code Auswählen#<deviceId>=<room>
amzn1.ask.device.AF...=wohnzimmer
VG Sebastian
Zitat von: binford6000 am 27 Januar 2019, 11:19:44
Doch zB beim FHEM Skill mit LightScenes:Code Auswählen"Alexa, aktiviere <scene name> <alexaRoom>"
VG Sebastian
Zitat von: MadMax-FHEM am 27 Januar 2019, 11:24:24
Aha, LightScene, nutze ich nicht ;)
Ist aber dann eins von den neuen Features extra für LightScene (dann sollte das auch dazu geschrieben werden) weil sonst hat alexaRoom bei Smart Home (noch) keine Bedeutung (liegt an der Entwicklung bei Amazon).
Gruß und danke, Joachim
Internals:
DEF bu_spot_licht bu_schreibtisch_licht
FUUID 5c44a502-f33f-0308-b014-2e0c0e3080f327f5
HAS_DataDumper 1
HAS_JSON 1
NAME bu_szene
NR 134
NTFY_ORDER 50-bu_szene
STATE abwesend
TYPE LightScene
mayBeVisible 1
CONTENT:
bu_schreibtisch_licht 1
bu_spot_licht 1
OLDREADINGS:
2019-01-27 07:51:55 state anwesend
READINGS:
2019-01-27 07:52:00 state abwesend
SCENES:
abwesend:
bu_schreibtisch_licht off
bu_spot_licht off
anwesend:
bu_schreibtisch_licht on
bu_spot_licht on
panik:
bu_schreibtisch_licht on
bu_spot_licht on
schlafen:
bu_schreibtisch_licht off
bu_spot_licht off
devices:
bu_schreibtisch_licht
bu_spot_licht
Attributes:
alexaName bu
alexaRoom büro
async_delay 0.25
genericDeviceType scene
group Lichtszenen
icon audio_eq
oldreadings state
room 20_Licht
webCmd sceneZitat von: topa_LE am 27 Januar 2019, 11:21:43
Ok, jetzt wird mir einiges wieder klar ;-)
Ich las das so:Code Auswählen{
"connections" : [
{
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "192.168.178.4",
"webname" : "fhem"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
}
}
Habe allerdings immer noch den Room Alexa, dort sind die Defines drin, die ich steuern möchte. Heißt das wenn in meinen Geräte das AlexaName Attribut gesetzt ist (ist es ja schon immer) , dann brauche ich diese Geräte nicht nochmal in den Room: Alexa zu setzen?
ZitatHeißt das wenn in meinen Geräte das AlexaName Attribut gesetzt ist (ist es ja schon immer) , dann brauche ich diese Geräte nicht nochmal in den Room: Alexa zu setzen?
{
"alexa": {
"port": 3000,
"name": "Alexa FHEM",
"keyFile": "./key.pem",
"certFile": "./cert.pem",
"nat-pmp": "",
"nat-upnp": false,
"applicationId": "amzn1.ask.skill.6b2457a1-2b15-xxx",
"oauthClientID": "amzn1.application-oa2-client.05d69bd0xxx"
},
"connections" : [
{
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "192.168.178.4",
"webname" : "fhem"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
}
}
Internals:
FD 27
FUUID 5c4cdb80-f33f-252b-7c50-8003deca2b817720
LAST_START 2019-01-27 11:47:43
NAME MyAlexa
NOTIFYDEV global
NR 272
NTFY_ORDER 50-MyAlexa
PID 3979
STARTS 1
STATE running /usr/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.14
currentlogfile ./log/alexa-2019-01-27.log
logfile ./log/alexa-%Y-%m-%d.log
.attraggr:
.attrminint:
CoProcess:
cmdFn alexa_getCMD
name alexaFHEM
state running /usr/bin/alexa-fhem
READINGS:
2019-01-27 11:47:43 alexaFHEM running /usr/bin/alexa-fhem
2019-01-27 11:47:58 alexaFHEM.ProxyConnection running; SSH connected
2019-01-27 10:20:49 alexaFHEM.bearerToken crypt:20777774000051015c5b267406227257
2019-01-27 10:21:02 alexaFHEM.skillRegKey crypt:26030773030053024854530576560f57085222055b70517c524e23777677565152060c0a777055712051
Attributes:
DbLogExclude .*
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log ./log/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nacht
room 99-System
stateFormat alexaFHEM
verbose 5
[2019-1-27 12:00:02] Got SIGTERM, shutting down alexa-fhem...
[2019-1-27 12:00:02] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-1-27 12:00:02] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20MyAlexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:02] Stopping SSH ...
[2019-1-27 12:00:02] Reading alexaFHEM.ProxyConnection set to stopped
[2019-1-27 12:00:02] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20MyAlexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:02] *** SSH: exited with 143
[2019-1-27 12:00:11] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-1-27 12:00:11] os.homedir()=/opt/fhem
[2019-1-27 12:00:11] this is alexa-fhem 0.5.14
[2019-1-27 12:00:11] connecting to FHEM ...
[2019-1-27 12:00:12] [FHEM] trying longpoll to listen for fhem events
[2019-1-27 12:00:12] [FHEM] starting longpoll: http://192.168.178.4:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1548586812391
[2019-1-27 12:00:12] Server listening on: https://:::3000 for direct connections
[2019-1-27 12:00:14] [FHEM] got csrfToken:
[2019-1-27 12:00:14] [FHEM] Checking devices and attributes...
[2019-1-27 12:00:14] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-1-27 12:00:14] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-1-27 12:00:14] [FHEM] waiting for events ...
[2019-1-27 12:00:14] [FHEM] Fetching FHEM devices...
[2019-1-27 12:00:14] [FHEM] fetching: http://192.168.178.4:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-1-27 12:00:14] [FHEM] alexa device is MyAlexa
[2019-1-27 12:00:14] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.14%22%7D%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:14] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20MyAlexa%20proxyToken%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:14] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20MyAlexa%20.eventToken%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:14] Server listening on: http://127.0.0.1:39121 for proxy connections
[2019-1-27 12:00:14] *** SSH: checking proxy configuration
[2019-1-27 12:00:14] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-1-27 12:00:14] Passed config: {"alexa":{"port":3000,"name":"Alexa FHEM","keyFile":"./key.pem","certFile":"./cert.pem","nat-pmp":"","nat-upnp":false,"applicationId":["amzn1.ask.skill.6b2457a1-2b15-4074-9458-09241bb9f127"],"oauthClientID":["amzn1.application-oa2-client.05d69bd0ecf64735b84da1047b84b830"]},"connections":[{"port":"8083","filter":"alexaName=..*","uid":999,"name":"FHEM","server":"192.168.178.4","webname":"fhem"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":39121}}
[2019-1-27 12:00:14] sshautoconf: SSH key seems to exist
[2019-1-27 12:00:15] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-1-27 12:00:15] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20MyAlexa%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-1-27 12:00:15] [FHEM] got: 36 results
[2019-1-27 12:00:15] [FHEM] Alexa.Weckzeit is clock
[2019-1-27 12:00:15] [FHEM] Alexa.Weckzeit has
[2019-1-27 12:00:15] [FHEM] Weckzeit [state]
[2019-1-27 12:00:15] [FHEM] Bettstrom_KZ_Patrick_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] Bettstrom_KZ_Patrick_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: Bettstrom_KZ_Patrick_Sonoff_S20-state: OFF
[2019-1-27 12:00:15] [FHEM] Dekolampe_Toilette_HUE_19 is light
[2019-1-27 12:00:15] [FHEM] Dekolampe_Toilette_HUE_19 has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
[2019-1-27 12:00:15] [FHEM] Custom Color Temperature [ct]
[2019-1-27 12:00:15] [FHEM] colormode [colormode]
2019-01-27 12:00:15 caching: Dekolampe_Toilette_HUE_19-onoff: 0
2019-01-27 12:00:15 caching: Dekolampe_Toilette_HUE_19-bri: 94
2019-01-27 12:00:15 caching: Dekolampe_Toilette_HUE_19-ct: 156 (6410K)
[2019-1-27 12:00:15] [FHEM] caching: Custom Color Temperature: 6410 (as number; from '156 (6410K)')
2019-01-27 12:00:15 caching: Dekolampe_Toilette_HUE_19-colormode: ct
[2019-1-27 12:00:15] [FHEM] FB_Dect_AZ_Lena is switch
[2019-1-27 12:00:15] [FHEM] FB_Dect_AZ_Lena has
[2019-1-27 12:00:15] [FHEM] Custom Voltage [voltage]
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
[2019-1-27 12:00:15] [FHEM] CurrentTemperature [temperature]
2019-01-27 12:00:15 caching: FB_Dect_AZ_Lena-voltage: 231.615 V
[2019-1-27 12:00:15] [FHEM] caching: Custom Voltage: 231.615 (as number; from '231.615 V')
2019-01-27 12:00:15 caching: FB_Dect_AZ_Lena-power: 0.00 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.00 W')
2019-01-27 12:00:15 caching: FB_Dect_AZ_Lena-energy: 2150044 Wh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 2150.044 (as number; from '2150044 Wh')
2019-01-27 12:00:15 caching: FB_Dect_AZ_Lena-state: off
2019-01-27 12:00:15 caching: FB_Dect_AZ_Lena-temperature: 23.5 C (measured)
[2019-1-27 12:00:15] [FHEM] FB_Dect_Garage_Heizung is switch
[2019-1-27 12:00:15] [FHEM] FB_Dect_Garage_Heizung has
[2019-1-27 12:00:15] [FHEM] Custom Voltage [voltage]
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
[2019-1-27 12:00:15] [FHEM] CurrentTemperature [temperature]
2019-01-27 12:00:15 caching: FB_Dect_Garage_Heizung-voltage: 230.293 V
[2019-1-27 12:00:15] [FHEM] caching: Custom Voltage: 230.293 (as number; from '230.293 V')
2019-01-27 12:00:15 caching: FB_Dect_Garage_Heizung-power: 0.00 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.00 W')
2019-01-27 12:00:15 caching: FB_Dect_Garage_Heizung-energy: 2097950 Wh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 2097.95 (as number; from '2097950 Wh')
2019-01-27 12:00:15 caching: FB_Dect_Garage_Heizung-state: off
2019-01-27 12:00:15 caching: FB_Dect_Garage_Heizung-temperature: 6.5 C (measured)
[2019-1-27 12:00:15] [FHEM] FB_Dect_WZ_TV_Anlage is switch
[2019-1-27 12:00:15] [FHEM] FB_Dect_WZ_TV_Anlage has
[2019-1-27 12:00:15] [FHEM] Custom Voltage [voltage]
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
[2019-1-27 12:00:15] [FHEM] CurrentTemperature [temperature]
2019-01-27 12:00:15 caching: FB_Dect_WZ_TV_Anlage-voltage: 232.550 V
[2019-1-27 12:00:15] [FHEM] caching: Custom Voltage: 232.55 (as number; from '232.550 V')
2019-01-27 12:00:15 caching: FB_Dect_WZ_TV_Anlage-power: 0.00 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.00 W')
2019-01-27 12:00:15 caching: FB_Dect_WZ_TV_Anlage-energy: 2795595 Wh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 2795.5950000000003 (as number; from '2795595 Wh')
2019-01-27 12:00:15 caching: FB_Dect_WZ_TV_Anlage-state: off
2019-01-27 12:00:15 caching: FB_Dect_WZ_TV_Anlage-temperature: 26.0 C (measured)
[2019-1-27 12:00:15] [FHEM] FL_Dekolicht is light
[2019-1-27 12:00:15] [FHEM] FL_Dekolicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: FL_Dekolicht-onoff: 0
2019-01-27 12:00:15 caching: FL_Dekolicht-bri: 24
[2019-1-27 12:00:15] [FHEM] Fernsehlampe_Sleep_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] Fernsehlampe_Sleep_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: Fernsehlampe_Sleep_Sonoff_S20-state: OFF
[2019-1-27 12:00:15] [FHEM] Garage_Aussenlicht_HUE_11 is light
[2019-1-27 12:00:15] [FHEM] Garage_Aussenlicht_HUE_11 has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: Garage_Aussenlicht_HUE_11-onoff: 0
2019-01-27 12:00:15 caching: Garage_Aussenlicht_HUE_11-bri: 1
[2019-1-27 12:00:15] [FHEM] Garage_Lampe_HUE_8 is light
[2019-1-27 12:00:15] [FHEM] Garage_Lampe_HUE_8 has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: Garage_Lampe_HUE_8-onoff: 0
2019-01-27 12:00:15 caching: Garage_Lampe_HUE_8-bri: 102
[2019-1-27 12:00:15] [FHEM] HWR_Deckenlicht is light
[2019-1-27 12:00:15] [FHEM] HWR_Deckenlicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: HWR_Deckenlicht-onoff: 1
2019-01-27 12:00:15 caching: HWR_Deckenlicht-bri: 254
[2019-1-27 12:00:15] [FHEM] KU_Deckenlicht is light
[2019-1-27 12:00:15] [FHEM] KU_Deckenlicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: KU_Deckenlicht-onoff: 1
2019-01-27 12:00:15 caching: KU_Deckenlicht-bri: 254
[2019-1-27 12:00:15] [FHEM] KU_Dekolampe is light
[2019-1-27 12:00:15] [FHEM] KU_Dekolampe has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
[2019-1-27 12:00:15] [FHEM] Custom Color Temperature [ct]
[2019-1-27 12:00:15] [FHEM] colormode [colormode]
2019-01-27 12:00:15 caching: KU_Dekolampe-onoff: 0
2019-01-27 12:00:15 caching: KU_Dekolampe-bri: 102
2019-01-27 12:00:15 caching: KU_Dekolampe-ct: 153 (6535K)
[2019-1-27 12:00:15] [FHEM] caching: Custom Color Temperature: 6535 (as number; from '153 (6535K)')
2019-01-27 12:00:15 caching: KU_Dekolampe-colormode: ct
[2019-1-27 12:00:15] [FHEM] LENA_Dekolicht is light
[2019-1-27 12:00:15] [FHEM] LENA_Dekolicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
[2019-1-27 12:00:15] [FHEM] Custom Color Temperature [ct]
[2019-1-27 12:00:15] [FHEM] colormode [colormode]
2019-01-27 12:00:15 caching: LENA_Dekolicht-onoff: 0
2019-01-27 12:00:15 caching: LENA_Dekolicht-bri: 128
2019-01-27 12:00:15 caching: LENA_Dekolicht-ct: 228 (4385K)
[2019-1-27 12:00:15] [FHEM] caching: Custom Color Temperature: 4385 (as number; from '228 (4385K)')
2019-01-27 12:00:15 caching: LENA_Dekolicht-colormode: ct
[2019-1-27 12:00:15] [FHEM] Nachtlampe_Sleep_Lena_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] Nachtlampe_Sleep_Lena_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: Nachtlampe_Sleep_Lena_Sonoff_S20-state: OFF
[2019-1-27 12:00:15] [FHEM] Nachtlampe_Sleep_Torsten_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] Nachtlampe_Sleep_Torsten_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: Nachtlampe_Sleep_Torsten_Sonoff_S20-state: OFF
[2019-1-27 12:00:15] [FHEM] Schreibtischlampe_Lena_AZ_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] Schreibtischlampe_Lena_AZ_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: Schreibtischlampe_Lena_AZ_Sonoff_S20-state: off
[2019-1-27 12:00:15] [FHEM] TV_Lampe_Patrick_Sonoff_S20 is switch
[2019-1-27 12:00:15] [FHEM] TV_Lampe_Patrick_Sonoff_S20 has
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: TV_Lampe_Patrick_Sonoff_S20-state: OFF
[2019-1-27 12:00:15] [FHEM] Terrassenlampe_HUE_14 is light
[2019-1-27 12:00:15] [FHEM] Terrassenlampe_HUE_14 has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: Terrassenlampe_HUE_14-onoff: 0
2019-01-27 12:00:15 caching: Terrassenlampe_HUE_14-bri: 1
[2019-1-27 12:00:15] [FHEM] WZ_Couchlicht is light
[2019-1-27 12:00:15] [FHEM] WZ_Couchlicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: WZ_Couchlicht-onoff: 0
2019-01-27 12:00:15 caching: WZ_Couchlicht-bri: 37
[2019-1-27 12:00:15] [FHEM] WZ_Dekolicht is light
[2019-1-27 12:00:15] [FHEM] WZ_Dekolicht has
[2019-1-27 12:00:15] [FHEM] On [onoff;on,off]
[2019-1-27 12:00:15] [FHEM] Brightness [bri]
2019-01-27 12:00:15 caching: WZ_Dekolicht-onoff: 0
2019-01-27 12:00:15 caching: WZ_Dekolicht-bri: 37
[2019-1-27 12:00:15] [FHEM] aeotec.trockner is switch
[2019-1-27 12:00:15] [FHEM] aeotec.trockner has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: aeotec.trockner-power: 0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0 W')
2019-01-27 12:00:15 caching: aeotec.trockner-energy: 9.513 kWh previous: 9.513 delta_time: 600 s
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 9.513 (as number; from ' 9.513 kWh previous: 9.513 delta_time: 600 s')
2019-01-27 12:00:15 caching: aeotec.trockner-state: on
[2019-1-27 12:00:15] [FHEM] zwave.fitnessraum_heizung is switch
[2019-1-27 12:00:15] [FHEM] zwave.fitnessraum_heizung has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.fitnessraum_heizung-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.fitnessraum_heizung-energy: 995.67 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 995.67 (as number; from ' 995.67 kWh')
2019-01-27 12:00:15 caching: zwave.fitnessraum_heizung-state: on
[2019-1-27 12:00:15] [FHEM] zwave.fitnessraum_tv is switch
[2019-1-27 12:00:15] [FHEM] zwave.fitnessraum_tv has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
[2019-1-27 12:00:15] [FHEM] CurrentRelativeHumidity [humidity]
2019-01-27 12:00:15 caching: zwave.fitnessraum_tv-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.fitnessraum_tv-energy: 15.85 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 15.85 (as number; from ' 15.85 kWh')
2019-01-27 12:00:15 caching: zwave.fitnessraum_tv-state: off
2019-01-27 12:00:15 caching: zwave.fitnessraum_tv-humidity: 0.0 %
[2019-1-27 12:00:15] [FHEM] zwave.garage_tor_links is switch
[2019-1-27 12:00:15] [FHEM] zwave.garage_tor_links has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.garage_tor_links-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.garage_tor_links-energy: 21146021.11 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 21146021.11 (as number; from '21146021.11 kWh')
2019-01-27 12:00:15 caching: zwave.garage_tor_links-state: off
[2019-1-27 12:00:15] [FHEM] zwave.garagenlampe is switch
[2019-1-27 12:00:15] [FHEM] zwave.garagenlampe has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.garagenlampe-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.garagenlampe-energy: 6.06 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 6.06 (as number; from '6.06 kWh')
2019-01-27 12:00:15 caching: zwave.garagenlampe-state: off
[2019-1-27 12:00:15] [FHEM] zwave.geraeteschuppen is switch
[2019-1-27 12:00:15] [FHEM] zwave.geraeteschuppen has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.geraeteschuppen-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.geraeteschuppen-energy: 15.1 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 15.1 (as number; from '15.1 kWh')
2019-01-27 12:00:15 caching: zwave.geraeteschuppen-state: off
[2019-1-27 12:00:15] [FHEM] zwave.poollampen3x is switch
[2019-1-27 12:00:15] [FHEM] zwave.poollampen3x has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.poollampen3x-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.poollampen3x-energy: 66.19 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 66.19 (as number; from '66.19 kWh')
2019-01-27 12:00:15 caching: zwave.poollampen3x-state: off
[2019-1-27 12:00:15] [FHEM] zwave.poolpumpe is switch
[2019-1-27 12:00:15] [FHEM] zwave.poolpumpe has
[2019-1-27 12:00:15] [FHEM] Custom Voltage [voltage]
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.poolpumpe-voltage: 0.002819 V
[2019-1-27 12:00:15] [FHEM] caching: Custom Voltage: 0.002819 (as number; from '0.002819 V')
2019-01-27 12:00:15 caching: zwave.poolpumpe-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.poolpumpe-energy: 611.18 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 611.18 (as number; from '611.18 kWh')
2019-01-27 12:00:15 caching: zwave.poolpumpe-state: off
[2019-1-27 12:00:15] [FHEM] zwave.poolscheinwerfer is switch
[2019-1-27 12:00:15] [FHEM] zwave.poolscheinwerfer has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.poolscheinwerfer-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.poolscheinwerfer-energy: 0.64 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 0.64 (as number; from '0.64 kWh')
2019-01-27 12:00:15 caching: zwave.poolscheinwerfer-state: off
[2019-1-27 12:00:15] [FHEM] zwave.switch_bl_lampen is switch
[2019-1-27 12:00:15] [FHEM] zwave.switch_bl_lampen has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.switch_bl_lampen-power: 0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0 W')
2019-01-27 12:00:15 caching: zwave.switch_bl_lampen-energy: 38.11 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 38.11 (as number; from '38.11 kWh')
2019-01-27 12:00:15 caching: zwave.switch_bl_lampen-state: off
[2019-1-27 12:00:15] [FHEM] zwave.tank_arbeitszimmer is switch
[2019-1-27 12:00:15] [FHEM] zwave.tank_arbeitszimmer has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.tank_arbeitszimmer-power: 15.5 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 15.5 (as number; from '15.5 W')
2019-01-27 12:00:15 caching: zwave.tank_arbeitszimmer-energy: 170.17 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 170.17 (as number; from '170.17 kWh')
2019-01-27 12:00:15 caching: zwave.tank_arbeitszimmer-state: on
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_lena is switch
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_lena has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.tv_cst_lena-power: 57.2 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 57.2 (as number; from '57.2 W')
2019-01-27 12:00:15 caching: zwave.tv_cst_lena-energy: 305.82 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 305.82 (as number; from '305.82 kWh')
2019-01-27 12:00:15 caching: zwave.tv_cst_lena-state: on
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_patrick is switch
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_patrick has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.tv_cst_patrick-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.tv_cst_patrick-energy: 205.77 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 205.77 (as number; from '205.77 kWh')
2019-01-27 12:00:15 caching: zwave.tv_cst_patrick-state: off
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_sleep is switch
[2019-1-27 12:00:15] [FHEM] zwave.tv_cst_sleep has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.tv_cst_sleep-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.tv_cst_sleep-energy: 184.03 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 184.03 (as number; from '184.03 kWh')
2019-01-27 12:00:15 caching: zwave.tv_cst_sleep-state: off
[2019-1-27 12:00:15] [FHEM] zwave.zisterne_pumpe is switch
[2019-1-27 12:00:15] [FHEM] zwave.zisterne_pumpe has
[2019-1-27 12:00:15] [FHEM] Custom Power [power]
[2019-1-27 12:00:15] [FHEM] Custom Energy [energy]
[2019-1-27 12:00:15] [FHEM] On [state;on,off]
2019-01-27 12:00:15 caching: zwave.zisterne_pumpe-power: 0.0 W
[2019-1-27 12:00:15] [FHEM] caching: Custom Power: 0 (as number; from '0.0 W')
2019-01-27 12:00:15 caching: zwave.zisterne_pumpe-energy: 13.62 kWh
[2019-1-27 12:00:15] [FHEM] caching: Custom Energy: 13.62 (as number; from '13.62 kWh')
2019-01-27 12:00:15 caching: zwave.zisterne_pumpe-state: off
[2019-1-27 12:00:15] BearerToken '...E4DE2' read from MyAlexa
[2019-1-27 12:00:15] 39_alexa.pm is new version: true
[2019-1-27 12:00:15] sshautoconf: completed successfully
[2019-1-27 12:00:15] *** SSH: proxy configuration set up done
[2019-1-27 12:00:15] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-1-27 12:00:15] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20MyAlexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:15] Starting SSH with -R 1234:127.0.0.1:39121 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-1-27 12:00:15] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-1-27 12:00:15] [FHEM] executing: http://192.168.178.4:8083/fhem?cmd=%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20MyAlexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7BMyAlexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-1-27 12:00:15] *** SSH: proxy connection established
[2019-1-27 12:00:15] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
Zitat von: topa_LE am 27 Januar 2019, 11:56:29
so perfekt, danke euch beiden ...
Besten Sonntagsdank!!! ;)
Zitat von: topa_LE am 27 Januar 2019, 11:56:29
noch das list vom Device:
Zitat von: topa_LE am 27 Januar 2019, 12:01:47
@Mad:
Noch das gewünschte Log von Stop/Start:
Zitat von: topa_LE am 27 Januar 2019, 13:50:01
Ja, alles bestens!
ZitatAlexa: using logfile: ./log/alexa-2019-01-29.log
PERL WARNING: Use of uninitialized value $logfile in string ne at ./FHEM/39_alexa.pm line 296.
Deleting alexa-2019-01-22.log
alexa device already defined as Alexa.[2019-1-31 18:40:22] [FHEM] trying longpoll to listen for fhem events
[2019-1-31 18:40:22] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=xxxxxxxxxxxxxx
[2019-1-31 18:40:22] [FHEM] got csrfToken: csrf_xxxxxxxxxxxxxxx
[2019-1-31 18:40:22] [FHEM] Checking devices and attributes...
[2019-1-31 18:40:22] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_xxxxxxxxxxxxxxx&XHR=1
[2019-1-31 18:40:22] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_xxxxxxxxxxxxxxx&XHR=1
[2019-1-31 18:40:22] [FHEM] waiting for events ...
[2019-1-31 18:40:22] [FHEM] Fetching FHEM devices...
[2019-1-31 18:40:22] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_xxxxxxxxxxxxxxx&XHR=1
[2019-1-31 18:40:22] [FHEM] longpoll ended, reconnect in: 21200msec
[2019-1-31 18:40:22] [FHEM] There was a problem connecting to FHEM (https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_xxxxxxxxxxxxxxx&XHR=1).
[2019-1-31 18:40:22] [FHEM] 401: Authorization Required
[2019-1-31 18:40:22] [FHEM] There was a problem connecting to FHEM (https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_xxxxxxxxxxxxxxx&XHR=1).
[2019-1-31 18:40:22] [FHEM] 401: Authorization Required
[2019-1-31 18:40:22] [FHEM] There was a problem connecting to FHEM
[2019-1-31 18:40:22] [FHEM] 401: Authorization Required
*** FHEM: connection failed: 401: Authorization RequiredZitat von: justme1968 am 31 Januar 2019, 18:49:24
du kannst nur ein alexa device haben und auch nur ein laufendes alexa-fhem.
also entweder die alte version deaktivieren und umsteigen oder im alexa device disable setzen und die alte version weiter verwenden.
Zitatalexa device already defined as Alexa.
Zitat von: justme1968 am 31 Januar 2019, 22:35:09
es gibt seit eben die version 0.5.16 von alexa-fhem.
ZitatSTATE stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
Zitatxxx@odroid:~# ps -ef | egrep '(alexa|ssh)'
xxx 508 1 0 12:22 ? 00:00:00 /usr/sbin/sshd -D
xxx 5584 508 0 14:37 ? 00:00:00 sshd: root@pts/0
xxx 7465 5690 0 14:55 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)
ZitatAttributes: alexaFHEM-cmd: /usr/local/bin/alexa-fhem.
root@raspberrypi:/opt/fhem/log# npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.15
updated 3 packages in 13.276s
list DummyNameZitat von: MadMax-FHEM am 03 Februar 2019, 20:19:20
Poste doch mal ein list des dummy:Code Auswählenlist DummyName
Und das Ergebnis bitte in "code-Tags" (das '#' im Menü) posten...
Gruß, Joachim
Internals: FUUID 5c542341-f33f-599c-5fa0-5089b1eda2f9e3a1
NAME Zentrale
NR 188
STATE Teilscharf
TYPE dummy
READINGS: 2019-02-03 19:30:06 state on
Attributes:
alexaName Zentrale
eventMap on:Teilscharf off:Aus dimup:Scharf dimdown:Alarm
room BMZ
webCmd Teilscharf:Aus:Scharf:Alarm
Zitat... aber mehr Infos gibt dies auch nicht aus ..
defmod du_Feb dummy
attr du_Feb alexaName zentrale
attr du_Feb eventMap on:Teilscharf off:Aus
attr du_Feb setList on off
attr du_Feb webCmd Teilscharf:Aus
Zitat von: TomLee am 03 Februar 2019, 21:03:12
Doch, wie überall erwähnt kein setlist bei einem dummy angegeben.
mappen kann man zwei Zustände on und off, so hab ichs zumindest verstanden.
Versuchs mal so:Code Auswählendefmod du_Feb dummy
attr du_Feb alexaName zentrale
attr du_Feb eventMap on:Teilscharf off:Aus
attr du_Feb setList on off
attr du_Feb webCmd Teilscharf:Aus
defmod du_Feb dummy
attr du_Feb alexaName zentrale
attr du_Feb eventMap Teilscharf:on Aus:off
attr du_Feb setList state:on,off
attr du_Feb webCmd Teilscharf:Aus
Zitat von: TomLee am 04 Februar 2019, 16:40:42
Korrektur :P:Code Auswählendefmod du_Feb dummy
attr du_Feb alexaName zentrale
attr du_Feb eventMap Teilscharf:on Aus:off
attr du_Feb setList state:on,off
attr du_Feb webCmd Teilscharf:Aus
Zitat von: TomLee am 04 Februar 2019, 17:25:15
Du kannst das mit deinem dummy, einem zusätzlichen readingsProxy und vier Routinen umsetzen, gar kein Problem.
Ich zeig dir später ein Beispiel.
defmod rp_Zentrale readingsProxy Zentrale:state
attr rp_Zentrale alexaName irgendwas
attr rp_Zentrale event-on-change-reading .*
attr rp_Zentrale genericDeviceType switch
attr rp_Zentrale room irgendwo bzw. Filter
attr rp_Zentrale setFn {($CMD eq "on")?"dimup":"dimdown"}
attr rp_Zentrale setList on offdefmod Zentrale dummy
attr Zentrale alexaName zentrale
attr Zentrale eventMap Teilscharf:on Aus:off Scharf:dimup Alarm:dimdown
attr Zentrale setList state:on,off,dimup,dimdown
attr Zentrale webCmd Teilscharf:Aus:Scharf:AlarmZitat von: TomLee am 04 Februar 2019, 18:16:07Code Auswählendefmod Zentrale dummy
attr Zentrale alexaName zentrale
attr Zentrale eventMap Teilscharf:on Aus:off Scharf:dimup Alarm:dimdown
attr Zentrale genericDeviceType light
attr Zentrale setList state:on,off,dimup,dimdown
attr Zentrale webCmd Teilscharf:Aus:Scharf:Alarm
ungetestet
wobei mir hier jetzt auffällt besser einen anderen alexaName zu verwenden
Internals:
FUUID 5c542341-f33f-599c-5fa0-5089b1eda2f9e3a1
NAME Zentrale
NR 188
STATE Teilscharf
TYPE dummy
READINGS:
2019-02-04 19:14:11 state on
Attributes:
alexaName Zentrale
eventMap on:Teilscharf off:Aus dimup:Scharf dimdown:Alarm
genericDeviceType light
room BMZ
setList state:on,off,dimup,dimdown
webCmd Teilscharf:Aus:Scharf:Alarm
Zitat von: moerte am 04 Februar 2019, 19:18:24
Hab die Attribute meinen Dummy jetzt hinzugefügt.
Alexa findet nur den rp_Zentrale.
Hier ein ListZitat
Internals:
FUUID 5c542341-f33f-599c-5fa0-5089b1eda2f9e3a1
NAME Zentrale
NR 188
STATE Teilscharf
TYPE dummy
READINGS:
2019-02-04 19:14:11 state on
Attributes:
alexaName Zentrale
eventMap on:Teilscharf off:Aus dimup:Scharf dimdown:Alarm
room BMZ
setList state:on,off,dimup,dimdown
webCmd Teilscharf:Aus:Scharf:Alarm
Zitat von: 87insane am 05 Februar 2019, 07:19:36
Guten Morgen zusammen,
aktuell überlege ich mir abhängig vom letzten Wecker, der morgens gestellt ist, die Rollos hoch zu fahren. Nehmen wir mal an ein Wecker steht auf 5:00 Uhr und einer um 6:00 Uhr, dann sollen meine Rollos mit dem 06:00 Uhr Wecker hoch fahren. Wie ich das über notify oder sonst wie lösen könnte, denke ich zu wissen. Mir fehlt aber so etwas wie ein reading "gestellte Wecker". Gibt es so etwas oder kann ich das irgendwie hinzufügen?
Die Wecker an sich werden direkt über Alexa gestellt. Nun muss Fhem nur die Info haben, welche Wecker gestellt sind.
https://wiki.fhem.de/wiki/Alexa-Fhem#Wecker habe ich gesehen aber verstehe es so, dass ich hierüber Wecker in Alexa einstelle und nicht auslese. Hinzu, denke ich, es müsste theoretisch auch ohne separaten Skill gehen..Nur wie?
Gruß,
Kai
ZitatAlexa-FHEM: AWS —> FHEM
EchoDevice: FHEM —> Echo-Geräte
Zitat von: 87insane am 05 Februar 2019, 08:21:08
Ich werde mich mit 37_ nochmal beschäftigen. Da es aber eine ADB Schnittstelle ist, kannst du bei FireTVs zB nur mit USB Debugging arbeiten.
Internals:
.attreocr-thresholdhumidity 43
.attreocr-thresholdtemperature 22.9
DEF 13
FUUID 5c460cd5-f33f-221a-1aec-6b0324b26b026767
IODev myJeeLink
LASTInputDev myJeeLink
LaCrosse_lastRcv 2019-02-07 18:27:39
MSGCNT 10512
NAME LaCrosse_Temperatur_Wohnzimmer
NR 212
STATE T: 22.9 H: 44
TYPE LaCrosse
addr 13
battery_new 0
corr1 0
corr2 0
myJeeLink_MSGCNT 10517
myJeeLink_RAWMSG OK 9 19 1 4 205 44
myJeeLink_TIME 2019-02-07 18:27:39
previousH 44
previousT 22.9
sensorType 0=T(H)
.attraggr:
.attreocr:
temperature:0.2
humidity:2
.*
.attrminint:
READINGS:
2019-02-07 18:22:49 1 9.0
2019-02-07 18:22:49 Ddewpoint 10.0
2018-10-23 06:44:35 GeraeteStatus ok
2019-02-07 18:22:49 absFeuchte 9.0
2019-02-07 18:27:39 battery ok
2019-02-07 18:27:39 humidity 44
2019-02-07 18:27:39 state T: 22.9 H: 44
2019-02-07 18:27:39 temperature 22.9
Attributes:
DTimeout 1
IODev myJeeLink
alexaName Wohnzimmer Temperatur
alexaRoom Wohnzimmer
alias Temperatur Wohnzimmer
event-on-change-reading temperature:0.2,humidity:2,.*
genericDeviceType thermometer
icon icoTemp
room 10_ Wohnzimmer,96_Temperatur,LaCrosse
ZitatWie ist die Temperatur von Wohnzimmer
ZitatTemperatur von Wohnzimmer
Zitat von: TomLee am 07 Februar 2019, 18:31:36Besser ist es den Sensor "TemperatursensorWohnzimmer" zu nennen, in der App eine Gruppe Wohnzimmer erstellen, und dort den Sensor reinzupacken.
alexaName ändern in Wohnzimmer und mit
abfragen.
Zitat von: TomLee am 07 Februar 2019, 18:31:36
alexaName ändern in Wohnzimmer und mit
abfragen.
Ich sag/frag immer:
Zitatüber die app in eine gruppe stecken
Zitat von: Esjay am 07 Februar 2019, 18:38:36
Besser ist es den Sensor "TemperatursensorWohnzimmer" zu nennen, in der App eine Gruppe Wohnzimmer erstellen, und dort den Sensor reinzupacken.
Dann blockierst du den Namen " Wohnzimmer" als Raum nicht, und kannst trotzdem fragen wie die Temp im Wohnzimmer ist.
Grüße
Zitataber das ist jeweils hoch und runter um 10%
ZitatEcho, fenster hoch
2019-02-07 21:14:18 caching: Rollo_EG_Kueche-motor: up:off
2019-02-07 21:14:25 caching: Rollo_EG_Kueche-motor: stop:25
2019-02-07 21:14:25 caching: Rollo_EG_Kueche-pct: 25
alexa-fhem -D -c /opt/fhem/config.json > debug.logStartup rejected. Reason: Error: ENOENT: no such file or directory, open './key.pem'
Zitat von: TomLee am 08 Februar 2019, 09:42:36
Mir ist jetzt nach der Umstellung gar nicht klar wie ich alexa im Debug-Modus starte.
Meine alte config.json, cert und key Dateien liegen in opt/fhem und attribute alexaFHEM-config ist gesetzt.
MitCode Auswählenalexa-fhem -D -c /opt/fhem/config.json > debug.log
bekomme ich einCode AuswählenStartup rejected. Reason: Error: ENOENT: no such file or directory, open './key.pem'
Zitat von: MadMax-FHEM am 08 Februar 2019, 09:53:23
Das alexa-log kannst du ganz einfach über das Alexa-Modul in fhem erreichen...
Gruß, Joachim
Zitatund alexa logfalsch
2019-02-07 21:14:18 caching: Rollo_EG_Kueche-motor: up:off
2019-02-07 21:14:25 caching: Rollo_EG_Kueche-motor: stop:25
2019-02-07 21:14:25 caching: Rollo_EG_Kueche-pct: 25Zitat-D in alexaFHEM-params setzen ins log
schauen. link links oben.
pi@raspberrypi:~ $ alexa-fhem -D -c /opt/fhem/config.json > debug.log
Startup rejected. Reason: Error: ENOENT: no such file or directory, open './key.pem'
ZitatEcho, fenster runter
Zitat[2019-2-8 12:12:56] >>>> [srv] {"directive":{"header":{"namespace":"Alexa.PercentageController","name":"AdjustPercentage","payloadVersion":"3","messageId":"ac868792-7e27-408c-83ba-e34ea1a1f79e","correlationToken":"AAAAAAAAAQDqQ7WIzSv50LZT/HSyE62bDAIAAAAAAAAvJh47W75LeJsJcBIzS9qzNKSBHIgdQioVFZLWrExviXlm0vi+XcF/AtyUjy9lhuDyeuqZn8t0jiDHx1BplaupKBFsnqyf3Z1JGca0U+2LL2nH5cv4FhVoTrIkUFjoJ4uinVMWmnGawRUJOxALZdHoDNJWJQdL/yVzcV44z97dK5AvDJb03Q0wzf2E/V6XXXXXXrmLG3dYkl/FvqIVsYmaBdnn/Eicq4TDaDQ4T5oQ277GpO7/R0Tk7O99u3ggtZ4ru1JzGETtQ3qugdzFm5RHb4gFp3UV5fiImgsvUjxG7tQGCbRvQsal0WYURa8/o7LlbA8aHUknVYfkIDczxMLhaIXXXXXXXXaHIHyU97mYx3jVRGut5Wqz2YSMg4LtScbq1aZRsL6D0eRXMqOt5ZmqK0vOK0XVjjHSf4iqh+2baTAzTAvkRWc/tOfugxGLQVjJGiXKqmzYRIJ4KcwtzZ+x2GRC5zcQJ1sWAQW0O8zUwv+sczvZ2sZWb8L1pW10n0AmA7Zx4m+LjWxZzMqlt2q9KgrMxBQhDn2YAw=="},"endpoint":{"scope":{"type":"BearerToken","token":"Atza|IwEBIN210DfxKc1WgFSer2mXXXXXg8-9IlBJvie6AiB0WN7chZB-quyEwpyiYoh_VHJKWpjVUkPeKYRHiIbHTiE_DPei98R44XW4dZQjeq5K0Dugt_h_hiua6wsNNAhuMnll0ebwNyo2KbQq07qTANkv2CWQhcsaSLtdpv-7VLXJMf1Cf_eT2VbI5YSc4mpvoKtfVIWJNJoTQ8-N4zycHj4ysXHSlhsxrBqASC33czt57ZBVwpA_R9RoG_Cp6L24WFLPXILTkY1J24gz52ndFxtJyHvFIs_irHkQi7nrF1iVLWZwhIDj9gQSj5oP-qjGJciWoqHiKMJ-1xEHxeiNASE3zRnoNvpRCXXXXX4VFbMxPQwEipmG9DjbGgCMCjgql14taLKt-idzrVug_7HC8vWH3i4S5rb5GprP8_IFFn34MAyRmlm5ZIHtovR4Od9h0IdQFNTQbA2VvDR7WgvleHsx4_LwKC2EAGJTuQ5XqEF2W54305Otn7nqRLwxuYQl4"},"endpointId":"NEQ0512XXX","cookie":{"fuuid":"5c48e035-f33f-ef3d-979d-f94b6d8253424926","device":"Rollo_EG_Kueche"}},"payload":{"percentageDelta":-25}}}
[2019-2-8 12:12:57] accepted new token
[2019-2-8 12:12:57] { aud:
'amzn1.application-oa2-client.707cce05387e443ca7e778056XXXXX0',
user_id: 'amzn1.account.AH6IOT3GZ6EL36WJP5M2USNXXXXX',
iss: 'https://www.amazon.com',
exp: 3598,
app_id: 'amzn1.application.e2e133bc63b04704a3e512589XXXXX',
iat: 1549624375 }
[2019-2-8 12:12:57] [FHEM] Rollo_EG_Kueche: executing set cmd for TargetPosition with value 75
[2019-2-8 12:12:57] [FHEM] executing: http://192.168.188.26:8083/fhem?cmd=set%20Rollo_EG_Kueche%20pct%2075&XHR=1
[2019-2-8 12:12:57] <<<< [srv] {"context":{"properties":[{"namespace":"Alexa.PercentageController","name":"percentage","value":75,"timeOfSample":"2019-02-08T11:12:57.328Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"ef947920-e162-4155-8f63-3fc8be0f9922","correlationToken":"AAAAAAAAAQDqQ7WIzSv50LZT/HSyE62bDAIAAAAAAAAvJh47W75LeJsJcBIzS9qzNKSBHIgdQioVFZLWrExviXlm0vi+XcF/AtyUjy9lhuDyeuqZn8t0jiDHx1BplauXXXXXXXddRtrTtrmLG3dYkl/FvqIVsYmaBdnn/Eicq4TDaDQ4T5oQ277GpO7/R0Tk7O99u3ggtZ4ru1JzGETtQ3qugdzFm5RHb4gFp3UV5fiImgsvUjxG7tQGCbRvQsal0WYURa8/o7LlbA8aHUknVYfkIDczxMLhaIXu4EzvoDswg0Mq1CiO/IMG0rUeKYizYeWye5TuhBTpQA37ILkAt0IouTyKaXxPAF22sEUJdWbnqLGfHmN5LaRRJ89lAHfk8FEQacgN4gTjZ/fnUZlPs6XR0LYMOqbU0OHQNSU8lRtSTywbyaHIHyU97mYx3jVRGut5Wqz2YSMg4LtScbq1aZRsL6D0eRXMqOt5ZmqK0vOK0XVjjHSf4iqh+2baTAzTAvkRWcXXXXXXXXczvZ2sZWb8L1pW10n0AmA7Zx4m+LjWxZzMqlt2q9KgrMxBQhDn2YAw=="},"endpoint":{"scope":{"type":"BearerToken","token":"Atza|IwEBIN210DfxKc1WgFSer2mh01TPSBg8-9IlBJvie6AiB0WN7chZB-quyEwpyiYoh_VHJKWpjVUkPeKYRHiIbHTiXXXXXE_DPei98R44XW4dZQjeq5K0Dugt_h_hiua6wsNNAhuMnll0ebwNyo2KbQq07qTANkv2CWQhcsaSLtdpv-7VLXJMf1Cf_eT2VbI5YSc4mpvoKtfVIWXL24WFLPXILTkY1J24gz52ndFxtJyHvFIs_irHkQi7nrF1iVLWZwhIDj9gQSj5oP-qjGJciWoqHiKMJ-1xEHxeiNASE3zRnoNvpRCM57LzkGRY4VFbMxPQwEipmG9DjbGgCMCjgql14taLKt-idzrVug_7HC8vWH3i4S5rb5GprP8_IFFn34MAyRmlm5ZIHtovR4Od9h0IdQFNTQbA2VvDR7WgvleHsx4_LwKC2EAGJTuQ5XqEF2W54305Otn7nqRLwxuYQl4"},"endpointId":"NEQ05XXXX"},"payload":{}}}
2019-02-08 12:13:02 caching: Rollo_EG_Kueche-motor: down:on
[2018-12-21 12:41:34] accepted new token
**** Received Directive: {"directive":{"header":{"namespace":"Alexa.PercentageController","name":"AdjustPercentage","payloadVersion":"3","messageId":"061fe4fa-7021-4934-bae9-001d4b24ea22","correlationToken":"...},"endpointId":"KEQ0155768","cookie":{"device":"Rolladen"}},"payload":{"percentageDelta":-10}}}
[2018-12-21 12:41:34] [FHEM Schlafzimmer] Rolladen: executing set cmd for TargetPosition with value 60
defmod Rollo_EG_Kueche CUL_HM 4AABAF
attr Rollo_EG_Kueche userattr room_map structexclude
attr Rollo_EG_Kueche IOgrp VCCU
attr Rollo_EG_Kueche alexaName fenster
attr Rollo_EG_Kueche autoReadReg 4_reqStatus
attr Rollo_EG_Kueche comment room Rollo_OG_Schlafzimmer Rollo_OG_Bad rp_EG_Rollo_Kueche_80
attr Rollo_EG_Kueche devStateIcon (100|on):fts_shutter_10@green (0|off):fts_shutter_100@red 1\d.*:fts_shutter_90 2\d.*:fts_shutter_80 3\d.*:fts_shutter_70 4\d.*:fts_shutter_60 5\d.*:fts_shutter_50 6\d.*:fts_shutter_40 7\d.*:fts_shutter_30 8\d.*:fts_shutter_20 9\d.*:fts_shutter_10 9\d.*:fts_shutter_10
attr Rollo_EG_Kueche expert 2_raw
attr Rollo_EG_Kueche firmware 2.8
attr Rollo_EG_Kueche genericDeviceType blind
attr Rollo_EG_Kueche model HM-LC-BL1-FM
attr Rollo_EG_Kueche peerIDs 00000000,
attr Rollo_EG_Kueche room Rollladen,Alexacontrol,CUL_HM,Homekit
attr Rollo_EG_Kueche serialNr NEQ0512953
attr Rollo_EG_Kueche structexclude alexaName
attr Rollo_EG_Kueche subType blindActuator
attr Rollo_EG_Kueche webCmd statusRequest:toggleDir:on:off:up:down:stop
nternals:
FUUID 5c44076b-f33f-f372-b514-07174390d07312a4
NAME alexa
NOTIFYDEV global
NR 799
NTFY_ORDER 50-alexa
STATE stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
TYPE alexa
logfile ./log/alexa-%Y-%m-%d.log
.attraggr:
.attrminint:
CoProcess:
cmdFn alexa_getCMD
name alexaFHEM
state stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
READINGS:
2019-01-17 07:33:45 .eventToken {"access_token":"Atza|IwEBIIrSp1v7NwQ6L3s3vlvZ2yeA9azRHmPVy59s0gsKxdNuudkNfZA503FQU4c0CxF_4dPui6nwr0kQZZaZrVM_f6DFGS1rn657OAwsyzU-6r1QC1-Sf0Xhg59Eh2cRt6B6JzwjEz3erztF0KSh45TNTF97bbnXXQp0RUECLT1RVjlRTpOQFNvRAQUS_cA-R_zL6IPnDYGlgCsgRNaYfUAzTDtowcFi-wOGWDTwa0Ws4KvVcA4XzF4QtBj9nnLd_CcMLbyTA77HwxYfRIDAYgPBfNZ45G1CFo6qnDknrcIHK0Gh9ujFPSM8DQBQWIJlR2NWgKkjhq2gOOQfjTMpqAbjb1RJ0Ga_3sbk8dHRtj6qhSr5_lAXs3KW8z0B0uS2Zg97S2XTNks2m9DZmxQ-HtS0KropUSid2g2H1BmmOrDL9AtVLS7BU-2nqa97BeSw8Pe_abDcshfvvaZc__C9LIKy6cUbGplFO22u2zunZcfQYex83w","refresh_token":"Atzr|IwEBIJuKngDQYT3n___qVWQNZb_2oWlAdxrIJnNiK0elFmgKUTJXWqYreE-nSAT0SN2wN5GNayBlvf9KKxxHq5m1M01bUbK6cuEvY3p49QhVfrQwDUeG0SEiqj9FgrLevUu6Y0CLKC9_hdOE98xBI0Oog3uVYTXFP3bBnO3d3yfhG0s6Lzt4HT5LDvTB7GiL0bCvM5KrQnhgzMkddbzcgycZdAMHqCmJfymcPOvqkJEYF10IxJpJ4aKqrHcIXMq70kAw9hu8pBVmWDKHMnbsL_T_f-GXBKBSuKDxUeUswaZrnDbWqTlks-OevurGqNAW7x7Ju5V4XXD9ojvl1GwxoYVY44azTCPIhA5AWA1dp5ntrGdaNiwvWZpY6sszLjMBHDgmntZDuGFBjkyvGayTsUiXMqE2AnrCcVYrDLt7lh8gNtaQrKDUkuGnyVQFQlZ7agzVBO1dgEphWCFd0pLVW8JGd6zHZfuUBmaCilBC2sbJhuBzyA","token_type":"bearer","expires_in":3600}
2019-02-08 10:06:29 alexaFHEM stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
2019-02-08 08:43:13 alexaFHEM.ProxyConnection stopped
2019-01-17 07:15:31 alexaFHEM.bearerToken crypt:737475240d57780e7673530d010f275a
2019-01-17 07:15:31 alexaFHEM.skillRegKey crypt:0175705e01270a761e745577000c5a572105540b5102757c031e232672210207730e76240f5d0e017608
2019-02-05 15:06:33 echoId amzn1.ask.device.AGDU6HCPG7NCO2HQ4N6PZDRX263X6MZFPI75P26BW7O7UXRHRFTHS7TUWAD34SN7RJ4H2WUUJKO3UZD2KH2BYYIA4PCISVCM37CRYLWEF4DWY4BYED7GR72KN5NTBS27HFYV2TOFZHTYYQWRAZL66MBONKSQM5C5DZVW7WPGPU3QEWQQHZ3XS
2019-02-05 15:06:33 echoRoom unknown
2019-02-05 15:06:33 fhemIntent woisttelefon
2019-01-31 10:41:16 intent SessionEndedRequest
Attributes:
DbLogExclude .*
alexaFHEM-auth crypt:5f5e580354165651470b0650555107110d450959
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log ./log/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nacht
{currentRadioTitle()}=was läuft gerade im radio
{currentRadioTitle()}=was gerade im radio läuft
aussentemp=aussen temperatur
wohnzimmertemp= wohnzimmer temperatur
feuchtebad= Luftfeuchtigkeit bad
luftfeuchte = Luftfeuchtigkeit aussen
denonauf = lauter
denonab = leiser
sonosab = Sonos leiser
sonosauf = Sonos lauter
tonean = ton ein
toneaus = ton aus
gutenabend = guten abend
bildterrasse= bild von terrasse
bildwohnzimmer = bild vom wohnzimmer
bilddachdoben = bild vom dachboden
bildkeller = bild vom keller
deckenlichtdunkler = deckenlicht dunkler
deckenlichtheller = deckenlicht heller
bogenlampedunkler= bogenlampe dunkler
bogenlampeheller = bogenlampe heller
fernsehlichtdunkler = fernsehlicht dunkler
fernsehlichtheller = fernsehlicht heller
{alexa_hallo_alexa()}=hallo alexa
{wohnstubetemperatur()}= wohnstube temperatur
{ fhem("set deckenlicht.dummy on");;;;return "das licht an der decke wurde eingeschalten"}:mach das licht an der decke an
{sonnenuntergang (30,"Milight_Bogenlampe")}=sonnen untergang
{wakeUp (30,"Milight_Deckenlampe")}=sonnen aufgang
woisttelefon = wo ist telefon
woisthandy = wo ist Handy
woistmeinhandy = wo ist mein Handy
{Alexacmd ("gutenmorgen")}=guten morgen
{Alexacmd ("guteNacht")}=gute nacht
{Alexacmd ("tvlauter")}=Fernseher lauter
{Alexacmd ("tvleiser")}=Fernseher leiser
{Alexacmd ("tvprgup")}=Fernseher nächstes Programm
{Alexacmd ("tvprgdown")}=Fernseher vorheriges Programm
{Alexacmd ("tverstes")}=Fernseher das erste
{Alexacmd ("tvzweites")}=Fernseher das zweite
{Alexacmd ("tvsateins")}=fernseher sat eins
{Alexacmd ("skyerstes")}=Fernseher sky eins
{Alexacmd ("skyzweites")}=fernseher sky zwei
{Alexacmd ("skysport")}=Fernseher sky sport eins
{Alexacmd ("skysport2")}=fernseher sky sport zwei
{Alexacmd ("tvaus")}= t v aus
{Alexacmd ("fernseheran)"}= fernseher einschalten
{Alexacmd ("fernseheraus)"}= fernseher ausschalten
{alexaRoomTemperature()}=wie warm ist es Zuhause
{alexastatusFensterOffen()}=ob noch fenster auf sind|welche fenster auf sind|welche fenster noch auf sind
room Alexa
stateFormat alexaFHEM
mikelsoft@mikelsoft-ZBOX-CI320NANO-series:/opt/fhem$ sudo npm install -g alexa-fhem
npm ERR! path /usr/lib/node_modules/alexa-fhem/node_modules/.bin/har-validator
npm ERR! code EEXIST
npm ERR! Refusing to delete /usr/lib/node_modules/alexa-fhem/node_modules/.bin/har-validator: is outside /usr/lib/node_modules/alexa-fhem/node_modules/har-validator and not a link
npm ERR! File exists: /usr/lib/node_modules/alexa-fhem/node_modules/.bin/har-validator
npm ERR! Move it away, and try again.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mikelsoft/.npm/_logs/2019-02-08T12_33_14_106Z-debug.log
Zitat von: Esjay am 22 Januar 2019, 18:35:45
Super danke.
Ich habe jetzt mal das mapping wie folgt gesetzt. Annahme meinerseits, reading=channel ist der aktuelle Kanal, cmd ist dementsprechend das set xyz channel xCode AuswählenChannelController:reading=channel,cmd=channelCode Auswählen{
"Arg":"FormularF1",
"Results": [
{
"Name":"FormularF1",
"PossibleSets":"toggle:noArg on:noArg off:noArg volume:slider,0,1,100 volumeUp:noArg volumeDown:noArg msg remoteControl channelUp:noArg channelDown:noArg play:noArg pause:noArg stop:noArg record:noArg showText downmix:on,off channel:Das_Erste_HD,ZDF_HD,RTL_HD,SAT.1_HD,ProSieben_HD,VOX_HD,kabel_eins_HD,SPORT1_HD,RTLII_HD,DMAX_HD,Sky_Cinema_HD,Sky_Cinema_+1_HD,Sky_Cinema_+24_HD,Sky_Cinema_Action_HD,Sky_Cinema_Hits_HD,Sky_Cinema_Family_HD,Sky_1_HD,Sky_Atlantic_HD,13th_Street_HD,SYFY_HD,Sky_Arts_HD,Beate-Uhse.TV_HD,SUPER_RTL_HD,Disney_Cinemagic_HD,Disney_Junior_HD,Discovery_HD,NatGeo_HD,Nat_Geo_Wild_HD,TNT_Comedy_HD,Universal_TV_HD,TNT_Serie_HD,History_HD,Spiegel_Geschichte_HD,E!_Entertainm._HD,TNT_Film_HD,Fox_HD mute:on,off input:tv,radio reboot:noArg restartGui:noArg shutdown:noArg statusRequest:noArg",
"PossibleAttrs":"alias comment:textField-long eventMap:textField-long group room suppressReading userReadings:textField-long verbose:0,1,2,3,4,5 disable:1,0 disabledForIntervals do_not_notify:1,0 https:0,1 http-method:GET,POST http-noshutdown:1,0 disable:0,1 bouquet-tv bouquet-radio timeout remotecontrol:standard,advanced,keyboard lightMode:0,1 ignoreState:0,1 macaddr:textField model wakeupCmd:textField WOL_useUdpBroadcast WOL_port WOL_mode:EW,UDP,BOTH event-aggregator event-min-interval event-on-change-reading event-on-update-reading oldreadings stateFormat:textField-long timestamp-on-change-reading alarmDevice:Actor,Sensor alarmSettings alexaName alexaRoom babbleDevice cmdIcon devStateIcon devStateIcon:textField-long devStateStyle genericDeviceType:security,ignore,switch,outlet,light,blind,thermometer,thermostat,contact,garage,window,lock homebridgeMapping:textField-long icon msgContactAudio msgContactLight msgContactMail msgContactPush msgContactScreen msgParams msgPriority msgRecipient msgRecipientAudio msgRecipientLight msgRecipientMail msgRecipientPush msgRecipientScreen msgRecipientText msgTitle msgTitleShrt msgType:text,push,mail,screen,light,audio,queue siriName sortby webCmd webCmdLabel:textField-long widgetOverride userattr",
"Internals": {
"CHANGED": "null",
"DEF": "192.168.178.55",
"INTERVAL": "45",
"NAME": "FormularF1",
"NR": "163",
"STATE": "on",
"TYPE": "ENIGMA2",
"URL": "http://192.168.178.55/",
"modelid": "F1"
},
"Readings": {
"acg": { "Value":"6", "Time":"2019-01-22 18:34:23" },
"apid": { "Value":"259", "Time":"2019-01-22 17:52:18" },
"ber": { "Value":"0", "Time":"2019-01-22 18:34:23" },
"channel": { "Value":"RTL_HD", "Time":"2019-01-22 18:02:56" },
"channelList": { "Value":"Das_Erste_HD,ZDF_HD,RTL_HD,SAT.1_HD,ProSieben_HD,VOX_HD,kabel_eins_HD,SPORT1_HD,RTLII_HD,DMAX_HD,Sky_Cinema_HD,Sky_Cinema_+1_HD,Sky_Cinema_+24_HD,Sky_Cinema_Action_HD,Sky_Cinema_Hits_HD,Sky_Cinema_Family_HD,Sky_1_HD,Sky_Atlantic_HD,13th_Street_HD,SYFY_HD,Sky_Arts_HD,Beate-Uhse.TV_HD,SUPER_RTL_HD,Disney_Cinemagic_HD,Disney_Junior_HD,Discovery_HD,NatGeo_HD,Nat_Geo_Wild_HD,TNT_Comedy_HD,Universal_TV_HD,TNT_Serie_HD,History_HD,Spiegel_Geschichte_HD,E!_Entertainm._HD,TNT_Film_HD,Fox_HD", "Time":"2019-01-22 18:23:59" },
"currentMedia": { "Value":"1:0:19:EF10:421:1:C00000:0:0:0:", "Time":"2019-01-22 18:02:56" },
"currentTitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"enigmaversion": { "Value":"2017-07-13", "Time":"2018-01-17 18:50:12" },
"eventcurrenttime": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventcurrenttime_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescription": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescription_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescriptionextended": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventdescriptionextended_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventduration_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventname": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventname_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventremaining_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventstart_next_hr": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventtitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"eventtitle_next": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"fpversion": { "Value":"None", "Time":"2018-01-17 18:50:12" },
"hdd1_capacity": { "Value":"0.9", "Time":"2018-03-02 08:52:46" },
"hdd1_free": { "Value":"0.9", "Time":"2018-03-02 08:52:46" },
"hdd1_model": { "Value":"Generic(Flash Disk)", "Time":"2018-03-02 08:52:46" },
"imageversion": { "Value":"6.0.1", "Time":"2018-01-17 18:50:12" },
"input": { "Value":"tv", "Time":"2019-01-22 17:14:10" },
"inputList": { "Value":"tv,radio", "Time":"2018-01-16 19:34:26" },
"iswidescreen": { "Value":"1", "Time":"2019-01-22 18:02:56" },
"lanmac": { "Value":"0c:8c:8f:00:45:78", "Time":"2018-03-02 08:52:46" },
"model": { "Value":"F1", "Time":"2018-01-17 18:50:12" },
"mute": { "Value":"off", "Time":"2019-01-22 17:14:10" },
"nextTitle": { "Value":"-", "Time":"2019-01-22 18:02:56" },
"onid": { "Value":"1", "Time":"2019-01-22 17:14:10" },
"pcrpid": { "Value":"255", "Time":"2019-01-22 17:52:18" },
"pmtpid": { "Value":"96", "Time":"2019-01-22 18:02:56" },
"power": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"presence": { "Value":"present", "Time":"2019-01-15 14:29:19" },
"providername": { "Value":"CBC", "Time":"2019-01-22 18:02:56" },
"recordings": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_error": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_finished": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next_counter": { "Value":"0", "Time":"2018-01-17 18:50:12" },
"recordings_next_counter_hr": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_hr": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_name": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"recordings_next_servicename": { "Value":"-", "Time":"2018-01-17 18:50:12" },
"servicename": { "Value":"RTL HD", "Time":"2019-01-22 18:02:56" },
"servicereference": { "Value":"1:0:19:EF10:421:1:C00000:0:0:0:", "Time":"2019-01-22 18:02:56" },
"servicevideosize": { "Value":"1920x1080", "Time":"2019-01-22 18:02:56" },
"sid": { "Value":"61200", "Time":"2019-01-22 18:02:56" },
"snr": { "Value":"83", "Time":"2019-01-22 18:34:23" },
"snrdb": { "Value":"16.71", "Time":"2019-01-22 18:34:23" },
"state": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"stateAV": { "Value":"on", "Time":"2019-01-22 17:14:10" },
"tsid": { "Value":"1057", "Time":"2019-01-22 18:02:56" },
"tuner_a": { "Value":"BCM7346 (internal) (DVB-S2)", "Time":"2018-01-17 18:50:12" },
"tuner_b": { "Value":"BCM7346 (internal) (DVB-S2)", "Time":"2018-01-17 18:50:12" },
"txtpid": { "Value":"32", "Time":"2019-01-22 17:52:18" },
"videoheight": { "Value":"1080", "Time":"2019-01-22 18:02:56" },
"videowidth": { "Value":"1920", "Time":"2019-01-22 18:02:56" },
"volume": { "Value":"100", "Time":"2019-01-22 17:48:30" },
"vpid": { "Value":"255", "Time":"2019-01-22 17:52:18" },
"webifversion": { "Value":"OWIF 1.2.5", "Time":"2018-01-17 18:50:12" }
},
"Attributes": {
"alexaName": "Test",
"bouquet-radio": "1:7:2:0:0:0:0:0:0:0:FROM BOUQUET \"userbouquet.favourites.radio\" ORDER BY bouquet",
"bouquet-tv": "1:7:1:0:0:0:0:0:0:0:FROM BOUQUET \"userbouquet.favourites.tv\" ORDER BY bouquet",
"devStateIcon": "on:rc_GREEN:off off:rc_YELLOW:on absent:rc_STOP:on",
"genericDeviceType": "media",
"homebridgeMapping": "ChannelController:reading=channel,cmd=channel",
"http-method": "GET",
"icon": "dreambox",
"model": "F1",
"room": "Spielzimmer",
"webCmd": "channel:input"
}
} ],
"totalResultsReturned":1
}
Das Log zeigt folgendes:Code Auswählen[1/22/2019, 6:24:38 PM] [FHEM] FormularF1 is media
[1/22/2019, 6:24:38 PM] [FHEM] FormularF1 has
[1/22/2019, 6:24:38 PM] [FHEM] Custom Volume [volume;cached]
[1/22/2019, 6:24:38 PM] [FHEM] Custom Power [power]
[1/22/2019, 6:24:38 PM] [FHEM] On [state;on,off]
[1/22/2019, 6:24:38 PM] [FHEM] ChannelController [channel]
2019-01-22 18:24:38 caching: FormularF1-volume: 100
[1/22/2019, 6:24:38 PM] [FHEM] caching: Custom Volume: 100 (as number; from '100')
2019-01-22 18:24:38 caching: FormularF1-power: on
[1/22/2019, 6:24:39 PM] [FHEM] FormularF1-power not a number: on
2019-01-22 18:24:39 caching: FormularF1-state: on
2019-01-22 18:24:39 caching: FormularF1-channel: RTL_HD
Alexa meldet aber, ich soll doch bitte einen Video-Skill in der Alexa App aktivieren. Zusätzlich vermute ich ein Problem damit, dass es für den Receiver kein reading gibt, welches den Kanal als Nummer beinhaltet.
Stimmen meine Annahmen soweit?
Grüße
sudo rm -rf /usr/lib/node_modules/alexa-fhem
# sudo npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.15Zitat von: justme1968 am 08 Februar 2019, 17:37:46
@dk3572: was soll es da neues geben? einfach das attribut setzen. attr <name> genericDeviceType media
attr SATReceiver genericDeviceType mediaChannelController:reading=channel,cmd=channelChannelController=verb=schalte,articles=den,valuePrefix=auf,value=ard,zdf,rtl,sat1,pro7,hessen
Zitat von: Esjay am 08 Februar 2019, 18:34:10
Einfach alexaName vergeben, in der App neu suchen lassen, darauf achten, dass er als Fernseher erkannt wird. anschließend wie Alexa vorschlägt den Ein Befehl geben, und dann kannst du ihn steuern.
Grüße
Zitat von: justme1968 am 08 Februar 2019, 18:50:47
du musst nix stoppen und neu starten. ein set <alexa> add <name> reicht.
welche alexa-fhem version hast du installiert?
und vor allem solltest du mal ins log schauen...
[2019-2-8 19:06:51] [FHEM] SATReceiver is media
[2019-2-8 19:06:51] [FHEM] SATReceiver has
[2019-2-8 19:06:51] [FHEM] Custom Volume [volume;cached]
[2019-2-8 19:06:51] [FHEM] Custom Power [power]
[2019-2-8 19:06:51] [FHEM] On [state;on,off]
[2019-2-8 19:06:51] [FHEM] Volume [volume]
[2019-2-8 19:06:51] [FHEM] Programm [channel]
[2019-2-8 19:06:51] [FHEM] LauterLeiser [state]
[2019-2-8 19:06:51] [FHEM] ChannelController [channel]
[2019-2-8 19:06:51] [FHEM] caching: Custom Volume: 65 (as number; from '65')
[2019-2-8 19:06:51] [FHEM] SATReceiver-power not a number: onZitat von: dk3572 am 08 Februar 2019, 19:12:07
Im Log taucht die Box jetzt aufCode Auswählen[2019-2-8 19:06:51] [FHEM] SATReceiver is media
[2019-2-8 19:06:51] [FHEM] SATReceiver has
[2019-2-8 19:06:51] [FHEM] Custom Volume [volume;cached]
[2019-2-8 19:06:51] [FHEM] Custom Power [power]
[2019-2-8 19:06:51] [FHEM] On [state;on,off]
[2019-2-8 19:06:51] [FHEM] Volume [volume]
[2019-2-8 19:06:51] [FHEM] Programm [channel]
[2019-2-8 19:06:51] [FHEM] LauterLeiser [state]
[2019-2-8 19:06:51] [FHEM] ChannelController [channel]
[2019-2-8 19:06:51] [FHEM] caching: Custom Volume: 65 (as number; from '65')
[2019-2-8 19:06:51] [FHEM] SATReceiver-power not a number: on
In der App wird sie nach wie vor als Schalter gefunden.
Edit:
In den customSlotTypes müsste nach dem add SatReceiver dieser doch auch dort auftauchen, oder?
Dort steht nur die Box mit dem alexaName als dreambox drin.
Edit2:
Jetzt auch den alexaName der Box geändert, Fhem neu gestartet, in App neu suchen lassen, alles ohne Erfolg.
Was kann ich noch tun oder an Infos liefern?
Zitat von: TomLee am 08 Februar 2019, 20:34:12
Welche der möglichen (https://forum.fhem.de/index.php/topic,95272.msg895281.html#msg895281) Befehle hast du denn bisher getestet ? oder wartest du nur auf ein kleines TV-Icon in der App ? hab gar kein genericDevicetype angegeben vor paar Tagen beim testen, meine 2 TVs werden aktuell als Typ sonstiges erkannt, testen kann ich gerade nicht.
Zitat von: justme1968 am 08 Februar 2019, 13:26:17
vermutlich hast du das npm
install in einem verzeichnis gemacht in dem noch eine alte version liegt.
Zitat von: justme1968 am 09 Februar 2019, 11:06:32
@dk3572: ich habe dich genau geschrieben was du setzen sollst. da steht nichts von einer auswahl.
es gibt keine 'richtigen' kommandos. was alexa versteht oder nicht ändert sich dauernd. du kannst nur die verlinkte doku lesen und probieren.
ich habe eben die prioritäten der erkannten device typen geändert. media hat jetzt vorrang und switch kommt als letztes
Zitat von: justme1968 am 09 Februar 2019, 11:06:32Ich würde an der Stelle um etwas Verständnis werben. Normalerweise wird man hier im Forum und auch hier im Thread immer wieder darauf hingewiesen, dass man sich an die Möglichkeiten/Vorgaben von FHEMWEB halten soll.
@dk3572: ich habe dich genau geschrieben was du setzen sollst. da steht nichts von einer auswahl.
Zitat von: justme1968 am 09 Februar 2019, 11:06:32
@ToKa: meinst du wirklich thermostat oder doch thermometer?
ich habe auch hier die reihenfolge geändert. damit müsste es gehen. vermutlich siehst du jetzt aber keine temperatur mehr. abfragen müsste trozdem noch gehen. wenn du den erst in der app auch sehen möchtest musst du den die temperatur auf ein anderes device kopieren und dies zusätzlich ein binden. z.b. per readingsProxy.
NR 195
NTFY_ORDER 50-alexa
STATE stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
TYPE alexa
active 0
alexa-fhem version 0.4.4
logfile ./log/alexa-%Y-%m-%d.log
Zitat von: Markus. am 10 Februar 2019, 07:21:36
Hallo Zusammen,
Hoffe das gehört hier hin.. ;-)
habe heute mal ein FHEM- Update gemacht. Verwende die Alexa-fhem V 0.4.4 und habe nund folgende ReadingsCode Auswählen
NR 195
NTFY_ORDER 50-alexa
STATE stopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
TYPE alexa
active 0
alexa-fhem version 0.4.4
logfile ./log/alexa-%Y-%m-%d.log
Habe irgendwie am Rande mitbekommen, das es eine neue Version gibt. Ich verwende eine Custom Skill mit dem normalen Smart Home skill von Amazon. Funktioniert auch alles weiterhin soweit, wie es im Moment aussieht.
Aber muss ich da was anpassen damit der ServiceStatus wieder normal angezeigt wird?
Hat das irgendwas mit den Umfangreichen Änderungen am Modul zu tun
Gruß
Markus
In eigener Sache: Kann mir bitte jemand sagen, wozu das Attribut alexaRoom gut ist? Ich hatte es mal gesetzt, mal nicht - konnte aber keinen Unterschied feststellen. Die Geräte wurden in der Alexa-App nicht einem Raum/einer Gruppe mit gleichem Wortlaut zugeordnet oder ähnlich.[2019-2-11 18:25:33] [FHEM] Fetching FHEM devices...
[2019-2-11 18:25:33] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20NAME=EG_ga_SEN_Tuerkontakt_Garagentor&XHR=1
*** FHEM: connected
[2019-2-11 18:25:33] [FHEM] got: 1 results
[2019-2-11 18:25:33] [FHEM] EG_ga_SEN_Tuerkontakt_Garagentor is contact
[2019-2-11 18:25:33] [FHEM] EG_ga_SEN_Tuerkontakt_Garagentor has
[2019-2-11 18:25:33] [FHEM] BatteryLevel [battery]
[2019-2-11 18:25:33] [FHEM] StatusLowBattery [battery]
[2019-2-11 18:25:33] [FHEM] CurrentTemperature [temperature]Internals:
DEF d14c12e6 34
FUUID 5c5bef9b-f33f-2e5f-2b1c-6c7c5f3889842337
IODev ZWAVE1
NAME EG_ga_SEN_Tuerkontakt_Garagentor
NR 205
STATE closed
TYPE ZWave
ZWaveSubDevice no
homeId d14c12e6
nodeIdHex 22
READINGS:
2017-10-22 17:34:51 alarm HomeSecurity: Tampering - product covering removed
2018-02-23 16:34:20 alarm_AccessControl Window/Door is closed, notificationIsOn
2017-10-22 17:42:03 alarm_HomeSecurity Event cleared: Previous Events cleared, notificationIsOn
2017-10-24 20:04:27 assocGroups 3
2018-02-22 02:30:42 battery 60 %
2018-01-04 18:07:09 model FIBARO System FGDW002 Door Opening Sensor 2
2018-01-04 18:07:09 modelConfig fibaro/fgdw2.xml
2018-01-04 18:07:09 modelId 010f-0702-1000
2018-01-14 13:16:41 neighborList ZWAVE1 ST_fl_US_Wandspot E1_wz_ZS_Tischleuchte_Wand E2_fl_ZS_Wandspot E2_ku_ZS_Tischleuchte E3_fl_ZS_Wandspot EG_ga_ZS_LEDStrip_Glasbausteine E1_wz_ZS_AllInOnePC
2018-01-04 01:12:41 neighborUpdate failed
2018-01-23 06:38:44 reportedState dim 19
2018-01-23 06:38:44 state dim 19
2018-02-23 06:15:15 temperature 6.4 C
2018-02-24 04:57:23 timeToAck 0.104
2018-02-24 04:57:23 transmit OK
2018-02-24 04:57:21 wakeup notification
2017-10-22 17:34:52 wakeupReport interval 64800 target 1
Attributes:
DbLogInclude alarm_AccessControl,alarm_HomeSecurity,temperature
IODev ZWAVE1
alexaName Garagentor
alias Garagentor
classes ZWAVEPLUS_INFO ASSOCIATION ASSOCIATION_GRP_INFO APPLICATION_STATUS BATTERY CONFIGURATION CRC_16_ENCAP DEVICE_RESET_LOCALLY FIRMWARE_UPDATE_MD MANUFACTURER_SPECIFIC MULTI_CHANNEL_ASSOCIATION ALARM POWERLEVEL SECURITY SENSOR_MULTILEVEL VERSION WAKE_UP
devStateIcon .*closed:fts_garage_door_100 .*open:fts_garage
event-on-change-reading .*
event-on-update-reading battery,temperature,wakeup
extendedAlarmReadings 1
genericDeviceType contact
group Sicherheit
icon hue_room_carport
room Garage,GoogleAssistant,Übersicht
stateFormat {(split(/,|is /, ReadingsVal($name,"alarm_AccessControl","")))[1]}
vclasses ALARM:5 APPLICATION_STATUS:1 ASSOCIATION:2 ASSOCIATION_GRP_INFO:1 BATTERY:1 CONFIGURATION:1 CRC_16_ENCAP:1 DEVICE_RESET_LOCALLY:1 FIRMWARE_UPDATE_MD:4 MANUFACTURER_SPECIFIC:2 MULTI_CHANNEL_ASSOCIATION:3 POWERLEVEL:1 SECURITY:1 SENSOR_MULTILEVEL:5 VERSION:2 WAKE_UP:2 ZWAVEPLUS_INFO:2
response.response.outputSpeech.text = 'Ich kenne: '+response.response.outputSpeech.text;
//fixme Fehler
} else if( command.characteristic && device !==undefined && command.device !== undefined) {
state += 'der Batteriestand ist '+ ((device.fhem.cached(device.mappings.StatusLowBattery.informId)==='ok')?'in ordnung':'niedrig');
}
//fixme doorstate
var patt = /open.*/i;
if( device.mappings.CurrentDoorState ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'ist '+ ((patt.test(device.fhem.cached(device.mappings.CurrentDoorState.informId)))?'geöffnet':'geschlossen');
} else if( device.mappings.ContactSensorState ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'ist '+ ((patt.test(device.fhem.cached(device.mappings.ContactSensorState.informId)))?'geöffnet':'geschlossen');
}
ret += '\n rollos';
//fixme Fenster
if( !seen['fenster'] )
ret +='\n fenster';
response.response.outputSpeech.ssml = result;
}
// fixme AudioPlayer Test
if( match = result.match( /<myaudiourl>(.*)<\/myaudiourl>/ ) ) {
log.info ( 'Audiourl Match: ' + match[1] );
var txt = result.match( /<myaudiotext>(.*)<\/myaudiotext>/ )
log.info ( 'Audiotext Match: ' + txt[1] );
response.response = {
shouldEndSession: true,
outputSpeech: {
type: "PlainText",
text: txt[1]
},
directives: [
{
type: "AudioPlayer.Play",
playBehavior: "REPLACE_ALL", // Setting to REPLACE_ALL means that this track will start playing immediately
audioItem: {
stream: {
url: match[1],
token: "1", // Unique token for the track - needed when queueing multiple tracks
offsetInMilliseconds: 0
}
}
}
]
}}
state += ' misst '+ device.fhem.cached(device.mappings.CurrentTemperature.informId).replace('.',',') +' Grad';
}
// fixme Humidity
if( device.mappings.CurrentRelativeHumidity ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
if ( state.search(' misst ') == -1) { state += ' misst ';};
state += device.fhem.cached(device.mappings.CurrentRelativeHumidity.informId).replace('.',',') +' Prozent Luftfeuchte';
}
// fixme Pressure
if( device.mappings.CurrentRelativePressure ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
if ( state.search(' misst ') == -1) { state += ' misst ';};
state += device.fhem.cached(device.mappings.CurrentRelativePressure.informId).replace('.',',') +' Hektopascal Luftdruck';
}
// fixme Wind
if( device.mappings.WindSpeed ) {
if( state ) { state = state.replace(' und ', ', ' ); state += ' und ' };
if ( state.search(' misst ') == -1) { state += ' misst ';};
state += device.fhem.cached(device.mappings.WindSpeed.informId).replace('.',',') +' kmH Windgeschwindigkeit';
}
// fixme UVIndex
if (device.mappings.UVIndex) {
if( parseInt(device.fhem.cached(device.mappings.UVIndex.informId)) > 0) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'der UV Index ist '+ device.fhem.cached(device.mappings.UVIndex.informId).replace('.',',');
}
}
// fixme CurrentLux
if (device.mappings.CurrentLux) {
if( parseInt(device.fhem.cached(device.mappings.CurrentLux.informId)) > 0) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
if ( state.search(' misst ') == -1) { state += ' misst ';};
state += device.fhem.cached(device.mappings.CurrentLux.informId).replace('.',',') +' Lux';;
}
}
// fixme Forecast
if( device.mappings.Forecastcode ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'die Vorhersage ist '+ device.fhem.cached(device.mappings.Forecastcode.informId);
}
// fixme CurrentLiter
if( device.mappings.CurrentLiter ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'der Füllstand ist '+ device.fhem.cached(device.mappings.CurrentLiter.informId) +' Liter';
}
// fixme CurrentKwh
if( device.mappings.CurrentKwh ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'der Zählerstand ist '+ device.fhem.cached(device.mappings.CurrentKwh.informId).replace('.',',') +' Kilowattstunden';;
}
// fixme CurrentSensorState
if( device.mappings.CurrentSensorState ) {
if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
state += 'der Status ist '+ device.fhem.cached(device.mappings.CurrentSensorState.informId).replace('.',' ');
}
nuc@NUC:/$ node --version
v8.9.4
nuc@NUC:/$ sudo npm install -g alexa-fhem
/usr/local/lib/node_modules/npm/bin/npm-cli.js:85
let notifier = require('update-notifier')({pkg})
^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:405:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Function.Module.runMain (module.js:430:10)
at startup (node.js:141:18)
at node.js:980:3
nuc@NUC:/$ nvm use v10.15.0
Now using node v10.15.0 (npm v6.4.1)
nuc@NUC:/$ node -v
v10.15.0
nuc@NUC:/$ sudo npm install -g alexa-fhem
/usr/local/lib/node_modules/npm/bin/npm-cli.js:85
let notifier = require('update-notifier')({pkg})
^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:405:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Function.Module.runMain (module.js:430:10)
at startup (node.js:141:18)
at node.js:980:3
nuc@NUC:~$ cd /home/nuc/.nvm/versions/node/v10.15.0/lib/node_modules/alexa-fhem/nuc@NUC:~/.nvm/versions/node/v10.15.0/lib/node_modules/alexa-fhem$ dir
bin createKey.sh lambda.js node_modules README.md
config-sample.json key lib package.json
Zitat von: justme1968 am 12 Februar 2019, 19:57:20
löschen und mit sudo und mit -g installieren.
Zitat von: justme1968 am 12 Februar 2019, 08:29:20
@ToKa: welche alexa-fhem version ist das ?
[2019-2-11 18:24:18] {"event":{"header":{"namespace":"Alexa.Discovery","name":"AddOrUpdateReport","payloadVersion":"3","messageId":"52af9543-b8f5-4785-89b6-aee549fa76bc"},"payload":{"endpoints":[{"endpointId":"ZWave_d14c12e6-34","manufacturerName":"FHEMZWave","modelName":"FHEMFIBARO System FGDW002 Door Opening Sensor 2","version":"<unknown>","friendlyName":"garagentor","description":"n: EG_ga_SEN_Tuerkontakt_Garagentor, r: garage,googleassistant,übersicht","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"EG_ga_SEN_Tuerkontakt_Garagentor","fuuid":"5c5bef9b-f33f-2e5f-2b1c-6c7c5f3889842337"}}],"scope":{"type":"BearerToken","token":"access-token-from-Amazon"}}}}
unknown option -- u
usage: ssh [-1246AaCfGgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
[-D [bind_address:]port] [-E log_file] [-e escape_char]
[-F configfile] [-I pkcs11] [-i identity_file]
[-J [user@]host[:port]] [-L address] [-l login_name] [-m mac_spec]
[-O ctl_cmd] [-o option] [-p port] [-Q query_option] [-R address]
[-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]]
[user@]hostname [command]
BEGININSTALL alexa-fhem
FINISHINSTALL alexa-fhem
BEGINUPDATE alexa-fhem
FINISHUPDATE alexa-fhem
BEGINUNINSTALL alexa-fhem
FINISHUNINSTALL alexa-fhem
[2/13/2019, 5:13:41 PM] [FHEM] caching: ChannelController: ProSieben_HD (as string; from 'ProSieben_HD')
[2/13/2019, 5:13:41 PM] [FHEM] FormularF1: executing set cmd for ChannelController with value -1
[2/13/2019, 5:13:41 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=set%20FormularF1%20channel%20-1&fwcsrf=csrf_119524027197013&XHR=1Zitat von: justme1968 am 13 Februar 2019, 11:09:37
@Loredo: die Idee ist klasse. aber ich habe ein kleines problem: wenn das event nicht von global kommt kann ich NOTIFYDEV micht einfach verwenden weil ich ja nicht weiss wie das npmjs device heisst und TYPE=npmjs geht an der stelle nicht. wie wäre es die events von global kommen zu lassen und npmjs mit in den text zu packen?
npmjsDeviceName BEGININSTALL alexa-fhem
npmjsDeviceName FINISHINSTALL alexa-fhem
NOTIFYDEV = global,$name,TYPE=npmjsdefmod str_OG_WZ_Deckenbeleuchtung structure wzdb MQTT2_zigbee_gu10_1 MQTT2_zigbee_gu10_2 MQTT2_zigbee_gu10_3
attr str_OG_WZ_Deckenbeleuchtung alexaName decke
attr str_OG_WZ_Deckenbeleuchtung async_delay 1
attr str_OG_WZ_Deckenbeleuchtung genericDeviceType scene
defmod MQTT2_zigbee_gu10_1 MQTT2_DEVICE zigbee_0x00158d0003274a6c
attr MQTT2_zigbee_gu10_1 userattr structexclude wzdb wzdb_map
attr MQTT2_zigbee_gu10_1 IODev MQTT2_CLIENT
attr MQTT2_zigbee_gu10_1 devStateIcon {zigbee2mqtt_devStateIcon255($name)}
attr MQTT2_zigbee_gu10_1 genericDeviceType light
attr MQTT2_zigbee_gu10_1 group ZIGBEE
attr MQTT2_zigbee_gu10_1 icon light_control
attr MQTT2_zigbee_gu10_1 model L_02a_zigbee2mqtt_bulb
attr MQTT2_zigbee_gu10_1 readingList zigbee2mqtt/0x00158d0003274a6c:.* { json2nameValue($EVENT) }\
zigbee2mqtt/0x00158d0003274a6c/set:.* { json2nameValue($EVENT) }
attr MQTT2_zigbee_gu10_1 room MQTT2_DEVICE
attr MQTT2_zigbee_gu10_1 setList on:noArg zigbee2mqtt/0x00158d0003274a6c/set {"state":"ON"}\
off:noArg zigbee2mqtt/0x00158d0003274a6c/set {"state":"OFF"}\
brightness:colorpicker,BRI,0,15,255 zigbee2mqtt/0x00158d0003274a6c/set {"state":"on","$EVTPART0":"$EVTPART1"}
attr MQTT2_zigbee_gu10_1 setStateList on off
attr MQTT2_zigbee_gu10_1 stateFormat {lc ReadingsVal("$name","state",0)}
attr MQTT2_zigbee_gu10_1 structexclude alexaName
attr MQTT2_zigbee_gu10_1 webCmd toggle:on:off:brightnessZitat von: justme1968 am 13 Februar 2019, 19:43:50
aber wir können auch im developer bereich diskutieren und schauen was rudi dazu sagt.
2019.02.14 21:48:20 2: alexa: starting alexa-fhem: /usr/bin/ssh pi@192.168.6.234 -c /tmp/alexa-fhem.cfgUnknown cipher type '/tmp/alexa-fhem.cfg'alexaFHEM running /usr/bin/ssh 2019-02-14 22:09:16
alexaFHEM.ProxyConnection stopped 2019-02-14 22:02:57
kill $(ps aux | grep 'alexa-fhem' | grep -v grep | awk '{print $2}')
Zitat von: binford6000 am 18 Januar 2019, 22:37:34
Vielleicht wäre noch ein Hinweis im Wiki hilfreich:
Das Hinzufügen des Eintrags scene in das Attribut genericDeviceType ist in global vorzunehmen:Code Auswählenattr global userattr genericDeviceType:switch,outlet,light,blind,scene,speaker,thermostat
Zitat von: justme1968 am 17 Februar 2019, 17:08:26
naja... es gibt genau eine FHEM connector seite und dort genau einen update eintrag.
Zitat von: Esjay am 13 Februar 2019, 17:30:32
Hallo Justme1968
kurze Frage/Hinweis zu dem ChannelController.
Kanal vor bzw. rück werden bei mir beide mit -1 im Log quittiert. In der App kann ich sehen, dass Alexa auch jeweils Kanal vor bzw. zurück erkannt hat.
Vll könnte jemand anderes, das mal bei sich verifizieren.Code Auswählen[2/13/2019, 5:13:41 PM] [FHEM] caching: ChannelController: ProSieben_HD (as string; from 'ProSieben_HD')
[2/13/2019, 5:13:41 PM] [FHEM] FormularF1: executing set cmd for ChannelController with value -1
[2/13/2019, 5:13:41 PM] [FHEM] executing: http://localhost:8083/fhem?cmd=set%20FormularF1%20channel%20-1&fwcsrf=csrf_119524027197013&XHR=1
Das nächste Problem besteht beim Enigma2 Modul, welches kein reading mit der Kanal Nummer hat, bzw. gibt die API das nicht her. Jedoch kann man ein set xyz channelUp bzw set xyz channelDown machen um den Kanal zu wechseln. Könnte man hier ein mapping dazwischen bauen?
VG
Edit:
Hier stand Blödsinn!
//fixme Audioplayer
var audioPlayer = function (audioURL, offsetInMilliseconds, playBehavior, token, previousToken) {
var response = {
shouldEndSession: true,
directives: [
{
type: "AudioPlayer.Play",
playBehavior: playBehavior,
audioItem: {
stream: {
url: audioURL,
token: token, // Unique token for the track - needed when queueing multiple tracks
expectedPreviousToken: previousToken, // The expected previous token - when using queues, ensures safety
offsetInMilliseconds: offsetInMilliseconds
}
}
}
]
};
//Fixme mp3list
var mp3list = [];
var mp3pos;
var mp3queued;
var mp3offset;
//Fixme mp3list end
// fixme AudioPlayer Start
if( match = result.match( /<myaudiourl>(.*)<\/myaudiourl>/ ) ) {
mp3list = match[1].split(" ");
mp3pos = 0;
response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
}
var audioPlayerResponse = function (event, response) {
if( event.request.type === 'AudioPlayer.PlaybackStarted' || event.request.type === 'AudioPlayer.PlaybackStopped' )
{ mp3pos = parseInt(event.request.token);
mp3offset = parseInt(event.request.offsetInMilliseconds);
response = {
"version": "1.0",
"response": {
"shouldEndSession": true
}
};
}
else if( event.request.type === 'AudioPlayer.PlaybackNearlyFinished' )
{
if ( mp3pos < mp3list.length - 1 )
{
response.response=audioPlayer(mp3list[mp3pos+1],0,"ENQUEUE",mp3pos+1,mp3pos);
}
}
return(response);
};
//fixme audioplayer response
response = audioPlayerResponse(event, response);
//fixme audioplayer response end
var audioPlayerIntents = function (event, response) {
if( event.request.intent.name === 'AMAZON.NextIntent' ) {
if ( mp3pos < mp3list.length - 1 )
{
mp3pos = mp3pos +1;
response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
}
}
else if( event.request.intent.name === 'AMAZON.PreviousIntent' ) {
mp3pos = mp3pos -1;
if ( mp3pos > -1 )
{
response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
}
}
else if( event.request.intent.name === 'AMAZON.PauseIntent' ) {
response.response = {
shouldEndSession: false,
directives: [
{
"type": "AudioPlayer.Stop"
}
]
}
}
else if( event.request.intent.name === 'AMAZON.ResumeIntent' ) {
response.response=audioPlayer(mp3list[mp3pos],mp3offset,"REPLACE_ALL",mp3pos);
}
return response;
};
//Fixme Ausioplayer Intents
if( event.request.intent.name === 'AMAZON.NextIntent' || event.request.intent.name === 'AMAZON.PreviousIntent' || event.request.intent.name === 'AMAZON.PauseIntent' || event.request.intent.name === 'AMAZON.ResumeIntent' ) {
response = audioPlayerIntents (event, response);
}
if( device.mappings.CurrentDoorState ) {
if( state ) { state.replace( ' und ', ', ' ); state += ' und ' };
state += 'ist '+ ((device.fhem.cached(device.mappings.CurrentDoorState.informId).indexOf('open') >= 0)?'geöffnet':'geschlossen');
} else if( device.mappings.ContactSensorState ) {
if( state ) { state.replace( ' und ', ', ' ); state += ' und ' };
state += 'ist '+ ((device.fhem.cached(device.mappings.ContactSensorState.informId).indexOf('open') >= 0)?'geöffnet':'geschlossen');
}
Zitat von: justme1968 am 22 Februar 2019, 21:39:19
nein. das log lässt sich nicht deaktivieren. dir ausgabe müssen ja irgendwohin.
warum willst du etwas deaktivieren?
root@raspberrypi:/usr/local/lib/node_modules/alexa-fhem/lib# diff server.js server.js_0_5_21_geht
4a5,10
> //Fixme mp3list
> var mp3list = [];
> var mp3pos;
> var mp3queued;
> var mp3offset;
> //Fixme mp3list end
685a692,695
> //fixme Fenster
> if( !seen['fenster'] )
> ret +='\n fenster';
> //fixme Fenster end
1475a1486,1491
> //fixme fix undefined
> if ( event === undefined || event.session === undefined )
> {
> sessions[session] = {};
> }
> else {
1481a1498
> }
1501c1518,1519
< if( event.session.application !== undefined && this.roomOfIntent[event.session.application.applicationId] )
---
> // fixme undefined
> if( event !== undefined && event.session !== undefined && event.session.application !== undefined && this.roomOfIntent[event.session.application.applicationId] )
1514a1533,1536
> //fixme audioplayer response
> response = audioPlayerResponse(event, response);
> //fixme audioplayer response end
>
1624a1647,1652
> // fixme AudioPlayer Start
> if( match = result.match( /<myaudiourl>(.*)<\/myaudiourl>/ ) ) {
> mp3list = match[1].split(" ");
> mp3pos = 0;
> response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
> }
1800c1828,1832
< if( event.request.intent.name === 'AMAZON.StopIntent' ) {
---
> //Fixme Ausioplayer Intents
> if( event.request.intent.name === 'AMAZON.NextIntent' || event.request.intent.name === 'AMAZON.PreviousIntent' || event.request.intent.name === 'AMAZON.PauseIntent' || event.request.intent.name === 'AMAZON.ResumeIntent' ) {
> response = audioPlayerIntents (event, response);
> }
> else if( event.request.intent.name === 'AMAZON.StopIntent' ) {
1840a1873,1874
> // Fixme OwnMappings
> state = ownMappings (device, state);
1875c1909
< state += 'ist '+ ((device.fhem.cached(device.mappings.CurrentDoorState.informId)==='open')?'geöffnet':'geschlossen');
---
> state += 'ist '+ ((device.fhem.cached(device.mappings.CurrentDoorState.informId).indexOf('open') >= 0)?'geöffnet':'geschlossen');
1878c1912
< state += 'ist '+ ((device.fhem.cached(device.mappings.ContactSensorState.informId)==='open')?'geöffnet':'geschlossen');
---
> state += 'ist '+ ((device.fhem.cached(device.mappings.ContactSensorState.informId).indexOf('open') >= 0)?'geöffnet':'geschlossen');
2683a2718,2719
> log.info( 'ContactSensor mapping' + device.fhem.cached(mapping.informId) );
>
2685c2721,2723
< if( current === 'CONTACT_DETECTED' || current === 'Closed' || current === 'closed' )
---
> log.info( 'ContactSensor current' + current);
> // Fixme Current
> if( current === 'CONTACT_DETECTED' || current.indexOf('CLOSED') >= 0 || current.indexOf('Closed') >= 0 || current.indexOf('closed') >= 0 )
2688a2727
> log.info( 'ContactSensor current' + current);
2700c2739,2740
< if( current === 'CLOSED' || current === 'Closed' || current === 'closed' )
---
> // Fixme Current
> if( current === 'CONTACT_DETECTED' || current.indexOf('CLOSED') >= 0 || current.indexOf('Closed') >= 0 || current.indexOf('closed') >= 0 )
2899a2940
> log.info( 'ContactSensor d.capabilities.push' );
4235a4277,4411
>
> //fixme Audioplayer
> var audioPlayer = function (audioURL, offsetInMilliseconds, playBehavior, token, previousToken) {
> var response = {
> shouldEndSession: true,
> directives: [
> {
> type: "AudioPlayer.Play",
> playBehavior: playBehavior,
> audioItem: {
> stream: {
> url: audioURL,
> token: token, // Unique token for the track - needed when queueing multiple tracks
> expectedPreviousToken: previousToken, // The expected previous token - when using queues, ensures safety
> offsetInMilliseconds: offsetInMilliseconds
> }
> }
> }
> ]
>
> };
>
> return(response);
> };
>
> var audioPlayerResponse = function (event, response) {
>
> if( event.request.type === 'AudioPlayer.PlaybackStarted' || event.request.type === 'AudioPlayer.PlaybackStopped' )
> { mp3pos = parseInt(event.request.token);
> mp3offset = parseInt(event.request.offsetInMilliseconds);
> response = {
> "version": "1.0",
> "response": {
> "shouldEndSession": true
> }
> };
> }
> else if( event.request.type === 'AudioPlayer.PlaybackNearlyFinished' )
> {
> if ( mp3pos < mp3list.length - 1 )
> {
> response.response=audioPlayer(mp3list[mp3pos+1],0,"ENQUEUE",mp3pos+1,mp3pos);
> }
> }
> return(response);
> };
>
> var audioPlayerIntents = function (event, response) {
> if( event.request.intent.name === 'AMAZON.NextIntent' ) {
> if ( mp3pos < mp3list.length - 1 )
> {
> mp3pos = mp3pos +1;
> response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
> }
> }
> else if( event.request.intent.name === 'AMAZON.PreviousIntent' ) {
> mp3pos = mp3pos -1;
> if ( mp3pos > -1 )
> {
> response.response=audioPlayer(mp3list[mp3pos],0,"REPLACE_ALL",mp3pos);
> }
> }
> else if( event.request.intent.name === 'AMAZON.PauseIntent' ) {
> response.response = {
> shouldEndSession: false,
> directives: [
> {
> "type": "AudioPlayer.Stop"
> }
> ]
> }
> }
> else if( event.request.intent.name === 'AMAZON.ResumeIntent' ) {
> response.response=audioPlayer(mp3list[mp3pos],mp3offset,"REPLACE_ALL",mp3pos);
> }
> return response;
> };
>
> // Fixme OwnMappings
> var ownMappings = function (device, state) {
> // fixme Humidity
> if( device.mappings.CurrentRelativeHumidity ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> if ( state.search(' misst ') == -1) { state += ' misst ';};
> state += device.fhem.cached(device.mappings.CurrentRelativeHumidity.informId).replace('.',',') +' Prozent Luftfeuchte';
> }
> // fixme Pressure
> if( device.mappings.CurrentRelativePressure ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> if ( state.search(' misst ') == -1) { state += ' misst ';};
> state += device.fhem.cached(device.mappings.CurrentRelativePressure.informId).replace('.',',') +' Hektopascal Luftdruck';
> }
> // fixme Wind
> if( device.mappings.WindSpeed ) {
> if( state ) { state = state.replace(' und ', ', ' ); state += ' und ' };
> if ( state.search(' misst ') == -1) { state += ' misst ';};
> state += device.fhem.cached(device.mappings.WindSpeed.informId).replace('.',',') +' kmH Windgeschwindigkeit';
> }
> // fixme UVIndex
> if (device.mappings.UVIndex) {
> if( parseInt(device.fhem.cached(device.mappings.UVIndex.informId)) > 0) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> state += 'der UV Index ist '+ device.fhem.cached(device.mappings.UVIndex.informId).replace('.',',');
> }
> }
> // fixme CurrentLux
> if (device.mappings.CurrentLux) {
> if( parseInt(device.fhem.cached(device.mappings.CurrentLux.informId)) > 0) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> if ( state.search(' misst ') == -1) { state += ' misst ';};
> state += device.fhem.cached(device.mappings.CurrentLux.informId).replace('.',',') +' Lux';;
> }
> }
> // fixme Forecast
> if( device.mappings.Forecastcode ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> state += 'die Vorhersage ist '+ device.fhem.cached(device.mappings.Forecastcode.informId);
> }
> // fixme CurrentLiter
> if( device.mappings.CurrentLiter ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> state += 'der Füllstand ist '+ device.fhem.cached(device.mappings.CurrentLiter.informId) +' Liter';
> }
> // fixme CurrentKwh
> if( device.mappings.CurrentKwh ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> state += 'der Zählerstand ist '+ device.fhem.cached(device.mappings.CurrentKwh.informId).replace('.',',') +' Kilowattstunden';;
> }
> // fixme CurrentSensorState
> if( device.mappings.CurrentSensorState ) {
> if( state ) {state = state.replace( ' und ', ', ' ); state += ' und ' };
> state += 'der Status ist '+ device.fhem.cached(device.mappings.CurrentSensorState.informId).replace('.',' ');
> }
> return state;
> };
[2019-2-24 19:43:25] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.Speaker","name":"SetMute","payloadVersion":"3","messageId":"xxx","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"xxx"},"endpointId":"xxx","cookie":{"fuuid":"xxx","device":"AVR"}},"payload":{"mute":true}}}
[2019-2-24 19:43:26] [FHEM] caching: Custom Volume: 22 (as number; from '22')
[2019-2-24 19:43:26] <<<< [ssh] {"header":{"namespace":"Alexa","name":"ErrorResponse","payloadVersion":"3","messageId":"xxx","correlationToken":"-"},"payload":{"type":"INVALID_DIRECTIVE","message":"unknown"},"endpoint":{"scope":{"type":"BearerToken","token":"xxx"},"endpointId":"xxx","cookie":{"fuuid":"xxx","device":"AVR"}}}
[2019-2-24 19:42:27] [FHEM] AVR is speaker
[2019-2-24 19:42:27] [FHEM] AVR has
[2019-2-24 19:42:27] [FHEM] Custom Volume [volume;cached]
[2019-2-24 19:42:27] [FHEM] Custom Power [power]
[2019-2-24 19:42:27] [FHEM] On [state;on,off]
[2019-2-24 19:42:27] [FHEM] Mute [mute]
[2019-2-24 19:42:27] [FHEM] caching: Custom Volume: 32 (as number; from '32')
[2019-2-24 19:42:27] [FHEM] AVR-power not a number: on
[2019-2-24 19:42:27] caching: AVR-mute: off
[2019-2-25 13:59:12] BearerToken '...375A9' read from alexa
[2019-2-25 13:59:12] 39_alexa.pm is new version: true
[2019-2-25 13:59:12] sshautoconf: completed successfully
[2019-2-25 13:59:12] *** SSH: proxy configuration set up done
[2019-2-25 13:59:12] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-2-25 13:59:12] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 13:59:12] Starting SSH with -R 1234:127.0.0.1:37577 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-2-25 13:59:13] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-2-25 13:59:13] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 13:59:13] *** SSH: proxy connection established
[2019-2-25 13:59:13] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
2019-02-25 13:59:49 caching: MAX_OG_AZ_WT_0e145e-temperature: 19.1
[2019-2-25 13:59:49] [FHEM] caching: CurrentTemperature: 19.1 (as number; from '19.1')
[2019-2-25 14:00:19] Got SIGTERM, shutting down alexa-fhem...
[2019-2-25 14:00:19] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-2-25 14:00:19] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:00:19] Stopping SSH ...
[2019-2-25 14:00:19] Reading alexaFHEM.ProxyConnection set to stopped
[2019-2-25 14:00:19] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:00:19] *** SSH: exited with 143
[2019-2-25 14:00:19] Got SIGTERM, shutting down alexa-fhem...
[2019-2-25 14:00:19] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-2-25 14:00:19] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:00:19] Stopping SSH ...
[2019-2-25 14:01:00] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-2-25 14:01:00] os.homedir()=/opt/fhem
[2019-2-25 14:01:00] this is alexa-fhem 0.5.19
[2019-2-25 14:01:00] connecting to FHEM ...
[2019-2-25 14:01:01] [FHEM] trying longpoll to listen for fhem events
[2019-2-25 14:01:01] [FHEM] starting longpoll: http://192.168.178.83:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1551099661982
[2019-2-25 14:01:04] [FHEM] got csrfToken:
[2019-2-25 14:01:04] [FHEM] Checking devices and attributes...
[2019-2-25 14:01:04] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[2019-2-25 14:01:04] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[2019-2-25 14:01:04] [FHEM] waiting for events ...
[2019-2-25 14:01:04] [FHEM] Fetching FHEM devices...
[2019-2-25 14:01:04] [FHEM] fetching: http://192.168.178.83:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2019-2-25 14:01:04] [FHEM] alexa device is alexa
[2019-2-25 14:01:04] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.19%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:01:04] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:01:04] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2019-2-25 14:01:04] Server listening on: http://127.0.0.1:39851 for proxy connections
[2019-2-25 14:01:04] *** SSH: checking proxy configuration
[2019-2-25 14:01:04] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-2-25 14:01:04] Passed config: {"connections":[{"uid":999,"name":"FHEM","server":"192.168.178.83","ssl":false,"webname":"fhem","port":"8083","filter":"alexaName=..*"}],"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":39851}}
[2019-2-25 14:01:04] sshautoconf: SSH key seems to exist
[2019-2-25 14:01:05] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-2-25 14:01:05] [FHEM] executing: http://192.168.178.83:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-2-25 14:01:05] [FHEM] got: 27 results
[2019-2-25 14:01:05] [FHEM] Fenst_li_EG_WZ is switch
[2019-2-25 14:01:05] [FHEM] Fenst_li_EG_WZ has
[2019-2-25 14:01:05] [FHEM] On [state;on,off]
2019.02.25 15:11:44 1: Server shutdown delayed due to alexa for max 10 sec
2019.02.25 15:11:46 3: alexa: read: end of file reached while sysread
2019.02.25 15:11:46 3: alexa: stopped
2019.02.25 15:11:46 0: Server shutdown
2019.02.25 15:11:46 2: DbLog DBLogging - waiting for shutdown 20 seconds ...
2019.02.25 15:12:06 2: DbLog DBLogging - continuing shutdown sequence
2019.02.25 15:12:06 1: Shutdown executed
2019-02-25 15:35:39 alexa alexa alexaFHEM: stopping
2019-02-25 15:35:39 alexa alexa alexaFHEM.ProxyConnection: stopping; alexa-fhem terminating
2019-02-25 15:35:39 alexa alexa alexaFHEM.ProxyConnection: stopping; alexa-fhem terminating
2019-02-25 15:35:39 alexa alexa alexaFHEM.ProxyConnection: stopped
2019-02-25 15:36:05 alexa alexa alexaFHEM.ProxyConnection: starting; starting SSH
2019-02-25 15:36:05 alexa alexa alexaFHEM.ProxyConnection: running; SSH connected
2019-02-25 15:37:12 alexa alexa alexaFHEM: stopping
2019-02-25 15:37:12 alexa alexa alexaFHEM.ProxyConnection: stopping; alexa-fhem terminating
2019-02-25 15:37:12 alexa alexa alexaFHEM.ProxyConnection: stopping; alexa-fhem terminating
2019-02-25 15:37:12 alexa alexa alexaFHEM.ProxyConnection: stopped
2019-02-25 15:37:37 alexa alexa alexaFHEM.ProxyConnection: starting; starting SSH
2019-02-25 15:37:38 alexa alexa alexaFHEM.ProxyConnection: running; SSH connected
Zitat von: dcdead am 25 Februar 2019, 17:48:47
Danke! Bei mir funktioniert es mit dem yamaha_avr modul zusammen problemlos (Habe es jetzt 20 Mal hintereinander probiert)
Habe folgendes Homebridgemapping:
homebridgeMapping Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
Zitat von: justme1968 am 25 Februar 2019, 21:32:36
die sprach kommandos gehen trotzdem. wenn sie erkannt werden. log ausgabe anschauen.
schalter weil es vermutlich on und off gibt. wenn du ras nicht magst hombridgeMapping mit On=clear anlegen.
Zitatmappings for dmMedienwiedergabe: { '00001001-0000-1000-8000-135D67EC4377':
mappings for dmTV: { '00001001-0000-1000-8000-135D67EC4377':
mappings for dmTest: { '00001001-0000-1000-8000-135D67EC4377':
Zitat von: MadMax-FHEM am 26 Februar 2019, 13:40:10
Hallo André,
danke für die stetige Weiterentwicklung! :)
Nachdem du mir hier: https://forum.fhem.de/index.php/topic,97887.msg911520.html#msg911520 neue Wege aufgezeigt hast ;)
Bin ich gerade (auch) am "Rumspielen" mit dem genericDeviceType media.
(speaker geht/ging [gefühlt] ganz gut / laut/leise geht auch bei media [meist] gut / Kanalwechsel ist [noch/manchmal] etwas zickig)
Es funktioniert mal gut mal schlecht, liegt aber eher daran, dass Alexa nicht (immer) weiß was ich will bzw. was sie machen soll ;)
(und sie schlägt mir immer irgendwelche "dummen" anderen Skills zur Aktivierung vor ;) )
Da ich denke, dass das wichtigste (zumindest war das oft so) der Name ist (aber er sollte auch zum Gesprochenen passen), spiele ich grad damit rum.
Daher habe ich aktuell 2 Dummy mit dem genericDeviceType media (so kann ich ausprobieren, mit welchem Namen ich besser zurecht komme und Alexa nat. auch), evtl. werden es noch ein paar mehr bis ich den passenden Namen "für uns" gefunden habe ;)
Ich habe den 2ten Dummy per "Raw Definition" kopiert und dann den Namen geändert (in der Raw Definition Ansicht).
Die FUUID ist unterschiedlich.
Einmal kam ein Befehl (obwohl eigentlich richtig verstanden) beim falschen Gerät an...
...also auch in der Payload stand schon das falsche drin (daher kann alexa-fhem nichts dafür ;) ).
Daher habe ich "Debugging" aktiviert und mich auf die Suche gemacht...
EDIT: eben hat es mal wieder funktioniert, also Alexa hat mich verstanden und es auch gemacht, allerdings erneut beim falschen Gerät... ;)Im Log gesehen, dass die ID bei beiden Geräten die selbe ist:
Heißt das, dass die irgendwie "identisch" sind!?
Oder interpretiere ich da etwas falsch und das ist gar keine Geräte-ID und auch kein Problem!?
EDIT4: ok, das war jetzt Quatsch, sorry! ;) Trotzdem bleibt das "Problem"...
EDIT2: alexa-fhem Version: 0.5.24 / bzw. alexa-fhem und fhem gestern ein Update durchgeführt.
EDIT3: jetzt bin ich sicher, die Einstellungen landen immer beim neu (copy/paste) angelegten Dummy. Egal welches Gerät ich über Alexa anspreche. Aktuell kann ich nur mit Lautstärke testen, weil nur das aktuell zuverlässig verstanden wird...
Danke schon mal (wieder!), Joachim
Zitat von: justme1968 am 26 Februar 2019, 14:25:31
schwierig schwierig ...
Zitat von: justme1968 am 26 Februar 2019, 14:25:31
amazon versucht ja bei den media und volume geschichten auch bei fehlendem device Namen
ein passendes oder das zuletzt verwendete gerät zu finden.
ich meine bemerkt zu habend scheinbar genau das recht oft schief geht.
d.h. auf jeden fall im log schauen welches gerät (fuuid) tatsächlich im event steht das von amazon kommt. wenn es das falsche ist -> feedback an amazon. am besten die ausführliche version.
Zitat von: justme1968 am 26 Februar 2019, 14:25:31
wenn es im event das richtige gerät ist und fhem trotzdem das falsche schaltet (kann ich mir garnicht vorstellen :) )-> dann müssen wir suchen. ein log mit verbose 5 und -D sollte weiter helfen.
Zitat von: doman75 am 26 Februar 2019, 14:20:42
Hallo Joachim,
würdest du mal deine raw Definition vom Dummy mit dem type media hier reinstellen? Das wäre sehr cool.
Grüße
Swen
defmod dmTest dummy
attr dmTest alexaName media box
attr dmTest alias Mediabox
attr dmTest genericDeviceType media
attr dmTest homebridgeMapping PlaybackController:reading=playback,values=Play;;Pause;;Stop;;Previous;;Next,cmd=playback ChannelController:reading=channel,cmd=channel
attr dmTest oldreadings volume
attr dmTest readingList volume mute playback channel
attr dmTest room Wohnzimmer,alexa
attr dmTest setList on off volume mute channel
setstate dmTest off
setstate dmTest 2019-02-26 13:41:31 channel 5
setstate dmTest 2019-02-25 23:20:27 mute 1
setstate dmTest 2019-02-26 00:29:44 playback Play
setstate dmTest 2019-02-25 23:45:32 state off
setstate dmTest 2019-02-26 14:29:29 volume 100
sub my_PlaybackControl($$)
{
my ($Device,$Event) = @_;
my $CurrentActivity = ReadingsVal("HarmonyHub", "currentActivity", "n.a.");
Log(1,"my_PlaybackControl Device: $Device Event: $Event");
# if($Event eq "on")
# {
# fhem("set HarmonyHub activity Fernsehen");
# }
# elsif($Event eq "off")
# {
# {fhem "set HarmonyHub activity PowerOff"}
# }
# elsif($Event =~ m/mute/)
if($Event =~ m/mute/)
{
fhem("set HarmonyHub command Mute");
}
elsif($Event =~ m/volume/)
{
if(OldReadingsVal($Device, "volume", 0) > ReadingsVal($Device, "volume", 0))
{
fhem("set HarmonyHub command VolumeDown; sleep 1; set HarmonyHub command VolumeDown; sleep 1; set HarmonyHub command VolumeDown");
}
else
{
if(ReadingsVal($Device, "mute", 0) eq "1")
{
fhem("set HarmonyHub command Mute");
fhem("setreading $Device mute 0");
}
else
{
# weil das erste VolumeUp "nur" die Anzeige "anwirft" und erst das zweite tatsächlich lauter macht und einmal ist ja bekanntlich keinmal ;)
fhem("set HarmonyHub command VolumeUp; sleep 1; set HarmonyHub command VolumeUp; sleep 1; set HarmonyHub command VolumeUp");
}
}
}
elsif($Event =~ m/playback/)
{
my $PlayState = (split(/: /, $Event))[1];
# irgendwie habe ich die Activity wohl "falsch" angelegt, sie hat kein Play/Stop/Pause, daher direkt über das "Gerät"
if($CurrentActivity =~ m/Amazon/)
{
fhem("set harmony_41290995 command $PlayState");
}
Log(1,"my_PlaybackControl Device: $Device Event: $Event PlayState: $PlayState");
}
elsif($Event =~ m/channel/)
{
my $ChannelNr = (split(/: /, $Event))[1];
Log(1,"my_PlaybackControl Device: $Device Event: $Event ChannelNr: $ChannelNr");
}
}
defmod nWiedergabeControl notify dmTest:(on|off|channel|mute|volume|playback).* {my_PlaybackControl($NAME, $EVENT)}
Zitat von: MadMax-FHEM am 26 Februar 2019, 15:00:19
Hi Swen,
klar:Code Auswählen
defmod dmTest dummy
attr dmTest alexaName media box
attr dmTest alias Mediabox
attr dmTest genericDeviceType media
attr dmTest homebridgeMapping PlaybackController:reading=playback,values=Play;;Pause;;Stop;;Previous;;Next,cmd=playback ChannelController:reading=channel,cmd=channel
attr dmTest oldreadings volume
attr dmTest readingList volume mute playback channel
attr dmTest room Wohnzimmer,alexa
attr dmTest setList on off volume mute channel
setstate dmTest off
setstate dmTest 2019-02-26 13:41:31 channel 5
setstate dmTest 2019-02-25 23:20:27 mute 1
setstate dmTest 2019-02-26 00:29:44 playback Play
setstate dmTest 2019-02-25 23:45:32 state off
setstate dmTest 2019-02-26 14:29:29 volume 100
Ob das setList (volume mute channel) Not tut weiß ich nicht...
Habe schon mit und ohne etc. probiert aber Kanalwechsel ist noch sehr unzuverlässig.
Liegt aber an Amazon/Alexa.
Mal geht es, dann im nächsten Moment schon wieder nicht usw. (gleichlautenden Befehl nur andere Kanalnummer [von Name was auch schon 1x funktioniert hat ;) ganz zu schweigen]).
Meist wird der Harmony oder irgendein RemoteTV Skill angepriesen...
Lautstärke geht ganz gut (bis auf die aktuelle "Verwechslung" [siehe Post zuvor])...
Das Attribut "oldreadings volume" habe ich, da ich eben mit Dummy/Notify arbeite.
Da Lautstärke (so wie ich es habe/nutze: Alexa mach lauter, leiser, schalte stumm [wie heißt denn "unstumm" in Deutsch? ;) / aktuell sage ich: mach wieder lauter :) ) nur 0-100 geht, rufe ich eine Sub, in der ich dann schaue was zu tun ist:Code Auswählen
sub my_PlaybackControl($$)
{
my ($Device,$Event) = @_;
my $CurrentActivity = ReadingsVal("HarmonyHub", "currentActivity", "n.a.");
Log(1,"my_PlaybackControl Device: $Device Event: $Event");
# if($Event eq "on")
# {
# fhem("set HarmonyHub activity Fernsehen");
# }
# elsif($Event eq "off")
# {
# {fhem "set HarmonyHub activity PowerOff"}
# }
# elsif($Event =~ m/mute/)
if($Event =~ m/mute/)
{
fhem("set HarmonyHub command Mute");
}
elsif($Event =~ m/volume/)
{
if(OldReadingsVal($Device, "volume", 0) > ReadingsVal($Device, "volume", 0))
{
fhem("set HarmonyHub command VolumeDown; sleep 1; set HarmonyHub command VolumeDown; sleep 1; set HarmonyHub command VolumeDown");
}
else
{
if(ReadingsVal($Device, "mute", 0) eq "1")
{
fhem("set HarmonyHub command Mute");
fhem("setreading $Device mute 0");
}
else
{
# weil das erste VolumeUp "nur" die Anzeige "anwirft" und erst das zweite tatsächlich lauter macht und einmal ist ja bekanntlich keinmal ;)
fhem("set HarmonyHub command VolumeUp; sleep 1; set HarmonyHub command VolumeUp; sleep 1; set HarmonyHub command VolumeUp");
}
}
}
elsif($Event =~ m/playback/)
{
my $PlayState = (split(/: /, $Event))[1];
# irgendwie habe ich die Activity wohl "falsch" angelegt, sie hat kein Play/Stop/Pause, daher direkt über das "Gerät"
if($CurrentActivity =~ m/Amazon/)
{
fhem("set harmony_41290995 command $PlayState");
}
Log(1,"my_PlaybackControl Device: $Device Event: $Event PlayState: $PlayState");
}
elsif($Event =~ m/channel/)
{
my $ChannelNr = (split(/: /, $Event))[1];
Log(1,"my_PlaybackControl Device: $Device Event: $Event ChannelNr: $ChannelNr");
}
}
und dann eben noch das Notify dazu:Code Auswählen
defmod nWiedergabeControl notify dmTest:(on|off|channel|mute|volume|playback).* {my_PlaybackControl($NAME, $EVENT)}
Das alles ist (wie man am Code und den Namen sieht) erst mal zum Testen...
(und [in vielen Dingen] sehr speziell auf meine Umgebung)
...mache ich eigentlich immer, bevor es dann auf das Hauptsystem (in schön und sauber) kommt...
UND JA: DUMMY und NOTIFY sind für Dummies ;)
-> das geht bestimmt auch besser/schöner/geschickter/schlanker/...
Gruß, Joachim
Zitatwie heißt denn "unstumm" in Deutsch?
Zitat von: justme1968 am 26 Februar 2019, 15:29:48
gestern hat jemand gepostet das es mit ton an und ton aus geht.
Attributes:
alexaName Receiver
alexaRoom Wohnzimmer
cmdIcon muteT:rc_MUTE
connectionCheck 240
devStateIcon on:rc_GREEN:off mainOff:rc_YELLOW:main_on off:rc_STOP:on absent:rc_RED muted:rc_MUTE@green:muteT playing:rc_PLAY@green:pause paused:rc_PAUSE@green:play
dlnaName DLNA_0005cd37a506
genericDeviceType speaker
group Multimedia
homebridgeMapping #On=zoneMain,cmdOn=on,cmdOff=off
#Volume=volume,minValue=0,maxValue=40,cmd=volume
#Favorit=favoriteList,cmd=favoriteList
#Eingang=input,cmd=input
#Sender=stream,cmd=stream
#InputController:reading=input:cmd=input,values=Sat/Cbl;Mediaplayer
#LauterLeiser=state,minValue=0,maxValue=40,minStep=5,cmd=+
#Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
icon it_server
room Multimedia
sortby 2
stateFormat stateAV
webCmd volume:mute:input:favoriteList:streamZitat von: Loredo am 26 Februar 2019, 16:36:17
Hast du alexa-fhem neu gestartet?
Es kann sein, dass das nicht automatisch passiert ist, weil sich das Event von "update" auf "install" geändert hat und André das womöglich im FHEM Modul bisher nicht berücksichtigt hat, so dass die Versionsnummer im alexa Device in FHEM noch nicht richtig angezeigt wird.
Zitat von: justme1968 am 26 Februar 2019, 16:56:01
hast du die detail ansicht neu geladen? internals werden nicht per longpoll aktualisiert.
warum ist dein hombridgeMapping komplett auskommentiert?
was steht bei der discovers und beim schalten im log?
@Loredo: die module reagieren auf alle BEGIN... und FINISH... events aus dem npmjs modul.
[2019-2-26 17:00:20] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.PowerController","name":"TurnOn","payloadVersion":"3","messageId":"1c508311-6bbe-46b6-add9-543d9afb1644","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"IT_F00000FFFF_FF_F0","cookie":{"fuuid":"5c44bfde-f33f-cd72-d80c-87152984df6ac9c0","device":"Samsung_TV_power"}},"payload":{}}}
[2019-2-26 17:00:20] [FHEM] Samsung_TV_power: executing set cmd for On with value 1
[2019-2-26 17:00:20] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20Samsung_TV_power%20on&fwcsrf=csrf_917993802964547&XHR=1
[2019-2-26 17:00:20] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"ON","timeOfSample":"2019-02-26T16:00:20.574Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"feb298ea-3ac0-457d-800d-d519633fb54e","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"IT_F00000FFFF_FF_F0"},"payload":{}}}
[2019-2-26 17:00:20] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.PowerController","name":"TurnOn","payloadVersion":"3","messageId":"7b17810e-a250-4b2d-8859-73a1cd72b133","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"5c44bfde-f33f-cd72-1e44-81c051f2f1eccde9","cookie":{"fuuid":"5c44bfde-f33f-cd72-1e44-81c051f2f1eccde9","device":"SATReceiver"}},"payload":{}}}
[2019-2-26 17:00:20] [FHEM] SATReceiver: executing set cmd for On with value 1
[2019-2-26 17:00:20] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20SATReceiver%20on&fwcsrf=csrf_917993802964547&XHR=1
[2019-2-26 17:00:20] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"ON","timeOfSample":"2019-02-26T16:00:20.714Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"b6ccca34-9255-44f7-ae50-73a691af0f30","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"5c44bfde-f33f-cd72-1e44-81c051f2f1eccde9"},"payload":{}}}
[2019-2-26 17:00:20] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.PowerController","name":"TurnOn","payloadVersion":"3","messageId":"5f1f21ec-1f86-4ea0-a98c-d067b1b4739d","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"5c44bfe1-f33f-cd72-6540-e0a626376ab66e6d","cookie":{"fuuid":"5c44bfe1-f33f-cd72-6540-e0a626376ab66e6d","device":"AVReceiver"}},"payload":{}}}
[2019-2-26 17:00:20] [FHEM] AVReceiver: executing set cmd for On with value 1
[2019-2-26 17:00:20] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20AVReceiver%20on&fwcsrf=csrf_917993802964547&XHR=1
[2019-2-26 17:00:20] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"ON","timeOfSample":"2019-02-26T16:00:20.845Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"bd5cfe1a-00a9-44e2-8773-0cc22838afcc","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"5c44bfe1-f33f-cd72-6540-e0a626376ab66e6d"},"payload":{}}}
2019-02-26 17:00:20 caching: Samsung_TV_power-state: on
[2019-2-26 17:00:20] [FHEM] caching: On: 1 (as number; from 'on')
2019-02-26 17:00:20 caching: AVReceiver-power: on
[2019-2-26 17:00:20] [FHEM] AVReceiver-power not a number: on
2019-02-26 17:00:21 caching: SATReceiver-power: on
[2019-2-26 17:00:21] [FHEM] SATReceiver-power not a number: on
2019-02-26 17:00:21 caching: SATReceiver-state: on
[2019-2-26 17:00:21] [FHEM] caching: On: 1 (as number; from 'on')
2019-02-26 17:00:22 caching: AVReceiver-state: on
[2019-2-26 17:00:22] [FHEM] caching: On: 1 (as number; from 'on')
2019-02-26 17:00:23 caching: SATReceiver-channel: Das_Erste_HD
[2019-2-26 17:00:23] [FHEM] caching: ChannelController: Das_Erste_HD (as string; from 'Das_Erste_HD')
2019-02-26 17:00:28 caching: SATReceiver-power: off
[2019-2-26 17:00:28] [FHEM] SATReceiver-power not a number: off
2019-02-26 17:00:28 caching: SATReceiver-state: off
[2019-2-26 17:00:28] [FHEM] caching: On: 0 (as number; from 'off')
2019-02-26 17:00:28 caching: SATReceiver-channel: -
[2019-2-26 17:00:28] [FHEM] caching: ChannelController: - (as string; from '-')Zitat von: dk3572 am 27 Februar 2019, 09:06:31
Und für einen Tipp zum hombridgeMapping für meinen AVReceiver wäre ich auch dankbar.
Zitat von: MadMax-FHEM am 27 Februar 2019, 09:15:49
Hallo Dieter,
als "was" willst du denn den AVR haben?
"Speaker": lauter/leiser/mute
"media": lauter/leiser/mute/play/pause/stop/forward/.../Kanalwechsel/...
Vielleicht hilft ja als Anregung dieser Dummy:
https://forum.fhem.de/index.php/topic,95272.msg911857.html#msg911857
Ansonsten braucht es ein list des AVR (und auch gleich die Befehle, die du brauchst um die gewünschte Aktion beim AVR auch auszulösen)...
Gruß, Joachim
Zitat von: dk3572 am 27 Februar 2019, 09:23:37
Hallo Joachim,
ja, deinen Beitrag mit dem dummy hatte ich auch bereits gelesen ;)
Den Receiver habe ich jetzt mal als speaker angelegt.
Das Problem und ein List der Attribute habe ich ja beschrieben
https://forum.fhem.de/index.php/topic,95272.630.html (https://forum.fhem.de/index.php/topic,95272.630.html)
Danke schon mal für deine Hilfe.
VG Dieter
Internals:
Clients :DENON_AVR_ZONE:
DEF 192.xxx.xxx.xx:xx
DeviceName 192.xxx.xxx.xx:xx
FD 25
FUUID 5c44bfe1-f33f-cd72-6540-e0a626376ab66e6d
NAME AVReceiver
NR 380
NTFY_ORDER 50-AVReceiver
PARTIAL
STATE off
TIMEOUT 3
TYPE DENON_AVR
READINGS:
2018-04-09 19:56:52 PLIIheightGain mid
2019-02-27 08:31:50 allZoneStereo off
2019-02-26 07:13:11 ampAssign 5.1-Channel+Zone2
2019-02-27 08:31:50 aspectRatio 16:9
2018-04-09 20:00:40 audioFormat 200
2018-04-09 19:57:54 audioOutHDMI unknown
2019-02-27 08:31:50 bass 0
2019-02-27 08:31:50 cinemaEQ off
2019-02-27 08:18:39 currentAlbum -
2019-02-27 08:18:39 currentArtist -
2019-02-27 08:18:39 currentBitrate -
2019-02-27 08:18:39 currentCover http://192.xxx.xxx.xx/img/album%20art_S.png?1551251919000
2019-02-27 08:18:39 currentMedia -
2019-02-27 08:18:39 currentPlaytime -
2019-02-27 08:18:39 currentStation -
2019-02-27 08:18:39 currentStream -
2019-02-27 08:18:39 currentTitle -
2019-02-27 08:31:50 digitalInput auto
2019-02-27 08:31:50 dynamicCompression off
2019-02-26 16:45:08 dynamicEQ on
2019-02-25 13:21:02 dynamicVolume heavy
2018-08-31 14:32:48 favorite 1
2018-04-09 20:00:40 firmware 4900-3876-1680
2019-02-27 08:11:01 ignore -
2019-02-27 08:18:39 input Sat/Cbl
2019-02-26 17:01:01 inputSound hdmi
2019-02-27 08:18:39 levelCenter -6
2019-02-27 08:18:39 levelFrontHeightLeft 0
2019-02-27 08:18:39 levelFrontHeightRight 0
2019-02-27 08:18:39 levelFrontLeft -1.5
2019-02-27 08:18:39 levelFrontRight -2
2019-02-27 08:18:39 levelFrontWideLeft 0
2019-02-27 08:18:39 levelFrontWideRight 0
2019-02-27 08:18:39 levelSourroundBack 0
2019-02-27 08:18:39 levelSourroundBackLeft 0
2019-02-27 08:18:39 levelSourroundBackRight 0
2019-02-27 08:18:39 levelSourroundLeft 2.5
2019-02-27 08:18:39 levelSourroundRight 1.5
2019-02-27 08:18:39 levelSubwoofer -7
2019-02-26 07:13:10 lock off
2019-02-24 08:24:43 loudness on
2019-02-27 08:31:50 lowFrequencyEffects 0
2019-02-26 07:13:10 model AVR-X3000
2018-04-09 20:00:41 monitorOut auto
2019-02-27 09:32:13 multEQ reference
2019-02-27 08:31:50 mute off
2018-04-09 19:56:52 panorama off
2019-02-27 09:32:13 playStatus stopped
2019-02-27 09:10:54 power off
2019-02-27 09:32:13 presence present
2017-02-19 11:19:32 quickselect 5
2019-02-24 08:44:32 resolution auto
2019-02-27 08:18:39 resolutionHDMI auto
2018-04-09 20:00:40 samplingRate 48 khz
2019-02-26 11:30:42 setup off
2018-04-09 20:00:40 signal PCM
2019-02-25 04:01:33 sleep off
2019-02-27 08:31:50 sound Dolby PL2 C
2019-02-27 09:32:08 state opened
2019-02-27 09:32:13 stateAV off
2018-01-20 13:43:05 surroundMode DTS_Surround
2019-02-27 08:31:50 toneControl off
2019-02-27 08:31:50 treble 0
2019-02-26 14:47:55 trigger1 on
2019-02-26 08:53:24 tunerBand FM
2019-02-26 08:53:24 tunerFrequency 88.55 MHz
2019-02-26 08:53:24 tunerMode manual
2019-02-26 08:53:24 tunerPreset 1
2019-02-26 08:45:23 videoProcessingMode auto
2019-02-27 08:18:39 videoSelect off
2019-02-27 09:32:13 volume 35
2019-02-27 09:32:13 volumeMax 60
2019-02-27 09:32:13 volumeStraight -45
2019-02-27 09:40:13 zone2 off
2019-02-27 09:10:54 zoneMain off
helper:
PARTIAL
deviceIP 192.xxx.xxx.xx
isPause 0
isPlaying 0
nextConnectionCheck 1551257053.8428
playTimeCheck 0
volume 35
Attributes:
alexaName Receiver
alexaRoom Wohnzimmer
brand Denon
cmdIcon muteT:rc_MUTE
connectionCheck 240
devStateIcon on:rc_GREEN:main_off main_off:rc_YELLOW:main_on off:rc_STOP:main_on absent:rc_RED:main_on muted:rc_MUTE@green:muteT playing:rc_PLAY@green:pause paused:rc_PAUSE@green:play disconnected:rc_RED
dlnaName DLNA_0005cd37a506
genericDeviceType speaker
group Multimedia
homebridgeMapping #On=zoneMain,cmdOn=on,cmdOff=off
#Volume=volume,minValue=0,maxValue=40,cmd=volume
#Favorit=favoriteList,cmd=favoriteList
#Eingang=input,cmd=input
#Sender=stream,cmd=stream
#InputController:reading=input:cmd=input,values=Sat/Cbl;Mediaplayer
#LauterLeiser=state,minValue=0,maxValue=40,minStep=5,cmd=+
#Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
icon it_server
room Multimedia
sortby 2
stateFormat stateAV
type AVR
webCmd volume:mute:input:favoriteList:streamZitat von: dk3572 am 27 Februar 2019, 09:06:31
hat sich einer von euch zufällig noch mal dem Problem angenommen?
Meine alexa Version ist immer noch 0.5.22
Heute Morgen fhem update gemacht und alles neu gestartet.
Kann es mit dieser Sache zu tun haben?
https://forum.fhem.de/index.php/topic,96525.msg911844.html#new
Jetzt solltest Du Dein Alexa-Device nicht mehr löschen, denn das im Reading angezeigte "bearerToken" zu löschen bedeutet, dass die Software die Zugriffe von nicht mehr überprüfen kann und keine Kommandos mehr funktionieren. In diesem Fall hilft nur die Neuinstallation des Skills.dieter@intelnuc:~$ ps -ef | egrep '(alexa|ssh)'
root 967 1 0 09:30 ? 00:00:00 /usr/sbin/sshd -D
fhem 20518 10426 0 14:54 ? 00:00:02 node /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx -s
fhem 20530 20518 0 14:54 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:46803 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root 23622 967 0 15:52 ? 00:00:00 sshd: dieter [priv]
dieter 23735 23622 0 15:52 ? 00:00:00 sshd: dieter@pts/0
dieter 24903 23736 0 16:11 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)sh: echo: I/O error
On=state,values=off:0;on:1,cmdOff=off,cmdOn=on[2/27/2019, 3:29:08 PM] [FHEM] caching: On: 1 (as number; from 'off')On=POWER,values=off:0;on:1,cmdOff=off,cmdOn=on 2019-02-27 15:56:50 caching: Tasmota_1-POWER: on
[2/27/2019, 3:56:50 PM] [FHEM] caching: On: 1 (as number; from 'on')
[2/27/2019, 3:56:53 PM] [FHEM] Tasmota_1: executing set cmd for On with value 0
2019-02-27 15:56:53 caching: Tasmota_1-POWER: off
[2/27/2019, 3:56:53 PM] [FHEM] caching: On: 0 (as number; from 'off')
[2/27/2019, 3:29:08 PM] [FHEM] caching: On: 1 (as number; from 'off')
[2/27/2019, 3:56:50 PM] [FHEM] caching: On: 1 (as number; from 'on')
[2/27/2019, 4:09:28 PM] [FHEM] Fibaro_DS_AZ_Michael_Ventilator has
[2/27/2019, 4:09:28 PM] [FHEM] On [reportedState;on,off]
[2/27/2019, 4:09:28 PM] [FHEM] Brightness [state]
[2/27/2019, 4:09:28 PM] [FHEM] Custom Power [power]
[2/27/2019, 4:09:28 PM] [FHEM] Custom Energy [energy]
sudo npm ls -depth=0 -gZitat von: justme1968 am 27 Februar 2019, 16:43:51
@dk3572: dein alexa-fhem meldet version 0.5.22 an fhem und es meldet sich selber im log mit 0.5.22. was gibt einCode Auswählensudo npm ls -depth=0 -g
/usr/lib
├── alexa-fhem@0.5.24
├── dorita980@3.1.1
└── npm@6.8.0
dieter@intelnuc:~$ sudo find / -name alexa-fhem -exec ls -ld {} \;
drwxr-xr-x 2 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 3 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/alexa-fhem
drwxr-xr-x 2 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 4 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/alexa-fhem
lrwxrwxrwx 1 root root 40 Feb 27 14:54 /usr/bin/alexa-fhem -> ../lib/node_modules/alexa-fhem/bin/alexa
lrwxrwxrwx 1 root root 40 Feb 20 11:22 /usr/local/bin/alexa-fhem -> ../lib/node_modules/alexa-fhem/bin/alexa
drwxr-xr-x 5 fhem dialout 4096 Feb 25 08:08 /usr/local/lib/node_modules/alexa-fhem
drwxr-xr-x 5 root root 4096 Feb 27 14:54 /usr/lib/node_modules/alexa-fhem
sudo apt-get --purge removesudo rm -fr /usr/bin/alexa-fhem /usr/local/bin/alexa-fhem /usr/lib/node_modules/alexa-fhem /usr/local/lib/node_modules/alexa-fhem
sudo npm install -g alexa-fhemdieter@intelnuc:~$ sudo find / -name alexa-fhem -exec ls -ld {} \;
drwxr-xr-x 2 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 3 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/alexa-fhem
drwxr-xr-x 2 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 4 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/alexa-fhem
lrwxrwxrwx 1 root root 40 Feb 27 17:11 /usr/bin/alexa-fhem -> ../lib/node_modules/alexa-fhem/bin/alexa
drwxr-xr-x 5 root root 4096 Feb 27 17:11 /usr/lib/node_modules/alexa-fhemZitat von: dk3572 am 27 Februar 2019, 09:49:56
ok, dann noch mal ein List vom ReceiverCode AuswählenInternals:
Clients :DENON_AVR_ZONE:
DEF 192.xxx.xxx.xx:xx
DeviceName 192.xxx.xxx.xx:xx
FD 25
FUUID 5c44bfe1-f33f-cd72-6540-e0a626376ab66e6d
NAME AVReceiver
NR 380
NTFY_ORDER 50-AVReceiver
PARTIAL
STATE off
TIMEOUT 3
TYPE DENON_AVR
READINGS:
2018-04-09 19:56:52 PLIIheightGain mid
2019-02-27 08:31:50 allZoneStereo off
2019-02-26 07:13:11 ampAssign 5.1-Channel+Zone2
2019-02-27 08:31:50 aspectRatio 16:9
2018-04-09 20:00:40 audioFormat 200
2018-04-09 19:57:54 audioOutHDMI unknown
2019-02-27 08:31:50 bass 0
2019-02-27 08:31:50 cinemaEQ off
2019-02-27 08:18:39 currentAlbum -
2019-02-27 08:18:39 currentArtist -
2019-02-27 08:18:39 currentBitrate -
2019-02-27 08:18:39 currentCover http://192.xxx.xxx.xx/img/album%20art_S.png?1551251919000
2019-02-27 08:18:39 currentMedia -
2019-02-27 08:18:39 currentPlaytime -
2019-02-27 08:18:39 currentStation -
2019-02-27 08:18:39 currentStream -
2019-02-27 08:18:39 currentTitle -
2019-02-27 08:31:50 digitalInput auto
2019-02-27 08:31:50 dynamicCompression off
2019-02-26 16:45:08 dynamicEQ on
2019-02-25 13:21:02 dynamicVolume heavy
2018-08-31 14:32:48 favorite 1
2018-04-09 20:00:40 firmware 4900-3876-1680
2019-02-27 08:11:01 ignore -
2019-02-27 08:18:39 input Sat/Cbl
2019-02-26 17:01:01 inputSound hdmi
2019-02-27 08:18:39 levelCenter -6
2019-02-27 08:18:39 levelFrontHeightLeft 0
2019-02-27 08:18:39 levelFrontHeightRight 0
2019-02-27 08:18:39 levelFrontLeft -1.5
2019-02-27 08:18:39 levelFrontRight -2
2019-02-27 08:18:39 levelFrontWideLeft 0
2019-02-27 08:18:39 levelFrontWideRight 0
2019-02-27 08:18:39 levelSourroundBack 0
2019-02-27 08:18:39 levelSourroundBackLeft 0
2019-02-27 08:18:39 levelSourroundBackRight 0
2019-02-27 08:18:39 levelSourroundLeft 2.5
2019-02-27 08:18:39 levelSourroundRight 1.5
2019-02-27 08:18:39 levelSubwoofer -7
2019-02-26 07:13:10 lock off
2019-02-24 08:24:43 loudness on
2019-02-27 08:31:50 lowFrequencyEffects 0
2019-02-26 07:13:10 model AVR-X3000
2018-04-09 20:00:41 monitorOut auto
2019-02-27 09:32:13 multEQ reference
2019-02-27 08:31:50 mute off
2018-04-09 19:56:52 panorama off
2019-02-27 09:32:13 playStatus stopped
2019-02-27 09:10:54 power off
2019-02-27 09:32:13 presence present
2017-02-19 11:19:32 quickselect 5
2019-02-24 08:44:32 resolution auto
2019-02-27 08:18:39 resolutionHDMI auto
2018-04-09 20:00:40 samplingRate 48 khz
2019-02-26 11:30:42 setup off
2018-04-09 20:00:40 signal PCM
2019-02-25 04:01:33 sleep off
2019-02-27 08:31:50 sound Dolby PL2 C
2019-02-27 09:32:08 state opened
2019-02-27 09:32:13 stateAV off
2018-01-20 13:43:05 surroundMode DTS_Surround
2019-02-27 08:31:50 toneControl off
2019-02-27 08:31:50 treble 0
2019-02-26 14:47:55 trigger1 on
2019-02-26 08:53:24 tunerBand FM
2019-02-26 08:53:24 tunerFrequency 88.55 MHz
2019-02-26 08:53:24 tunerMode manual
2019-02-26 08:53:24 tunerPreset 1
2019-02-26 08:45:23 videoProcessingMode auto
2019-02-27 08:18:39 videoSelect off
2019-02-27 09:32:13 volume 35
2019-02-27 09:32:13 volumeMax 60
2019-02-27 09:32:13 volumeStraight -45
2019-02-27 09:40:13 zone2 off
2019-02-27 09:10:54 zoneMain off
helper:
PARTIAL
deviceIP 192.xxx.xxx.xx
isPause 0
isPlaying 0
nextConnectionCheck 1551257053.8428
playTimeCheck 0
volume 35
Attributes:
alexaName Receiver
alexaRoom Wohnzimmer
brand Denon
cmdIcon muteT:rc_MUTE
connectionCheck 240
devStateIcon on:rc_GREEN:main_off main_off:rc_YELLOW:main_on off:rc_STOP:main_on absent:rc_RED:main_on muted:rc_MUTE@green:muteT playing:rc_PLAY@green:pause paused:rc_PAUSE@green:play disconnected:rc_RED
dlnaName DLNA_0005cd37a506
genericDeviceType speaker
group Multimedia
homebridgeMapping #On=zoneMain,cmdOn=on,cmdOff=off
#Volume=volume,minValue=0,maxValue=40,cmd=volume
#Favorit=favoriteList,cmd=favoriteList
#Eingang=input,cmd=input
#Sender=stream,cmd=stream
#InputController:reading=input:cmd=input,values=Sat/Cbl;Mediaplayer
#LauterLeiser=state,minValue=0,maxValue=40,minStep=5,cmd=+
#Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
icon it_server
room Multimedia
sortby 2
stateFormat stateAV
type AVR
webCmd volume:mute:input:favoriteList:stream
Befehle sind
set AVReceiver volumeUP / VolumeDown
set AVReceiver mute on/off
set AVReceiver zoneMain on/off
Und wie bereits erwähnt, beim direkten ansprechen per alexa bekomme ich als Antwort, der Hub reagiert nicht.
Über eine Gruppe in der der Receiver steckt, lässt er sich an- und ausschalten.
Mute=mute,values=off:0;on:1,cmds=0:mute+off;1:mute+on
Zitat von: justme1968 am 27 Februar 2019, 17:31:42
aktuell kann alexa-fhem nur absolute laustärke.
Zitat von: justme1968 am 27 Februar 2019, 17:55:21
es gibt noch einen StepSpeaker. dort wird die laustärke relativ um bis zu -100 oder +100 geändert. es kann sein das man dann auch lauter und leiser sagen kann. aber so wirklich besser scheint mir das eigentlich nicht deshalb habe ich es noch nicht eingebaut.
Zitat von: server.js
switch (requestedName) {
case 'AdjustVolume':
target = current + event.directive.payload.volume;
break;
Zitat von: dk3572 am 27 Februar 2019, 17:12:36
Jetzt sieht es so ausCode Auswählendieter@intelnuc:~$ sudo find / -name alexa-fhem -exec ls -ld {} \;
drwxr-xr-x 2 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 3 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/alexa-fhem
drwxr-xr-x 2 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 4 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/alexa-fhem
lrwxrwxrwx 1 root root 40 Feb 27 17:11 /usr/bin/alexa-fhem -> ../lib/node_modules/alexa-fhem/bin/alexa
drwxr-xr-x 5 root root 4096 Feb 27 17:11 /usr/lib/node_modules/alexa-fhem
Und die Version in alexa stimmt ;)
Welche Einträge stimmen jetzt und was ist mit home/dieter/...... ?
Zitat von: MadMax-FHEM am 27 Februar 2019, 17:29:50
Hallo,
so ich hab echt einiges rumprobiert (lerne grad selber erst homebridgeMapping ;) )...
...ich hab auch mal im Code "gewühlt"...
Aber bzgl. Lautstärke sehe ich nur eine Möglichkeit per readingsProxy oder Dummy:
intern wird immer ein tatsächlicher/absoluter Lautstärkewert "berechnet" und gesetzt.
Auch wenn von Alexa ein "lauter/leiser" kommt...
Wenn du also kein "setze-absolute Lautstärke" Kommando hast (bzw. dein AVR) wird es (zumindest soweit ich das überblicke) nicht anders gehen...
Bei Mute könnte das funktionieren:Code Auswählen
Mute=mute,values=off:0;on:1,cmds=0:mute+off;1:mute+on
Konnte es nur an einem Dummy testen... ;)
Achja bzgl. sprechen (habe auch lange rum experimentiert ;) ):
Mute: Alexa, schalte Lautstärke von Gerät aus | Alexa, schalte Gerät stumm
UnMute: Alexa, schalte Lautstärke von Gerät wieder an|ein (ohne "wieder" geht es bei mir auch nicht so)
Ein: Alexa, schalte den Ton von Gerät an -> endet (zumindest bei meinen Versuchen) immer mit: das Gerät wird eingeschaltet (statt der Ton ;) )
Was ist mit den Kommandos "set AVReceiver zoneMain on/off" ?
Gruß, Joachim
Zitat von: justme1968 am 27 Februar 2019, 16:43:51
@OppiM: dein fibaro schalter liefert On, in deinem mapping steht aber on.
2019-02-27 19:10:49.001 ZWave Fibaro_DS_AZ_Michael_Ventilator set_on
2019-02-27 19:10:49.019 ZWave Fibaro_DS_AZ_Michael_Ventilator on
2019-02-27 19:10:49.126 ZWave Fibaro_DS_AZ_Michael_Ventilator on
2019-02-27 19:10:49.126 ZWave Fibaro_DS_AZ_Michael_Ventilator reportedState: on
2019-02-27 19:10:51.808 ZWave Fibaro_DS_AZ_Michael_Ventilator power: 15 W
2019-02-27 19:11:10.837 ZWave Fibaro_DS_AZ_Michael_Ventilator set_off
2019-02-27 19:11:10.865 ZWave Fibaro_DS_AZ_Michael_Ventilator off
[2/27/2019, 7:11:26 PM] [FHEM] caching: Brightness: 0 (as number; from 'set_on')
2019-02-27 19:11:26 caching: Fibaro_DS_AZ_Michael_Ventilator-state: on
[2/27/2019, 7:11:26 PM] [FHEM] caching: Brightness: 0 (as number; from 'on')
2019-02-27 19:11:26 caching: Fibaro_DS_AZ_Michael_Ventilator-reportedState: on
[2/27/2019, 7:11:26 PM] [FHEM] caching: On: 1 (as number; from 'on')
2019-02-27 19:11:30 caching: Fibaro_DS_AZ_Michael_Ventilator-power: 10.7 W
[2/27/2019, 7:11:30 PM] [FHEM] caching: Custom Power: 10.7 (as number; from ' 10.7 W')
2019-02-27 19:11:30 caching: Fibaro_DS_Emma_Licht-state: on
[2/27/2019, 7:11:30 PM] [FHEM] caching: On: 1 (as number; from 'on')
[2/27/2019, 7:11:30 PM] [FHEM] caching: Brightness: 0 (as number; from 'on')
2019-02-27 19:11:32 caching: Fibaro_DS_Emma_Licht-power: 8.4 W
[2/27/2019, 7:11:32 PM] [FHEM] caching: Custom Power: 8.4 (as number; from ' 8.4 W')
2019-02-27 19:11:37 caching: Fibaro_DS_AZ_Michael_Ventilator-state: set_off
[2/27/2019, 7:11:37 PM] [FHEM] caching: Brightness: 0 (as number; from 'set_off')
2019-02-27 19:11:37 caching: Fibaro_DS_AZ_Michael_Ventilator-state: off
[2/27/2019, 7:11:37 PM] [FHEM] caching: Brightness: 0 (as number; from 'off')
2019-02-27 19:11:37 caching: Fibaro_DS_AZ_Michael_Ventilator-reportedState: off
[2/27/2019, 7:11:37 PM] [FHEM] caching: On: 1 (as number; from 'off')
2019-02-27 19:11:37 caching: Fibaro_DS_AZ_Michael_Ventilator-power: 0 W
[2/27/2019, 7:11:37 PM] [FHEM] caching: Custom Power: 0 (as number; from ' 0 W')
On=reportedState,values=Off:0;On:1,cmdOff=off,cmdOn=on Brightness=clear[2/27/2019, 7:20:29 PM] [FHEM] caching: On: 1 (as number; from 'on')
[2/27/2019, 7:20:35 PM] [FHEM] caching: On: 1 (as number; from 'off')Zitat von: MadMax-FHEM am 27 Februar 2019, 19:18:36
Poste doch mal ein aktuelles list...
Wobei das mit dem Hub halt eigenartig ist.
Nochmal: Harmony Hub? Einen zusätzlichen Skill aktiviert?
Gruß, Joachim
Zitat von: dk3572 am 27 Februar 2019, 19:25:41
Ein List vom Receiver? Das hat sich heute nicht verändert ;)
Zitat von: dk3572 am 27 Februar 2019, 19:25:41
Habe noch die Dreambox. Hier funktioniert an/aus, lauter/leiser.
Und das ohne jegliches homebridgeMapping.
Zitat von: dk3572 am 26 Februar 2019, 15:55:29
Hallo,
ich habe bei meinem AVReceiver den typ speaker eingestellt.
In der App wird er auch als Lautsprecher gefunden.
Allerdings kann ich ihn nicht mehr per alexa steuern (an/aus/laut/leise).
Es folgt immer die Aussage, der hub reagiert nicht.
Den Receiver habe ich in einer Gruppe mit weiteren Geräten. Über diese Gruppe kann ich ihn per alexa an und ausschalten.
Im Verlauf der Sprachinteraktion wird der Name auch richtig verstanden.
Woran kann das liegen?Code AuswählenAttributes:
alexaName Receiver
alexaRoom Wohnzimmer
cmdIcon muteT:rc_MUTE
connectionCheck 240
devStateIcon on:rc_GREEN:off mainOff:rc_YELLOW:main_on off:rc_STOP:on absent:rc_RED muted:rc_MUTE@green:muteT playing:rc_PLAY@green:pause paused:rc_PAUSE@green:play
dlnaName DLNA_0005cd37a506
genericDeviceType speaker
group Multimedia
homebridgeMapping #On=zoneMain,cmdOn=on,cmdOff=off
#Volume=volume,minValue=0,maxValue=40,cmd=volume
#Favorit=favoriteList,cmd=favoriteList
#Eingang=input,cmd=input
#Sender=stream,cmd=stream
#InputController:reading=input:cmd=input,values=Sat/Cbl;Mediaplayer
#LauterLeiser=state,minValue=0,maxValue=40,minStep=5,cmd=+
#Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
icon it_server
room Multimedia
sortby 2
stateFormat stateAV
webCmd volume:mute:input:favoriteList:streamCode Auswählendieter@intelnuc:~$ sudo find / -name alexa-fhem -exec ls -ld {} \;
drwxr-xr-x 2 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 3 dieter dieter 4096 Feb 20 11:22 /home/dieter/.npm/alexa-fhem
drwxr-xr-x 2 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/registry.npmjs.org/alexa-fhem
drwxr-xr-x 4 fhem dialout 4096 Feb 25 08:08 /opt/fhem/.npm/alexa-fhem
lrwxrwxrwx 1 root root 40 Feb 27 17:11 /usr/bin/alexa-fhem -> ../lib/node_modules/alexa-fhem/bin/alexa
drwxr-xr-x 5 root root 4096 Feb 27 17:11 /usr/lib/node_modules/alexa-fhem
Hallo justme1968,
hast du zu den 2 Fällen noch irgendwelche Ideen?
Woher kommt z.B. die Meldung mit dem Hub?
Danke und VG
Dieter
Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off
ChannelController:reading=channel,cmd=channelZitat von: justme1968 am 28 Februar 2019, 20:47:42
@dk3572: was steht im alexa log?
2019-02-28 20:52:05 caching: AVReceiver-volume: 35.5
[2019-2-28 20:52:05] [FHEM] caching: Custom Volume: 36 (as number; from '35.5')
[2019-2-28 20:52:05] [FHEM] caching: Volume: 35.5 (as string; from '35.5')
Zitat von: justme1968 am 28 Februar 2019, 11:51:37
du kannst mit factor im homebridgeMapping arbeiten.
Volume=volume,minValue=0,maxValue=40,cmd=volume,factor=5Zitat von: ToKa am 28 Februar 2019, 20:56:57
Hallo justme,
wird denn dann von alexa-fhem automatische ein "set <device> channel XXX" ausgeführt, wobei XXX = aktueller Channel +/- 1 ist?
Dann müsste ich ja eigentlich nichts tun oder habe ich das falsch verstanden?
Beste Grüße
Torsten
set%20ReceiverAxBox4K%20channel%20-1&fwcsrf=csrf_1cccccccccccccccc&XHR=1defmod ChannelDownAlexaWZ cmdalias set ReceiverAxBox4K channel -1 AS set ReceiverAxBox4K channelDown
setstate ChannelDownAlexaWZ defined
Zitat von: justme1968 am 01 März 2019, 08:29:55
@dk3572: und wie reagiert alexa wenn du das kommando gibts? was steht der app history?
es ist etwas schwer zu helfen wenn man jede kleinigkeit nachfragen muss.
Zitat von: dk3572 am 01 März 2019, 09:17:12
Wenn ich gesagt bekomme was ich liefern soll mache ich das möglichst umgehend. ;)
Was z.B. ist die app history? Der Verlauf in der alexa web app?
Was bzw. was nicht im log steht habe ich gestern geschrieben.
Wie alexa reagiert habe ich auch des öfteren geschrieben.
Sie gibt als Antwort "der hub reagiert nicht, bitte Netzwerk od. Stromversorgung prüfen".
Und wie gesagt, mit der Dreambox funktioniert das ganze (an/aus, lauter/leiser).
Bin jetzt auch nicht zuhause, liefere aber gerne weitere Infos. Wenn ich denn weiß was.
Danke schon mal und VG
Dieter
Zitat von: justme1968 am 01 März 2019, 09:37:56
ja. der verlauf in der alexa app.
ich sehr keine antwort auf:
- wie reagiert alexa (bei lauter leiser)
oben steht es passiert nix. was genau ist das? das ist etwas völlig anderes als reagiert nicht.
- was steht bei der suche im log?
- was steht beim alexa start im alexa log?
[2019-3-1 15:14:20] Got SIGTERM, shutting down alexa-fhem...
[2019-3-1 15:14:20] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2019-3-1 15:14:20] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:20] Stopping SSH ...
[2019-3-1 15:14:20] Reading alexaFHEM.ProxyConnection set to stopped
[2019-3-1 15:14:20] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:20] *** SSH: exited with 0
[2019-3-1 15:14:40] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-3-1 15:14:40] os.homedir()=/opt/fhem
[2019-3-1 15:14:40] this is alexa-fhem 0.5.24
[2019-3-1 15:14:40] connecting to FHEM ...
[2019-3-1 15:14:40] [FHEM] trying longpoll to listen for fhem events
[2019-3-1 15:14:40] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1551449680700
[2019-3-1 15:14:40] [FHEM] got csrfToken: csrf_285798315395932
[2019-3-1 15:14:40] [FHEM] Checking devices and attributes...
[2019-3-1 15:14:40] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] [FHEM] waiting for events ...
[2019-3-1 15:14:40] [FHEM] Fetching FHEM devices...
[2019-3-1 15:14:40] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] [FHEM] alexa device is alexa
[2019-3-1 15:14:40] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.24%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:40] Server listening on: http://127.0.0.1:46685 for proxy connections
[2019-3-1 15:14:40] *** SSH: checking proxy configuration
[2019-3-1 15:14:40] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2019-3-1 15:14:40] Passed config: {"sshproxy":{"description":"FHEM Connector","ssh":"/usr/bin/ssh","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":46685},"connections":[{"webname":"fhem","uid":999,"filter":"alexaName=..*","server":"127.0.0.1","name":"FHEM","port":"8083"}]}
[2019-3-1 15:14:40] sshautoconf: SSH key seems to exist
[2019-3-1 15:14:41] sshautoconf: Our SSH key is known at the reverse proxy, good!
[2019-3-1 15:14:41] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
*** FHEM: connected
[2019-3-1 15:14:41] [FHEM] got: 25 results
[2019-3-1 15:14:41] [FHEM] wrong syntax: reading=input:cmd=input
[2019-3-1 15:14:41] [FHEM] AVReceiver is media
[2019-3-1 15:14:41] [FHEM] AVReceiver has
[2019-3-1 15:14:41] [FHEM] Custom Volume [volume;cached]
[2019-3-1 15:14:41] [FHEM] Mute [mute]
[2019-3-1 15:14:41] [FHEM] Custom Power [power]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [firmware]
[2019-3-1 15:14:41] [FHEM] On [zoneMain;on,off]
[2019-3-1 15:14:41] [FHEM] Volume [volume]
[2019-3-1 15:14:41] [FHEM] InputController [undefined]
2019-03-01 15:14:41 caching: AVReceiver-volume: 35
[2019-3-1 15:14:41] [FHEM] caching: Custom Volume: 35 (as number; from '35')
2019-03-01 15:14:41 caching: AVReceiver-mute: off
2019-03-01 15:14:41 caching: AVReceiver-power: on
[2019-3-1 15:14:41] [FHEM] AVReceiver-power not a number: on
2019-03-01 15:14:41 caching: AVReceiver-firmware: 4900-3876-1680
2019-03-01 15:14:41 caching: AVReceiver-zoneMain: off
2019-03-01 15:14:41 caching: AVReceiver-state: on
[2019-3-1 15:14:41] [FHEM] Dunstabzug is switch
[2019-3-1 15:14:41] [FHEM] Dunstabzug has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Dunstabzug-state: off
[2019-3-1 15:14:41] [FHEM] Esszimmer is light
[2019-3-1 15:14:41] [FHEM] Esszimmer has
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Esszimmer-D-firmware: 1.12
2019-03-01 15:14:41 caching: Esszimmer-state: off
[2019-3-1 15:14:41] [FHEM] Fenster_Bad is contact
[2019-3-1 15:14:41] [FHEM] Fenster_Bad has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Fenster_Bad-battery: ok
2019-03-01 15:14:41 caching: Fenster_Bad-D-firmware: 2.4
2019-03-01 15:14:41 caching: Fenster_Bad-state: closed
2019-03-01 15:14:41 caching: Fenster_Bad-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Fenster_Erker is contact
[2019-3-1 15:14:41] [FHEM] Fenster_Erker has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Fenster_Erker-battery: ok
2019-03-01 15:14:41 caching: Fenster_Erker-D-firmware: 2.4
2019-03-01 15:14:41 caching: Fenster_Erker-state: closed
2019-03-01 15:14:41 caching: Fenster_Erker-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Fenster_Kueche is contact
[2019-3-1 15:14:41] [FHEM] Fenster_Kueche has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Fenster_Kueche-battery: ok
2019-03-01 15:14:41 caching: Fenster_Kueche-D-firmware: 2.4
2019-03-01 15:14:41 caching: Fenster_Kueche-state: closed
2019-03-01 15:14:41 caching: Fenster_Kueche-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Fenster_Schlafzimmer is contact
[2019-3-1 15:14:41] [FHEM] Fenster_Schlafzimmer has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Fenster_Schlafzimmer-battery: ok
2019-03-01 15:14:41 caching: Fenster_Schlafzimmer-D-firmware: 2.4
2019-03-01 15:14:41 caching: Fenster_Schlafzimmer-state: closed
2019-03-01 15:14:41 caching: Fenster_Schlafzimmer-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Fenster_WC is contact
[2019-3-1 15:14:41] [FHEM] Fenster_WC has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Fenster_WC-battery: ok
2019-03-01 15:14:41 caching: Fenster_WC-D-firmware: 2.4
2019-03-01 15:14:41 caching: Fenster_WC-state: closed
2019-03-01 15:14:41 caching: Fenster_WC-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Gartenlicht is light
[2019-3-1 15:14:41] [FHEM] Gartenlicht has
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Gartenlicht-D-firmware: 1.12
2019-03-01 15:14:41 caching: Gartenlicht-state: off
[2019-3-1 15:14:41] [FHEM] Haustuer is contact
[2019-3-1 15:14:41] [FHEM] Haustuer has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [contact]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Haustuer-battery: ok
2019-03-01 15:14:41 caching: Haustuer-D-firmware: 2.4
2019-03-01 15:14:41 caching: Haustuer-contact: open (to VCCU)
[2019-3-1 15:14:41] [FHEM] KuecheSensorTemp is thermometer
[2019-3-1 15:14:41] [FHEM] KuecheSensorTemp has
[2019-3-1 15:14:41] [FHEM] BatteryLevel [battery]
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] CurrentTemperature [temperature]
2019-03-01 15:14:41 caching: KuecheSensorTemp-battery: 100
2019-03-01 15:14:41 caching: KuecheSensorTemp-temperature: 18.74
[2019-3-1 15:14:41] [FHEM] Ro_Erkerfenster is blind
[2019-3-1 15:14:41] [FHEM] Ro_Erkerfenster has
[2019-3-1 15:14:41] [FHEM] PositionState [motor]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] CurrentPosition [pct]
[2019-3-1 15:14:41] [FHEM] TargetPosition [pct]
2019-03-01 15:14:41 caching: Ro_Erkerfenster-motor: stop:on
2019-03-01 15:14:41 caching: Ro_Erkerfenster-D-firmware: 2.3
2019-03-01 15:14:41 caching: Ro_Erkerfenster-pct: 100
[2019-3-1 15:14:41] [FHEM] Ro_Terrassenfenster is blind
[2019-3-1 15:14:41] [FHEM] Ro_Terrassenfenster has
[2019-3-1 15:14:41] [FHEM] PositionState [motor]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] CurrentPosition [pct]
[2019-3-1 15:14:41] [FHEM] TargetPosition [pct]
2019-03-01 15:14:41 caching: Ro_Terrassenfenster-motor: stop:on
2019-03-01 15:14:41 caching: Ro_Terrassenfenster-D-firmware: 2.3
2019-03-01 15:14:41 caching: Ro_Terrassenfenster-pct: 100
[2019-3-1 15:14:41] [FHEM] Ro_Terrassentuer is blind
[2019-3-1 15:14:41] [FHEM] Ro_Terrassentuer has
[2019-3-1 15:14:41] [FHEM] PositionState [motor]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] CurrentPosition [pct]
[2019-3-1 15:14:41] [FHEM] TargetPosition [pct]
2019-03-01 15:14:41 caching: Ro_Terrassentuer-motor: stop:on
2019-03-01 15:14:41 caching: Ro_Terrassentuer-D-firmware: 2.3
2019-03-01 15:14:41 caching: Ro_Terrassentuer-pct: 100
[2019-3-1 15:14:41] [FHEM] SATReceiver is media
[2019-3-1 15:14:41] [FHEM] SATReceiver has
[2019-3-1 15:14:41] [FHEM] Custom Volume [volume;cached]
[2019-3-1 15:14:41] [FHEM] Mute [mute]
[2019-3-1 15:14:41] [FHEM] Custom Power [power]
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
[2019-3-1 15:14:41] [FHEM] ChannelController [channel]
[2019-3-1 15:14:41] [FHEM] PlaybackController [playback]
2019-03-01 15:14:41 caching: SATReceiver-volume: 70
[2019-3-1 15:14:41] [FHEM] caching: Custom Volume: 70 (as number; from '70')
2019-03-01 15:14:41 caching: SATReceiver-mute: off
2019-03-01 15:14:41 caching: SATReceiver-power: on
[2019-3-1 15:14:41] [FHEM] SATReceiver-power not a number: on
2019-03-01 15:14:41 caching: SATReceiver-state: on
2019-03-01 15:14:41 caching: SATReceiver-channel: 3sat_HD
[2019-3-1 15:14:41] [FHEM] Samsung_TV_power is switch
[2019-3-1 15:14:41] [FHEM] Samsung_TV_power has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Samsung_TV_power-state: on
[2019-3-1 15:14:41] [FHEM] Sideboardlampe is light
[2019-3-1 15:14:41] [FHEM] Sideboardlampe has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Sideboardlampe-state: off
[2019-3-1 15:14:41] [FHEM] Steckdosen_Stein is switch
[2019-3-1 15:14:41] [FHEM] Steckdosen_Stein has
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Steckdosen_Stein-D-firmware: 1.12
2019-03-01 15:14:41 caching: Steckdosen_Stein-state: off
[2019-3-1 15:14:41] [FHEM] Stehlampe is light
[2019-3-1 15:14:41] [FHEM] Stehlampe has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Stehlampe-state: off
[2019-3-1 15:14:41] [FHEM] Terrassentuer is contact
[2019-3-1 15:14:41] [FHEM] Terrassentuer has
[2019-3-1 15:14:41] [FHEM] StatusLowBattery [battery]
[2019-3-1 15:14:41] [FHEM] FirmwareRevision [D-firmware]
[2019-3-1 15:14:41] [FHEM] ContactSensorState [state]
[2019-3-1 15:14:41] [FHEM] CurrentDoorState [contact]
2019-03-01 15:14:41 caching: Terrassentuer-battery: ok
2019-03-01 15:14:41 caching: Terrassentuer-D-firmware: 2.4
2019-03-01 15:14:41 caching: Terrassentuer-state: closed
2019-03-01 15:14:41 caching: Terrassentuer-contact: closed (to VCCU)
[2019-3-1 15:14:41] [FHEM] Thermostat_Bad_Climate is thermostat
[2019-3-1 15:14:41] [FHEM] Thermostat_Bad_Climate has
[2019-3-1 15:14:41] [FHEM] TargetTemperature [desired-temp]
[2019-3-1 15:14:41] [FHEM] CurrentTemperature [measured-temp]
[2019-3-1 15:14:41] [FHEM] CurrentRelativeHumidity [humidity]
[2019-3-1 15:14:41] [FHEM] CurrentHeatingCoolingState [undefined]
2019-03-01 15:14:41 caching: Thermostat_Bad_Climate-desired-temp: 21.0
2019-03-01 15:14:41 caching: Thermostat_Bad_Climate-measured-temp: 21.0
2019-03-01 15:14:41 caching: Thermostat_Bad_Climate-humidity: 44
[2019-3-1 15:14:41] [FHEM] Ventilator_Terrasse is switch
[2019-3-1 15:14:41] [FHEM] Ventilator_Terrasse has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: Ventilator_Terrasse-state: off
[2019-3-1 15:14:41] [FHEM] echovoice is switch
[2019-3-1 15:14:41] [FHEM] echovoice has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
[2019-3-1 15:14:41] [FHEM] echovoice [state]
2019-03-01 15:14:41 caching: echovoice-state: on
[2019-3-1 15:14:41] [FHEM] hifi is switch
[2019-3-1 15:14:41] [FHEM] hifi has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
2019-03-01 15:14:41 caching: hifi-state: off
[2019-3-1 15:14:41] [FHEM] sender is switch
[2019-3-1 15:14:41] [FHEM] sender has
[2019-3-1 15:14:41] [FHEM] On [state;on,off]
[2019-3-1 15:14:41] [FHEM] aktion [state]
2019-03-01 15:14:41 caching: sender-state: off
[2019-3-1 15:14:41] BearerToken '...27815' read from alexa
[2019-3-1 15:14:41] [FHEM] got .eventToken
[2019-3-1 15:14:41] refreshing token
[2019-3-1 15:14:41] 39_alexa.pm is new version: true
[2019-3-1 15:14:41] sshautoconf: completed successfully
[2019-3-1 15:14:41] *** SSH: proxy configuration set up done
[2019-3-1 15:14:41] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-3-1 15:14:41] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:41] Starting SSH with -R 1234:127.0.0.1:46685 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-3-1 15:14:41] got fresh token
[2019-3-1 15:14:42] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-3-1 15:14:42] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:14:42] *** SSH: proxy connection established
[2019-3-1 15:14:42] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
Der Hub, mit dem das Netzwerkgerät verbunden ist, reagiert nicht. Bitte überprüfe Netzwerkverbindung und Stromversorgung.defmod AVReceiver DENON_AVR 192.xxx.xxx.xx
attr AVReceiver alexaName Receiver
attr AVReceiver alexaRoom Wohnzimmer
attr AVReceiver brand Denon
attr AVReceiver cmdIcon muteT:rc_MUTE
attr AVReceiver connectionCheck 240
attr AVReceiver devStateIcon on:rc_GREEN:main_off main_off:rc_YELLOW:main_on off:rc_STOP:main_on absent:rc_RED:main_on muted:rc_MUTE@green:muteT playing:rc_PLAY@green:pause paused:rc_PAUSE@green:play disconnected:rc_RED
attr AVReceiver dlnaName DLNA_0005cd37a506
attr AVReceiver genericDeviceType media
attr AVReceiver group Multimedia
attr AVReceiver homebridgeMapping On=zoneMain,cmdOn=on,cmdOff=off \
Volume=volume,minValue=0,maxValue=40,cmd=volume\
Mute=mute,cmd=mute,ValueOn=on,ValueOff=off,cmdOn=mute+on,cmdOff=mute+off\
InputController:reading=input:cmd=input,values=Sat/Cbl;;Mediaplayer\
\
#Favorit=favoriteList,cmd=favoriteList\
#Eingang=input,cmd=input\
#Sender=stream,cmd=stream\
#LauterLeiser=state,minValue=0,maxValue=40,minStep=5,cmd=+
attr AVReceiver icon it_server
attr AVReceiver room Multimedia
attr AVReceiver sortby 2
attr AVReceiver stateFormat stateAV
attr AVReceiver type AVR
attr AVReceiver webCmd volume:mute:input:favoriteList:stream
setstate AVReceiver on
setstate AVReceiver 2018-04-09 19:56:52 PLIIheightGain mid
setstate AVReceiver 2019-02-27 08:31:50 allZoneStereo off
setstate AVReceiver 2019-02-26 07:13:11 ampAssign 5.1-Channel+Zone2
setstate AVReceiver 2019-02-28 17:39:39 aspectRatio 16:9
setstate AVReceiver 2018-04-09 20:00:40 audioFormat 200
setstate AVReceiver 2018-04-09 19:57:54 audioOutHDMI unknown
setstate AVReceiver 2019-03-01 04:01:57 bass 0
setstate AVReceiver 2019-02-28 19:47:36 cinemaEQ off
setstate AVReceiver 2019-03-01 15:20:47 currentAlbum -
setstate AVReceiver 2019-03-01 15:20:47 currentArtist -
setstate AVReceiver 2019-03-01 15:20:47 currentBitrate -
setstate AVReceiver 2019-03-01 15:20:47 currentCover http://192.xxx.xxx.xx/img/album%20art_S.png?1551450047000
setstate AVReceiver 2019-03-01 15:20:47 currentMedia -
setstate AVReceiver 2019-03-01 15:20:47 currentPlaytime -
setstate AVReceiver 2019-03-01 15:20:47 currentStation -
setstate AVReceiver 2019-02-28 19:43:19 currentStream -
setstate AVReceiver 2019-03-01 15:20:47 currentTitle -
setstate AVReceiver 2019-02-28 04:01:58 digitalInput auto
setstate AVReceiver 2019-03-01 04:01:57 dynamicCompression off
setstate AVReceiver 2019-02-26 16:45:08 dynamicEQ on
setstate AVReceiver 2019-02-25 13:21:02 dynamicVolume heavy
setstate AVReceiver 2018-08-31 14:32:48 favorite 1
setstate AVReceiver 2018-04-09 20:00:40 firmware 4900-3876-1680
setstate AVReceiver 2019-03-01 15:20:47 ignore -
setstate AVReceiver 2019-03-01 14:40:27 input Sat/Cbl
setstate AVReceiver 2019-03-01 04:01:57 inputSound hdmi
setstate AVReceiver 2019-02-28 04:01:57 levelCenter -6
setstate AVReceiver 2019-02-28 04:01:57 levelFrontHeightLeft 0
setstate AVReceiver 2019-02-28 04:01:57 levelFrontHeightRight 0
setstate AVReceiver 2019-02-28 04:01:57 levelFrontLeft -1.5
setstate AVReceiver 2019-02-28 04:01:57 levelFrontRight -2
setstate AVReceiver 2019-02-28 04:01:57 levelFrontWideLeft 0
setstate AVReceiver 2019-02-28 04:01:57 levelFrontWideRight 0
setstate AVReceiver 2019-02-28 04:01:57 levelSourroundBack 0
setstate AVReceiver 2019-02-28 04:01:57 levelSourroundBackLeft 0
setstate AVReceiver 2019-02-28 04:01:57 levelSourroundBackRight 0
setstate AVReceiver 2019-02-28 04:01:57 levelSourroundLeft 2.5
setstate AVReceiver 2019-02-28 04:01:57 levelSourroundRight 1.5
setstate AVReceiver 2019-02-28 04:01:57 levelSubwoofer -7
setstate AVReceiver 2019-02-26 07:13:10 lock off
setstate AVReceiver 2019-02-24 08:24:43 loudness on
setstate AVReceiver 2019-03-01 04:01:57 lowFrequencyEffects 0
setstate AVReceiver 2019-02-26 07:13:10 model AVR-X3000
setstate AVReceiver 2018-04-09 20:00:41 monitorOut auto
setstate AVReceiver 2019-02-28 19:43:19 multEQ reference
setstate AVReceiver 2019-02-28 04:01:57 mute off
setstate AVReceiver 2018-04-09 19:56:52 panorama off
setstate AVReceiver 2019-03-01 15:20:47 playStatus stopped
setstate AVReceiver 2019-03-01 14:39:18 power on
setstate AVReceiver 2019-03-01 04:01:57 presence present
setstate AVReceiver 2017-02-19 11:19:32 quickselect 5
setstate AVReceiver 2019-02-28 19:47:36 resolution auto
setstate AVReceiver 2019-02-28 17:39:39 resolutionHDMI auto
setstate AVReceiver 2018-04-09 20:00:40 samplingRate 48 khz
setstate AVReceiver 2019-02-28 04:01:57 setup off
setstate AVReceiver 2018-04-09 20:00:40 signal PCM
setstate AVReceiver 2019-02-28 19:47:40 sleep off
setstate AVReceiver 2019-03-01 04:01:57 sound Dolby PL2 C
setstate AVReceiver 2019-03-01 14:39:18 state on
setstate AVReceiver 2019-03-01 15:25:07 stateAV on
setstate AVReceiver 2018-01-20 13:43:05 surroundMode DTS_Surround
setstate AVReceiver 2019-03-01 04:01:57 toneControl off
setstate AVReceiver 2019-03-01 04:01:57 treble 0
setstate AVReceiver 2019-03-01 04:01:57 trigger1 off
setstate AVReceiver 2019-02-28 04:01:58 tunerBand FM
setstate AVReceiver 2019-02-28 04:01:58 tunerFrequency 88.55 MHz
setstate AVReceiver 2019-02-28 04:01:58 tunerMode manual
setstate AVReceiver 2019-02-28 04:01:58 tunerPreset 1
setstate AVReceiver 2019-03-01 04:01:57 videoProcessingMode auto
setstate AVReceiver 2019-02-28 19:47:35 videoSelect off
setstate AVReceiver 2019-02-28 20:52:34 volume 35
setstate AVReceiver 2019-02-28 20:52:34 volumeMax 60
setstate AVReceiver 2019-02-28 20:52:34 volumeStraight -45
setstate AVReceiver 2019-03-01 15:25:10 zone2 on
setstate AVReceiver 2019-03-01 15:25:07 zoneMain ondefmod alexa alexa
attr alexa alexaFHEM-auth crypt:565c575600545828720f5807054d7a555011772a202c
attr alexa alexaFHEM-config ./alexa-fhem.cfg
attr alexa alexaFHEM-log ./log/alexa-%Y-%m-%d.log
attr alexa alexaMapping #Characteristic=<name>=<value>,...\
On=verb=schalte,valueOn=an;;ein,valueOff=aus,valueToggle=um\
\
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent\
\
Hue=verb=stelle,valuePrefix=auf,values=rot:0;;grün:128;;blau:200\
Hue=verb=färbe,values=rot:0;;grün:120;;blau:220\
\
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER\
Saturation=verb=sättige,values=AMAZON.NUMBER\
\
TargetPosition=verb=mach,articles=den;;die,values=auf:100;;zu:0\
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent\
\
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad\
\
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent\
\
#Weckzeit=verb=stelle,valuePrefix=auf;;für,values=AMAZON.TIME,valueSuffix=uhr
attr alexa alexaTypes #Type=<alias>[,<alias2>[,...]]\
light=licht,lampen\
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
attr alexa devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
attr alexa echoRooms #<deviceId>=<room>\
attr alexa fhemIntents #IntentName=<sample utterance>\
gutenMorgen=guten morgen\
guteNacht=gute nacht
attr alexa icon alexa
attr alexa room Amazon
attr alexa stateFormat alexaFHEM
setstate alexa running /usr/bin/alexa-fhem
setstate alexa 2019-02-27 12:03:38 .eventToken {"access_token":"Atza|IwEBIGfmGZSRgnHbyZafmJrO7eosSoyJVOakyvz9mQDh5K97Jqo-_mVgOSOlQvP9zooDWfYHGoJaKSn4vD9WGqpQxUTDv-nJ8T3lAsrEVlrR-sStzxLwjYBZjvZJkjPhlCfZmivZ_WpEHFG3JWTlR23YmtzYSXXNrTIfUu5vHEwepGo4OzcXGqxrCziRRdGNzCx57__x0-2RcnEV9C5EkjmSZ0YZFK4Rfe0f3tqiH6fpAaZya27vby_mMKNv195o5_UOjtBurm3c6bLtdSEvO0fZNjOOH5noPrxlHQsMalGlF2A-y_BI1IzEFktIX4ePLLQKHwuSmwXiXnFKsMl_Vph-BSQV","refresh_token":"Atzr|IwEBIEeQKu1JJBJC1HfWDvtA7S20Csa_Rgp6zoMfRQDwux2z9p9dinjwhelGxE1dvvfv2GQWMxQ5RDYi4rcG2cPv5m-nW2LEz_45aBhEfMGCodDAfGSssCtZ2fXme7CR3J7_CSLqTyEerqhWAsbfkAsZSOUXOsOdrnLfi_pFJu2iWcYjkX7hogZywczxKeekSFMCDa9qO91gL4ojsKrcgJ2ODlC9G0QV4drku0NU8IE_oYyYuFyKbiG5FyUMaxte9Rr2AGVyKGGXl3hlXQ9XRTpliRF9g5E01JMHjw--ffYk5SWJcdHPCdGamSuUBSfk_pe7yFI8OSsEAxKxJCsEt9HSTCLI","token_type":"bearer","expires_in":3600}
setstate alexa 2019-03-01 15:14:40 alexaFHEM running /usr/bin/alexa-fhem
setstate alexa 2019-03-01 15:14:42 alexaFHEM.ProxyConnection running;; SSH connected
setstate alexa 2019-02-27 12:00:19 alexaFHEM.bearerToken crypt:02065556065023500c530005015b0657
setstate alexa 2019-02-27 12:00:19 alexaFHEM.skillRegKey crypt:0372265272552355185f780e725b05215605702150585d740b490652010c050f73025d560e54555d0453[2019-3-1 15:35:08] [FHEM] caching: Custom Volume: 20 (as number; from '20')
[2019-3-1 15:35:08] [FHEM] SATReceiver: executing set cmd for 00001001-0000-1000-8000-135D67EC4377 with value 10
[2019-3-1 15:35:08] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=set%20SATReceiver%20volume%2010&fwcsrf=csrf_285798315395932&XHR=1
[2019-3-1 15:35:08] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.Speaker","name":"volume","value":10,"timeOfSample":"2019-03-01T14:35:08.677Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"5831f724-987d-48c9-8c02-05bf749c89e5","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1EB1E3A0-011516A595927815"},"endpointId":"5c44bfde-f33f-cd72-1e44-81c051f2f1eccde9"},"payload":{}}}
2019-03-01 15:35:08 caching: SATReceiver-volume: 10
[2019-3-1 15:35:08] [FHEM] caching: Custom Volume: 10 (as number; from '10')ChannelController:reading=channel,cmd=channel
PlaybackController:playback,values=Play;Pause;Stop;Previous;NextZitat von: justme1968 am 01 März 2019, 08:29:55
@Abercrombie1892: was steht im log?
[3/1/2019, 6:13:04 PM] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.Speaker","name":"SetVolume","payloadVersion":"3","messageId":"d4f74a7a-23fc-4372-ac49-aba808ab3328","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"C1F00A04-03E7B9B0198FF781"},"endpointId":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca","cookie":{"fuuid":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca","device":"WZ.Pioneer"}},"payload":{"volume":2}}}
[3/1/2019, 6:13:04 PM] [FHEM] WZ.Pioneer: executing set cmd for 00001001-0000-1000-8000-135D67EC4377 with value 2
[3/1/2019, 6:13:04 PM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20WZ.Pioneer%20volume%202&XHR=1
[3/1/2019, 6:13:04 PM] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.Speaker","name":"volume","value":2,"timeOfSample":"2019-03-01T17:13:04.399Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"67aa06f9-0439-4ef2-b7ee-678eaeba1b2c","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"C1F00A04-03E7B9B0198FF781"},"endpointId":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca"},"payload":{}}}
2019-03-01 18:13:04 caching: WZ.Pioneer-volume: 1
[3/1/2019, 6:13:04 PM] [FHEM] caching: Custom Volume: 1 (as number; from '1')
[3/1/2019, 6:13:04 PM] [FHEM] caching: Volume: 1 (as string; from '1')homebridgeMapping
Volume=volume,minValue=0,maxValue=40,cmd=volume,factor=5
Zitat von: justme1968 am 27 Februar 2019, 17:08:04
nur keine angst. da ist scheinbar schon was vermurkst :)Code Auswählensudo rm -fr /usr/bin/alexa-fhem /usr/local/bin/alexa-fhem /usr/lib/node_modules/alexa-fhem /usr/local/lib/node_modules/alexa-fhem
Zitat von: topa_LE am 07 März 2019, 12:35:47
Hallo,
weiß nicht ob das hier rein gehört, Frage wurde schon mal gestellt.
Könnte man eigentlich mit dem alexa-fhem Modul KODI per Sprache steuern? Da gibt es ja im Netz diverse andere Kodi Custom Skill HowTo's.
Hat das vielleicht einer schon erfolgreich umgesetzt?
Zitat von: Esjay am 07 März 2019, 12:55:22
Wenn du Kodi in Fhem integriert hast, könntest du mit Hilfe des Wikis das durchaus umsetzten. Zumindest Play, Stop,mute usw.
grüße
InputController=input,cmd=input,values=TUNER:tuner;FERNSEHER:tv;HDMI+1:hdmi1executing: http://127.0.0.1:8083/fhem?cmd=set%20WZ.Pioneer%20input%20FERNSEHER&XHR=1if( typeof device.mappings.InputController.value2homekit === 'object' && device.mappings.InputController.value2homekit[target] !== undefined)
target = device.mappings.InputController.value2homekit[target]; switch (requestedName) {
case 'SelectInput':
target = event.directive.payload.input;
if( typeof device.mappings.InputController.value2homekit === 'object' && device.mappings.InputController.value2homekit[target] !== undefined)
target = device.mappings.InputController.value2homekit[target];
device.command( mapping, target );
break;
default:
return createError(ERROR3_INVALID_DIRECTIVE, undefined, event);
break;
}Zitat von: Esjay am 07 März 2019, 12:55:22
Wenn du Kodi in Fhem integriert hast, könntest du mit Hilfe des Wikis das durchaus umsetzten. Zumindest Play, Stop,mute usw.
grüße
Zitat von: Abercrombie1892 am 01 März 2019, 18:19:40Code Auswählen[3/1/2019, 6:13:04 PM] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.Speaker","name":"SetVolume","payloadVersion":"3","messageId":"d4f74a7a-23fc-4372-ac49-aba808ab3328","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"C1F00A04-03E7B9B0198FF781"},"endpointId":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca","cookie":{"fuuid":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca","device":"WZ.Pioneer"}},"payload":{"volume":2}}}
[3/1/2019, 6:13:04 PM] [FHEM] WZ.Pioneer: executing set cmd for 00001001-0000-1000-8000-135D67EC4377 with value 2
[3/1/2019, 6:13:04 PM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20WZ.Pioneer%20volume%202&XHR=1
[3/1/2019, 6:13:04 PM] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.Speaker","name":"volume","value":2,"timeOfSample":"2019-03-01T17:13:04.399Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"67aa06f9-0439-4ef2-b7ee-678eaeba1b2c","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"C1F00A04-03E7B9B0198FF781"},"endpointId":"5c4b080f-f33f-903f-df6a-d166b1dca6907dca"},"payload":{}}}
2019-03-01 18:13:04 caching: WZ.Pioneer-volume: 1
[3/1/2019, 6:13:04 PM] [FHEM] caching: Custom Volume: 1 (as number; from '1')
[3/1/2019, 6:13:04 PM] [FHEM] caching: Volume: 1 (as string; from '1')Code AuswählenhomebridgeMapping
Volume=volume,minValue=0,maxValue=40,cmd=volume,factor=5
Zitat von: erotikbaer am 17 März 2019, 00:47:44
hi,
gibts aktuell irgendwelche Probleme mit dem Vereinsserver?
ich bekomme plötzlich beim alexaFHEM.ProxyConnection:
error; Reverse Proxy replied with neither registered nor unregistered status: out: err:ssh_exchange_identification: read: Connection reset by peer
oder hab ich hier unbewusst irgendeinen mist gemacht?
gruß christian
stopped; Terminated with ssh_exchange_identification: read: Connection reset by peer , ssh will restart at 00:57:55pi@FHEM:/opt/fhem/log $ ps -ef | egrep '(alexa|ssh)'
root 356 1 0 2018 ? 00:00:00 /usr/sbin/sshd -D
pi 499 391 0 2018 ? 00:01:48 /usr/bin/ssh-agent x-session-manager
pi 542 1 0 2018 ? 00:00:00 /usr/bin/ssh-agent -s
root 12363 356 0 08:50 ? 00:00:00 sshd: pi [priv]
pi 12373 12363 0 08:50 ? 00:00:01 sshd: pi@pts/1
fhem 13989 13615 1 09:25 ? 00:00:06 node /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
fhem 14014 13989 0 09:25 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:32771 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
pi 14489 12376 0 09:36 pts/1 00:00:00 grep -E --color=auto (alexa|ssh) | fhem.log 019.03.23 09:25:46 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg 2019.03.23 09:25:46 3: alexa: starting 2019.03.23 09:25:46 3: alexa: using logfile: ./log/alexa-2019-03-23.log alexa.log [23.3.2019, 09:25:43] Got SIGTERM, shutting down alexa-fhem... [23.3.2019, 09:25:43] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating [23.3.2019, 09:25:43] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa %20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269 378733265&XHR=1 [23.3.2019, 09:25:43] Stopping SSH ... [23.3.2019, 09:25:43] Reading alexaFHEM.ProxyConnection set to stopped [23.3.2019, 09:25:43] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa %20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:43] *** SSH: exited with 143 [23.3.2019, 09:25:50] using config from ./alexa-fhem.cfg *** CONFIG: parsed completely [23.3.2019, 09:25:50] os.homedir()=/opt/fhem [23.3.2019, 09:25:50] this is alexa-fhem 0.5.26 [23.3.2019, 09:25:50] connecting to FHEM ... [23.3.2019, 09:25:52] [FHEM] trying longpoll to listen for fhem events [23.3.2019, 09:25:52] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=155332955 2132 [23.3.2019, 09:25:52] [FHEM] got csrfToken: csrf_562269378733265 [23.3.2019, 09:25:52] [FHEM] Checking devices and attributes... [23.3.2019, 09:25:52] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:52] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:52] [FHEM] waiting for events ... [23.3.2019, 09:25:52] [FHEM] Fetching FHEM devices... [23.3.2019, 09:25:52] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:52] [FHEM] alexa device is alexa [23.3.2019, 09:25:52] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa %7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.26%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265 &XHR=1 [23.3.2019, 09:25:52] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20prox yToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:52] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.ev entToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265&XHR=1 [23.3.2019, 09:25:52] Server listening on: http://127.0.0.1:32771 for proxy connections [23.3.2019, 09:25:52] *** SSH: checking proxy configuration [23.3.2019, 09:25:52] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh [23.3.2019, 09:25:52] Passed config: {"sshproxy":{"description":"FHEM Connector","ssh":"/usr/bin/ssh","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va .fhem.de"],"bind-ip":"127.0.0.1","port":32771},"connections":[{"filter":"alexaName=..*","uid":999,"name":"FHEM","webname":"fhem","server":"127.0.0.1","port":"808 3"}]} [23.3.2019, 09:25:52] sshautoconf: SSH key seems to exist [23.3.2019, 09:25:53] sshautoconf: Our SSH key is known at the reverse proxy, good! --More--(94%) [23.3.2019, 09:25:53] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa% 3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265&XHR=1 *** FHEM: connected [23.3.2019, 09:25:53] [FHEM] got: 0 results [23.3.2019, 09:25:53] BearerToken '...E02E1' read from alexa [23.3.2019, 09:25:53] 39_alexa.pm is new version: true [23.3.2019, 09:25:53] sshautoconf: completed successfully [23.3.2019, 09:25:53] *** SSH: proxy configuration set up done [23.3.2019, 09:25:53] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH [23.3.2019, 09:25:53] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa %20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265& XHR=1 [23.3.2019, 09:25:53] Starting SSH with -R 1234:127.0.0.1:32771 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de [23.3.2019, 09:25:54] Reading alexaFHEM.ProxyConnection set to running;; SSH connected [23.3.2019, 09:25:54] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa %20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_562269378733265& XHR=1 [23.3.2019, 09:25:54] *** SSH: proxy connection established [23.3.2019, 09:25:54] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated. pi@FHEM:/opt/fhem/log $ |
pi@FHEM:/opt/fhem/log $ sudo npm ls -depth=0 -g
(node:14834) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
/usr/local/lib
└── alexa-fhem@0.5.26
2019.03.27 18:44:05.866 1: reload: Error:Modul 39_alexa deactivated:
GPUtils.pm did not return a true value at FHEM/Meta.pm line 16, <$fh> line 901.
BEGIN failed--compilation aborted at FHEM/Meta.pm line 16, <$fh> line 901.
Compilation failed in require at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
BEGIN failed--compilation aborted at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
2019.03.27 18:44:05.866 0: GPUtils.pm did not return a true value at FHEM/Meta.pm line 16, <$fh> line 901.
BEGIN failed--compilation aborted at FHEM/Meta.pm line 16, <$fh> line 901.
Compilation failed in require at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
BEGIN failed--compilation aborted at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
2019.03.27 18:44:05.893 1: Including ./log/fhem.save
2019.03.27 18:44:06.386 1: configfile: Cannot load module alexa
Please define Alexa 5xxxxxxx5-f33f-9xx2-f4dc-38xxxxxxxxxxf3b firstZitat von: G4Cab am 27 März 2019, 19:38:01
Hi, nach dem fhem update all gestern seh ich nur noch das im Log
Idee?Code Auswählen
2019.03.27 18:44:05.866 1: reload: Error:Modul 39_alexa deactivated:
GPUtils.pm did not return a true value at FHEM/Meta.pm line 16, <$fh> line 901.
BEGIN failed--compilation aborted at FHEM/Meta.pm line 16, <$fh> line 901.
Compilation failed in require at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
BEGIN failed--compilation aborted at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
2019.03.27 18:44:05.866 0: GPUtils.pm did not return a true value at FHEM/Meta.pm line 16, <$fh> line 901.
BEGIN failed--compilation aborted at FHEM/Meta.pm line 16, <$fh> line 901.
Compilation failed in require at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
BEGIN failed--compilation aborted at ./FHEM/39_alexa.pm line 8, <$fh> line 901.
2019.03.27 18:44:05.893 1: Including ./log/fhem.save
2019.03.27 18:44:06.386 1: configfile: Cannot load module alexa
Please define Alexa 5xxxxxxx5-f33f-9xx2-f4dc-38xxxxxxxxxxf3b first
Zitat von: Loredo am 29 März 2019, 11:13:47Dann kann ich das auch nicht 100%ig mehr nachvollziehen.
Nein. GPUtils.pm ist Teil von FHEM und liegt nicht extern.
Weshalb bei dir ein apt-get upgrade geholfen haben soll, ist unverständlich.
938 verbose stack at Promise._fulfill (/usr/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:638:18)
938 verbose stack at /usr/lib/node_modules/npm/node_modules/bluebird/js/release/nodeback.js:42:21
938 verbose stack at <anonymous>
939 verbose cwd /home/pi
940 verbose Linux 4.19.30-v7+
941 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "alexa-fhem"
942 verbose node v8.15.1
943 verbose npm v6.9.0
944 error Cannot read property '0' of undefined
945 verbose exit [ 1, true ]
root@raspberrypi:~/.npm/_logs# 944 error Cannot read property '0' of undefined
-bash: 944: Kommando nicht gefunden.
ZitatWie kann ich das so konfigurieren, dass es sich wie die alte Lösung verhält?
Zitat@olili: natürlich. genau so wie früher.
{
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
},
"connections" : [
{
"filter" : "alexaName=..*",
"webname" : "fhem",
"port" : "8083",
"name" : "FHEM",
"server" : "127.0.0.1",
"uid" : 999
}
]
}homebridgeMapping Saturation=ct,cmd=ct,minStep=50alexaMapping Saturation=ver=mach,articles=das,values=wärmerZitat von: justme1968 am 11 April 2019, 20:08:25
einfach ohne homebridgeMapping. es sollte alles automatisch erkannt werden.
alexaMapping ist nur für den custom skill und für smart home nicht relevant.
Internals:
CHANGED
DEF 4 IODev=HueBridge
FUUID 5c54b1ff-f33f-cd72-d6de-c8c727991af062c2
FVERSION 31_HUEDevice.pm:0.190980/2019-04-02
ID 4
INTERVAL
IODev HueBridge
NAME Sofalicht
NR 288
STATE off
TYPE HUEDevice
desired 0
manufacturername Neuhaus Lighting Group
modelid NLG-RGBW light
name Sofalicht
swversion 1001-0007
type Extended color light
uniqueid 00:15:8d:00:02:93:58:ec-02
READINGS:
2019-04-11 15:45:41 alert select
2019-04-11 19:04:38 bri 52
2019-04-11 19:06:48 colormode ct
2019-04-11 20:24:39 ct 370 (2702K)
2019-04-11 15:45:41 effect none
2019-04-11 20:24:47 hue 6069
2019-04-11 20:25:41 onoff 0
2019-04-11 20:25:41 pct 0
2019-04-11 20:25:41 reachable 1
2019-04-11 20:24:39 rgb ffc698
2019-04-11 20:24:47 sat 220
2019-04-11 20:25:41 state off
2019-04-11 20:24:47 xy 0.4623,0.4149
helper:
alert select
bri 52
colormode ct
ct 370
devtype
effect none
hue 6069
on 0
pct 0
reachable 1
rgb ffc698
sat 220
update_timeout -1
xy 0.4623,0.4149
helper:
Attributes:
IODev HueBridge
alexaName Sofalicht
alexaRoom Wohnzimmer
alias Sofalicht
color-icons 2
devStateIcon {(HUEDevice_devStateIcon($name),"toggle")}
group Wohnzimmerlicht
icon light_ceiling
model NLG-RGBW light
room HUEDevice,Wohnzimmer
sortby 1
subType extcolordimmer
userattr Alles_aus Alles_aus_map lightSceneParamsToSave lightSceneRestoreOnlyIfChanged:1,0 structexclude
webCmd pct:ct 490:ct 380:ct 270:ct 160:toggle:on:offZitat von: justme1968 am 11 April 2019, 20:32:22Ja, über die App kann ich alles steuern.
geht es über die alexa app?
alexaFHEM.ProxyConnection
error; ssh-keygen command not found, please check if your installation of SSH is complete.
[13.4.2019, 15:14:14] >>>> [srv] {"directive":{"header":{"namespace":"Alexa.BrightnessController","name":"SetBrightness","payloadVersion":"3","messageId":"9e8b7f33-9b45-4550-8384-59f93fe03099","correlationToken":"AAAAAAAAAQBYs7jaIx19BUtlFgYn4a5cDAIAAAAAAACgK6YSt1/yksPnNlRgVieHHvX7uopPH8dbaFqK9SX0ShbGwKcvXgGvTZJmYnYqDYAUjUEZgljt3kB/EOUIZqyL9JsfAj5f88BR7P7N8tAghB3S9daYxMG5svIqnTJkN9k0T0/0Pu9SN3vdz2ZT+ICYkdbIAMR2BmFcReWfxeW6F5npiNBYPwXmkYjPKhC7NMhAGg95pV1NRcQr7NntSU/JuR+ITK8xaOLKa+wDD5UaA752hCI8sfNo4WSobtj8I3BeRKnwmuqakkX2jxdSc/D4xhBhgIUHjnogs4wguD1SeqocZ5J9C6o6LocQ0czRAYcSc3BsIM0e+xkq0+tPf8Ih9YBaRmkhA6d4oMzkZWXlyPFB72G6jtME7GC5G8KRqn+uXzTX6cWrMMtcV6PU3izw8eAIoaXPDtXTQv9mqSkn0YWUR7q7dohY9soxe7WSu3Z9YrxF3Lh2ovN+t7mFmudDb0bFQgK3Tfk4jBSP9ptmuAMbLwCdU0DTSjzX3CmJ3qN3MgYitu03BLoLx872V+O8kfaNhullmREDYxoH/Tnr7Q7mlHLDRQl5nDboplhNA++EhvuENCTcs2VVUoshLYhmRB9U0C3ldNBS1F3CxC4AOUdAnN7luyM3ghk3hdpCLL9tfLqixm3e9QWtmmYYSsy+NAW6LDx69wDV3TBlbk3WHP0sS5qNB40+NN9bYg=="},"endpoint":{"scope":{"type":"BearerToken","token":"Atza|IwEBIHwkCt2v5iBPPlgo2L0hkDItXz_FILIUP7Afuya7_DHrwPFX7WQdKmIynnkJWetPRyyV8fqihGRp0xTLbOFO_SVYrGONl4kzGlGbw5ouYz41uLRn2ui_0QUJZEG1Tic_0-VraP_wKr0820dXSsQneblZwyIl8mQLuIcI4-CXbOf3EqPBkASIShE_vy8cKrhB5EWQCQce4jb2yLZI-znJ8jMtrQ30EpPyVgGCQdIgYJ1r-xHmDDuXxI9H729Dq_rltH-ogsNGb0D2G5UYg0Rn_j7r0MQc3Et9sWuEKvcK35kWO-jattwvZHjB06iF2VFjuzYyIpZsBeKycR0dM-agfWLD1BVhk_03ItzqoDc8YJF9I2TJncgTxr-DFniXZqFSYURc6uajXpHW8ofNdItTLHPh2FoW4hhbJFy9zRF7s85tO67eQ8v-Rqwk9rxGh1gmBQBzeAlwRrv-yhbSJKwAsdhbYlkwq9KlC8OIxIxVtz5mVg"},"endpointId":"5c93e232-f33f-0c45-f528-70f8b16469d9e705","cookie":{"fuuid":"5c93e232-f33f-0c45-f528-70f8b16469d9e705","device":"StimmungsLicht"}},"payload":{"brightness":30}}}
[13.4.2019, 15:14:16] accepted new token
[13.4.2019, 15:14:16] [FHEM] caching: Brightness: 100 (as number; from 'FF4D00')
[13.4.2019, 15:14:16] [FHEM] StimmungsLicht: executing set cmd for Brightness with value 30
2019-04-13 15:14:16 caching: StimmungsLicht-rgb: 4d1700
[13.4.2019, 15:14:16] [FHEM] caching: Brightness: 30 (as number; from '4d1700')
[13.4.2019, 15:14:16] [FHEM] caching: Hue: 17 (as number; from '4d1700')
[13.4.2019, 15:14:16] [FHEM] caching: Saturation: 100 (as number; from '4d1700')
[13.4.2019, 15:14:16] [FHEM] value converted to 4d1700
[13.4.2019, 15:14:16] [FHEM] executing: http://192.168.69.94:8083/fhem?cmd=set%20StimmungsLicht%20rgb%204d1700&XHR=1
[13.4.2019, 15:14:16] <<<< [srv] {"context":{"properties":[{"namespace":"Alexa.BrightnessController","name":"brightness","value":30,"timeOfSample":"2019-04-13T13:14:16.464Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"6f3f4ab5-d804-484a-a10e-6ca6ddd37458","correlationToken":"AAAAAAAAAQBYs7jaIx19BUtlFgYn4a5cDAIAAAAAAACgK6YSt1/yksPnNlRgVieHHvX7uopPH8dbaFqK9SX0ShbGwKcvXgGvTZJmYnYqDYAUjUEZgljt3kB/EOUIZqyL9JsfAj5f88BR7P7N8tAghB3S9daYxMG5svIqnTJkN9k0T0/0Pu9SN3vdz2ZT+ICYkdbIAMR2BmFcReWfxeW6F5npiNBYPwXmkYjPKhC7NMhAGg95pV1NRcQr7NntSU/JuR+ITK8xaOLKa+wDD5UaA752hCI8sfNo4WSobtj8I3BeRKnwmuqakkX2jxdSc/D4xhBhgIUHjnogs4wguD1SeqocZ5J9C6o6LocQ0czRAYcSc3BsIM0e+xkq0+tPf8Ih9YBaRmkhA6d4oMzkZWXlyPFB72G6jtME7GC5G8KRqn+uXzTX6cWrMMtcV6PU3izw8eAIoaXPDtXTQv9mqSkn0YWUR7q7dohY9soxe7WSu3Z9YrxF3Lh2ovN+t7mFmudDb0bFQgK3Tfk4jBSP9ptmuAMbLwCdU0DTSjzX3CmJ3qN3MgYitu03BLoLx872V+O8kfaNhullmREDYxoH/Tnr7Q7mlHLDRQl5nDboplhNA++EhvuENCTcs2VVUoshLYhmRB9U0C3ldNBS1F3CxC4AOUdAnN7luyM3ghk3hdpCLL9tfLqixm3e9QWtmmYYSsy+NAW6LDx69wDV3TBlbk3WHP0sS5qNB40+NN9bYg=="},"endpoint":{"scope":{"type":"BearerToken","token":"Atza|IwEBIHwkCt2v5iBPPlgo2L0hkDItXz_FILIUP7Afuya7_DHrwPFX7WQdKmIynnkJWetPRyyV8fqihGRp0xTLbOFO_SVYrGONl4kzGlGbw5ouYz41uLRn2ui_0QUJZEG1Tic_0-VraP_wKr0820dXSsQneblZwyIl8mQLuIcI4-CXbOf3EqPBkASIShE_vy8cKrhB5EWQCQce4jb2yLZI-znJ8jMtrQ30EpPyVgGCQdIgYJ1r-xHmDDuXxI9H729Dq_rltH-ogsNGb0D2G5UYg0Rn_j7r0MQc3Et9sWuEKvcK35kWO-jattwvZHjB06iF2VFjuzYyIpZsBeKycR0dM-agfWLD1BVhk_03ItzqoDc8YJF9I2TJncgTxr-DFniXZqFSYURc6uajXpHW8ofNdItTLHPh2FoW4hhbJFy9zRF7s85tO67eQ8v-Rqwk9rxGh1gmBQBzeAlwRrv-yhbSJKwAsdhbYlkwq9KlC8OIxIxVtz5mVg"},"endpointId":"5c93e232-f33f-0c45-f528-70f8b16469d9e705"},"payload":{}}}
[2019-4-30 20:17:22] BearerToken '...ne 1.' read from System.Alexa
[2019-4-30 20:17:22] sshautoconf: aborted with Trying to fetch alexadevice failed with SyntaxError: Unexpected token B in JSON at position 0
[2019-4-30 20:17:22] *** SSH: proxy configuration failed: Trying to fetch alexadevice failed with SyntaxError: Unexpected token B in JSON at position 0
[2019-4-30 20:17:23] Reading alexaFHEM.ProxyConnection set to error;; Trying to fetch alexadevice failed with SyntaxError: Unexpected token B in JSON at position 0
stopped; failed to connect to fhem: Error: connect ECONNREFUSED 192.168.1.121:8083
{
"connections": [{
"port": "8083",
"webname": "fhem",
"uid": 999,
"filter": "alexaName=..*",
"server": "127.0.0.1",
"name": "FHEM"
},
{
"port": "8083",
"webname": "fhem",
"uid": 999,
"filter": "alexaName=..*",
"server": "192.168.1.120",
"name": "FHEM"
},
{
"port": "8083",
"webname": "fhem",
"uid": 999,
"filter": "alexaName=..*",
"server": "192.168.1.121",
"name": "FHEM"
}
],
"sshproxy": {
"ssh": "/usr/bin/ssh",
"description": "FHEM Connector"
}
}
Zitat von: gvzdus am 03 Juni 2019, 17:15:32
Hi Madmax,
wenn ich den Code auf die Schnelle interpretiere, stammt das noch aus meiner Prototypenzeit. Es geht auch um dieser User-ID (die von fhem), und nicht eine UUID. M.E. wird die uid nicht ausgewertet.
ssh -v -4 -p 58824 fhem-va.fhem.de status
OpenSSH_8.0p1, OpenSSL 1.1.1c 28 May 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to fhem-va.fhem.de [88.99.31.202] port 58824.
debug1: Connection established.
debug1: identity file /root/.ssh/id_rsa type 0
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: identity file /root/.ssh/id_xmss type -1
debug1: identity file /root/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.0
debug1: Remote protocol version 2.0, remote software version APACHE-SSHD-2.2.0
debug1: no match: APACHE-SSHD-2.2.0
debug1: Authenticating to fhem-va.fhem.de:58824 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:faKHDj9WmNmjRbq3SXmzb0FNfNxqond1TJQk9DLaBwQ
debug1: Host '[fhem-va.fhem.de]:58824' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
debug1: Will attempt key: /root/.ssh/id_rsa RSA SHA256:yjhgMRG4EyZ7pdNqViRfJL3gBiziLg8iol73i0WNRkI
debug1: Will attempt key: /root/.ssh/id_dsa
debug1: Will attempt key: /root/.ssh/id_ecdsa
debug1: Will attempt key: /root/.ssh/id_ed25519
debug1: Will attempt key: /root/.ssh/id_xmss
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: keyboard-interactive,publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa RSA SHA256:yjhgMRG4EyZ7pdNqViRfJL3gBiziLg8iol73i0WNRkI
debug1: Server accepts key: /root/.ssh/id_rsa RSA SHA256:yjhgMRG4EyZ7pdNqViRfJL3gBiziLg8iol73i0WNRkI
debug1: Authentication succeeded (publickey).
Authenticated to fhem-va.fhem.de ([88.99.31.202]:58824).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: network
debug1: Sending command: status
debug1: channel 0: free: client-session, nchannels 1
Attributes:
IODev radinoCC1101
alexaName badrollo
alexaRoom Bad
devStateIcon closed:fts_shutter_100 open:fts_shutter_10 my:fts_shutter_50
eventMap on:ab off:auf go-my:my on:close off:open
genericDeviceType blind
group Rolladen
homebridgeMapping clear
CurrentPosition=userposition,minValue=0,maxValue=100,minStep=50
TargetPosition=userposition,minValue=0,maxValue=100,minStep=50,cmds=0:close;;50:my;;100:open
model somfyshutter
positionInverse 1
room Alexa,Bad,Homekit,Somfy
siriName Badrolladen
userReadings userposition {(ReadingsVal($NAME,"state","open") eq "open")?100:(ReadingsVal($NAME,"state","open") eq "go-my")?50:0}
webCmd auf:my:ab
Zitat von: hoppel118 am 30 Juli 2019, 18:35:17
Moinsen,
habe auch mal eine Frage. Für was ist der alexaRoom gut?
Dort habe ich typische Raumnamen wie bspw. Wohnzimmer oder Badezimmer hinterlegt.
Wenn ich ein neues Gerät per alexaName mit Alexa bekannt mache, befindet sich das Gerät nicht automatisch in dem richtigen Raum in der Alexa-App.
Was habe ich falsch verstanden?
Viele Grüße Hoppel
Zitat von: MadMax-FHEM am 30 Juli 2019, 18:40:49
Tausendfach gestellt...
...tausendfach beantwortet... ;)
Hier Antwort 1001 ;)
alexaRoom ist NUR FÜR DEN CUSTOM SKILL relevant.
Ansonsten geht nur in Gruppen (die Raumnamen haben) anordnen in der Alexa-App...
Gruß, Joachim
Zitat von: hoppel118 am 31 Juli 2019, 13:10:07
OK, wenn es schon 1000 bzw. "nur" 100 Mal beantwortet wurde :D , dann sollten wir dazu einen kleinen Hinweis im Wiki ergänzen. Dann können wir uns die 102te Frage dazu evtl. ersparen... ;) Ich habe einfach nur die Anleitung im Wiki abgearbeitet (ohne erstmal einen ca. 50 Seiten-Thread zu durchforsten) und mich anschließend gefragt: "Wofür brauche ich den alexaRoom?". Keine Ahnung, wie der custom skill funktioniert, bin Neu bei Alexa. Der Alexa FHEM Connector scheint die für meinen Bedarf richtige Lösung zu sein.
Ich habe gerade einfach Mal folgenden Satz im Kapitel "Geräte im FHEM-Webfrontend zuweisen" ergänzt:
https://wiki.fhem.de/wiki/FHEM_Connector_f%C3%BCr_Amazon_Alexa#Ger.C3.A4te_im_FHEM-Webfrontend_zuweisen
Gruß Hoppel
ZitatDocument at least, and please work at least slowly on IDN
For SmartHome-Skills & German language, there has IMHO been no progress within the last 6 months. Undocumented non-support for certain languages e.g. for scheduling with ThermostatController is a No-Go. My preferred shortlist for german language support expansion: 1) Scheduling, 2) Sensors (Liters, Watt, kWh, mm etc.) to query all kind of numbers.
ZitatSollte jemand meine Meinung teilen, würde ich mich über Support für mein Anliegen freuen, 3 bis 4 positive Votes würden vielleicht Amazon doch etwas mehr Drive geben...
Zitat von: TomLee am 31 Juli 2019, 23:50:54
Oder gehts auch über den nomalen Account ?
Internals:
CFGFN ./cfg/Room_GR.cfg
DEF 52B6E5
FUUID 5c4993cd-f33f-02bc-3430-299953e1ce8c9912
HMLAN1_MSGCNT 9
HMLAN1_RAWMSG E52B6E5,0000,094F1015,FF,FFA9,35A41052B6E50000010601C800
HMLAN1_RSSI -87
HMLAN1_TIME 2019-08-01 21:13:20
IODev HMLAN1
LASTInputDev HMLAN1
MSGCNT 9
NAME GR_Blind
NOTIFYDEV global
NR 2326
NTFY_ORDER 50-GR_Blind
STATE open
TYPE CUL_HM
chanNo 01
lastMsg No:35 - t:10 s:52B6E5 d:000001 0601C800
protLastRcv 2019-08-01 21:13:20
protRcv 8 last_at:2019-08-01 21:13:20
protResnd 2 last_at:2019-08-01 21:13:03
protSnd 9 last_at:2019-08-01 21:13:20
protState CMDs_done
rssi_HMLAN1 cnt:4 min:-101 max:-92 avg:-94.75 lst:-93
rssi_at_HMLAN1 cnt:9 min:-94 max:-83 avg:-87.66 lst:-87
Helper:
DBLOG:
deviceMsg:
myDbLog:
TIME 1564686800.75837
VALUE open (to VCCU)
level:
myDbLog:
TIME 1564686800.75837
VALUE 100
motor:
myDbLog:
TIME 1564686800.75837
VALUE stop:open
pct:
myDbLog:
TIME 1564686800.75837
VALUE 100
state:
myDbLog:
TIME 1564686800.75837
VALUE on
timedOn:
myDbLog:
TIME 1564686800.75837
VALUE closed
READINGS:
2019-08-01 21:13:04 CommandAccepted yes
2019-07-11 07:47:26 D-firmware 2.11
2019-07-11 07:47:26 D-serialNr NEQ1768484
2019-07-11 09:55:20 PairedTo 0x000001
2019-07-11 09:55:20 R-confBtnTime permanent
2019-07-11 09:55:21 R-driveDown 27 s
2019-07-11 09:55:21 R-driveTurn 0.5 s
2019-07-11 09:55:21 R-driveUp 30 s
2019-07-11 09:55:20 R-intKeyVisib invisib
2019-07-11 09:55:20 R-localResDis off
2019-07-11 09:55:20 R-pairCentral 0x000001
2019-07-11 09:55:21 R-refRunCounter 0
2019-07-11 09:55:21 R-sign off
2019-07-11 09:55:21 R-statusInfoMinDly 2 s
2019-07-11 09:55:21 R-statusInfoRandom 1 s
2019-07-11 09:55:21 R-transmitTryMax 6
2019-08-01 21:13:20 deviceMsg on (to VCCU)
2019-08-01 21:13:20 level 100
2019-08-01 21:13:20 motor stop:on
2019-08-01 21:13:20 pct 100
2019-08-01 21:13:20 recentStateType info
2019-08-01 21:13:20 state on
2019-08-01 21:13:20 timedOn off
helper:
HM_CMDNR 53
cSnd 1100000152B6E50201C8,1100000152B6E5020100
dlvlCmd ++A01100000152B6E5020100
mId 0005
peerFriend peerSens,peerVirt
peerOpt 3:blindActuator
regLst 0,1,3p
rxType 1
supp_Pair_Rep 0
dir:
cur stop
rct up
expert:
def 1
det 1
raw 0
tpl 0
io:
newChn +52B6E5,00,00,00
nextSend 1564686800.76614
rxt 0
vccu VCCU
p:
52B6E5
00
00
00
prefIO:
HMLAN1
mRssi:
mNo 35
io:
HMLAN1:
-85
-85
prt:
bErr 0
sProc 0
rspWait:
q:
qReqConf
qReqStat
role:
chn 1
dev 1
prs 1
rpt:
IO HMLAN1
flg A
ts 1564686800.67855
ack:
HASH(0x61da3b8)
35800200000152B6E500
rssi:
HMLAN1:
avg -94.75
cnt 4
lst -93
max -92
min -101
at_HMLAN1:
avg -87.6666666666667
cnt 9
lst -87
max -83
min -94
tmpl:
Attributes:
IODev HMLAN1
IOgrp VCCU:HMLAN1
alexaName Rollladen
alexaRoom Gästezimmer
alias Roller Shutter
autoReadReg 4_reqStatus
devStateIcon open:fts_shutter_10@lightblue closed:fts_shutter_100 9\d.*:fts_shutter_10 8\d.*:fts_shutter_20 7\d.*:fts_shutter_30 6\d.*:fts_shutter_40 5\d.*:fts_shutter_50 4\d.*:fts_shutter_60 3\d.*:fts_shutter_70 2\d.*:fts_shutter_80 1\d.*:fts_shutter_90 0\d.*:fts_shutter_100
eventMap on:open off:closed stop:stop
expert 1_allReg
firmware 2.11
genericDeviceType blind
group Guest Room
model HM-LC-BL1PBU-FM
peerIDs 00000000,
room Guest Room,alexa
serialNr NEQxxxxxxxx
subType blindActuator
webCmd stop:up:open:100:90:80:70:60:50:40:30:20:10:0:closed:downInternals:
FD 4
FUUID 5d26d8bc-f33f-02bc-998a-5f78b3e8507f92a8
FVERSION 39_alexa.pm:0.190980/2019-04-02
LAST_START 2019-08-01 21:08:53
LAST_STOP 2019-08-01 21:08:52
NAME AC_Alexa
NOTIFYDEV global,global:npmjs.*alexa-fhem.*
NR 3629
NTFY_ORDER 50-AC_Alexa
PARTIAL
PID 2152
STARTS 23
STATE running /usr/local/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.28
currentlogfile /mnt/ElbeNetBoxStorage/fhemlog-archive/alexa-2019-08-01.log
logfile %L/alexa-%Y-%m-%d.log
CoProcess:
cmdFn alexa_getCMD
name alexaFHEM
state running /usr/local/bin/alexa-fhem
Helper:
DBLOG:
alexaFHEM:
myDbLog:
TIME 1564686533.27702
VALUE running /usr/local/bin/alexa-fhem
alexaFHEM.ProxyConnection:
myDbLog:
TIME 1564686544.50569
VALUE running; SSH connected
READINGS:
2019-08-01 21:08:53 alexaFHEM running /usr/local/bin/alexa-fhem
2019-08-01 21:09:03 alexaFHEM.ProxyConnection running; SSH connected
2019-07-11 08:35:40 alexaFHEM.bearerToken crypt:2626710225060b077303275907545157
2019-07-11 08:35:40 alexaFHEM.skillRegKey crypt:205a0a765473097318015523722456215423590f247b0c7f501b7c277201715250577405210e0b040004
helper:
Attributes:
alexaFHEM-auth crypt:30035b5c0c4402745d53082c510b171107105501570914
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log %L/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach:mache,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stell:stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampe,lampen,leuchte,leuchten
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
window=fenster,tür,türen
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
{alexa_guten_morgen()}=guten morgen
{alexa_gute_nacht()}=gute nacht
{alexa_ueberpruefe_fenster()}=überprüfe fenster|ob noch fenster auf sind|welche fenster auf sind|welche fenster noch auf sind|ob alle fenster zu sind|ob alle fenster geschlossen sind
{alexa_ueberpruefe_warmwasser()}=ob ich duschen kann|ob ich baden kann|ob ich ein bad nehmen kann|kann ich duschen|kann ich baden|ist das wasser warm genug|ist das warmwasser warm genug|wie warm ist der warmwasserspeicher|wieviel grad hat der warmwasserspeicher|wie warm ist der boiler|wieviel grad hat der boiler
{alexa_ueberpruefe_batteriestatus()}=ob irgendwelche geräte einen batteriewechsel brauchen|ob irgendwelche geräte einen batteriewechsel benötigen|ob irgendwelche batterien leer sind|ob irgendwelche batterien getauscht werden müssen|ob irgendwelche batterien ersetzt werden müssen|wie der status der batterien ist
room Alexa-Control
stateFormat alexaFHEM
verbose 2attr <device> genericDeviceTyp light
attr <device> subType blindActuator{
"endpointId": "OEQ1854504",
"manufacturerName": "FHEMCUL_HM",
"modelName": "FHEMHM-LC-BL1PBU-FM",
"version": "<unknown>",
"friendlyName": "rollladen küche",
"description": "n: eg_kueche_rl, r: cul_hm",
"actions": [],
"capabilities": [{
"type": "AlexaInterface",
"interface": "Alexa.PercentageController",
"version": "3",
"properties": {
"supported": [{
"name": "percentage"
}],
"proactivelyReported": false,
"retrievable": true
}
}],
"displayCategories": [],
"cookie": {
"device": "eg_kueche_rl",
"fuuid": "5c4d5eff-f33f-8d06-7b50-3ca753177a5783a9"
}
}
Zitat von: balli1187 am 02 August 2019, 23:34:49
@Sailor:
Ich habe folgende Attribute bei meinen:Code Auswählenattr <device> genericDeviceTyp light
attr <device> subType blindActuator
ZitatAlexa, setze den Rolladen auf 100%..
ZitatAlexa, setze den Rolladen im Gästezimmer auf 100%.ohne gleich die Antwort zu bekommen
ZitatTut mir leid, ich kann kein Gerät mit den Namen Rollladen Gästezimmer finden.obwohl es der alexa.amazon - Gruppe "Gästezimmer" zugewiesen ist.
Zitat von: Sailor am 05 August 2019, 21:40:32
PS: Wie kann man eigentlich den Programmierer dazu animieren, die Rolladen ein wenig zu verbessern um auf die Kommandos "auf" und "zu" zu reagieren - Flasche Rotwein, Pfund Kaffee? ;)
Zitatattr <device> genericDeviceTyp light
Alexa, stelle das Licht/Lampen im Gästezimmer auf 100%Alexa, stelle das Licht/Lampen auf 100%Zitat von: balli1187 am 05 August 2019, 22:54:41
... die der Gruppe Licht (in der App) angehört.
Alexa, stelle Rollladen im Licht auf 100%Alexa Rollos auf 20%Alexa, Rolllladen Küche auf 20%Zitat von: gvzdus am 05 August 2019, 22:09:54
Bei mir heißen die Rollläden (also "alexaName") "Rollladen Kind", "Rollladen Büro" u.s.w.. Ich versuche es gar nicht erst über die 2-gliedrige Suche "Raum -> Gerät", sondern bleibe einstufig. Das klappt stabil.
Die Tücken hatten wir schon mal diskutiert, manche Namen sind sehr kniffelig. Z.B. habe ich ein Thermometer "außen". Dessen Temperatur erhalte ich mit "Wie ist die Temperatur außen?". Mit "Wie ist die Temperatur von außen?" erhalte ich hingegen den Wetterbericht.
Und nein: Ich habe in den letzten Monaten keine Fortschritte bei Alexa im Smarthome-Sprachverständnis feststellen können. Da ist gefühlt seit ca. 9 (?) Monaten Stillstand.
ZitatAlexa, schalte das Licht im Gästezimmer an, dann geht auch nur das Licht im Gästezimmer an.
ZitatAlexa, schalte das Licht in der Waschküche an, dann geht auch nur das Licht in der Waschküche an.
ZitatAlexa, setze den Rolladen auf 100%, dann macht er den Rolladen im Gästezimmer auf aber alle anderen im Haus nicht.
ZitatAlexa, setze den Rolladen im Gästezimmer auf 100%, dann bekomme ich die Antwort "Tut mir leid, ich kann kein Gerät mit den Namen Rollladen Gästezimmer finden."
ZitatAlexa, setze den Rolladen in der Waschküche auf 100%, dann bekomme ich die Antwort "Tut mir leid, ich kann kein Gerät mit den Namen Rollladen Waschküche finden."
Zitat
Wenn ich sageZitatAlexa, schalte das Licht im Gästezimmer an
, dann geht auch nur das Licht im Gästezimmer an.
Wenn ich sageZitatAlexa, schalte das Licht in der Waschküche an
, dann geht auch nur das Licht in der Waschküche an.
ZitatAlexa, stelle das Licht im Gästezimmer auf 60%
ZitatAlexa, Gästezimmer auf 60%
ZitatWenn es mehrere Rollos in einem Raum gibt, kann man die ja auch "Röllläden Wohnzimmer" oder "Rollos Wohnzimmer" nennen und über eine structure als ein gemeinsames FHEM-Device für Alexa freigeben.
Alexa, Rollläden Wohnzimmer auf 60%
Zitat von: TomLee am 06 August 2019, 11:05:36
Nochmal, und was passiert wenn du sagstZitatAlexa, stelle das Licht im Gästezimmer auf 60%
Alexa, Gästezimmer auf 60%
ZitatAlexa, Rolladen auf 30%wird brav ausgeführt.
Zitat von: gvzdus am 06 August 2019, 07:59:01
Mit einem Restrisiko auch darin, dass Du Dir nicht ganz schlüssig zu sein scheinst, ob man Rollladen mit 2 oder 3 "L" schreibt.
defmod Rollo_EG_Kueche CUL_HM 4AABAF
attr Rollo_EG_Kueche IOgrp VCCU
attr Rollo_EG_Kueche alexaName erdbeere
attr Rollo_EG_Kueche autoReadReg 4_reqStatus
attr Rollo_EG_Kueche devStateIcon (100|on):fts_shutter_10@green (0|off):fts_shutter_100@red 1\d.*:fts_shutter_90 2\d.*:fts_shutter_80 3\d.*:fts_shutter_70 4\d.*:fts_shutter_60 5\d.*:fts_shutter_50 6\d.*:fts_shutter_40 7\d.*:fts_shutter_30 8\d.*:fts_shutter_20 9\d.*:fts_shutter_10 9\d.*:fts_shutter_10
attr Rollo_EG_Kueche expert 2_raw
attr Rollo_EG_Kueche firmware 2.8
attr Rollo_EG_Kueche genericDeviceType light
attr Rollo_EG_Kueche model HM-LC-BL1-FM
attr Rollo_EG_Kueche peerIDs 00000000,
attr Rollo_EG_Kueche room Homekit,Homematic,Rollladen
attr Rollo_EG_Kueche serialNr NEQ0512953
attr Rollo_EG_Kueche subType blindActuator
attr Rollo_EG_Kueche verbose 2
attr Rollo_EG_Kueche webCmd statusRequest:toggleDir:on:off:up:down:stop
defmod Rollo_OG_Bad CUL_HM 3B865B
attr Rollo_OG_Bad IOgrp VCCU
attr Rollo_OG_Bad alexaName himbeere
attr Rollo_OG_Bad autoReadReg 4_reqStatus
attr Rollo_OG_Bad devStateIcon (100|on):fts_shutter_10@green (0|off):fts_shutter_100@red 1\d.*:fts_shutter_90 2\d.*:fts_shutter_80 3\d.*:fts_shutter_70 4\d.*:fts_shutter_60 5\d.*:fts_shutter_50 6\d.*:fts_shutter_40 7\d.*:fts_shutter_30 8\d.*:fts_shutter_20 9\d.*:fts_shutter_10 9\d.*:fts_shutter_10
attr Rollo_OG_Bad expert 2_full
attr Rollo_OG_Bad firmware 2.5
attr Rollo_OG_Bad genericDeviceType light
attr Rollo_OG_Bad model HM-LC-BL1-FM
attr Rollo_OG_Bad peerIDs 00000000,
attr Rollo_OG_Bad room Homekit,Homematic,Rollladen
attr Rollo_OG_Bad serialNr MEQ0392459
attr Rollo_OG_Bad subType blindActuator
attr Rollo_OG_Bad verbose 2
attr Rollo_OG_Bad webCmd statusRequest:toggleDir:on:off:up:down:stopOn=state,valueOn=/up/,valueOff=/down/,cmdOn=up,cmdOff=downInternals:
CHANGED
DEF 192.168.178.51 55000
FUUID 5d4c4eb9-f33f-0804-e70e-******
Host 192.168.178.51
MAC b8:27:******
Mode
MyIP 192.168.178.29
NAME SchlafzimmerTV
NR 420
NTFY_ORDER 50-SchlafzimmerTV
Port 55000
STATE absent
TYPE SamsungAV
READINGS:
2019-08-08 20:02:27 state absent
helper:
Attributes:
alexaName SchalfzimmerTV
alexaRoom Schlafzimmer
homebridgeMapping On:cmdOn=poweron,CmdOff=poweroff
room ALEXA,SCHLAFZIMMERInternals:
CHANGED
FUUID 5d374cda-f33f-0804-4b5c-3d0c6c0cc4eb97ee
NAME Kamin
NR 284
STATE off
TYPE dummy
READINGS:
2018-12-03 16:15:29 AlarmTemperatur 90
2019-08-08 21:17:16 Temp_im_Puffer_oben 46.9
2019-08-08 21:17:16 Temp_im_Puffer_unten 30.6
2019-08-08 21:17:16 Temp_in_Wassertasche 26.5
Attributes:
alexaName Kamintemperatur
alexaRoom Wohnzimmer
devStateIcon on:icoZirkulationAn
event-on-change-reading .*
homebridgeMapping CurrentTemperature:reading=Temp_in_Wassertasche
icon icoHEIZUNG
readingList Temp_in_Wassertasche Temp_im_Puffer_oben Temp_im_Puffer_unten AlarmTemperatur
room ALEXA,WOHNZIMMER
setList AlarmTemperatur
stateFormat {ReadingsVal("LAD7","solarPump","off")}ZitatGerät 2: Ein DummyDevice, welches ich mir gebaut habe um Temperaturwerte auszulesen
Hier habe ich auch mit dem HomebridgeMapping gearbeitet, damit ich mir die Temperatur ansagen lassen kann. Den Wert den ich brauche ist in Temp_in_Wassertasche
attr Kamin genericDeviceType thermometer
attr Kamin homebridgeMapping CurrentTemperature=Temp_in_Wassertasche
Wie ist die Temperatur von KamintemperaturhomebridgeMapping
CurrentTemperature:reading=Temp_in_Wassertasche
homebridgeMapping On=state,cmdOn=poweron,CmdOff=poweroff
[2019-8-8 22:08:29] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.PowerController","name":"TurnOff","payloadVersion":"3","messageId":"f09e17b6-b28c-416d-9f36-82b996d93c89","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1A535A34-*****"},"endpointId":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef","cookie":{"fuuid":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef","device":"SchlafzimmerTV"}},"payload":{}}}
[b][2019-8-8 22:08:29] [FHEM] SchlafzimmerTV: executing set cmd for On with value 0[/b]
[2019-8-8 22:08:29] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20SchlafzimmerTV%200&fwcsrf=csrf_120040747355665&XHR=1
[2019-8-8 22:08:29] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"OFF","timeOfSample":"2019-08-08T20:08:29.449Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"da07f66b-6d00-4fb1-a285-cec0085528d6","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1A535A34-****"},"endpointId":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef"},"payload":{}}}
[2019-8-8 22:11:38] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.PowerController","name":"TurnOn","payloadVersion":"3","messageId":"003eb972-e547-4246-818f-a1adfd639a3b","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1A535A34-0833CE779BEE0B33"},"endpointId":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef","cookie":{"fuuid":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef","device":"SchlafzimmerTV"}},"payload":{}}}
[b][2019-8-8 22:11:38] [FHEM] SchlafzimmerTV: executing set cmd for On with value 1[/b]
[2019-8-8 22:11:38] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20SchlafzimmerTV%20poweron&fwcsrf=csrf_120040747355665&XHR=1
[2019-8-8 22:11:38] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"ON","timeOfSample":"2019-08-08T20:11:38.630Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"d77417cc-ddcb-4792-9b08-86af2a524fa8","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"1A535A34-0833CE779BEE0B33"},"endpointId":"5d4c4eb9-f33f-0804-e70e-ddc56b88fdc474ef"},"payload":{}}}Zitat
set%20SchlafzimmerTV%20poweron
set SchlafzimmerTV poweronZitat von: MadMax-FHEM am 08 August 2019, 22:39:16
Interessant ist oft auch im "Verlauf" zu schauen was Alexa verstanden hat...
[2019-8-10 08:51:44] [FHEM] SchlafzimmerTV: executing set cmd for On with value 1
[2019-8-10 08:51:44] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20SchlafzimmerTV%20poweron&fwcsrf=csrf_120040747355665&XHR=1
und
[2019-8-10 08:51:57] [FHEM] SchlafzimmerTV: executing set cmd for On with value 0
[2019-8-10 08:51:57] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=set%20SchlafzimmerTV%20poweroff&fwcsrf=csrf_120040747355665&XHR=1
Zitat von: TomLee am 10 August 2019, 10:38:20Hallo Thomas,
Ab hier (https://forum.fhem.de/index.php/topic,95272.msg892897.html#msg892897) mal die nächsten Seiten lesen.
Zusammenfassend brauchst eigentlich nur ein Reading channel und volume, ein homebridgemapping ist dazu gar nicht nötig.
Gruß
Thomas
alexa, schalte Fernseher auf Kanal 5fernseher unterstützt das nicht.Zitatalexa, schalte Fernseher auf Kanal 5
[8/19/2019, 3:09:23 PM] ERROR: InvalidAccessTokenError from 127.0.0.1[4.9.2019, 10:40:15] sshautoconf: *** Error: Your Homedirectory is writable by group/other. This will not work with SSH
[4.9.2019, 10:40:15] sshautoconf: aborted with user homedir writable by group/other ('chmod 755 /opt/fhem' required)
[4.9.2019, 10:40:15] *** SSH: proxy configuration failed: user homedir writable by group/other ('chmod 755 /opt/fhem' [2019-9-4 7:13:03 PM] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-4 7:13:03 PM] os.homedir()=/opt/fhem
[2019-9-4 7:13:03 PM] this is alexa-fhem 0.5.28
[2019-9-4 7:13:03 PM] connecting to FHEM ...
Startup rejected. Reason: Error: Cannot find module 'tough-cookie'
Require stack:
- /usr/local/lib/node_modules/alexa-fhem/node_modules/request/lib/cookies.js
- /usr/local/lib/node_modules/alexa-fhem/node_modules/request/index.js
- /usr/local/lib/node_modules/alexa-fhem/lib/fhem.js
- /usr/local/lib/node_modules/alexa-fhem/lib/user.js
- /usr/local/lib/node_modules/alexa-fhem/lib/server.js
- /usr/local/lib/node_modules/alexa-fhem/lib/cli.js
- /usr/local/lib/node_modules/alexa-fhem/bin/alexa
pi@Raspi:~ $ node -v
v12.10.0
pi@Raspi:~ $ npm -v
6.10.3
pi@Raspi:~ $ sudo npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.28
added 60 packages from 67 contributors in 15.112s
ZitatSelbst ein "sudo chown -R fhem:dialout /opt/fhem && sudo chmod 777 -R /opt/fhem" brachte kein erfolg.natürlich nicht. genau damit machst du das verzeichnis und alles darunter ja schreibbar für alle.
Zitat von: stera am 05 September 2019, 08:34:10Ursprünglich hatte ich diese Meldung:Code Auswählen[4.9.2019, 10:40:15] sshautoconf: *** Error: Your Homedirectory is writable by group/other. This will not work with SSH
[4.9.2019, 10:40:15] sshautoconf: aborted with user homedir writable by group/other ('chmod 755 /opt/fhem' required)
[4.9.2019, 10:40:15] *** SSH: proxy configuration failed: user homedir writable by group/other ('chmod 755 /opt/fhem'
Zitat von: stera am 05 September 2019, 08:34:10
chmod 777 -R /opt/fhem
chmod 755 /opt/fhem' required[2019-9-14 17:09:59] [FHEM] caching: CurrentTemperature: 20.5 (as number; from '20.5')
[2019-9-14 17:26:02] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2019-9-14 17:26:02] os.homedir()=/opt/fhem
[2019-9-14 17:26:02] this is alexa-fhem 0.5.28
[2019-9-14 17:26:02] connecting to FHEM ...
[2019-9-14 17:26:03] [FHEM] trying longpoll to listen for fhem events
2019.09.14 17:10:36 1: Alexa is against deletion (Alexa will be deleted after alexa-fhem has stopped or after 5 seconds. whatever comes first.), continuing with rereadcfg anyway
2019.09.14 17:26:01 2: Alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
2019.09.14 17:26:02 3: Alexa: starting
2019.09.14 17:26:02 3: Alexa: using logfile: ./log/alexa-2019-09-14.logdefine mySwitch1 dummy
attr mySwitch1 room Training
attr mySwitch1 webCmd on:offdefine d1 dummy
attr d1 readingList state
attr d1 setList state:on,off
attr d1 webCmd state
attr d1 alexaName Duda
attr d1 room AlexaZitat von: CatWeazle am 15 September 2019, 14:16:38
Hallo ihr Zwei,
also mein Fehler, ich habe in meiner Frage zum Thema nur geschrieben das ich das attr on:off benutzt habe, ohne zu erwähnen das dies im Zusammenhang mit "webCmd" gemacht wurde.
Joachims Erklärung folgend, war das in dem Fall mit ":" also richtig.
Bleibt nur die Frage, warum übernimmt Alexa das Gerät nicht ?
*
define dmAlexaFhemDummy dummy
attr dmAlexaFhemDummy alexaName WieWillstDuEsAnsprechen
attr dmAlexaFhemDummy genericDeviceType switch
attr dmAlexaFhemDummy setList on off
define d1 dummy
attr d1 alexaName Duda
attr d1 genericDeviceType switch
attr d1 room Alexa
attr d1 setList on offZitatBei meinem FHEM Wissensstand war es für mich der einfachste Weg über ein notify auf einen Schalter zu reagieren, so dass mir das notify drei Lampen im Abstand von 0.5Sec. nacheinander ein, bzw. aus schaltet.
Zitat von: CatWeazle am 15 September 2019, 15:17:00
Nochmal kurz zu meinem Verhältnis zu Dummy's allgemein.
Ich habe sie nie gemocht und wenn ich schon mal einen Trigger für ein notify oder doif brauchte, habe ich für die zwei Fälle in denen ich es mal brauchte ein IT Fantasiegerät angelegt.
Zurück zu deiner Frage Joachim.
Bei meinem FHEM Wissensstand war es für mich der einfachste Weg über ein notify auf einen Schalter zu reagieren, so dass mir das notify drei Lampen im Abstand von 0.5Sec. nacheinander ein, bzw. aus schaltet.
Übrigens, nach deiner Erklärung zum ALEXA-Dummy habe ich dann doch vom IT Fantasiegerät auf ein Dummy umgestellt. :)
Nochmals besten Dank!
*
no device created for Ferdinand (XiaomiDevice)
[2019-9-15 18:09:45] [FHEM] Sonoff_Aquarium: no service type detected
[2019-9-15 18:09:45] [FHEM] no device created for Sonoff_Aquarium (MQTT_DEVICE)
[2019-9-15 18:09:45] [FHEM] Sonoff_Flur_Licht: no service type detected
[2019-9-15 18:09:45] [FHEM] no device created for Sonoff_Flur_Licht (MQTT_DEVICE)
[2019-9-15 18:09:45] [FHEM] Sonoff_Spielzimmerlicht: no service type detected
[2019-9-15 18:09:45] [FHEM] no device created for Sonoff_Spielzimmerlicht (MQTT_DEVICE)homebridgeMapping On:start,Off:chargehomebridgeMapping On=cmdOn:start,cmdOff:charge
Zitat von: justme1968 am 15 September 2019, 19:36:22Code AuswählenhomebridgeMapping On=cmdOn:start,cmdOff:charge
Internals:
CHANGED
DEF 192.168.0.217 xxx
FD 52
FUUID 5c49df8b-f33f-a3b0-1e51-98570c89b4f9f356
NAME Ferdinand
NR 569
STATE Charging
TYPE XiaomiDevice
hardware Linux
mac 7C:49:EB:9D:B2:F6
model roborock.vacuum.s5
token xxx
READINGS:
2019-09-15 20:04:46 app_bom A.03.0005
2019-09-15 20:04:46 app_language en
2019-09-15 20:04:46 app_location de
2019-09-15 20:04:46 app_logserver awsde0.fds.api.xiaomi.com
2019-09-15 20:04:46 app_name custom_A.03.0005_CE
2019-09-15 20:04:46 app_timezone Europe/Berlin
2018-08-31 10:40:01 battery ok
2018-08-31 10:40:01 batteryLevel 100
2019-09-15 20:45:47 batteryPercent 96
2019-09-15 20:45:47 batteryState ok
2019-09-15 20:04:45 carpet_high 500
2019-09-15 20:04:45 carpet_integral 450
2019-09-15 20:04:45 carpet_low 400
2019-09-15 20:04:45 carpet_mode on
2019-09-15 20:04:45 carpet_stall_time 10
2019-09-15 20:45:47 cleaning_mode max
2019-09-15 20:04:44 consumables_filter 85
2019-09-15 20:04:44 consumables_main_brush 92
2019-09-15 20:04:44 consumables_sensors 28
2019-09-15 20:04:44 consumables_side_brush 89
2019-09-15 20:04:42 device_firmware 3.3.9_001886
2019-09-15 20:04:46 device_fw_features 102,103,104,105
2019-09-15 20:04:42 device_uptime 16.46
2019-09-15 20:45:47 dnd on
2019-09-15 20:04:45 dnd_enabled on
2019-09-15 20:04:45 dnd_end 08:00
2019-09-15 20:04:45 dnd_start 20:00
2019-09-15 20:45:47 error none
2019-09-15 20:45:47 error_code None
2019-09-15 20:36:47 event clean_complete
2019-09-15 20:45:47 fan_power 100
2019-09-15 20:37:48 history_0 2019-09-15 20:29:46: 5.74m² in 0.12h, finished cleaning
2019-09-15 20:37:48 history_1 2019-09-15 20:26:41: 1.62m² in 0.04h, finished cleaning
2019-09-15 20:37:48 history_2 2019-09-15 19:08:30: 0.00m² in 0.00h, not finished
2019-09-15 20:37:48 history_3 2019-09-15 12:17:32: 28.12m² in 0.45h, finished cleaning
2019-09-15 20:37:48 history_4 2019-09-15 09:33:09: 30.16m² in 0.50h, finished cleaning
2019-09-15 20:37:48 history_5 2019-09-14 10:18:29: 22.58m² in 0.34h, not finished
2019-09-15 20:37:48 history_6 2019-09-13 11:22:01: 30.70m² in 0.48h, finished cleaning
2019-09-15 20:37:48 history_7 2019-09-12 14:29:04: 29.20m² in 0.49h, finished cleaning
2019-09-15 20:37:48 history_8 2019-09-12 11:22:01: 30.52m² in 0.50h, finished cleaning
2019-09-15 20:37:48 history_9 2019-09-11 11:22:00: 30.43m² in 0.49h, finished cleaning
2019-09-15 20:45:47 in_cleaning no
2019-09-15 20:45:47 in_fresh_state yes
2019-09-15 20:45:47 in_returning no
2019-09-15 20:45:47 lab_status no
2019-09-15 20:45:47 last_clean_area 5.74
2019-09-15 20:45:47 last_clean_time 0.12
2019-09-15 20:37:48 last_timestamp 1568572186
2019-09-15 20:45:47 letzteReinigung 2019-09-15 20:29:46
2019-09-15 20:45:47 map_present yes
2019-09-15 20:04:42 serial_number R0018S82406226
2019-09-15 20:45:47 state Charging
2019-09-15 20:04:45 timer1 on
2019-09-15 20:04:45 timer1_power 100
2019-09-15 20:04:45 timer1_program start_clean
2018-08-31 09:42:59 timer1_time 11:22
2019-09-15 20:04:42 timezone Europe/Berlin
2019-09-15 20:37:47 total_clean_area 14851.48
2019-09-15 20:37:47 total_clean_time 255.69
2019-09-15 20:37:47 total_cleans 684
2019-09-15 20:04:45 volume 90
2019-09-15 20:04:41 wifi_auth_fail_count 0
2019-09-15 20:04:41 wifi_conn_fail_count 0
2019-09-15 20:04:41 wifi_conn_success_count 1
2019-09-15 20:04:41 wifi_dhcp_fail_count 0
2019-09-15 20:04:42 wifi_rssi -50
2019-09-15 20:04:41 wifi_state online
helper:
ConnectionState connected
cleanrecord 10
crypt Rijndael
delay 60
dev 05c2
historydays 10
id 80d5
ip 192.168.0.217
last_read 1568573147
packetid 6266
port 54321
sequence 0
timer1 1535037722033
timer1_cron 2211**1,2,3,4,5
timers 1
token xxx
zone_names kueche,wohnzimmer,flur
day:
history:
packet:
1007 get_status
1703 get_status
1865 get_status
192 get_status
2058 get_status
2253 get_status
24 get_status
2415 get_status
2416 get_status
2572 get_status
2718 get_status
2962 get_status
2976 get_status
3303 get_status
3324 get_status
3326 get_status
3339 get_status
3498 get_status
38 get_status
3895 get_status
394 get_status
4218 get_status
4738 get_status
4986 get_status
5280 get_status
5488 get_status
5652 get_status
6004 get_status
6164 get_status
zones:
flur [24431,21394,28231,24544,1],[22455,21419,25005,23769,1]
kueche [22804,25820,26204,27070,1],[22831,25557,26081,26057,1],[24769,25041,26069,25541,1]
wohnzimmer [26387,24638,31887,27688,1],[28370,22389,31770,24739,1]
Attributes:
alexaName Ferdinand
event-on-change-reading .*
genericDeviceType switch
homebridgeMapping On=cmdOn:start,cmdOff:charge
intervalData 60
room Saugroboter
sortby 1
stateFormat state
subType VacuumCleaner
userReadings letzteReinigung {ReadingsVal("Ferdinand","history_0","")=~ m/\b\d{4}\W\d{2}\W\d{2}\s\d{2}\W\d{2}\W\d{2}\b/;;;; return $&;;;;}
zone_names kueche:[22804,25820,26204,27070,1],[22831,25557,26081,26057,1],[24769,25041,26069,25541,1] wohnzimmer:[26387,24638,31887,27688,1],[28370,22389,31770,24739,1] flur:[24431,21394,28231,24544,1],[22455,21419,25005,23769,1]7:34] [FHEM] executing: http://127.0.0.1:8083/fhem3?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
*** FHEM: connected
[2019-9-15 20:47:34] [FHEM] got: 7 results
[2019-9-15 20:47:34] [FHEM] Ferdinand is switch
[2019-9-15 20:47:34] [FHEM] Ferdinand has
[2019-9-15 20:47:34] [FHEM] Custom Volume [volume;cached]
[2019-9-15 20:47:34] [FHEM] StatusLowBattery [battery]
[2019-9-15 20:47:34] [FHEM] On [cmdOff.charge;undefined,undefined]
2019-09-15 20:47:34 caching: Ferdinand-volume: 90
[2019-9-15 20:47:34] [FHEM] caching: Custom Volume: 90 (as number; from '90')
2019-09-15 20:47:34 caching: Ferdinand-battery: ok
[2019-9-15 20:47:34] [FHEM] query: On for cmdOff-charge
[2019-9-15 20:47:34] [FHEM] not cached
[2019-9-15 20:47:34] [FHEM] executing: http://127.0.0.1:8083/fhem3?cmd=%7BReadingsVal(%22cmdOff%22%2C%22charge%22%2C%22%22)%7D&XHR=1
[2019-9-15 20:47:34] [FHEM] Kueche_Rollo is light
[2019-9-15 20:47:34] [FHEM] Kueche_Rollo has
[2019-9-15 20:47:34] [FHEM] PositionState [motor]
[2019-9-15 20:47:34] [FHEM] CurrentPosition [pct]
[2019-9-15 20:47:34] [FHEM] TargetPosition [pct]
2019-09-15 20:47:34 caching: Kueche_Rollo-motor: stop:off
2019-09-15 20:47:34 caching: Kueche_Rollo-pct: 0
[2019-9-15 20:47:34] [FHEM] Licht_Wohnzimmer is switch
[2019-9-15 20:47:34] [FHEM] Licht_Wohnzimmer has
[2019-9-15 20:47:34] [FHEM] On [state;on,off]
2019-09-15 20:47:34 caching: Licht_Wohnzimmer-state: on
[2019-9-15 20:47:34] [FHEM] Markise is light
[2019-9-15 20:47:34] [FHEM] Markise has
[2019-9-15 20:47:34] [FHEM] PositionState [motor]
[2019-9-15 20:47:34] [FHEM] CurrentPosition [pct]
[2019-9-15 20:47:34] [FHEM] TargetPosition [pct]
2019-09-15 20:47:34 caching: Markise-motor: stop:1
2019-09-15 20:47:34 caching: Markise-pct: 1
[2019-9-15 20:47:34] [FHEM] Sonoff_Aquarium is light
[2019-9-15 20:47:34] [FHEM] Sonoff_Aquarium has
[2019-9-15 20:47:34] [FHEM] Sonoff_Flur_Licht is light
[2019-9-15 20:47:34] [FHEM] Sonoff_Flur_Licht has
[2019-9-15 20:47:34] [FHEM] Sonoff_Spielzimmerlicht is light
[2019-9-15 20:47:34] [FHEM] Sonoff_Spielzimmerlicht has
Zitat von: MadMax-FHEM am 15 September 2019, 19:55:22
Wenn du das homebridgeMapping beim Ferdinand setzt und auch Ferdinand mit entsprechenden Attributen z.B. genericDeviceType switch bzw. auf jeden Fall: alexaName=Ferdinand (oder was halt immer) damit eben Ferdinand auch "gefunden" werden kann versehen hast...
...dann sollte eben das entsprechend gemappte Kommando ja bei Ferdinand (dort wo das "on" ankommt und dann dank Mapping auf start bzw. off auf charge gemapped wird/wurde) landen...
So zumindest die Theorie...
Poste doch mal ein list von Ferdinand und Auszüge aus dem alexa-fhem Log (NICHT fhem Log!) beim Starten von alexa-fhem...
...also dort wo dann Ferdinand gefunden werden sollte...
EDIT: das mit Flurreinigung ist eine Routine!? Welches Gerät wird denn am Ende der Routine geschalten? Da muss natürlich dann Ferdinand geschalten werden (also das per alexa-fhem erkannte Gerät! / nicht das evtl. noch aus der ha-bridge "zur Verfügung gestellte" Gerät...)
EDIT2: ganz grob: "Alexa schalte XY ein" -> "on" für Gerät XY kommt zu alexa-fhem und ohne homebridgeMapping geht das "on" dann direkt zum fhem-Device XY / mit homebridgeMapping eben das entspr. gemappte Kommando (start, charge, ...)... Bei Verwendung einer Routine kommt eben eine "Indirektion" hinzu: "Alexa, starte Irgendwas" am Ende der Routine soll dann Gerät XY eingeschaltet werden ab hier siehe vorher... ;)
Gruß, Joachim
Zitat von: hene42 am 16 September 2019, 10:23:31
ein Hallo an alle,
ich hoffe ich darf das hier mal Fragen um nicht extra einen neuen Eintrag aufzumachen....
Bis gestern lief bei mir alles Super, dann habe ich den Entschluss getroffen meine Alexa ein wenig aufzuräumen und habe dabei auch Fhem Connect gelöscht.
Jetzt habe ich alles (Skills) wieder eingespielt und alles geht, nur Fhem Connect findet keine Geräte mehr.
Der Skill lässt sich super installieren und auch aktivieren, findet jedoch keine Geräte. Auch ein extra neu angelegter Dummy Schalter wird nicht gefunden.
Hat eventuell jemand eine Idee wo der Fehler liegen könnte? Wenn weitere Infos benötigt werden bitte einfach fragen.
Bilder habe ich mal angehangen...
Danke
Henri
[2019-9-16 05:50:36] Reading alexaFHEM.ProxyConnection set to running;; stderr=Timeout, server fhem-va.fhem.de not responding.
[2019-9-16 05:50:36] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20stderr%3DTimeout%2C%20server%20fhem-va.fhem.de%20not%20responding.%20%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_197632157904202&XHR=1
[2019-9-16 05:50:36] *** SSH: stderr: Timeout, server fhem-va.fhem.de not responding.
[2019-9-16 05:50:36] SSH: exited with 255 - will restart in 125.97842139509113 seconds
[2019-9-16 05:50:36] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with Timeout, server fhem-va.fhem.de not responding. , ssh will restart at 05:52:42
[2019-9-16 05:50:36] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%3B%20Terminated%20with%20Timeout%2C%20server%20fhem-va.fhem.de%20not%20responding.%20%20%2C%20ssh%20will%20restart%20at%2005%3A52%3A42%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_197632157904202&XHR=1
2019-09-16 05:52:40 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 22.1
[2019-9-16 05:52:40] [FHEM] caching: CurrentTemperature: 22.1 (as number; from '22.1')
[2019-9-16 05:52:42] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2019-9-16 05:52:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_197632157904202&XHR=1
[2019-9-16 05:52:42] Starting SSH with -R 1234:127.0.0.1:32951 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2019-9-16 05:52:43] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2019-9-16 05:52:43] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_197632157904202&XHR=1
[2019-9-16 05:52:43] *** SSH: proxy connection established
[2019-9-16 05:52:43] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
2019-09-16 05:54:57 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 22.0
[2019-9-16 05:54:57] [FHEM] caching: CurrentTemperature: 22 (as number; from '22.0')
2019-09-16 05:55:06 caching: SD_WS37_TH_1-humidity: 67
[2019-9-16 05:55:06] [FHEM] caching: CurrentRelativeHumidity: 67 (as number; from '67')
2019-09-16 06:00:44 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 06:00:44] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 06:01:45 caching: SD_WS37_TH_1-temperature: 16.7
[2019-9-16 06:01:45] [FHEM] caching: CurrentTemperature: 16.7 (as number; from '16.7')
2019-09-16 06:04:51 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 22.1
[2019-9-16 06:04:51] [FHEM] caching: CurrentTemperature: 22.1 (as number; from '22.1')
2019-09-16 06:06:30 caching: SD_WS37_TH_1-humidity: 68
[2019-9-16 06:06:30] [FHEM] caching: CurrentRelativeHumidity: 68 (as number; from '68')
2019-09-16 06:06:59 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 22.0
[2019-9-16 06:06:59] [FHEM] caching: CurrentTemperature: 22 (as number; from '22.0')
2019-09-16 06:07:27 caching: SD_WS37_TH_1-temperature: 16.6
[2019-9-16 06:07:27] [FHEM] caching: CurrentTemperature: 16.6 (as number; from '16.6')
2019-09-16 06:10:09 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 06:10:09] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 06:12:10 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 06:12:10] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 06:12:12 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 06:12:12] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 06:13:09 caching: SD_WS37_TH_1-temperature: 16.6
[2019-9-16 06:13:09] [FHEM] caching: CurrentTemperature: 16.6 (as number; from '16.6')
2019-09-16 06:21:25 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 06:21:25] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 06:25:30 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 06:25:30] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 06:29:18 caching: SD_WS37_TH_1-temperature: 16.6
[2019-9-16 06:29:18] [FHEM] caching: CurrentTemperature: 16.6 (as number; from '16.6')
2019-09-16 06:31:35 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 06:31:35] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 06:33:02 caching: SD_WS37_TH_2-temperature: 23.3
[2019-9-16 06:33:02] [FHEM] caching: CurrentTemperature: 23.3 (as number; from '23.3')
2019-09-16 06:36:45 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 06:36:45] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 06:38:48 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 06:38:48] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 06:44:30 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 06:44:30] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 06:47:05 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 06:47:05] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 06:47:21 caching: SD_WS37_TH_1-humidity: 68
[2019-9-16 06:47:21] [FHEM] caching: CurrentRelativeHumidity: 68 (as number; from '68')
2019-09-16 06:54:00 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 06:54:00] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 06:56:29 caching: SD_WS37_TH_2-temperature: 23.2
[2019-9-16 06:56:29] [FHEM] caching: CurrentTemperature: 23.2 (as number; from '23.2')
2019-09-16 07:00:39 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 07:00:39] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 07:07:39 caching: SD_WS37_TH_2-temperature: 23.3
[2019-9-16 07:07:39] [FHEM] caching: CurrentTemperature: 23.3 (as number; from '23.3')
2019-09-16 07:08:46 caching: SD_WS37_TH_2-temperature: 23.2
[2019-9-16 07:08:46] [FHEM] caching: CurrentTemperature: 23.2 (as number; from '23.2')
2019-09-16 07:13:00 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 07:13:00] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 07:13:57 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 07:13:57] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 07:17:45 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 07:17:45] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 07:18:36 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 07:18:36] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 07:18:42 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 07:18:42] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 07:18:49 caching: SD_WS37_TH_2-temperature: 23.3
[2019-9-16 07:18:49] [FHEM] caching: CurrentTemperature: 23.3 (as number; from '23.3')
2019-09-16 07:19:56 caching: SD_WS37_TH_2-temperature: 23.2
[2019-9-16 07:19:56] [FHEM] caching: CurrentTemperature: 23.2 (as number; from '23.2')
2019-09-16 07:21:03 caching: SD_WS37_TH_2-temperature: 23.3
[2019-9-16 07:21:03] [FHEM] caching: CurrentTemperature: 23.3 (as number; from '23.3')
2019-09-16 07:21:33 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 07:21:33] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 07:21:36 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 07:21:36] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 07:22:10 caching: SD_WS37_TH_2-temperature: 23.2
[2019-9-16 07:22:10] [FHEM] caching: CurrentTemperature: 23.2 (as number; from '23.2')
2019-09-16 07:25:21 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 07:25:21] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 07:25:31 caching: SD_WS37_TH_2-temperature: 23.3
[2019-9-16 07:25:31] [FHEM] caching: CurrentTemperature: 23.3 (as number; from '23.3')
2019-09-16 07:28:12 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 07:28:12] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 07:32:57 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 07:32:57] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 07:35:48 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 07:35:48] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 07:36:42 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 07:36:42] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 07:36:45 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 07:36:45] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 07:37:42 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 07:37:42] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 07:38:39 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 07:38:39] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 07:38:46 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 07:38:46] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 07:39:05 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 07:39:05] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 07:41:30 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 07:41:30] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 07:43:56 caching: FL_Temperatursensor_1-temperature: 20.18
[2019-9-16 07:43:56] [FHEM] caching: CurrentTemperature: 20.18 (as number; from '20.18')
2019-09-16 07:49:06 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 07:49:06] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 07:54:16 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 07:54:16] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 07:56:42 caching: SD_WS37_TH_1-temperature: 16.3
[2019-9-16 07:56:42] [FHEM] caching: CurrentTemperature: 16.3 (as number; from '16.3')
2019-09-16 08:00:08 caching: SD_WS37_TH_2-humidity: 50
[2019-9-16 08:00:08] [FHEM] caching: CurrentRelativeHumidity: 50 (as number; from '50')
2019-09-16 08:00:30 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:00:30] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:02:24 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 08:02:24] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 08:02:24 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 08:02:24] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 08:03:21 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:03:21] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:04:18 caching: SD_WS37_TH_1-temperature: 16.3
[2019-9-16 08:04:18] [FHEM] caching: CurrentTemperature: 16.3 (as number; from '16.3')
2019-09-16 08:06:12 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 08:06:12] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 08:07:09 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:07:09] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:09:14 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 08:09:14] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 08:15:42 caching: SD_WS37_TH_1-temperature: 16.2
[2019-9-16 08:15:42] [FHEM] caching: CurrentTemperature: 16.2 (as number; from '16.2')
2019-09-16 08:17:36 caching: SD_WS37_TH_1-humidity: 72
[2019-9-16 08:17:36] [FHEM] caching: CurrentRelativeHumidity: 72 (as number; from '72')
2019-09-16 08:18:33 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:18:33] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:19:30 caching: SD_WS37_TH_1-humidity: 72
[2019-9-16 08:19:30] [FHEM] caching: CurrentRelativeHumidity: 72 (as number; from '72')
2019-09-16 08:20:06 caching: FL_Temperatursensor_1-temperature: 19.76
[2019-9-16 08:20:06] [FHEM] caching: CurrentTemperature: 19.76 (as number; from '19.76')
2019-09-16 08:21:24 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:21:24] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:23:18 caching: SD_WS37_TH_1-humidity: 72
[2019-9-16 08:23:18] [FHEM] caching: CurrentRelativeHumidity: 72 (as number; from '72')
2019-09-16 08:25:12 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:25:12] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:25:16 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 08:25:16] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 08:27:06 caching: SD_WS37_TH_1-temperature: 16.3
[2019-9-16 08:27:06] [FHEM] caching: CurrentTemperature: 16.3 (as number; from '16.3')
2019-09-16 08:32:48 caching: SD_WS37_TH_1-temperature: 16.4
[2019-9-16 08:32:48] [FHEM] caching: CurrentTemperature: 16.4 (as number; from '16.4')
2019-09-16 08:35:36 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 08:35:36] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 08:36:58 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 08:36:58] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 08:45:54 caching: FL_Bewegungsmelder_AnAus-state: off
[2019-9-16 08:45:54] [FHEM] caching: On: 0 (as number; from 'off')
2019-09-16 08:48:57 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 08:48:57] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 08:51:30 caching: SD_WS37_TH_2-humidity: 49
[2019-9-16 08:51:30] [FHEM] caching: CurrentRelativeHumidity: 49 (as number; from '49')
2019-09-16 08:54:39 caching: SD_WS37_TH_1-humidity: 72
[2019-9-16 08:54:39] [FHEM] caching: CurrentRelativeHumidity: 72 (as number; from '72')
2019-09-16 08:55:10 caching: Heizung_Bad_Clima-measured-temp: 22.6
[2019-9-16 08:55:10] [FHEM] caching: CurrentTemperature: 22.6 (as number; from '22.6')
2019-09-16 08:55:36 caching: SD_WS37_TH_1-humidity: 71
[2019-9-16 08:55:36] [FHEM] caching: CurrentRelativeHumidity: 71 (as number; from '71')
2019-09-16 08:58:37 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 21.9
[2019-9-16 08:58:37] [FHEM] caching: CurrentTemperature: 21.9 (as number; from '21.9')
2019-09-16 08:59:24 caching: SD_WS37_TH_1-temperature: 16.6
[2019-9-16 08:59:24] [FHEM] caching: CurrentTemperature: 16.6 (as number; from '16.6')
2019-09-16 09:00:21 caching: SD_WS37_TH_1-temperature: 16.5
[2019-9-16 09:00:21] [FHEM] caching: CurrentTemperature: 16.5 (as number; from '16.5')
2019-09-16 09:00:21 caching: SD_WS37_TH_1-humidity: 70
[2019-9-16 09:00:21] [FHEM] caching: CurrentRelativeHumidity: 70 (as number; from '70')
2019-09-16 09:01:00 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 21.7
[2019-9-16 09:01:00] [FHEM] caching: CurrentTemperature: 21.7 (as number; from '21.7')
2019-09-16 09:01:18 caching: SD_WS37_TH_1-temperature: 16.6
[2019-9-16 09:01:18] [FHEM] caching: CurrentTemperature: 16.6 (as number; from '16.6')
2019-09-16 09:01:33 caching: SD_WS37_TH_2-temperature: 23.2
[2019-9-16 09:01:33] [FHEM] caching: CurrentTemperature: 23.2 (as number; from '23.2')
2019-09-16 09:03:08 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 21.5
[2019-9-16 09:03:08] [FHEM] caching: CurrentTemperature: 21.5 (as number; from '21.5')
2019-09-16 09:04:37 caching: FL_Temperatursensor_1-temperature: 20.04
[2019-9-16 09:04:37] [FHEM] caching: CurrentTemperature: 20.04 (as number; from '20.04')
2019-09-16 09:04:54 caching: SD_WS37_TH_2-humidity: 48
[2019-9-16 09:04:54] [FHEM] caching: CurrentRelativeHumidity: 48 (as number; from '48')
2019-09-16 09:05:06 caching: SD_WS37_TH_1-temperature: 16.7
[2019-9-16 09:05:06] [FHEM] caching: CurrentTemperature: 16.7 (as number; from '16.7')
2019-09-16 09:05:27 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 09:05:27] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 09:06:06 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 21.1
[2019-9-16 09:06:06] [FHEM] caching: CurrentTemperature: 21.1 (as number; from '21.1')
2019-09-16 09:08:50 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 21.0
[2019-9-16 09:08:50] [FHEM] caching: CurrentTemperature: 21 (as number; from '21.0')
2019-09-16 09:10:14 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 09:10:14] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 09:11:19 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.8
[2019-9-16 09:11:19] [FHEM] caching: CurrentTemperature: 20.8 (as number; from '20.8')
2019-09-16 09:13:33 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.6
[2019-9-16 09:13:33] [FHEM] caching: CurrentTemperature: 20.6 (as number; from '20.6')
2019-09-16 09:13:50 caching: SD_WS37_TH_2-temperature: 23.1
[2019-9-16 09:13:50] [FHEM] caching: CurrentTemperature: 23.1 (as number; from '23.1')
2019-09-16 09:14:57 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 09:14:57] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 09:15:06 caching: Heizung_Bad_Clima-measured-temp: 22.5
[2019-9-16 09:15:06] [FHEM] caching: CurrentTemperature: 22.5 (as number; from '22.5')
2019-09-16 09:15:33 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.5
[2019-9-16 09:15:33] [FHEM] caching: CurrentTemperature: 20.5 (as number; from '20.5')
2019-09-16 09:17:27 caching: SD_WS37_TH_1-temperature: 16.8
[2019-9-16 09:17:27] [FHEM] caching: CurrentTemperature: 16.8 (as number; from '16.8')
2019-09-16 09:17:43 caching: Heizung_Bad_Clima-measured-temp: 22.4
[2019-9-16 09:17:43] [FHEM] caching: CurrentTemperature: 22.4 (as number; from '22.4')
2019-09-16 09:18:04 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.4
[2019-9-16 09:18:04] [FHEM] caching: CurrentTemperature: 20.4 (as number; from '20.4')
2019-09-16 09:20:19 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.3
[2019-9-16 09:20:19] [FHEM] caching: CurrentTemperature: 20.3 (as number; from '20.3')
2019-09-16 09:22:21 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 20.2
[2019-9-16 09:22:21] [FHEM] caching: CurrentTemperature: 20.2 (as number; from '20.2')
2019-09-16 09:23:09 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 09:23:09] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 09:25:12 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.9
[2019-9-16 09:25:12] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 09:25:17 caching: FL_Temperatursensor_1-temperature: 19.76
[2019-9-16 09:25:17] [FHEM] caching: CurrentTemperature: 19.76 (as number; from '19.76')
2019-09-16 09:27:48 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.8
[2019-9-16 09:27:48] [FHEM] caching: CurrentTemperature: 19.8 (as number; from '19.8')
2019-09-16 09:30:10 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.7
[2019-9-16 09:30:10] [FHEM] caching: CurrentTemperature: 19.7 (as number; from '19.7')
2019-09-16 09:30:27 caching: FL_Temperatursensor_1-temperature: 19.62
[2019-9-16 09:30:27] [FHEM] caching: CurrentTemperature: 19.62 (as number; from '19.62')
2019-09-16 09:30:35 caching: SD_WS37_TH_2-temperature: 23.0
[2019-9-16 09:30:35] [FHEM] caching: CurrentTemperature: 23 (as number; from '23.0')
2019-09-16 09:32:18 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.6
[2019-9-16 09:32:18] [FHEM] caching: CurrentTemperature: 19.6 (as number; from '19.6')
2019-09-16 09:35:03 caching: SD_WS37_TH_2-temperature: 22.9
[2019-9-16 09:35:03] [FHEM] caching: CurrentTemperature: 22.9 (as number; from '22.9')
2019-09-16 09:35:15 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.4
[2019-9-16 09:35:15] [FHEM] caching: CurrentTemperature: 19.4 (as number; from '19.4')
2019-09-16 09:35:37 caching: FL_Temperatursensor_1-temperature: 19.76
[2019-9-16 09:35:37] [FHEM] caching: CurrentTemperature: 19.76 (as number; from '19.76')
2019-09-16 09:37:58 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.3
[2019-9-16 09:37:58] [FHEM] caching: CurrentTemperature: 19.3 (as number; from '19.3')
2019-09-16 09:38:29 caching: Heizung_Bad_Clima-measured-temp: 22.3
[2019-9-16 09:38:29] [FHEM] caching: CurrentTemperature: 22.3 (as number; from '22.3')
2019-09-16 09:40:47 caching: FL_Temperatursensor_1-temperature: 19.9
[2019-9-16 09:40:47] [FHEM] caching: CurrentTemperature: 19.9 (as number; from '19.9')
2019-09-16 09:41:04 caching: Heizung_Bad_Clima-measured-temp: 22.1
[2019-9-16 09:41:04] [FHEM] caching: CurrentTemperature: 22.1 (as number; from '22.1')
2019-09-16 09:45:43 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.1
[2019-9-16 09:45:43] [FHEM] caching: CurrentTemperature: 19.1 (as number; from '19.1')
2019-09-16 09:48:26 caching: Heizung_Bad_Clima-measured-temp: 22.0
[2019-9-16 09:48:26] [FHEM] caching: CurrentTemperature: 22 (as number; from '22.0')
2019-09-16 09:48:32 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.2
[2019-9-16 09:48:32] [FHEM] caching: CurrentTemperature: 19.2 (as number; from '19.2')
2019-09-16 09:48:48 caching: SD_WS37_TH_1-temperature: 16.9
[2019-9-16 09:48:48] [FHEM] caching: CurrentTemperature: 16.9 (as number; from '16.9')
2019-09-16 09:49:45 caching: SD_WS37_TH_1-humidity: 68
[2019-9-16 09:49:45] [FHEM] caching: CurrentRelativeHumidity: 68 (as number; from '68')
2019-09-16 09:50:41 caching: SD_WS37_TH_2-temperature: 22.8
[2019-9-16 09:50:41] [FHEM] caching: CurrentTemperature: 22.8 (as number; from '22.8')
2019-09-16 09:50:42 caching: SD_WS37_TH_1-temperature: 16.8
[2019-9-16 09:50:42] [FHEM] caching: CurrentTemperature: 16.8 (as number; from '16.8')
2019-09-16 09:51:07 caching: Heizung_Bad_Clima-measured-temp: 21.9
[2019-9-16 09:51:07] [FHEM] caching: CurrentTemperature: 21.9 (as number; from '21.9')
2019-09-16 09:53:34 caching: Heizung_Bad_Clima-measured-temp: 21.8
[2019-9-16 09:53:34] [FHEM] caching: CurrentTemperature: 21.8 (as number; from '21.8')
2019-09-16 09:55:33 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.1
[2019-9-16 09:55:33] [FHEM] caching: CurrentTemperature: 19.1 (as number; from '19.1')
2019-09-16 09:57:58 caching: HomeMatic_Steckdose-state: on
[2019-9-16 09:57:58] [FHEM] caching: On: 1 (as number; from 'on')
2019-09-16 09:58:12 caching: WZ_Sat_Receiver-power: on
[2019-9-16 09:58:12] [FHEM] WZ_Sat_Receiver-power not a number: on
2019-09-16 09:58:12 caching: WZ_Sat_Receiver-state: on
[2019-9-16 09:58:12] [FHEM] caching: On: 1 (as number; from 'on')
2019-09-16 09:58:12 caching: WZ_Sat_Receiver-mute: off
[2019-9-16 09:58:12] [FHEM] caching: Mute: off (as string; from 'off')
2019-09-16 09:58:29 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 19.0
[2019-9-16 09:58:29] [FHEM] caching: CurrentTemperature: 19 (as number; from '19.0')
2019-09-16 10:01:10 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 18.9
[2019-9-16 10:01:10] [FHEM] caching: CurrentTemperature: 18.9 (as number; from '18.9')
2019-09-16 10:02:58 caching: SD_WS37_TH_2-temperature: 22.7
[2019-9-16 10:02:58] [FHEM] caching: CurrentTemperature: 22.7 (as number; from '22.7')
[2019-9-16 10:03:28] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.Discovery","name":"Discover","payloadVersion":"3","messageId":"60dff71b-39d6-4914-b882-a78b9326f927"},"payload":{"scope":{"type":"BearerToken","token":"5524C13-6626C74233AC6F5A"}}}}
[2019-9-16 10:03:28] found 14 device(s)
[2019-9-16 10:03:28] <<<< [ssh] {"event":{"header":{"namespace":"Alexa.Discovery","name":"Discover.Response","payloadVersion":"3","messageId":"1463785f-a14b-4f2f-9683-22be91eea6bc"},"payload":{"endpoints":[{"endpointId":"5d628ce8-f33f-f879-6087-c0b8eb80d71a7453","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"bewegung flur","description":"n: FL_Bewegungsmelder_AnAus, r: flur","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"FL_Bewegungsmelder_AnAus","fuuid":"5d628ce8-f33f-f879-6087-c0b8eb80d71a7453"}},{"endpointId":"00:17:88:01:03:28:74:f3-02-0402","manufacturerName":"FHEMHUEDevice","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"flur","description":"n: FL_Temperatursensor_1, r: 1000_flur,1010_flur_plot,9960_sensoren,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"FL_Temperatursensor_1","fuuid":"5c4e123f-f33f-f879-3f42-c9695d78ed211ef2"}},{"endpointId":"5c502d82-f33f-f879-a3a2-4f6f6aaf18899ed0","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"ladegeräte","description":"n: Gosund_001, r: googleassistant,8000_keller,8010_keller_plot,9300_schaltsteckdosen,mqtt2_device","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Gosund_001","fuuid":"5c502d82-f33f-f879-a3a2-4f6f6aaf18899ed0"}},{"endpointId":"CUL_HM_63896704","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-CC-RT-DN","version":"<unknown>","friendlyName":"bad","description":"n: Heizung_Bad_Clima, r: 6000_bad,6010_bad_plot,9000_heizung,9010_heizung_plot,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"}],"configuration":{"supportsScheduling":false},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"Heizung_Bad_Clima","fuuid":"5c845835-f33f-f879-f875-d4b8a8a82b89670d"}},{"endpointId":"CUL_HM_5F96ED04","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-CC-RT-DN","version":"<unknown>","friendlyName":"wohnzimmer","description":"n: Heizung_Wohnen_Balkon_Clima, r: 2000_wohnzimmer,2010_wohnzimmer_plot,9000_heizung,9010_heizung_plot,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"}],"configuration":{"supportsScheduling":false},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"Heizung_Wohnen_Balkon_Clima","fuuid":"5c84568c-f33f-f879-04d1-884f27e3a35b4c5d"}},{"endpointId":"OEQ0817521","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-LC-SW1-PL-DN-R1","version":"<unknown>","friendlyName":"notebook steckdosen","description":"n: HomeMatic_Steckdose, r: 2000_wohnzimmer,9300_schaltsteckdosen,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"HomeMatic_Steckdose","fuuid":"5c8511ba-f33f-f879-d1e3-8c762881a3ae5f94"}},{"endpointId":"5c4e26a7-f33f-f879-fb17-e005aace1f643f7b","manufacturerName":"FHEMWOL","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"server","description":"n: KL_Synology_WOL, r: 8000_keller,8010_keller_plot,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"KL_Synology_WOL","fuuid":"5c4e26a7-f33f-f879-fb17-e005aace1f643f7b"}},{"endpointId":"5d1d8aee-f33f-f879-c5d9-458fc6705f0919c4","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"arbeitsplatte","description":"n: MQTT2_McLighting01, r: 7000_küche,9150_mclighting,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.ColorController","version":"3","properties":{"supported":[{"name":"color"}],"proactivelyReported":false,"retrievable":false}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"MQTT2_McLighting01","fuuid":"5d1d8aee-f33f-f879-c5d9-458fc6705f0919c4"}},{"endpointId":"5c533aaf-f33f-f879-cae8-be54b1cda56ed9ba","manufacturerName":"FHEMSD_WS","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"balkon","description":"n: SD_WS37_TH_1, r: balkon","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"SD_WS37_TH_1","fuuid":"5c533aaf-f33f-f879-cae8-be54b1cda56ed9ba"}},{"endpointId":"5c533b44-f33f-f879-f677-a4c905ab5e236570","manufacturerName":"FHEMSD_WS","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"schlafzimmer","description":"n: SD_WS37_TH_2, r: 3000_schlafzimmer,3010_schlafzimmer_plot,9960_sensoren","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"SD_WS37_TH_2","fuuid":"5c533b44-f33f-f879-f677-a4c905ab5e236570"}},{"endpointId":"5d4ae259-f33f-f879-ab94-5e0cb84a2af7a78c","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"bewegung schlafzimmer","description":"n: SZ_Bewegungsmelder, r: 3000_schlafzimmer,9905_logik,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"SZ_Bewegungsmelder","fuuid":"5d4ae259-f33f-f879-ab94-5e0cb84a2af7a78c"}},{"endpointId":"5ce81d8e-f33f-f879-2041-1d868824a9649d0d","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"kommode","description":"n: SonOff_001, r: 3000_schlafzimmer,3010_schlafzimmer_plot,9300_schaltsteckdosen,googleassistant,mqtt2_device","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"SonOff_001","fuuid":"5ce81d8e-f33f-f879-2041-1d868824a9649d0d"}},{"endpointId":"5c52430b-f33f-f879-bb53-bbed75bf3e8a2c85","manufacturerName":"FHEMENIGMA2","modelName":"FHEMQuad Plus","version":"<unknown>","friendlyName":"sat","description":"n: WZ_Sat_Receiver, r: wohnzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.Speaker","version":"3","properties":{"supported":[{"name":"mute"},{"name":"volume"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SPEAKER"],"cookie":{"device":"WZ_Sat_Receiver","fuuid":"5c52430b-f33f-f879-bb53-bbed75bf3e8a2c85"}},{"endpointId":"5d060471-f33f-f879-815f-86d2b2e712587b46","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"dummy","description":"n: testdummy, r: dachboden","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"testdummy","fuuid":"5d060471-f33f-f879-815f-86d2b2e712587b46"}}]}}}
2019-09-16 10:03:36 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 18.8
[2019-9-16 10:03:36] [FHEM] caching: CurrentTemperature: 18.8 (as number; from '18.8')
2019-09-16 10:05:48 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 18.7
[2019-9-16 10:05:48] [FHEM] caching: CurrentTemperature: 18.7 (as number; from '18.7')
2019-09-16 10:06:27 caching: Heizung_Bad_Clima-measured-temp: 21.9
[2019-9-16 10:06:27] [FHEM] caching: CurrentTemperature: 21.9 (as number; from '21.9')
2019-09-16 10:07:26 caching: SD_WS37_TH_2-humidity: 47
[2019-9-16 10:07:26] [FHEM] caching: CurrentRelativeHumidity: 47 (as number; from '47')
2019-09-16 10:07:55 caching: WZ_Sat_Receiver-power: off
[2019-9-16 10:07:55] [FHEM] WZ_Sat_Receiver-power not a number: off
2019-09-16 10:07:55 caching: WZ_Sat_Receiver-state: absent
[2019-9-16 10:07:55] [FHEM] caching: On: 1 (as number; from 'absent')
2019-09-16 10:07:55 caching: WZ_Sat_Receiver-mute: -
[2019-9-16 10:07:55] [FHEM] caching: Mute: - (as string; from '-')
2019-09-16 10:08:12 caching: WZ_Sat_Receiver-power: on
[2019-9-16 10:08:12] [FHEM] WZ_Sat_Receiver-power not a number: on
2019-09-16 10:08:12 caching: WZ_Sat_Receiver-state: on
[2019-9-16 10:08:12] [FHEM] caching: On: 1 (as number; from 'on')
2019-09-16 10:08:13 caching: WZ_Sat_Receiver-mute: off
[2019-9-16 10:08:13] [FHEM] caching: Mute: off (as string; from 'off')
2019-09-16 10:08:50 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 18.5
[2019-9-16 10:08:50] [FHEM] caching: CurrentTemperature: 18.5 (as number; from '18.5')
2019-09-16 10:11:36 caching: SD_WS37_TH_1-humidity: 69
[2019-9-16 10:11:36] [FHEM] caching: CurrentRelativeHumidity: 69 (as number; from '69')
2019-09-16 10:11:37 caching: Heizung_Wohnen_Balkon_Clima-measured-temp: 18.4
[2019-9-16 10:11:37] [FHEM] caching: CurrentTemperature: 18.4 (as number; from '18.4')
2019-09-16 10:12:55 caching: WZ_Sat_Receiver-power: off
[2019-9-16 10:12:55] [FHEM] WZ_Sat_Receiver-power not a number: off
2019-09-16 10:12:55 caching: WZ_Sat_Receiver-state: absent
[2019-9-16 10:12:55] [FHEM] caching: On: 1 (as number; from 'absent')
2019-09-16 10:12:55 caching: WZ_Sat_Receiver-mute: -
[2019-9-16 10:12:55] [FHEM] caching: Mute: - (as string; from '-')
2019-09-16 10:13:12 caching: WZ_Sat_Receiver-power: on
[2019-9-16 10:13:12] [FHEM] WZ_Sat_Receiver-power not a number: on
2019-09-16 10:13:12 caching: WZ_Sat_Receiver-state: on
[2019-9-16 10:13:12] [FHEM] caching: On: 1 (as number; from 'on')
2019-09-16 10:13:13 caching: WZ_Sat_Receiver-mute: off
[2019-9-16 10:13:13] [FHEM] caching: Mute: off (as string; from 'off')
[2019-9-16 10:13:49] >>>> [ssh] {"directive":{"header":{"namespace":"Alexa.Discovery","name":"Discover","payloadVersion":"3","messageId":"0815"},"payload":{"scope": {"type":"BearerToken","token":"5524C13-6626C74233AC6F5A"}}}}
[2019-9-16 10:13:49] found 14 device(s)
[2019-9-16 10:13:49] <<<< [ssh] {"event":{"header":{"namespace":"Alexa.Discovery","name":"Discover.Response","payloadVersion":"3","messageId":"507fa4b8-a13f-464d-8ddb-fcfa0b76b2ef"},"payload":{"endpoints":[{"endpointId":"5d628ce8-f33f-f879-6087-c0b8eb80d71a7453","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"bewegung flur","description":"n: FL_Bewegungsmelder_AnAus, r: flur","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"FL_Bewegungsmelder_AnAus","fuuid":"5d628ce8-f33f-f879-6087-c0b8eb80d71a7453"}},{"endpointId":"00:17:88:01:03:28:74:f3-02-0402","manufacturerName":"FHEMHUEDevice","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"flur","description":"n: FL_Temperatursensor_1, r: 1000_flur,1010_flur_plot,9960_sensoren,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"FL_Temperatursensor_1","fuuid":"5c4e123f-f33f-f879-3f42-c9695d78ed211ef2"}},{"endpointId":"5c502d82-f33f-f879-a3a2-4f6f6aaf18899ed0","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"ladegeräte","description":"n: Gosund_001, r: googleassistant,8000_keller,8010_keller_plot,9300_schaltsteckdosen,mqtt2_device","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"Gosund_001","fuuid":"5c502d82-f33f-f879-a3a2-4f6f6aaf18899ed0"}},{"endpointId":"CUL_HM_63896704","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-CC-RT-DN","version":"<unknown>","friendlyName":"bad","description":"n: Heizung_Bad_Clima, r: 6000_bad,6010_bad_plot,9000_heizung,9010_heizung_plot,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"}],"configuration":{"supportsScheduling":false},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"Heizung_Bad_Clima","fuuid":"5c845835-f33f-f879-f875-d4b8a8a82b89670d"}},{"endpointId":"CUL_HM_5F96ED04","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-CC-RT-DN","version":"<unknown>","friendlyName":"wohnzimmer","description":"n: Heizung_Wohnen_Balkon_Clima, r: 2000_wohnzimmer,2010_wohnzimmer_plot,9000_heizung,9010_heizung_plot,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.ThermostatController","version":"3","properties":{"supported":[{"name":"targetSetpoint"}],"configuration":{"supportsScheduling":false},"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["THERMOSTAT"],"cookie":{"device":"Heizung_Wohnen_Balkon_Clima","fuuid":"5c84568c-f33f-f879-04d1-884f27e3a35b4c5d"}},{"endpointId":"OEQ0817521","manufacturerName":"FHEMCUL_HM","modelName":"FHEMHM-LC-SW1-PL-DN-R1","version":"<unknown>","friendlyName":"notebook steckdosen","description":"n: HomeMatic_Steckdose, r: 2000_wohnzimmer,9300_schaltsteckdosen,9972_homematic,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"HomeMatic_Steckdose","fuuid":"5c8511ba-f33f-f879-d1e3-8c762881a3ae5f94"}},{"endpointId":"5c4e26a7-f33f-f879-fb17-e005aace1f643f7b","manufacturerName":"FHEMWOL","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"server","description":"n: KL_Synology_WOL, r: 8000_keller,8010_keller_plot,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"KL_Synology_WOL","fuuid":"5c4e26a7-f33f-f879-fb17-e005aace1f643f7b"}},{"endpointId":"5d1d8aee-f33f-f879-c5d9-458fc6705f0919c4","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"arbeitsplatte","description":"n: MQTT2_McLighting01, r: 7000_küche,9150_mclighting,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.BrightnessController","version":"3","properties":{"supported":[{"name":"brightness"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.ColorController","version":"3","properties":{"supported":[{"name":"color"}],"proactivelyReported":false,"retrievable":false}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"MQTT2_McLighting01","fuuid":"5d1d8aee-f33f-f879-c5d9-458fc6705f0919c4"}},{"endpointId":"5c533aaf-f33f-f879-cae8-be54b1cda56ed9ba","manufacturerName":"FHEMSD_WS","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"balkon","description":"n: SD_WS37_TH_1, r: balkon","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"SD_WS37_TH_1","fuuid":"5c533aaf-f33f-f879-cae8-be54b1cda56ed9ba"}},{"endpointId":"5c533b44-f33f-f879-f677-a4c905ab5e236570","manufacturerName":"FHEMSD_WS","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"schlafzimmer","description":"n: SD_WS37_TH_2, r: 3000_schlafzimmer,3010_schlafzimmer_plot,9960_sensoren","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.TemperatureSensor","version":"3","properties":{"supported":[{"name":"temperature"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["TEMPERATURE_SENSOR"],"cookie":{"device":"SD_WS37_TH_2","fuuid":"5c533b44-f33f-f879-f677-a4c905ab5e236570"}},{"endpointId":"5d4ae259-f33f-f879-ab94-5e0cb84a2af7a78c","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"bewegung schlafzimmer","description":"n: SZ_Bewegungsmelder, r: 3000_schlafzimmer,9905_logik,googleassistant","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"SZ_Bewegungsmelder","fuuid":"5d4ae259-f33f-f879-ab94-5e0cb84a2af7a78c"}},{"endpointId":"5ce81d8e-f33f-f879-2041-1d868824a9649d0d","manufacturerName":"FHEMMQTT2_DEVICE","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"kommode","description":"n: SonOff_001, r: 3000_schlafzimmer,3010_schlafzimmer_plot,9300_schaltsteckdosen,googleassistant,mqtt2_device","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"SonOff_001","fuuid":"5ce81d8e-f33f-f879-2041-1d868824a9649d0d"}},{"endpointId":"5c52430b-f33f-f879-bb53-bbed75bf3e8a2c85","manufacturerName":"FHEMENIGMA2","modelName":"FHEMQuad Plus","version":"<unknown>","friendlyName":"sat","description":"n: WZ_Sat_Receiver, r: wohnzimmer","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.Speaker","version":"3","properties":{"supported":[{"name":"mute"},{"name":"volume"}],"proactivelyReported":false,"retrievable":true}},{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SPEAKER"],"cookie":{"device":"WZ_Sat_Receiver","fuuid":"5c52430b-f33f-f879-bb53-bbed75bf3e8a2c85"}},{"endpointId":"5d060471-f33f-f879-815f-86d2b2e712587b46","manufacturerName":"FHEMdummy","modelName":"FHEM<unknown>","version":"<unknown>","friendlyName":"dummy","description":"n: testdummy, r: dachboden","actions":[],"capabilities":[{"type":"AlexaInterface","interface":"Alexa.PowerController","version":"3","properties":{"supported":[{"name":"powerState"}],"proactivelyReported":false,"retrievable":true}}],"displayCategories":["SWITCH"],"cookie":{"device":"testdummy","fuuid":"5d060471-f33f-f879-815f-86d2b2e712587b46"}}]}}}
2019-09-16 10:14:04 caching: Heizung_Bad_Clima-measured-temp: 22.0
Zitatnrarchive im alexa device setzen.
2019.09.25 22:01:00 3: myalexa: using logfile: ./log/alexa-2019-09-25.log
2019.09.25 22:01:00 5: myalexa: read: /usr/local/lib/node_modules/alexa-fhem/lib/user.js:92
2019.09.25 22:01:00 5: myalexa: read: (async () => {
2019.09.25 22:01:00 5: myalexa: read: ^
2019.09.25 22:01:00 5: myalexa: read: SyntaxError: Unexpected token (
2019.09.25 22:01:00 5: myalexa: read: at Object.exports.runInThisContext (vm.js:78:16)
2019.09.25 22:01:00 5: myalexa: read: at Module._compile (module.js:543:28)
2019.09.25 22:01:00 5: myalexa: read: at Object.Module._extensions..js (module.js:580:10)
2019.09.25 22:01:00 5: myalexa: read: at Module.load (module.js:488:32)
2019.09.25 22:01:00 5: myalexa: read: at tryModuleLoad (module.js:447:12)
2019.09.25 22:01:00 5: myalexa: read: at Function.Module._load (module.js:439:3)
2019.09.25 22:01:00 5: myalexa: read: at Module.require (module.js:498:17)
2019.09.25 22:01:00 5: myalexa: read: at require (internal/module.js:20:19)
2019.09.25 22:01:00 5: myalexa: read: at Object.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:11:12)
2019.09.25 22:01:00 5: myalexa: read: at Module._compile (module.js:571:32)
2019.09.25 22:01:00 3: myalexa: read: end of file reached while sysread
2019.09.25 22:01:00 3: myalexa: stopped
[9/29/2019, 5:07:39 PM] [FHEM] HEOSPlayer376628887 is media
[9/29/2019, 5:07:39 PM] [FHEM] HEOSPlayer376628887 has
[9/29/2019, 5:07:39 PM] [FHEM] Custom Volume [volume;cached]
[9/29/2019, 5:07:39 PM] [FHEM] Mute [mute]
2019-09-29 17:07:39 caching: HEOSPlayer376628887-volume: 0
[9/29/2019, 5:07:39 PM] [FHEM] caching: Custom Volume: 0 (as number; from '0')
2019-09-29 17:07:39 caching: HEOSPlayer376628887-mute: offInternals:
DEF -376628887 IODev=HEOS_Master
FUUID 5c5bcb7f-f33f-b5ae-872d-7abee1a5e7c7a7e6
HEOS_Master_MSGCNT 1381
HEOS_Master_TIME 2019-09-29 17:15:06
IODev HEOS_Master
LASTInputDev HEOS_Master
MSGCNT 1381
NAME HEOSPlayer376628887
NR 497
PID -376628887
STATE on
TYPE HEOSPlayer
VERSION 1.0.4
READINGS:
2019-09-29 17:15:06 channel 3
2019-09-29 17:15:06 currentAlbum
2019-09-29 17:15:06 currentArtist
2019-09-29 17:15:06 currentImageUrl
2019-09-29 17:15:06 currentMedia station
2019-09-29 17:15:06 currentMid http://addrad.io/4WRFb3
2019-09-29 17:15:06 currentQid 1
2019-09-29 17:15:06 currentSid 3
2019-09-29 17:15:06 currentStation YOU FM - music like me
2019-09-29 17:15:06 currentTitle 128 kbps mp3
2019-09-14 14:13:07 error Unable to play media. Please try again later.
2019-09-27 13:29:51 ip-address 192.168.178.37
2019-09-27 13:29:51 lineout 0
2019-09-27 13:29:51 model HEOS 1
2019-09-29 17:07:47 mute off
2019-09-27 13:29:51 name Büro
2019-09-27 13:29:51 network wifi
2019-09-29 17:15:06 playStatus stop
2019-09-27 13:29:44 repeat off
2019-09-27 13:29:44 shuffle off
2019-09-27 13:29:51 state on
2019-09-27 13:29:51 version 1.520.200
2019-09-29 17:07:47 volume 12
2019-09-27 13:29:26 volumeDown 5
2019-09-27 13:29:26 volumeUp 5
helper:
aux:
HASH(0x41ab4e0)
queue:
Attributes:
IODev HEOS_Master
alexaName heos
alias Büro
channelring 1
devStateIcon on:10px-kreis-gruen off:10px-kreis-rot
genericDeviceType media
mute2play 1
room HEOSZitat von: MadMax-FHEM am 29 September 2019, 18:23:38ohne homebridgemapping kommt nur "das device unterstützt das nicht". Joachim, würdest Du mir mal das homebridgemapping für play/stop skizzieren? Ich hab schon zig Varianten probiert, verstehe aber die Syntax nicht wirklich, mir fehlen einfach die Zusammenhänge mit den characteristics
Was gehen sollte (mittels homebridgeMapping bzw. teilweise eigentlich schon ohne!?):
play/stop: "Alexa, Wiedergabe auf Name starten/stoppen" bzw. pausieren/fortsetzen (sollte eigentlich sogar mit dem playStatus gehen bzw. musst du halt angeben welche "set-Befehle" für play/stopp/pause notwendig sind. Diese dann im homebridgeMapping angeben)
PlaybackController:playback,values=play;stop;[9/29/2019, 7:28:16 PM] [FHEM] HEOSPlayer376628887 is media
[9/29/2019, 7:28:16 PM] [FHEM] HEOSPlayer376628887 has
[9/29/2019, 7:28:16 PM] [FHEM] Custom Volume [volume;cached]
[9/29/2019, 7:28:16 PM] [FHEM] Mute [mute]
[9/29/2019, 7:28:16 PM] [FHEM] PlaybackController [playStatus]
2019-09-29 19:28:16 caching: HEOSPlayer376628887-volume: 12
[9/29/2019, 7:28:16 PM] [FHEM] caching: Custom Volume: 12 (as number; from '12')
2019-09-29 19:28:16 caching: HEOSPlayer376628887-mute: off
2019-09-29 19:28:16 caching: HEOSPlayer376628887-playStatus: stopZitat von: monosurr0und am 02 Oktober 2019, 14:18:29Dies wäre prinzipiell über den Umweg einer Routine und Aktivierung mit dem echodevice-Modul möglich.
Erlaubt mir mal eine Frage ohne die Suche gequält zu haben:
Reicht Alexa auch Geräte zurück? Also wie den Smart Plug zBsp?
LG
Zitat von: justme1968 am 12 Februar 2019, 22:12:07
@ToKa: du brauchst ein homebridgeMapping in dem du alles was automatisch erkannt wird mit
clear löschst und ausserdem noch einen fix der demnächst für alexa-fhem kommt.
bis dahin: wenn du dir ein user reading bauen kannst das nur open oder closed enthält müsste fürs erste so etwas gehen:
clear ContactSensorState:<reading>,values=closed:CONTACT_DETECTED;/.*/:CONTACT_NOT_DETECTED
ContactSensorState { ReadingsVal("Buerofenster","value",0) }Internals:
DEF sensor 4 1 IODev=deCONZ
FUUID 5d177d50-f33f-cd72-1dfd-f2982c28fdc08130
FVERSION 31_HUEDevice.pm:0.204260/2019-10-30
ID S4
INTERVAL 1
IODev deCONZ
NAME Fenster_Buero
NR 326
STATE closed
TYPE HUEDevice
lastupdated 2019-11-10 16:19:36
lastupdated_local 2019-11-10 17:19:36
manufacturername LUMI
modelid lumi.sensor_magnet.aq2
name Fenster_Buero
on 1
reachable 1
swversion 20161128
type ZHAOpenClose
uniqueid 00:15:8d:00:03:09:c1:2f-01-0006
READINGS:
2019-11-10 17:19:36 ContactSensorState 0
2019-11-10 16:34:16 battery 81
2019-11-10 16:34:16 reachable 1
2019-11-10 17:19:36 state closed
2019-11-10 16:34:16 temperature 20
helper:
devtype S
reachable 0
update_timeout 1
configList:
setList:
Attributes:
HomeContactType window
HomeModeAlarmActive armaway
HomeOpenMaxTrigger 3
HomeOpenTimeDividers 2 1 2 3
HomeOpenTimes 30
IODev deCONZ
alexaName Bürofenster
alexaRoom Büro
alias Bürofenster
devStateIcon open:fts_window_1w_open@#e56524 closed:fts_window_1w
genericDeviceType contact
group Fenster-/Türkontakte
homebridgeMapping clear ContactSensorState:<reading>,values=closed:CONTACT_DETECTED;/.*/:CONTACT_NOT_DETECTED
icon fts_window_1w
room HUEDevice
userReadings ContactSensorState { ReadingsVal("Fenster_Buero","value",0) }
userattr HomeModeAlarmActive HomeReadings HomeValues HomeContactType:doorinside,dooroutside,doormain,window HomeOpenMaxTrigger HomeOpenDontTriggerModes HomeOpenDontTriggerModesResidents HomeOpenTimeDividers HomeOpenTimes
clear ContactSensorState:state,values=closed:CONTACT_DETECTED;open:CONTACT_NOT_DETECTEDclear ContactSensorState:state,values=closed:CONTACT_DETECTED;;open:CONTACT_NOT_DETECTEDZitatstopped; alexa-fhem not installed. install with 'sudo npm install -g alexa-fhem'.
/usr/local/lib/node_modules/alexa-fhem/lib/user.js:92
(async () => {
^
SyntaxError: Unexpected token (
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/usr/local/lib/node_modules/alexa-fhem/lib/server.js:11:29)
/usr/local/lib/node_modules/alexa-fhem/lib/user.js:92
(async () => {
^Zitatexport PATH=$PATH:/usr/local/bin
export NODE_PATH=$NODE_PATH:/usr/local/lib/node_modules
#!/bin/sh
# description: Start or stop the fhem server
### BEGIN INIT INFO
# Provides: fhem.pl
# Required-Start: $local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: FHEM server
### END INIT INFO
set -e
cd /opt/fhem
port=7072
case "$1" in
'start')
echo "Starting fhem..."
/opt/hmcfgusb/hmland -l 127.0.0.1 -p 1234 -r 03:00 -d
perl fhem.pl fhem.cfg
RETVAL=$?
;;
'stop')
echo "Stopping fhem..."
perl fhem.pl $port "shutdown"
RETVAL=$?
sudo pkill hmland
;;
'status')
cnt=`ps -ef | grep "fhem.pl" | grep -v grep | wc -l`
if [ "$cnt" -eq "0" ] ; then
echo "fhem is not running"
else
echo "fhem is running"
fi
;;
*)
echo "Usage: $0 { start | stop | status }"
RETVAL=1
;;
esac
exit $RETVAL
kill( SIGKILL, $hash->{PID} ); Your vendor has not defined POSIX macro SIGKILL, used at FHEM/CoProcess.pm line 250Zitat*** CONFIG: parsed completely
[2019-12-14 20:27:53] os.homedir()=/opt/fhem
[2019-12-14 20:27:53] this is alexa-fhem 0.5.37
Startup rejected. Reason: Error: ENOENT: no such file or directory, open './key.pem'
ZitatalexaFHEMstopped; failed to connect to fhem: Error: connect ENETUNREACH 10.0.1.21:8083
Zitat von: gvzdus am 17 Dezember 2019, 14:16:57
Deine alexa-fhem.cfg scheint ziemlich im Argen...
ZitatDeine alexa-fhem.cfg scheint ziemlich im Argen...Das scheint mir auch so ;-)
{
"connections" : [
{
"webname" : "fhem",
"server" : "10.0.1.21",
"name" : "FHEM",
"filter" : "room=alexa",
"uid" : 999,
"port" : "8083"
}
],
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
},
"alexa" : {
"oauthClientID" : "amzn1.application-oa2-client.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"port" : 3000,
"keyFile" : "./key.pem",
"name" : "Alexa TEST",
"certFile" : "./cert.pem",
"applicationId" : "amzn1.ask.skill.XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"permissions" : {
"<skill-id>" : {
"client_secret" : "123",
"client_id" : "xyz"
}
}
}
}set <alexa> createDefaultConfigsollte reichen.
Zitatset <alexa> createDefaultConfigWerde ich heute Abend aus probieren und berichten....
SET alexa createDfaultConfig.
defmod dmAlleFenster dummy
attr dmAlleFenster alexaName alle Fenster
attr dmAlleFenster alias Übersicht Fensterstatus
attr dmAlleFenster genericDeviceType contact
attr dmAlleFenster group Fenster und Türen
attr dmAlleFenster homebridgeMapping clear ContactSensorState:contact,values=closed:CONTACT_DETECTED;;open:CONTACT_NOT_DETECTED
attr dmAlleFenster icon fts_window_2w_open_l
attr dmAlleFenster readingList contact
attr dmAlleFenster room Eingang,alexa
attr dmAlleFenster setList open closed
attr dmAlleFenster userReadings contact {ReadingsVal($NAME,"state","n.a.")}
/opt/alexa-fhem/lib/user.js:92
(async () => {
^
SyntaxError: Unexpected token (
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:542:28)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/opt/alexa-fhem/lib/server.js:11:29)Zitat von: justme1968 am 01 Februar 2020, 14:30:48
kann es sein das du mehrere node versionen installiert hast und die falsche genommen wird?
v12.14.16.13.7v6.11.4 :'(
/usr/bin/env which node und ist es das gleiche wie bei which node
/usr/bin/env which node gibt leider, genauso wie which node /usr/local/bin/node/opt/alexa-fhem/bin/alexasystemctl status alexa alexa.service - Node.js Alexa Server
Loaded: loaded (/etc/systemd/system/alexa.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2020-02-02 09:47:25 CET; 55s ago
Process: 2738 ExecStart=/opt/alexa-fhem/bin/alexa -U /home/alexa/.alexa (code=exited, status=0/SUCCESS)
Main PID: 2738 (code=exited, status=0/SUCCESS)
CPU: 273ms
Feb 02 09:47:25 inet systemd[1]: Started Node.js Alexa Server.
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] using config from /home/alexa/.alexa/config.json
Feb 02 09:47:25 inet alexa[2738]: *** CONFIG: parsed completely
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] this is alexa-fhem 0.5.40
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] connecting to FHEM ...
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] [FHEM] trying longpoll to listen for fhem events
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] [FHEM] starting longpoll: http://192.168.23.202:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=nul
Feb 02 09:47:25 inet alexa[2738]: [2020-2-2 9:47:25] Server listening on: https://:::3000 for direct connections
Feb 02 09:47:25 inet alexa[2738]: STDIN EOFZitat von: justme1968 am 02 Februar 2020, 11:27:02
oder viel besser: den autostart aus dem fhem modul nutzen und nicht von hand starten.
Zitat von: justme1968 am 02 Februar 2020, 12:03:31
das würde per ssh auch gehen.
attr myAlexa alexaFHEM-cmd /opt/alexa-fhem/bin/alexa --dockerDetached &
attr myAlexa alexaFHEM-config /home/alexa/.alexa/config.json
attr myAlexa alexaFHEM-host 192.168.x.y (IP der alexa-fhem-Maschine)
attr myAlexa alexaFHEM-log ./log/alexa-%Y-%m-%d.log
attr myAlexa alexaFHEM-sshUser alexaZitat von: Xsantos am 11 Februar 2020, 22:58:28Antwort in der identischen Frage im anderen Thread...
Hallo, ich habe eine Verständnisfrage, ich habe meine Alexa über ein Skill mit einer Wifi Lampe verbunden. Dieser Skill ermöglicht mir, dass ich die Lampe als Smartgerät in meiner Alexa-App finde. Ist es möglich dieses Gerät über Fhem anzusteuern?
Ich wünsche einen entspannten Tag,
Marco
Zitat von: MadMax-FHEM am 14 Februar 2020, 20:18:52
Mach doch die Logik in fhem und die Ausgabe mit dem echodevice-Modul...
https://forum.fhem.de/index.php/topic,82631.msg747482.html#msg747482
Gruß, Joachim
2020.02.18 10:05:16 3: alexa: read: end of file reached while sysread
2020.02.18 10:05:16 3: alexa: stopped
2020.02.18 10:05:16 2: alexa: starting alexa-fhem: /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx -s
2020.02.18 10:05:16 3: alexa: starting
2020.02.18 10:05:16 3: alexa: using logfile: ./log/alexa-2020-02-18.log
Zitat von: justme1968 am 18 Februar 2020, 19:52:12letzte Stunde ca alle 10 min (heute bis 19:47, siehe den Ausschnitt aus dem alexa.log
was heißt häufen und was steht dazu im alexa log file?
[2/18/2020, 7:39:20 PM] [FHEM] longpoll JSON.parse: SyntaxError: Unexpected token , in JSON at position 59
[2/18/2020, 7:39:20 PM] [FHEM] longpoll JSON.parse: SyntaxError: Unexpected token in JSON at position 30
[2/18/2020, 7:47:19 PM] [FHEM] longpoll ended, reconnect in: 200msec
[2/18/2020, 7:47:19 PM] [FHEM] trying longpoll to listen for fhem events
[2/18/2020, 7:47:19 PM] [FHEM] starting longpoll: https://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=1582051625.052;fmt=JSON×tamp=1582051639563
[2/18/2020, 7:47:30 PM] [FHEM] got csrfToken:
[2/18/2020, 7:47:30 PM] [FHEM] Checking devices and attributes...
[2/18/2020, 7:47:30 PM] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2/18/2020, 7:47:30 PM] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20TYPE%3Dalexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2/18/2020, 7:47:30 PM] [FHEM] waiting for events ...
[2/18/2020, 7:47:30 PM] [FHEM] Fetching FHEM devices...
[2/18/2020, 7:47:30 PM] [FHEM] fetching: https://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
[2/18/2020, 7:47:48 PM] [FHEM] alexa device is alexa
[2/18/2020, 7:47:48 PM] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.28%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2/18/2020, 7:47:48 PM] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2/18/2020, 7:47:48 PM] [FHEM] executing: https://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2/18/2020, 7:47:48 PM] Server emitted error: {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"127.0.0.1","port":42439}
[2/18/2020, 7:47:48 PM] Terminating - starting the listener not possible (another instance running?)
[2/18/2020, 7:47:53 PM] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
root 409 1 0 Mai15 ? 00:00:00 /usr/sbin/sshd -D
fhem 1600 1298 0 Mai15 ? 00:00:34 node /usr/local/bin/alexa-fhem -c ./alexa-fhem.cfg
fhem 3645 1600 0 03:25 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:40199 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root 5428 409 0 08:32 ? 00:00:00 sshd: pi [priv]
pi 5451 5428 0 08:32 ? 00:00:00 sshd: pi@pts/0
pi 5500 5454 0 08:38 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)
[2020-5-16 09:02:19] [FHEM] Fetching FHEM devices...
[2020-5-16 09:02:19] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=...*&fwcsrf=csrf_272960626917906&XHR=1
[2020-5-16 09:02:20] [FHEM] got: 33 results
[2020-5-16 09:02:20] [FHEM] HUEDevice2 is light
[2020-5-16 09:02:20] [FHEM] HUEDevice2 has
[2020-5-16 09:02:20] [FHEM] On [onoff;on,off]
[2020-5-16 09:02:20] [FHEM] Brightness [bri]
[2020-5-16 09:02:20] [FHEM] Reachable [reachable]
[2020-5-16 09:02:20] [FHEM] HUEDevice2 will not send proactive events
[2020-5-16 09:02:20] [FHEM] HUEDevice2 uses ID: 00:17:88:01:02:fe:34:0d-0b
[2020-5-16 3:23:30 AM] Reading alexaFHEM.ProxyConnection set to running;; stderr=packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe
[2020-5-16 3:23:30 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20stderr%3Dpacket_write_wait%3A%20Connection%20to%2088.99.31.202%20port%2058824%3A%20Broken%20pipe%20%20%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:23:30 AM] *** SSH: stderr: packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe
[2020-5-16 3:23:30 AM] SSH: exited with 255 - will restart in 107.54226315823752 seconds
[2020-5-16 3:23:30 AM] Reading alexaFHEM.ProxyConnection set to stopped;; Terminated with packet_write_wait: Connection to 88.99.31.202 port 58824: Broken pipe , ssh will restart at 03:25:18
[2020-5-16 3:23:30 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%3B%20Terminated%20with%20packet_write_wait%3A%20Connection%20to%2088.99.31.202%20port%2058824%3A%20Broken%20pipe%20%20%2C%20ssh%20will%20restart%20at%2003%3A25%3A18%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:25:18 AM] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2020-5-16 3:25:18 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:25:18 AM] Starting SSH with -R 1234:127.0.0.1:40199 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2020-5-16 3:25:19 AM] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[2020-5-16 3:25:19 AM] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[2020-5-16 3:25:19 AM] *** SSH: proxy connection established
[2020-5-16 3:25:19 AM] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
[2020-5-16 8:43:04 AM] reloading http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing CharlotteLicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing Heizung from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing JetteLicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing MQTT2_LRlamp_CH1 from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing MQTT2_LRlamp_CH2 from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing TV_on from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing Terrasse from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing WG_Belechtung from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing backlight from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing lamp1_wohnzimmer from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing tree from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] removing wintergartenlicht from http://127.0.0.1:8083/fhem
[2020-5-16 8:43:04 AM] [FHEM] Fetching FHEM devices...
[2020-5-16 8:43:04 AM] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&XHR=1
*** FHEM: connected
[2020-5-16 8:43:05 AM] [FHEM] got: 12 results
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht is switch
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] CharlotteLicht uses ID: 5e34774f-f33f-bbdb-81bd-f6816bee42c712d6
[2020-5-16 8:43:05 AM] [FHEM] Heizung is switch
[2020-5-16 8:43:05 AM] [FHEM] Heizung has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] Heizung will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] Heizung uses ID: 5e24a4cb-f33f-bbdb-e2df-7bc984434c4adad4
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht is switch
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] JetteLicht uses ID: 5e34774f-f33f-bbdb-952c-8c201d6ff94f8227
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 is switch
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH1 uses ID: 5dc825f1-f33f-bbdb-e48e-1c7661d7d7a3aeae
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 is switch
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] MQTT2_LRlamp_CH2 uses ID: 5e53f705-f33f-bbdb-c888-edfd86130b13af52
[2020-5-16 8:43:05 AM] [FHEM] TV_on is switch
[2020-5-16 8:43:05 AM] [FHEM] TV_on has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] TV_on will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] TV_on uses ID: 5c49d87b-f33f-59e6-5d6c-771a26e7ca102d7f
[2020-5-16 8:43:05 AM] [FHEM] Terrasse is switch
[2020-5-16 8:43:05 AM] [FHEM] Terrasse has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] Terrasse will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] Terrasse uses ID: 5e34774f-f33f-bbdb-8f43-2329215b39e4367f
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung is switch
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] WG_Belechtung uses ID: 5e273d31-f33f-bbdb-ca7e-d02b95165a26728b
[2020-5-16 8:43:05 AM] [FHEM] backlight is switch
[2020-5-16 8:43:05 AM] [FHEM] backlight has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] backlight will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] backlight uses ID: 5e34774f-f33f-bbdb-5784-4e5cba808fcf49a5
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer is switch
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] lamp1_wohnzimmer uses ID: 5dd6b162-f33f-bbdb-62ab-fc1f2b4bfb5fcbf8
[2020-5-16 8:43:05 AM] [FHEM] tree is switch
[2020-5-16 8:43:05 AM] [FHEM] tree has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] tree will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] tree uses ID: 5c49d87b-f33f-59e6-b662-090fbcdbd4a820f2
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht is switch
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht has
[2020-5-16 8:43:05 AM] [FHEM] On [state;on,off]
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht will not send proactive events
[2020-5-16 8:43:05 AM] [FHEM] wintergartenlicht uses ID: 5e347750-f33f-bbdb-200d-0124688d53628afc
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token available
[2020-5-16 8:43:05 AM] no event token availableZitat von: matthias soll am 17 Mai 2020, 12:10:47
Richtig ich habe schwer aufgeräumt und bin auf eine neue sd Karte umgezogen.
Nachdem ich das Skill neu installiert habe läuft alles wieder wie gewohnt. Danke für die Hilfe!!!
alexa-fhem -D -c /opt/fhem/alexa-fhem.cfg > debug.log über die kommandozeile funktioniert leider nicht:[11/07/2020, 11:35:56] [FHEM] There was a problem connecting to FHEM (null)
[11/07/2020, 11:35:56] [FHEM] 401: Authorization Required
[11/07/2020, 11:46:38] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=c&XHR=1
[11/07/2020, 11:46:38] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":43107}
[11/07/2020, 11:46:38] Terminating - starting the listener not possible (another instance running?)
[11/07/2020, 11:46:39] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[11/07/2020, 11:46:40] os.homedir()=/opt/fhem
[11/07/2020, 11:46:40] this is alexa-fhem 0.5.55
[11/07/2020, 11:46:40] connecting to FHEM ...
[11/07/2020, 11:46:40] [FHEM] defaults to: will not send proactive events
[11/07/2020, 11:46:41] [FHEM] trying longpoll to listen for fhem events
[11/07/2020, 11:46:41] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594460801536
[11/07/2020, 11:46:41] [FHEM] got csrfToken: x
[11/07/2020, 11:46:41] [FHEM] Checking devices and attributes...
[11/07/2020, 11:46:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%xxy(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=o&XHR=1
[11/07/2020, 11:46:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=xr&XHR=1
[11/07/2020, 11:46:41] [FHEM] waiting for events ...
[11/07/2020, 11:46:41] [FHEM] Fetching FHEM devices...
[11/07/2020, 11:46:41] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=xr&XHR=1
[11/07/2020, 11:46:42] [FHEM] alexa device is alexa
[11/07/2020, 11:46:42] [FHEM] alexa will not send proactive events
[11/07/2020, 11:46:42] [FHEM] alexa uses ID: 5f0xxxx
[11/07/2020, 11:46:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.55%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=xr&XHR=1
[11/07/2020, 11:46:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:42] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:42] Server listening on: http://127.0.0.1:39079 for proxy connections
[11/07/2020, 11:46:42] *** SSH: checking proxy configuration
[11/07/2020, 11:46:42] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[11/07/2020, 11:46:42] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":39079},"connections":[{"name":"FHEM","webname":"fhem","filter":"alexaName=..*","server":"127.0.0.1","port":"8083","uid":999}]}
[11/07/2020, 11:46:42] sshautoconf: SSH key seems to exist
[11/07/2020, 11:46:43] sshautoconf: Our SSH key is known at the reverse proxy, good!
[11/07/2020, 11:46:43] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
*** FHEM: connected
[11/07/2020, 11:46:43] [FHEM] got: 14 results
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung is switch
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung has
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Aussenbeleuchtung uses ID: 5db85d09-f33f-de02-f113-7cbd651a895ba0e6
2020-07-11 11:46:43 caching: Aussenbeleuchtung-state: off
[11/07/2020, 11:46:43] [FHEM] Denon is switch
[11/07/2020, 11:46:43] [FHEM] Denon has
[11/07/2020, 11:46:43] [FHEM] Custom Volume [volume;cached]
[11/07/2020, 11:46:43] [FHEM] Mute [mute]
[11/07/2020, 11:46:43] [FHEM] Custom Power [power]
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Denon will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Denon uses ID: 5c8a745b-f33f-de02-5af9-43776d8ef42c297c
2020-07-11 11:46:43 caching: Denon-volume: 17.5
[11/07/2020, 11:46:43] [FHEM] caching: Custom Volume: 18 (as number; from '17.5')
2020-07-11 11:46:43 caching: Denon-mute: off
2020-07-11 11:46:43 caching: Denon-power: on
[11/07/2020, 11:46:43] [FHEM] Denon-power not a number: on
2020-07-11 11:46:43 caching: Denon-state: on
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l is light
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l has
[11/07/2020, 11:46:43] [FHEM] PositionState [motor]
[11/07/2020, 11:46:43] [FHEM] FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM] CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM] TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l will not send proactive events
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_l uses ID: OEQ1312732
2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-motor: stop:93.5
2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-D-firmware: 2.11
2020-07-11 11:46:43 caching: EG_Rolll_Wz_l-pct: 93.5
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r is light
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r has
[11/07/2020, 11:46:43] [FHEM] PositionState [motor]
[11/07/2020, 11:46:43] [FHEM] FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM] CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM] TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r will not send proactive events
[11/07/2020, 11:46:43] [FHEM] EG_Rolll_Wz_r uses ID: OEQ1310914
2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-motor: stop:on
2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-D-firmware: 2.11
2020-07-11 11:46:43 caching: EG_Rolll_Wz_r-pct: 100
[11/07/2020, 11:46:43] [FHEM] FireTV is switch
[11/07/2020, 11:46:43] [FHEM] FireTV has
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] FireTV will not send proactive events
[11/07/2020, 11:46:43] [FHEM] FireTV uses ID: 5c8a745e-f33f-de02-1d89-4d08327f4b5d5b8a
2020-07-11 11:46:43 caching: FireTV-state: on
[11/07/2020, 11:46:43] [FHEM] Garage_1 is switch
[11/07/2020, 11:46:43] [FHEM] Garage_1 has
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] valueOn [auf]
[11/07/2020, 11:46:43] [FHEM] Garage_1 will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Garage_1 uses ID: 5db3fe97-f33f-de02-9a3c-5b05b09ada6880e6
2020-07-11 11:46:43 caching: Garage_1-state: on
[11/07/2020, 11:46:43] [FHEM] Garage_2 is switch
[11/07/2020, 11:46:43] [FHEM] Garage_2 has
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] Garage_2 will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Garage_2 uses ID: 5db40275-f33f-de02-e1bd-d3649e5460ab6b30
2020-07-11 11:46:43 caching: Garage_2-state: on
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima is thermostat
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima has
[11/07/2020, 11:46:43] [FHEM] TargetTemperature [desired-temp]
[11/07/2020, 11:46:43] [FHEM] Custom Actuation [ValvePosition]
[11/07/2020, 11:46:43] [FHEM] CurrentTemperature [measured-temp]
[11/07/2020, 11:46:43] [FHEM] CurrentHeatingCoolingState [undefined]
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima will not send proactive events
[11/07/2020, 11:46:43] [FHEM] HM_Karsten_Stube_Clima uses ID: CUL_HM.5FA47004
2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-desired-temp: 5.0
2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-ValvePosition: 0
[11/07/2020, 11:46:43] [FHEM] caching: Custom Actuation: 0 (as number; from '0')
2020-07-11 11:46:43 caching: HM_Karsten_Stube_Clima-measured-temp: 17.3
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima is thermostat
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima has
[11/07/2020, 11:46:43] [FHEM] TargetTemperature [desired-temp]
[11/07/2020, 11:46:43] [FHEM] Custom Actuation [ValvePosition]
[11/07/2020, 11:46:43] [FHEM] CurrentTemperature [measured-temp]
[11/07/2020, 11:46:43] [FHEM] CurrentHeatingCoolingState [undefined]
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima will not send proactive events
[11/07/2020, 11:46:43] [FHEM] HM_Mutti_Stube_links_Clima uses ID: CUL_HM.5FA99D04
2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-desired-temp: 24.0
2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-ValvePosition: 100
[11/07/2020, 11:46:43] [FHEM] caching: Custom Actuation: 100 (as number; from '100')
2020-07-11 11:46:43 caching: HM_Mutti_Stube_links_Clima-measured-temp: 21.7
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur is thermometer
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur has
[11/07/2020, 11:46:43] [FHEM] StatusLowBattery [battery]
[11/07/2020, 11:46:43] [FHEM] CurrentTemperature [temperature]
[11/07/2020, 11:46:43] [FHEM] CurrentRelativeHumidity [humidity]
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Mebus_Aussentemperatur uses ID: 5c8e84b4-f33f-de02-9d27-615f1a8f73328845
2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-battery: ok
2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-temperature: 19.1
2020-07-11 11:46:43 caching: Mebus_Aussentemperatur-humidity: 46
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l is blind
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l has
[11/07/2020, 11:46:43] [FHEM] PositionState [motor]
[11/07/2020, 11:46:43] [FHEM] FirmwareRevision [D-firmware]
[11/07/2020, 11:46:43] [FHEM] CurrentPosition [pct]
[11/07/2020, 11:46:43] [FHEM] TargetPosition [pct]
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l will not send proactive events
[11/07/2020, 11:46:43] [FHEM] OG_Rolll_Ez_l uses ID: OEQ1312811
2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-motor: stop:on
2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-D-firmware: 2.11
2020-07-11 11:46:43 caching: OG_Rolll_Ez_l-pct: 100
[11/07/2020, 11:46:43] [FHEM] Poolheizung is thermometer
[11/07/2020, 11:46:43] [FHEM] Poolheizung has
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] CurrentTemperature [DS18B20-2_Temperature]
[11/07/2020, 11:46:43] [FHEM] Poolheizung will not send proactive events
[11/07/2020, 11:46:43] [FHEM] Poolheizung uses ID: 5f052f05-f33f-de02-13af-b53ede879c3a52ef
2020-07-11 11:46:43 caching: Poolheizung-state: on
2020-07-11 11:46:43 caching: Poolheizung-DS18B20-2_Temperature: 21.25
[11/07/2020, 11:46:43] [FHEM] SATReceiver is light
[11/07/2020, 11:46:43] [FHEM] SATReceiver has
[11/07/2020, 11:46:43] [FHEM] Custom Volume [volume;cached]
[11/07/2020, 11:46:43] [FHEM] Mute [mute]
[11/07/2020, 11:46:43] [FHEM] Custom Power [power]
[11/07/2020, 11:46:43] [FHEM] On [state;on,off]
[11/07/2020, 11:46:43] [FHEM] SATReceiver will not send proactive events
[11/07/2020, 11:46:43] [FHEM] SATReceiver uses ID: 5c8a745c-f33f-de02-2e1a-a7c3160eec5522aa
2020-07-11 11:46:43 caching: SATReceiver-volume: 100
[11/07/2020, 11:46:43] [FHEM] caching: Custom Volume: 100 (as number; from '100')
2020-07-11 11:46:43 caching: SATReceiver-mute: -
2020-07-11 11:46:43 caching: SATReceiver-power: off
[11/07/2020, 11:46:43] [FHEM] SATReceiver-power not a number: off
2020-07-11 11:46:43 caching: SATReceiver-state: off
[11/07/2020, 11:46:44] [FHEM] Strassenbewaesserung: no service type detected
[11/07/2020, 11:46:44] [FHEM] no device created for Strassenbewaesserung (MQTT_DEVICE)
[11/07/2020, 11:46:44] BearerToken '...B181F' read from alexa
[11/07/2020, 11:46:44] [FHEM] got .eventToken
[11/07/2020, 11:46:44] refreshing token
[11/07/2020, 11:46:44] 39_alexa.pm is new version: true
[11/07/2020, 11:46:44] sshautoconf: completed successfully
[11/07/2020, 11:46:44] *** SSH: proxy configuration set up done
[11/07/2020, 11:46:44] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[11/07/2020, 11:46:44] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:44] Starting SSH with -R 1234:127.0.0.1:39079 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[11/07/2020, 11:46:44] got fresh token
[11/07/2020, 11:46:45] Reading alexaFHEM.ProxyConnection set to running;; SSH connected
[11/07/2020, 11:46:45] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20running%3B%3B%20SSH%20connected%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=x&XHR=1
[11/07/2020, 11:46:45] *** SSH: proxy connection established
[11/07/2020, 11:46:45] SSH: Welcome at the reverse proxy! This pseudoshell does not react to any input - do not get irritated.
2020-07-11 11:46:50 caching: Mebus_Aussentemperatur-temperature: 19.0
[11/07/2020, 11:46:50] [FHEM] caching: CurrentTemperature: 19 (as number; from '19.0')sudo rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* /usr/local/lib/dtrace/node.d ~/.npm ~/.node-gyp /opt/local/bin/node /opt/local/include/node /opt/local/lib/node_modules
sudo rm -rf /usr/local/lib/node*
sudo rm -rf /usr/local/include/node*
sudo rm -rf /usr/local/bin/node*
curl -sL https://deb.nodesource.com/setup_14.x | bash -
apt-get install -y nodejssudo npm install -g alexa-fhemsudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister
Save config ?
1_Wohnzimmer
2_ROLLLADEN
3_Handy
4_Beregnung
5_SYSTEM
6_Heizung
7_Alexa
8_Amazon
CUL_HM
CUL_TCM97001
CUL_WS
ESPEasy
FLAMINGO
IT
MQTT2_DEVICE
OREGON
Plots
SD_BELL
SD_UT
SD_WS
SD_WS07
SIGNALduino_un
Unsorted
Wetter-vorhersage
icoEverything Everything
Logfile
Commandref
Remote doc
Edit files
Select style
Event monitor
Update
UpdateCheck
Restart
Internals:
FD 13
FUUID 5f094ae8-f33f-de02-b693-32cc3527f13fa79f
FVERSION 39_alexa.pm:0.216510/2020-04-12
LAST_START 2020-07-11 11:46:38
LAST_STOP 2020-07-11 11:46:38
NAME alexa
NOTIFYDEV global,global:npmjs.*alexa-fhem.*
NR 658
NTFY_ORDER 50-alexa
PARTIAL
PID 2008
STARTS 9
STATE running /usr/bin/alexa-fhem
TYPE alexa
active 0
alexa-fhem version 0.5.55
currentlogfile ./log/alexa-2020-07-11.log
logfile ./log/alexa-%Y-%m-%d.log
CoProcess:
cmdFn alexa_getCMD
name alexaFHEM
state running /usr/bin/alexa-fhem
READINGS:
2020-07-11 11:46:38 alexaFHEM running /usr/bin/alexa-fhem
2020-07-11 11:46:45 alexaFHEM.ProxyConnection running; SSH connected
2020-07-11 07:15:59 alexaFHEM.bearerToken crypt:xxxxxxx
2020-07-11 07:15:59 alexaFHEM.skillRegKey crypt:xxxxxxx
helper:
Attributes:
alexaFHEM-auth crypt:xxxx
alexaFHEM-config ./alexa-fhem.cfg
alexaFHEM-log ./log/alexa-%Y-%m-%d.log
alexaMapping #Characteristic=<name>=<value>,...
On=verb=schalte,valueOn=an;ein,valueOff=aus,valueToggle=um
Brightness=verb=stelle,property=helligkeit,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
Hue=verb=stelle,valuePrefix=auf,values=rot:0;grün:128;blau:200
Hue=verb=färbe,values=rot:0;grün:120;blau:220
Saturation=verb=stelle,property=sättigung,valuePrefix=auf,values=AMAZON.NUMBER
Saturation=verb=sättige,values=AMAZON.NUMBER
TargetPosition=verb=mach,articles=den;die,values=auf:100;zu:0
TargetPosition=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
TargetTemperature=verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=grad
Volume:verb=stelle,valuePrefix=auf,values=AMAZON.NUMBER,valueSuffix=prozent
#Weckzeit=verb=stelle,valuePrefix=auf;für,values=AMAZON.TIME,valueSuffix=uhr
alexaTypes #Type=<alias>[,<alias2>[,...]]
light=licht,lampen
blind=rolladen,rolläden,jalousie,jalousien,rollo,rollos
devStateIcon stopped:control_home@red:start stopping:control_on_off@orange running.*:control_on_off@green:stop
echoRooms #<deviceId>=<room>
fhemIntents #IntentName=<sample utterance>
gutenMorgen=guten morgen
guteNacht=gute nacht
persons #<personId>=<name>
room 7_Alexa
stateFormat alexaFHEM
verbose 5
[11/07/2020, 11:46:38] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":43107}
[11/07/2020, 11:46:38] Terminating - starting the listener not possible (another instance running?)ps -ef | grep alexafhem 2008 500 0 11:46 ? 00:00:10 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
root 2870 1088 0 12:16 pts/0 00:00:00 grep alexa
ps -ef | egrep '(alexa|ssh)'pi@raspberrypi:~ $ ps -ef | egrep '(alexa|ssh)'
root 475 1 0 09:20 ? 00:00:00 /usr/sbin/sshd -D
root 664 475 0 09:21 ? 00:00:00 sshd: root@notty
root 689 664 0 09:21 ? 00:00:00 /usr/lib/openssh/sftp-server
root 873 475 0 09:25 ? 00:00:03 sshd: root@pts/0
fhem 5399 5180 0 10:49 ? 00:00:07 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
fhem 5411 5399 0 10:49 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:44003 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root 6013 475 0 11:03 ? 00:00:00 sshd: pi [priv]
pi 6042 6013 0 11:03 ? 00:00:00 sshd: pi@pts/1
pi 6655 6045 0 11:14 pts/1 00:00:00 grep -E --color=auto (alexa|ssh)
pi@raspberrypi:~ $
pi@raspberrypi:~ $ ps -e
PID TTY TIME CMD
1 ? 00:00:04 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 rcu_gp
4 ? 00:00:00 rcu_par_gp
8 ? 00:00:00 mm_percpu_wq
9 ? 00:00:01 ksoftirqd/0
10 ? 00:00:05 rcu_sched
11 ? 00:00:00 rcu_bh
12 ? 00:00:00 migration/0
13 ? 00:00:00 cpuhp/0
14 ? 00:00:00 cpuhp/1
15 ? 00:00:00 migration/1
16 ? 00:00:00 ksoftirqd/1
18 ? 00:00:01 kworker/1:0H-kblockd
19 ? 00:00:00 cpuhp/2
20 ? 00:00:00 migration/2
21 ? 00:00:00 ksoftirqd/2
23 ? 00:00:01 kworker/2:0H-kblockd
24 ? 00:00:00 cpuhp/3
25 ? 00:00:00 migration/3
26 ? 00:00:00 ksoftirqd/3
29 ? 00:00:00 kdevtmpfs
30 ? 00:00:00 netns
34 ? 00:00:00 khungtaskd
35 ? 00:00:00 oom_reaper
36 ? 00:00:00 writeback
37 ? 00:00:00 kcompactd0
38 ? 00:00:00 crypto
39 ? 00:00:00 kblockd
40 ? 00:00:00 watchdogd
42 ? 00:00:00 rpciod
43 ? 00:00:00 kworker/u9:0-hci0
44 ? 00:00:00 xprtiod
47 ? 00:00:06 kswapd0
48 ? 00:00:00 nfsiod
59 ? 00:00:00 kthrotld
60 ? 00:00:00 iscsi_eh
61 ? 00:00:00 dwc_otg
62 ? 00:00:00 DWC Notificatio
63 ? 00:00:00 vchiq-slot/0
64 ? 00:00:00 vchiq-recy/0
65 ? 00:00:00 vchiq-sync/0
66 ? 00:00:00 vchiq-keep/0
67 ? 00:00:00 SMIO
69 ? 00:00:00 irq/86-mmc1
71 ? 00:00:00 mmc_complete
75 ? 00:00:01 kworker/3:1H-kblockd
76 ? 00:00:00 jbd2/mmcblk0p2-
77 ? 00:00:00 ext4-rsv-conver
81 ? 00:00:00 ipv6_addrconf
122 ? 00:00:04 systemd-journal
128 ? 00:00:00 irq/166-usb-001
142 ? 00:00:00 systemd-udevd
177 ? 00:00:00 SMIO
187 ? 00:00:00 mmal-vchiq
188 ? 00:00:00 mmal-vchiq
189 ? 00:00:00 mmal-vchiq
220 ? 00:00:00 cfg80211
225 ? 00:00:00 brcmf_wq/mmc1:0
226 ? 00:00:00 brcmf_wdog/mmc1
260 ? 00:00:00 systemd-timesyn
297 ? 00:00:00 alsactl
299 ? 00:00:00 systemd-logind
301 ? 00:00:00 cron
302 ? 00:00:00 thd
305 ? 00:00:09 avahi-daemon
306 ? 00:00:01 rsyslogd
307 ? 00:00:10 rngd
315 ? 00:00:00 dbus-daemon
316 ? 00:00:00 wpa_supplicant
356 ? 00:00:00 avahi-daemon
393 ? 00:00:00 wpa_supplicant
457 ? 00:00:00 dhcpcd
459 ? 00:01:14 java
462 ? 00:00:03 mosquitto
465 tty1 00:00:00 agetty
471 ? 00:00:00 hciattach
473 ? 00:00:00 kworker/u9:2-hci0
475 ? 00:00:00 sshd
476 ? 00:00:00 bluetoothd
664 ? 00:00:00 sshd
670 ? 00:00:00 systemd
673 ? 00:00:00 (sd-pam)
689 ? 00:00:00 sftp-server
873 ? 00:00:03 sshd
884 pts/0 00:00:00 bash
3101 ? 00:00:03 kworker/u8:1+events_unbound
4834 ? 00:00:01 kworker/0:2H-mmc_complete
4891 ? 00:00:00 kworker/u8:2-events_unbound
5180 ? 00:04:10 perl
5289 ? 00:00:00 kworker/1:0-mm_percpu_wq
5399 ? 00:00:07 node
5411 ? 00:00:00 ssh
5608 ? 00:00:00 kworker/3:0-mm_percpu_wq
5910 ? 00:00:00 kworker/0:1-mm_percpu_wq
5935 ? 00:00:00 kworker/0:1H
5962 ? 00:00:00 kworker/3:1-mm_percpu_wq
6013 ? 00:00:00 sshd
6021 ? 00:00:00 kworker/3:0H
6022 ? 00:00:00 kworker/1:2H
6023 ? 00:00:00 systemd
6026 ? 00:00:00 (sd-pam)
6042 ? 00:00:00 sshd
6045 pts/1 00:00:00 bash
6098 ? 00:00:00 kworker/2:0-events
6197 ? 00:00:00 kworker/1:1-mm_percpu_wq
6248 ? 00:00:00 kworker/0:2-events
6399 ? 00:00:00 kworker/2:2H
6424 ? 00:00:00 kworker/2:1-events_freezable
6475 ? 00:00:00 kworker/3:2H
6476 ? 00:00:00 kworker/1:1H
6503 ? 00:00:00 kworker/3:2
6504 ? 00:00:00 kworker/0:0H
6529 ? 00:00:00 kworker/1:2
6556 ? 00:00:00 kworker/0:0-events
6680 pts/1 00:00:00 ps
pi@raspberrypi:~ $
{
"sshproxy" : {
"ssh" : "/usr/bin/ssh",
"description" : "FHEM Connector"
},
"connections" : [
{
"webname" : "fhem",
"port" : "8083",
"filter" : "alexaName=..*",
"uid" : 999,
"name" : "FHEM",
"server" : "127.0.0.1"
}
]
}sudo npm install -g alexa-fhem
/usr/bin/alexa-fhem -> /usr/lib/node_modules/alexa-fhem/bin/alexa
+ alexa-fhem@0.5.55
added 63 packages from 71 contributors in 9.37s
node --version
v12.18.2
sudo npm update -g alexa-fhem
[2020-7-14 22:47:58] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2020-7-14 22:47:58] os.homedir()=/opt/fhem
[2020-7-14 22:47:58] this is alexa-fhem 0.5.55
[2020-7-14 22:47:58] connecting to FHEM ...
[2020-7-14 22:47:58] [FHEM] defaults to: will not send proactive events
[2020-7-14 22:47:59] [FHEM] trying longpoll to listen for fhem events
[2020-7-14 22:47:59] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594759679544
[2020-7-14 22:47:59] [FHEM] got csrfToken: csrf_352794428950318
[2020-7-14 22:47:59] [FHEM] Checking devices and attributes...
[2020-7-14 22:47:59] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:47:59] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:47:59] [FHEM] waiting for events ...
[2020-7-14 22:47:59] [FHEM] Fetching FHEM devices...
[2020-7-14 22:47:59] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:47:59] [FHEM] longpoll ended, reconnect in: 200msec
[2020-7-14 22:47:59] [FHEM] There was a problem connecting to FHEM (http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_352794428950318&XHR=1).
[2020-7-14 22:47:59] [FHEM] 401: Authorization Required
[2020-7-14 22:47:59] [FHEM] There was a problem connecting to FHEM (null)
[2020-7-14 22:47:59] [FHEM] 401: Authorization Required
*** FHEM: connection failed: 401: Authorization Required
[2020-7-14 22:47:59] [FHEM] There was a problem connecting to FHEM (http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_352794428950318&XHR=1).
[2020-7-14 22:47:59] [FHEM] 401: Authorization Required
[2020-7-14 22:47:59] Got SIGTERM, shutting down alexa-fhem...
[2020-7-14 22:47:59] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2020-7-14 22:48:08] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2020-7-14 22:48:08] os.homedir()=/opt/fhem
[2020-7-14 22:48:08] this is alexa-fhem 0.5.55
[2020-7-14 22:48:08] connecting to FHEM ...
[2020-7-14 22:48:08] [FHEM] defaults to: will not send proactive events
[2020-7-14 22:48:09] [FHEM] trying longpoll to listen for fhem events
[2020-7-14 22:48:09] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594759689475
[2020-7-14 22:48:09] [FHEM] got csrfToken: csrf_352794428950318
[2020-7-14 22:48:09] [FHEM] Checking devices and attributes...
[2020-7-14 22:48:09] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] [FHEM] waiting for events ...
[2020-7-14 22:48:09] [FHEM] Fetching FHEM devices...
[2020-7-14 22:48:09] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] [FHEM] alexa device is alexa
[2020-7-14 22:48:09] [FHEM] alexa will not send proactive events
[2020-7-14 22:48:09] [FHEM] alexa uses ID: 5f0e19fd-f33f-fc78-fa57-5eaeaed46fe6afe7
[2020-7-14 22:48:09] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.55%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:09] Server listening on: http://127.0.0.1:42221 for proxy connections
[2020-7-14 22:48:09] *** SSH: checking proxy configuration
[2020-7-14 22:48:09] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2020-7-14 22:48:09] sshautoconf: env={"LANG":"de_DE.UTF-8","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","HOME":"/opt/fhem","LOGNAME":"fhem","USER":"fhem","INVOCATION_ID":"cff7d779d35d43ee8df52a5077c309f0","JOURNAL_STREAM":"8:23284"}
[2020-7-14 22:48:09] sshautoconf: Creating directory /opt/fhem/.alexa
[2020-7-14 22:48:09] Passed config: {"sshproxy":{"ssh":"/usr/bin/ssh","description":"FHEM Connector","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":42221},"connections":[{"server":"127.0.0.1","uid":999,"name":"FHEM","filter":"alexaName=..*","port":"8083","webname":"fhem"}]}
[2020-7-14 22:48:09] sshautoconf: No SSH public key found, we have to generate one.
[2020-7-14 22:48:32] sshautoconf: Generating public/private rsa key pair.
Created directory '/opt/fhem/.ssh'.
Your identification has been saved in /opt/fhem/.ssh/id_rsa.
Your public key has been saved in /opt/fhem/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:zxYQpmZDXNSMo2b8smvWY7w3gRfQgJiprLA1P6C9Ots fhem@SmartHomeNG
The key's randomart image is:
+---[RSA 4096]----+
| =.+** |
| +.oo+.+ |
| . . .=..o |
|. * o=. .. |
|.* + o .S... |
|+ . o . ooo. |
| . . = .+. |
|... + =.o |
|o+E o.o.+ . |
+----[SHA256]-----+
[2020-7-14 22:48:32] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
*** FHEM: connected
[2020-7-14 22:48:32] [FHEM] got: 0 results
[2020-7-14 22:48:32] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2020-7-14 22:48:32] 39_alexa.pm is new version: true
[2020-7-14 22:48:32] sshautoconf: TypeError: Cannot read property '1' of null
[2020-7-14 22:48:32] sshautoconf: completed successfully
[2020-7-14 22:48:32] *** SSH: proxy configuration set up done
[2020-7-14 22:48:32] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2020-7-14 22:48:32] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:32] Starting SSH with -R 1234:127.0.0.1:42221 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2020-7-14 22:48:36] Reading alexaFHEM.ProxyConnection set to stopped
[2020-7-14 22:48:36] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_352794428950318&XHR=1
[2020-7-14 22:48:36] *** SSH: exited with 255
/home/fhem/.ssh/
sudo -u fhem ssh -p 58824 fhem-va.fhem.de unregister
Your public key was not found
Zitat von: Monosurround am 14 Juli 2020, 23:12:41
sorry, wohl ins falsche thema gepostet :-X
Zitat von: MadMax-FHEM am 14 Juli 2020, 23:19:31
Mal langsam und etwas mitdenken... ;)
Also was ist größer: 6 oder 55!? ;)
Die Version 0.5.55 ist STAND JETZT die aktuellste -> passt
Zitat
Hast du ein allowed Device bzgl. fhemWEB!?
Nur dann brauchst du das Attr authToken
Zitat
Und was macht die Vergabe von User/PW für einen Sinn, wenn man dann KEIN https nutzt, also die Anmeldedaten "plain text" überträgt...
https://wiki.fhem.de/wiki/FHEM_Connector_f%C3%BCr_Amazon_Alexa2020.07.14 22:47:31 3: FHEMWEB WEB CSRF error: csrf_264304260969047 ne csrf_352794428950318 for client WEB_192.168.1.1_54118 / command define alexa alexa. For details see the csrfToken FHEMWEB attribute.
2020.07.14 22:47:35 1: PERL WARNING: \b+ matches null string many times in regex; marked by <-- HERE in m/\b+ <-- HERE 50:([^ ]*)/ at ./FHEM/01_FHEMWEB.pm line 1857.
2020.07.14 22:47:35 1: PERL WARNING: \b+ matches null string many times in regex; marked by <-- HERE in m/\b+ <-- HERE 100:([^ ]*)/ at ./FHEM/01_FHEMWEB.pm line 1857.
2020.07.14 22:47:57 2: alexa: created default configfile: ./alexa-fhem.cfg
2020.07.14 22:47:57 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.14 22:47:57 3: alexa: starting
2020.07.14 22:47:57 3: alexa: using logfile: ./log/alexa-2020-07-14.log
2020.07.14 22:47:57 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.14 22:47:57 3: alexa: read: end of file reached while sysread
2020.07.14 22:47:57 3: alexa: stopped
2020.07.14 22:47:57 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.14 22:47:57 3: alexa: starting
2020.07.14 22:47:57 3: alexa: using logfile: ./log/alexa-2020-07-14.log
2020.07.14 22:47:59 3: alexa: read: end of file reached while sysread
2020.07.14 22:47:59 3: alexa: stopped
2020.07.14 22:48:07 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
2020.07.14 22:48:07 3: alexa: starting
2020.07.14 22:48:07 3: alexa: using logfile: ./log/alexa-2020-07-14.log
get alexa proxyKey oder get alexa proxyToken
[2020-7-15 17:57:17] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2020-7-15 17:57:17] os.homedir()=/opt/fhem
[2020-7-15 17:57:17] this is alexa-fhem 0.5.55
[2020-7-15 17:57:17] connecting to FHEM ...
[2020-7-15 17:57:17] [FHEM] defaults to: will not send proactive events
[2020-7-15 17:57:18] [FHEM] trying longpoll to listen for fhem events
[2020-7-15 17:57:18] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594828638610
[2020-7-15 17:57:18] [FHEM] got csrfToken: csrf_797341777806776
[2020-7-15 17:57:18] [FHEM] Checking devices and attributes...
[2020-7-15 17:57:18] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:18] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:18] [FHEM] waiting for events ...
[2020-7-15 17:57:18] [FHEM] Fetching FHEM devices...
[2020-7-15 17:57:18] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:18] [FHEM] longpoll ended, reconnect in: 200msec
[2020-7-15 17:57:18] [FHEM] There was a problem connecting to FHEM (http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_797341777806776&XHR=1).
[2020-7-15 17:57:18] [FHEM] 401: Authorization Required
[2020-7-15 17:57:18] [FHEM] There was a problem connecting to FHEM (http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_797341777806776&XHR=1).
[2020-7-15 17:57:18] [FHEM] 401: Authorization Required
[2020-7-15 17:57:18] [FHEM] There was a problem connecting to FHEM (null)
[2020-7-15 17:57:18] [FHEM] 401: Authorization Required
*** FHEM: connection failed: 401: Authorization Required
[2020-7-15 17:57:18] Got SIGTERM, shutting down alexa-fhem...
[2020-7-15 17:57:18] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[2020-7-15 17:57:38] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[2020-7-15 17:57:38] os.homedir()=/opt/fhem
[2020-7-15 17:57:38] this is alexa-fhem 0.5.55
[2020-7-15 17:57:38] connecting to FHEM ...
[2020-7-15 17:57:38] [FHEM] defaults to: will not send proactive events
[2020-7-15 17:57:38] [FHEM] trying longpoll to listen for fhem events
[2020-7-15 17:57:38] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1594828658859
[2020-7-15 17:57:38] [FHEM] got csrfToken: csrf_797341777806776
[2020-7-15 17:57:38] [FHEM] Checking devices and attributes...
[2020-7-15 17:57:38] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:38] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:38] [FHEM] waiting for events ...
[2020-7-15 17:57:38] [FHEM] Fetching FHEM devices...
[2020-7-15 17:57:38] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName=..*&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:39] [FHEM] alexa device is alexa
[2020-7-15 17:57:39] [FHEM] alexa will not send proactive events
[2020-7-15 17:57:39] [FHEM] alexa uses ID: 5f0f275c-f33f-fc78-aa75-14d5ee57bf0a15b6
[2020-7-15 17:57:39] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.55%22%7D%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:39] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:39] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:39] Server listening on: http://127.0.0.1:43731 for proxy connections
[2020-7-15 17:57:39] *** SSH: checking proxy configuration
[2020-7-15 17:57:39] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[2020-7-15 17:57:39] sshautoconf: env={"LANG":"de_DE.UTF-8","PATH":"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","HOME":"/opt/fhem","LOGNAME":"fhem","USER":"fhem","INVOCATION_ID":"24ae03c2eb9a4785af391605fb03db15","JOURNAL_STREAM":"8:581750"}
[2020-7-15 17:57:39] sshautoconf: Creating directory /opt/fhem/.alexa
[2020-7-15 17:57:39] Passed config: {"connections":[{"name":"FHEM","server":"127.0.0.1","webname":"fhem","uid":999,"filter":"alexaName=..*","port":"8083"}],"sshproxy":{"description":"FHEM Connector","ssh":"/usr/bin/ssh","options":["-i","/opt/fhem/.ssh/id_rsa","-p",58824,"fhem-va.fhem.de"],"bind-ip":"127.0.0.1","port":43731}}
[2020-7-15 17:57:39] sshautoconf: No SSH public key found, we have to generate one.
[2020-7-15 17:57:40] sshautoconf: Generating public/private rsa key pair.
Created directory '/opt/fhem/.ssh'.
Your identification has been saved in /opt/fhem/.ssh/id_rsa.
Your public key has been saved in /opt/fhem/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:1RBB8vxL29lfmM/aZidz7oLy3LgIq0Lvp6j5+CUyNT0 fhem@SmartHomeNG
The key's randomart image is:
+---[RSA 4096]----+
| ..=o |
| + o |
| + . |
| . . . |
| o E S o |
| ... . . + = |
| o.... . o.= o|
| =.+. .o.o.o++B|
| +++o++. .o=.o@O|
+----[SHA256]-----+
[2020-7-15 17:57:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bjsonlist2%20alexa%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
*** FHEM: connected
[2020-7-15 17:57:41] [FHEM] got: 0 results
[2020-7-15 17:57:41] No reading "alexaFHEM.bearerToken" found in "alexa" - incoming Cloud requests cannot be validated.
[2020-7-15 17:57:41] 39_alexa.pm is new version: true
[2020-7-15 17:57:41] sshautoconf: TypeError: Cannot read property '1' of null
[2020-7-15 17:57:41] sshautoconf: completed successfully
[2020-7-15 17:57:41] *** SSH: proxy configuration set up done
[2020-7-15 17:57:41] Reading alexaFHEM.ProxyConnection set to starting;; starting SSH
[2020-7-15 17:57:41] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20starting%3B%3B%20starting%20SSH%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:41] Starting SSH with -R 1234:127.0.0.1:43731 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
[2020-7-15 17:57:45] Reading alexaFHEM.ProxyConnection set to stopped
[2020-7-15 17:57:45] [FHEM] executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7Balexa%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_797341777806776&XHR=1
[2020-7-15 17:57:45] *** SSH: exited with 255
2020.07.15 17:57:15 1: FHEM::Meta::__GetUpdatedata: ERROR: FHEM/14_SD_UT.pm belongs to source repository "fhem". Ignoring identical file name from source repository signalduino
2020.07.15 17:57:16 2: alexa: created default configfile: ./alexa-fhem.cfg
2020.07.15 17:57:16 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.15 17:57:16 3: alexa: starting
2020.07.15 17:57:16 3: alexa: using logfile: ./log/alexa-2020-07-15.log
2020.07.15 17:57:16 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.15 17:57:17 3: alexa: read: end of file reached while sysread
2020.07.15 17:57:17 3: alexa: stopped
2020.07.15 17:57:17 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.15 17:57:17 3: alexa: starting
2020.07.15 17:57:17 3: alexa: using logfile: ./log/alexa-2020-07-15.log
2020.07.15 17:57:18 3: alexa: read: end of file reached while sysread
2020.07.15 17:57:18 3: alexa: stopped
2020.07.15 17:57:37 2: alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg -a xx:xx
2020.07.15 17:57:37 3: alexa: starting
2020.07.15 17:57:37 3: alexa: using logfile: ./log/alexa-2020-07-15.log
Zitat von: MadMax-FHEM am 15 Juli 2020, 18:21:22
Besser mal Ausgaben des alexa-fhem Logs posten...
Zitat
Und dann mal STOPP und warten bevor du (wieder wild) rumtust...
...und wir immer "hinterher" sind... ;)
Zitat
P.S.: hast du den anderen Thread gelöscht!? (oder ging es nicht)
Zitat von: fireball am 21 Juli 2020, 18:30:45
Ok, ich habe mal auf 0.5.55 upgedatet und beobachte jetzt mal...
VG
René
Zitat von: fireball am 21 Juli 2020, 18:30:45
Ok, ich habe mal auf 0.5.55 upgedatet und beobachte jetzt mal...
VG
René
2020.07.31 16:11:00 2: Alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.31 16:11:00 3: Alexa: starting
2020.07.31 16:11:00 3: Alexa: using logfile: ./log/alexa-2020-07-31.log
2020.07.31 16:11:15 3: Alexa: read: end of file reached while sysread
2020.07.31 16:11:15 3: Alexa: stopped
2020.07.31 16:11:35 2: Alexa: starting alexa-fhem: /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
2020.07.31 16:11:35 3: Alexa: starting
2020.07.31 16:11:35 3: Alexa: using logfile: ./log/alexa-2020-07-31.log
2020.07.31 16:11:50 3: Alexa: read: end of file reached while sysread
2020.07.31 16:11:50 3: Alexa: stopped
[7/31/2020, 4:12:58 PM] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":45827}
[7/31/2020, 4:12:58 PM] Terminating - starting the listener not possible (another instance running?)
ZitatIm Alexa Log folgende Einräge:Code Auswählen
[7/31/2020, 4:12:58 PM] Server emitted error: {"code":"EADDRINUSE","errno":-98,"syscall":"listen","address":"127.0.0.1","port":45827}
[7/31/2020, 4:12:58 PM] Terminating - starting the listener not possible (another instance running?)
Der Port wird jedoch definitiv nicht verwendet.
sudo netstat -tulpn |grep 45827
root@fhem3:~# ps -ef | egrep '(alexa|ssh)'
root 663 1 0 18:23 ? 00:00:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
root 848 663 0 18:24 ? 00:00:00 sshd: cobra [priv]
cobra 1175 848 0 18:24 ? 00:00:00 sshd: cobra@pts/0
fhem 16582 703 47 20:16 ? 00:00:00 node /usr/bin/alexa-fhem -c ./alexa-fhem.cfg
fhem 16595 16582 3 20:16 ? 00:00:00 /usr/bin/ssh -R 1234:127.0.0.1:42291 -oServerAliveInterval=90 -i /opt/fhem/.ssh/id_rsa -p 58824 fhem-va.fhem.de
root 16598 15670 0 20:16 pts/0 00:00:00 grep -E --color=auto (alexa|ssh)
root@fhem3:~# sudo netstat -tulpn |grep 42291
root@fhem3:~#
Zitatsudo netstat -tulpn |grep 58824 liefert hier kein ErgebnisDas ist normal, 58824 ist der Port auf dem fhem-va Server
sudo lsof -i:42291 in den 30 Sek. würde vielleicht mehr zeigen?
root@fhem3:~# nc -zv 127.0.0.1 42280-42300
nc: connect to 127.0.0.1 port 42280 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42281 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42282 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42283 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42284 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42285 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42286 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42287 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42288 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42289 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42290 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42291 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42292 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42293 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42294 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42295 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42296 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42297 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42298 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42299 (tcp) failed: Connection refused
nc: connect to 127.0.0.1 port 42300 (tcp) failed: Connection refused
Zitatconnected but loginerror