First steps in FHEM - Versionsgeschichte

Ph1959de: Sichtung der letzten Änderungen; kleinere Korrekturen

2025-01-01T16:12:31Z

Sichtung der letzten Änderungen; kleinere Korrekturen

← Nächstältere Version		Version vom 1. Januar 2025, 18:12 Uhr
Zeile 350:		Zeile 350:
	As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.		As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.

	[[Datei:GotoRAW-Import firststeps.PNG\|thumb\|left\|300px]]For this purpose, we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ''room Stairwell''. In order to enter the following commands on one piece, click the framed "+" icon next to the command line (only available in the default Style f18), add the following lines with copy&paste to the dialog box that appears and press {{Taste\|Execute}}:		[[Datei:GotoRAW-Import firststeps.PNG\|thumb\|left\|300px]]For this purpose, we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ''room Stairwell''. In order to enter the following commands in one piece, click the framed "+" icon next to the command line (only available in the default Style f18), add the following lines with copy&paste to the dialog box that appears and press {{Taste\|Execute}}:
	define sw_Switch dummy		define sw_Switch dummy
	attr sw_Switch room Stairwell		attr sw_Switch room Stairwell
Zeile 358:		Zeile 358:
	[[Datei:RAW-Import firststeps.PNG]]		[[Datei:RAW-Import firststeps.PNG]]

	Then you can close the dialog or enter the following commands. Note that with ''Execute'' all statements from the dialog box are executed, which may lead to error messages e.g. if a device has already been defined before. Lines with commands that have already been adopted into the configuration can therefore confidently ~~delete~~ to avoid such effects.		Then you can close the dialog or enter the following commands. Note that with ''Execute'' all statements from the dialog box are executed, which may lead to error messages e.g. if a device has already been defined before. Lines with commands that have already been adopted into the configuration can therefore confidently be deleted to avoid such effects.

	Now the Notify is missing, which reacts to ''sw_Switch:on'' and executes two commands:		Now the Notify is missing, which reacts to ''sw_Switch:on'' and executes two commands:

Afo-solar: In the English wiki the page "Import-of-Code-Snippets" is missing, hence I deleted the phrase "please note this article Import-of-Code-Snippets". I corrected the German word "und" in the headline "Event-driven timer start - notify und at" to the English word "and".

2024-12-31T20:03:59Z

In the English wiki the page "Import-of-Code-Snippets" is missing, hence I deleted the phrase "please note this article Import-of-Code-Snippets". I corrected the German word "und" in the headline "Event-driven timer start - notify und at" to the English word "and".

← Nächstältere Version		Version vom 31. Dezember 2024, 22:03 Uhr
Zeile 345:		Zeile 345:
	[[Datei:ErsteSchritteInFhem18B.png]]		[[Datei:ErsteSchritteInFhem18B.png]]

	== Event-driven timer start - notify ~~und~~ at ==		== Event-driven timer start - notify and at ==
	{{Randnotiz\|RNText='''Time and Event Control with DOIF'''		{{Randnotiz\|RNText='''Time and Event Control with DOIF'''
	Since the release of the original article in early 2014, another way of time and event control has been introduced. See: {{Link2CmdRef\|Anker=DOIF}} for DOIF}}		Since the release of the original article in early 2014, another way of time and event control has been introduced. See: {{Link2CmdRef\|Anker=DOIF}} for DOIF}}
	As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.		As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.

	[[Datei:GotoRAW-Import firststeps.PNG\|thumb\|left\|300px]]For this purpose, we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ''room Stairwell''. In order to enter the following commands on one piece, click the framed "+" icon next to the command line (only available in the default Style f18 ~~- please note this article [[Import von Code Snippets\|Import-of-Code-Snippets]]~~), add the following lines with copy&paste to the dialog box that appears and press {{Taste\|Execute}}:		[[Datei:GotoRAW-Import firststeps.PNG\|thumb\|left\|300px]]For this purpose, we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ''room Stairwell''. In order to enter the following commands on one piece, click the framed "+" icon next to the command line (only available in the default Style f18), add the following lines with copy&paste to the dialog box that appears and press {{Taste\|Execute}}:
	define sw_Switch dummy		define sw_Switch dummy
	attr sw_Switch room Stairwell		attr sw_Switch room Stairwell

