A quick hello

Begonnen von andyclimb, 11 Februar 2013, 17:10:41

Vorheriges Thema - Nächstes Thema



Hoping to install fhem either on a computer or rasberry pi with the COC board.  

couple of questions...

1) is the software all in german?  

I downloaded it for the mac and followed the instructions and got no errors, the log says it started but when i enter the IP:8083/fhem i get a password box and nothing seems to work. Am i missing something rather important here?





I use

Zitatdefine WEB FHEMWEB 8083 global

In my config.txt file and can open the web front end no problems.

Also, you dont require /fhem at the end of the address.

Are you also opening a telnet session?

Can you telnet to the box, or use one of the smart phone apps to see fhem is running?



Oh and another warning,

Make sure you turn google translate off when viewing code,

In my post above it has messed it up.



Thanks for the reply.  
I figured it out in the end. The default file had frizzbox authentication enabled for some reason. I disabled it and now it works just fine.
Bit complicated to get everything to work... But I have a rasberry pi and a COC BOARD on order so shall see how it all runs together.

What's the command for setting a password

#attr telnetPort password {use "1234"}


Zitat von: Fonz schrieb am Di, 12 Februar 2013 14:34Oh and another warning,

Make sure you turn google translate off when viewing code,

In my post above it has messed it up.



Avoid the # as I think it makes fhem ignore the line.

Im not sure about the web interface As I dont use it from outside of my home network, but for the telnet one I use,

Zitatattr telnetPort globalpassword mypassword

Please keep posting, (even if its not a question but something you have found,) as it would appear there is only a few of us that speak English that post on here. I would be interested in anything you have discovered...



Ah that is great.  yes i will let you know.  rPi has been ordered, along with the COC.  

I only have, currently 5 FHT8b s to control so... i think if i use the rPi image from bus ware, it will work straight away, and even comes with fhem i think...

will keep you posted... got the password to work, so thanks.
How secure is fhem...  I would like to control is away from home with a password, but setting that up seems to be pretty difficult...  / time consuming...

i'd also like to maybe run one of the fancier front ends, but they require web severs and stuff, so i'll have to wait for the Pi to arrive to do that..  Are there any in English?




If you can telnet to it, then you could run one of the fancy "Smart phone" front ends? They are in english.

How much memory does the Pi have?

Where are you going to store all the logs?



i've got fhemobile and got it connecting so that is good.  

the pi has 512mb ram, but its the SD card that the main thing.  It comes as a 2Gb image, but you can resize the partitions. i've bought a 16gb card so that should be plenty.  

I've also got a NAS...  

What i'd like to do from the software point of view is to specify much more complex temperature settings.  currently the fht's support night and day temp...

but i'd like  

OFF = 13 deg
home = 16 deg
comfort = 19
hot = 22

so bathroom for example can be 13 during the day, 22 in the morning , but 16 when im home....  which is not currently possible... any ideas... i'd have no idea how to program fhem to do that.

I'd also like to interface other wireless devices.  How do the fht's play when there are other things on the network, especially none fs20...?  is this even possible...  ie... temp sensors etc...

What sort of set up do you have?  



I have 7 FHTb's,

I also have the fht8w boiler connect. This will switch my heating on, if any FHT's valve is open more than a % that I set.

The idea here being if my computer dies, the system will still operate. It is possible to let your computer receive the % the valve is open and then let your computer switch the heating on, but again you will have no redundancy.

Iv also gone a bought a few fs20 plug sockets. PITA because they are a europian plug so I have to convert them twice. Once to be able to plug into a UK plug socket, and then again to plug a UK plug into them.

Its a steep learning curve, especially if you dont know Perl.

I started off by getting my FHT's reporting there state to a text file.
Next step was to use andfhem from the google apps store on my android device to see wtf was going on with temperatures and valve openings etc.

It takes some time to actually understand the data, and with several weeks of tweeking what valve should be open with what % to activate the heating im nearly there....

I also found the placement of the FHT to be very important in getting the heating to swtich off. (after all, that is our goal!) So dont go nailing these to the wall just yet.

I have a young daughter and its important for me that her bedroom cant drop below a certain temperature at night. However I dont want that same high limit during the day when the room is unoccupied, so like you I wanted to change the daytime and nighttime temperatures automaticly.

