Provide config example for FHEM

[moustic999]

as we have some config for Home Assistant and some others,
It should be fine to have also some configuration example for FHEM
(www.fhem.de)

[oorotor]

I'm using the MQTT2_SERVER in fhem, so if you are using this also and activate the autocreate attribute, then the mqtt-devices should be setup automatically.
My implementation in fhem for testing is very simple (caution, this example is without any encryption/user/password):

define m2s MQTT2_SERVER 1883 global
attr m2s room MQTT

define MQTT2_ems_esp MQTT2_DEVICE ems_esp
attr MQTT2_ems_esp IODev m2s
attr MQTT2_ems_esp readingList ems_esp:EMS/ems-esp/status:.* status
ems_esp:EMS/ems-esp/start:.* start
ems_esp:EMS/ems-esp/heartbeat:.* { json2nameValue($EVENT) }
ems_esp:EMS/ems-esp/shower_data:.* { json2nameValue($EVENT) }
ems_esp:EMS/ems-esp/boiler_data:.* { json2nameValue($EVENT) }
ems_esp:EMS/ems-esp/tapwater_active:.* tapwater_active
ems_esp:EMS/ems-esp/heating_active:.* heating_active
ems_esp:EMS/ems-esp/thermostat_data:.* { json2nameValue($EVENT) }
attr MQTT2_ems_esp room MQTT

[moustic999]

I have mqtt2_client, but works the same. I have the readings created under a mqtt2_device. That s the easy part. Now I want to have publish enabled as well as a convenient way of displaying data .... A template for mqtt2_device would be great.... Envoyé depuis mon smartphone Samsung Galaxy.

…

-------- Message d'origine -------- De : oorotor <[email protected]> Date : 1/11/19 15:14 (GMT+01:00) À : proddy/EMS-ESP <[email protected]> Cc : Ludovic Laurent <[email protected]>, Author <[email protected]> Objet : Re: [proddy/EMS-ESP] Provide config example for FHEM (#227) I'm using the MQTT2_SERVER in fhem, so if you are using this also and activate the autocreate attribute, then the mqtt-devices should be setup automatically. My implementation in fhem for testing is very simple (caution, this example is without any encryption/user/password): define m2s MQTT2_SERVER 1883 global attr m2s room MQTT define MQTT2_ems_esp MQTT2_DEVICE ems_esp attr MQTT2_ems_esp IODev m2s attr MQTT2_ems_esp readingList ems_esp:EMS/ems-esp/status:.* status ems_esp:EMS/ems-esp/start:.* start ems_esp:EMS/ems-esp/heartbeat:.* { json2nameValue($EVENT) } ems_esp:EMS/ems-esp/shower_data:.* { json2nameValue($EVENT) } ems_esp:EMS/ems-esp/boiler_data:.* { json2nameValue($EVENT) } ems_esp:EMS/ems-esp/tapwater_active:.* tapwater_active ems_esp:EMS/ems-esp/heating_active:.* heating_active ems_esp:EMS/ems-esp/thermostat_data:.* { json2nameValue($EVENT) } attr MQTT2_ems_esp room MQTT — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fproddy%2FEMS-ESP%2Fissues%2F227%3Femail_source%3Dnotifications%26email_token%3DACLI2P5RYYMBU3IZGMN32Q3QRQ2UXA5CNFSM4JHLJOS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC3BDZI%23issuecomment-548803045&data=02%7C01%7C%7C688d02949c104838b4f508d75ed5d3af%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637082144773923428&sdata=tPxUWJMeyiKlBDCmzcScxM0Zg6eng8V2CfQ%2F5GpgGtc%3D&reserved=0>, or unsubscribe<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACLI2P5LZQE6MSTS67JCB7DQRQ2UXANCNFSM4JHLJOSQ&data=02%7C01%7C%7C688d02949c104838b4f508d75ed5d3af%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637082144773933439&sdata=tTP%2F7AKzJJYM32JtmCg3DQUgRa%2BKuhUrQT7onNlIQFU%3D&reserved=0>.

[moustic999]

beginning of a config :

define buderus.thermostat MQTT2_DEVICE
setuuid buderus.thermostat 5dbc5776-f33f-c58d-6657-0d77e45cd1e175d6
attr buderus.thermostat IODev mqttBroker
attr buderus.thermostat devStateIcon auto:time_automatic:heat manual:time_manual_mode:auto
attr buderus.thermostat eventMap /auto:auto/heat:manual
attr buderus.thermostat readingList mqttBroker:home/ems-esp/thermostat_data:.* { json2nameValue($EVENT) }
attr buderus.thermostat room Chauffage
attr buderus.thermostat setList auto home/ems-esp/thermostat_cmd_mode1 auto
heat home/ems-esp/thermostat_cmd_mode1 manual
temp home/ems-esp/thermostat_cmd_temp1 $EVTPART1
attr buderus.thermostat stateFormat hc1_mode

[moustic999]

I made some progress

defmod buderus_thermostat MQTT2_DEVICE
attr buderus_thermostat IODev mqttBroker
attr buderus_thermostat devStateIcon set.auto:edit_settings:mode+manual set.manual:edit_settings:mode+auto auto:time_automatic:mode+manual manual:time_manual_mode:mode+auto .*set.°C:edit_settings
attr buderus_thermostat icon temp_control
attr buderus_thermostat jsonMap hc1_mode:mode hc1_seltemp:desired-temp
attr buderus_thermostat readingList mqttBroker:home/ems-esp/thermostat_data:. { json2nameValue($EVENT, '',$JSONMAP) }
attr buderus_thermostat room Chauffage
attr buderus_thermostat setList mode:uzsuSelectRadio,auto,manual home/ems-esp/thermostat_cmd_mode1 $EVTPART1
desired-temp:slider,15.0,0.5,30.0,1 home/ems-esp/thermostat_cmd_temp1 $EVTPART1
attr buderus_thermostat setStateList on off
attr buderus_thermostat stateFormat mode
desired-temp °C
attr buderus_thermostat webCmd mode:desired-temp

This allow to manage the thermostat, changing temp and mode. It works for a RC300, maybe it will require some adaptation for RC35, such as the modes