Afo-solar: I changed the English text according to the German version. The German version makes use of the framed "+" button, which is very useful, if you want to enter multiple commands in one run. When using the "first steps" text myself I started with the German version and switched to the English one in the end. This had the consequence that I missed section about the usage of the "+" button. Hence, in the ongoing work I wondered how one can upload batch files and used only single command lines.

2024-12-31T19:56:58Z

I changed the English text according to the German version. The German version makes use of the framed "+" button, which is very useful, if you want to enter multiple commands in one run. When using the "first steps" text myself I started with the German version and switched to the English one in the end. This had the consequence that I missed section about the usage of the "+" button. Hence, in the ongoing work I wondered how one can upload batch files and used only single command lines.

← Nächstältere Version		Version vom 31. Dezember 2024, 21:56 Uhr
Zeile 350:		Zeile 350:
	As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.		As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.

	~~To do~~ this we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ~~room~~ ''Stairwell''. ~~To create~~ the ~~''Stairwell'' room assign~~ the ~~room~~ to the ~~first device via~~ the ~~command field~~, ~~then click on all other attributes in~~ the ~~detail screen~~:		[[Datei:GotoRAW-Import firststeps.PNG\|thumb\|left\|300px]]For this purpose, we create a Stairwell: create the Dummy-Devices ''sw_Switch'' and ''sw_Light'' in the ''room Stairwell''. In order to enter the following commands on one piece, click the framed "+" icon next to the command line (only available in the default Style f18 - please note this article [[Import von Code Snippets\|Import-of-Code-Snippets]]), add the following lines with copy&paste to the dialog box that appears and press {{Taste\|Execute}}:
	define sw_Switch dummy		define sw_Switch dummy
	attr sw_Switch room Stairwell		attr sw_Switch room Stairwell
Zeile 356:		Zeile 356:
	define sw_Light dummy		define sw_Light dummy
	attr sw_Light room Stairwell		attr sw_Light room Stairwell
			[[Datei:RAW-Import firststeps.PNG]]

			Then you can close the dialog or enter the following commands. Note that with ''Execute'' all statements from the dialog box are executed, which may lead to error messages e.g. if a device has already been defined before. Lines with commands that have already been adopted into the configuration can therefore confidently delete to avoid such effects.

	Now the Notify is missing, which reacts to ''sw_Switch:on'' and executes two commands:		Now the Notify is missing, which reacts to ''sw_Switch:on'' and executes two commands:
Zeile 377:		Zeile 380:
	define n_sw_Switch_on notify sw_Switch:on set sw_Light on-for-timer 60		define n_sw_Switch_on notify sw_Switch:on set sw_Light on-for-timer 60

	== What's next? ==		==What's next?==
	You have now been introduced to:		You have now been introduced to:
	* Creating FHEM devices with '''define'''		*Creating FHEM devices with '''define'''
	* '''Events''' and the Event Monitor		*'''Events''' and the Event Monitor
	* Switching Devices with '''set'''		*Switching Devices with '''set'''
	* Modifying Devices with '''modify''', '''rename''' and '''delete'''		*Modifying Devices with '''modify''', '''rename''' and '''delete'''
	* Setting and editing '''Attributs'''		*Setting and editing '''Attributs'''
	* Event driven actions by '''notify'''		*Event driven actions by '''notify'''
	* Time-controlled switching with '''at'''		*Time-controlled switching with '''at'''

	So you know the most basic mechanisms of FHEM. Details of these commands can be found in the FHEM command reference {{Link2CmdRef}}		So you know the most basic mechanisms of FHEM. Details of these commands can be found in the FHEM command reference {{Link2CmdRef}}
Zeile 407:		Zeile 410:
	----		----
	This is the english version of [[Erste Schritte in FHEM]]		This is the english version of [[Erste Schritte in FHEM]]
	* Last edit German article: {{REVISIONDAY2: Erste Schritte in FHEM}}.{{REVISIONMONTH: Erste Schritte in FHEM}}.{{REVISIONYEAR: Erste Schritte in FHEM}}		* Last edit German article: {{REVISIONDAY2: Erste Schritte in FHEM}}.{{REVISIONMONTH: Erste Schritte in FHEM}}.{{REVISIONYEAR: Erste Schritte in FHEM}}
	* Last edit English article: {{REVISIONDAY2: First steps in FHEM}}.{{REVISIONMONTH: First steps in FHEM}}.{{REVISIONYEAR: First steps in FHEM}}		*Last edit English article: {{REVISIONDAY2: First steps in FHEM}}.{{REVISIONMONTH: First steps in FHEM}}.{{REVISIONYEAR: First steps in FHEM}}
	* '''Newer''' Version is: '''{{#ifexpr: {{REVISIONTIMESTAMP: Erste Schritte in FHEM}} > {{REVISIONTIMESTAMP: First steps in FHEM}}\| dt. Version\|engl. Version}}'''		*'''Newer''' Version is: '''{{#ifexpr: {{REVISIONTIMESTAMP: Erste Schritte in FHEM}} > {{REVISIONTIMESTAMP: First steps in FHEM}}\| dt. Version\|engl. Version}}'''
	----		----
	----		----