I learned how to use the "at" command. And I can now change the day and night temperature when I want to.

An example,

Zitatdefine a2 at *07:00:00 set FHTNAME night-temp 6.0

The * denotes that it should be done every day.

However, these units are dumb. If I were to issue that command when the night temperature was already in use, it wouldnt actually change the desired temperature. It only seems to work when I send this signal whilst the day temperature is in use, and then when it go's to night mode it notices the night temperature, and sets the desired temperature to the one I requested.

I then wanted to (for the wife who isnt too technical) have a button on the wall that switched the heating off and on. (also off for one hour, or three hours if she is out for a while)

I used another FS20 switch and programmed it so that on the click of a button it would set all the fht's to night mode, set the mode to manual rather than auto,  and also set all the fht's night temperature to 6. (no point having a higher value as I would really at night, if no one is in the house)

This is where I have started to have problems.

1) If you send loads of signals at once, the buffer in your transmitter will become full. Once thats full, its broke, or signals maybe sent hours later. Remember the term "Lovf" and revisit this post when you see it.

The first time I tried to test this I pressed my button, waited, then saw loads of Lovf's. I hurried arround and reset all the Fht's to how they should be, gave up and went to bed.

Now during the night somehow some of these messages finally got through and I woke up to a cold house.

I learnt that you can oversome this by using one "set" command. Previously I had something like,
"If this button is pressed, set fhta off, set fhtb off, set fhtc off... etc"
I have learnt that its better to have
"If this button is pressed set fhta,fhtb,fhtc off."

They are not real commands but more to help you understand.

heres an example of a real command.

Zitatdefine Out notify button1 set Front,Rear,Izzy,Main,Hallway desired-temp 6.0 mode manual

The Front,Rear,Izzy,Main,Hallway are names of my FHT's.

2) I imagined that when I came home, I could just set the units to Auto and they would go to whatever temp they should be at, at that time of that day.

This is wrong, again they are dumb. So I used this code