Afo-solar: To set the attribute "disable" in detail view, one has to chose the attribute in a drop-down menu. This point is clarified by the submitted changes

2024-12-05T08:11:50Z

To set the attribute "disable" in detail view, one has to chose the attribute in a drop-down menu. This point is clarified by the submitted changes

← Nächstältere Version		Version vom 5. Dezember 2024, 10:11 Uhr
Zeile 191:		Zeile 191:

	#'''Delete''' a notify with command <code>delete <name></code>, e. g. with <code>delete n_mySwitch1_on</code>. By the way, command <code>delete</code> works with any object in FHEM. So you can delete this way "real" devices too.		#'''Delete''' a notify with command <code>delete <name></code>, e. g. with <code>delete n_mySwitch1_on</code>. By the way, command <code>delete</code> works with any object in FHEM. So you can delete this way "real" devices too.
	#'''Deactivate''' a notify, using attribute ''disable''. You can assign it in detail view of the related notify (~~find~~ attribute ''disable'' in lower part and choose value ''1'' with a following click at {{Taste\|attr}})~~, or~~ enter in command line: <code>attr n_mySwitch1_off disable 1</code>.		#'''Deactivate''' a notify, using attribute ''disable''. You can assign it in detail view of the related notify. (Choose the attribute ''disable'' in drop-down menu next to {{Taste\|attr}} in lower part and choose value ''1'' with a following click at {{Taste\|attr}}.) Or enter in command line: <code>attr n_mySwitch1_off disable 1</code>.

	== Save Config ==		== Save Config ==

AndreasMohr: Typos/Spelling

2018-12-31T21:27:38Z

Typos/Spelling

Änderungen zeigen

Baumbuwe: Template Link2CmdRef

2018-01-31T17:05:58Z

Template Link2CmdRef

Krikan: Baustelle entfernt

2017-12-24T23:12:10Z

Baustelle entfernt

← Nächstältere Version		Version vom 25. Dezember 2017, 01:12 Uhr
Zeile 1:		Zeile 1:
	~~{{Baustelle}}~~
	~~----~~
	~~----~~
	~~Hier entsteht die englische Fassung von [[Erste Schritte in FHEM]]...~~

	* Letzte Änderung der dt. Fassung: {{REVISIONDAY2: Erste Schritte in FHEM}}.{{REVISIONMONTH: Erste Schritte in FHEM}}.{{REVISIONYEAR: Erste Schritte in FHEM}}
	* Letzte Änderung der engl. Fassung: {{REVISIONDAY2: First steps in FHEM}}.{{REVISIONMONTH: First steps in FHEM}}.{{REVISIONYEAR: First steps in FHEM}}
	* '''Neuere''' Version ist: '''{{#ifexpr: {{REVISIONTIMESTAMP: Erste Schritte in FHEM}} > {{REVISIONTIMESTAMP: First steps in FHEM}}\| dt. Version\|engl. Version}}'''

	~~----~~
	~~----~~

	This a beginners course for those starting to work with FHEM. After you have installed FHEM on your server you may reproduce all steps without any additional smart home hardware.		This a beginners course for those starting to work with FHEM. After you have installed FHEM on your server you may reproduce all steps without any additional smart home hardware.

Zeile 415:		Zeile 403:

	[[Kategorie:HOWTOS]]		[[Kategorie:HOWTOS]]


			----
			----
			This is the english version of [[Erste Schritte in FHEM]]
			* Last edit german article: {{REVISIONDAY2: Erste Schritte in FHEM}}.{{REVISIONMONTH: Erste Schritte in FHEM}}.{{REVISIONYEAR: Erste Schritte in FHEM}}
			* Last edit english article: {{REVISIONDAY2: First steps in FHEM}}.{{REVISIONMONTH: First steps in FHEM}}.{{REVISIONYEAR: First steps in FHEM}}
			* '''Newer''' Version is: '''{{#ifexpr: {{REVISIONTIMESTAMP: Erste Schritte in FHEM}} > {{REVISIONTIMESTAMP: First steps in FHEM}}\| dt. Version\|engl. Version}}'''
			----
			----

Krikan: /* First attempt */

2017-12-24T23:05:04Z

First attempt

← Nächstältere Version		Version vom 25. Dezember 2017, 01:05 Uhr
Zeile 31:		Zeile 31:
	* In the lower block there are further links, which we will also discuss later.		* In the lower block there are further links, which we will also discuss later.

	The ''Security Check'' note indicates that you have not yet set a password for FHEM. To set up password protection, see the FHEM command reference [http://fhem.de/commandref.html#~~basicAuth~~ commandref], which contains a description of all FHEM functions and modules. To suppress this message for now, enter the following in the command line:		The ''Security Check'' note indicates that you have not yet set a password for FHEM. To set up password protection, see the FHEM command reference [http://fhem.de/commandref.html#allowed commandref], which contains a description of all FHEM functions and modules. To suppress this message for now, enter the following in the command line:
	attr global motd none		attr global motd none
	and confirm this change with {{Taste\|Enter}}.		and confirm this change with {{Taste\|Enter}} or click on the link of the same name.

	[[Datei:ErsteSchritteInFhem02.png\|border]]		[[Datei:ErsteSchritteInFhem02.png\|border]]

Krikan: /* Event-driven timer start - notify und at */

2017-12-24T23:01:34Z

Event-driven timer start - notify und at

@@ Zeile 359: / Zeile 359: @@
 == Event-driven timer start - notify und at ==
 == What's next? ==
 You have now been introduced:

Krikan: /* Scheduler - at */

2017-12-24T22:40:03Z

Scheduler - at

@@ Zeile 289: / Zeile 289: @@
 == Scheduler - at ==
 == Event-driven timer start - notify und at ==
 == What's next? ==

← Nächstältere Version		Version vom 31. Januar 2018, 19:05 Uhr
Zeile 19:		Zeile 19:
	* In the lower block there are further links, which we will also discuss later.		* In the lower block there are further links, which we will also discuss later.

	The ''Security Check'' note indicates that you have not yet set a password for FHEM. To set up password protection, see the FHEM command reference ~~[http://fhem.de/commandref.html#~~allowed ~~commandref]~~, which contains a description of all FHEM functions and modules. To suppress this message for now, enter the following in the command line:		The ''Security Check'' note indicates that you have not yet set a password for FHEM. To set up password protection, see the FHEM command reference {{Link2CmdRef\|Anker=allowed}}, which contains a description of all FHEM functions and modules. To suppress this message for now, enter the following in the command line:
	attr global motd none		attr global motd none
	and confirm this change with {{Taste\|Enter}} or click on the link of the same name.		and confirm this change with {{Taste\|Enter}} or click on the link of the same name.
Zeile 348:		Zeile 348:
	== Event-driven timer start - notify und at ==		== Event-driven timer start - notify und at ==
	{{Randnotiz\|RNText='''Time and Event Control with DOIF'''		{{Randnotiz\|RNText='''Time and Event Control with DOIF'''
	Since the release of the original article in early 2014, another way of time and event control has been introduced. See: ~~[https://fhem.de/commandref.html#~~DOIF ~~commandref~~ for DOIF]}}		Since the release of the original article in early 2014, another way of time and event control has been introduced. See: {{Link2CmdRef\|Anker=DOIF}} for DOIF}}
	As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.		As a last exercise we want to combine a ''notify'' and an ''at''. The timer should now not start when you enter the command in the command field, but when an event occurs.

Zeile 388:		Zeile 388:
	* Time-controlled switching with '''at'''		* Time-controlled switching with '''at'''

	So you know the most basic mechanisms of FHEM. Details of these commands can be found in the FHEM command reference ~~[http://fhem.de/commandref.html commandref]~~		So you know the most basic mechanisms of FHEM. Details of these commands can be found in the FHEM command reference {{Link2CmdRef}}

	In the commandref you will find the description of all FHEM commands as well as the list of all device types that can be integrated in FHEM.		In the commandref you will find the description of all FHEM commands as well as the list of all device types that can be integrated in FHEM.