Zitatdefine ExtendedAutoMode notify .*mode.*auto {\
    my $r = $defs{@}{READINGS};;\
    return if (!defined($r));;\
    my $olddesired = $r->{"desired-temp"}{VAL};;\
    return if (!defined($olddesired));;\
    my @@day = ("sun", "mon", "tue", "wed", "thu", "fri", "sat");;\
    my $now = sprintf("%%02d:%%02d", $hour, $min);;\
    my $wd = $day[$wday];;\
    my $desired;;\
    if (defined($r->{"warnings"}{VAL}) && $r->{"warnings"}{VAL} eq "Window open") {\
      $desired = $r->{"windowopen-temp"}{VAL};;\
    } elsif (defined($r->{"$wd-from1"}{VAL}) && $r->{"$wd-from1"}{VAL} le $now && defined($r->{"$wd-to1"}{VAL}) && $r->{"$wd-to1"}{VAL} ge $now) {\
      $desired = $r->{"day-temp"}{VAL};;\
    } elsif (defined($r->{"$wd-from2"}{VAL}) && $r->{"$wd-from2"}{VAL} le $now && defined($r->{"$wd-to2"}{VAL}) && $r->{"$wd-to2"}{VAL} ge $now) {\
      $desired = $r->{"day-temp"}{VAL};;\
    } else {\
      $desired = $r->{"night-temp"}{VAL};;\
    fhem ("set @ desired-temp $desired") if (defined($desired) && $desired ne $olddesired);;\

Stolen from a post on here.

With that code in your config file, it will automatic look at what your intentions were in the diary for that given time and then set the desired temp to the correct temperature when you go from manual mode to auto.

However, more problems lie in wait for you.

That code will generate a lot of RT traffic. Because the first bunch of traffic is you requesting all the FHT's to go to auto, then this codes tells all the FHT's to change their desired temperature.

Its just too much and your going to get lots of LOVF's.

Thats about where I am, trying to create a software buffer for my CUL deivce to stop this, or working out how to delay the signals being sent out so that they dont all go at once and jam my CUL.

The FS20 plugs are easy to install and setup, but... They will never tell you if they have received the signal to turn on, so they can be problematic if they are in an area of week reception.

Several times iv turned our electric blanket on from downstairs, to only go upstairs and find the signal was not received.

Im thinking about buying another Cul, and maybe locating it upstairs for better reception, and offloading some of the FHT's onto it, to reduce the work on my primary CUL.

Over to you....



Zitat von: andyclimb schrieb am Mi, 13 Februar 2013 21:11What i'd like to do from the software point of view is to specify much more complex temperature settings.  currently the fht's support night and day temp...
Have a look at Heating Control
FHEM auf Synology Diskstation DS413j (DSM4.3), HM LAN Adapter
Steuerung für Nachtspeicheröfen:
Ladung:   HM-WDS10-TH-O, HM-LC-Sw4-DR, Weather-Modul
Gebläse: HM-CC-TC, HM-LC-SW1-FM, HM-Sec-RHS
FHEM auf FritzBox 7390 für Telefon Funktionen


That is a similar set up to what I had imagined doing... looking at this though i think it is way beyond me... at least until i have some serious free time!  no experience with perl at all... and im totally failing to understand how to structure this stuff.  we shall see...

i had previous read about this buffer limit problem, as well as the fact that these devices are only syncing every 10mins or so, which means updates can be very very long...  

My immediate thoughts are that instead of reprogramming all the thermostats when you leave i was thinking about putting an fs20 relay in line with the fhb 8w... conrad cell one for 40 quid...   this means that both have to be one for the heating to work..  then the manual switch your wife presses just essentially turns the boiler off, and without that the thermostats can continue with their original settings but with no heat, which means no wasted energy.  the advantage of that relay is that you can still control it, so it can be on a time delay.. come back on at certain times etc etc...  but with no complicated radio chatter to clog things up...  just an on/off command..  just a thought....

have you tried the calendar thingy...  i can't get it to work following the instructions at all...  even if i create a device as they do EVTPART1, call my calendar event the same, and make a device called that...  i get argument missing.. also the calendar is out by a day..  so today is the 14th but i have to put events in the 15th for them to appear in the 14th in fhem... it is very very strange...

013.02.14 12:27:04 3: get calendar summary modeStarted: EVTPART1 : argument is missing
2013.02.14 12:27:04 3: set argument is missing on : Please define argument first
2013.02.14 12:27:04 3: SwitchActorOn return value: Please define argument first

any thoughts...  

i've not even looked at heating control yet.. think i need my pi first so that fhem actually registers the correct devices...



Fonz. Tried to pm you the other day but not sure it worked.  How's it going?

I've managed to get fhem to ping my phone and with around a 20min max delay it knows if I've left and turns heating etc off... I then used the heating control option to control the fht 8w so that I can monitor the boiler usage and use the thermostat options etc... Seems to be working ok so far.

Getting lots of LOVF as you said... Software buffer is working but not all the time...




Are you saying its possible to turn a fht8w on or off with fhem?




First delete all your valves from the fht 8w

Then define a dummy variable, I called mine boiler. Could probably also use an fs20 switch with attr dummy 1
Define a HCS and configure it to turn the dummy variable on/off. t will automatically monitor all your FHTs.
Define FHT8V and give it some random code
Define a set of notifies to turn the valve to 100 when boiler:on and one to zero when boiler:off. I've also d eifned a watchdog to make sure the boiler gets turned off...

Finally go to the fht8w and put it in learn, then go to the fht8w menu and select the other option pair and just click set... The fht will flash the code you gave it.. So essentially the CUL pretends to send out a 100% to a valve only the only thing that is listening is the fht8w. It introduced a couple of minute delay but the advantage is you can control the boiler.  I would also mean you could link up you fs20 switch to just have timed offs for when you leave.. And with the advantage only one radio signal is sent and no buffers being filled etc...  

I can copy the code if you want..


Andy, thats genius!

Yes, any code you could supply will make me spend less time thanks,

Just seen your PM.

Not being familiar with this forum I never noticed I had it before.

Suggest we keep all conversations on the forum rather than PM as It will help any other non speaking German folk who stumble apon it.

As to the software buffering, it would appear not to work with a CUL.

The ATTR is not recognised by fhem, in my logs...?