Originally posted by: <email address deleted>
As my problem is now slightly different, I thought I would start a
separate thread from this one:
FHT80b not transmitting properly (
http://groups.google.com/group/fhem-users/browse_thread/thread/58b677e2a2362927#
)
I am trying to set-up FHEM to run on a Windows 7 X64 system.
I was having a problem with three of my FHT80Bs, where I wasn't
getting any output from them (other than actuator values and end-xmit:
100 values) and the other 7 FHT80Bs aren't accepting (or processing)
any commands sent from the web interface (e.g. setting desired
temperature) although they are sending info back.
Worried that I might have a FHT80B hardware failure issue, I thought I
would re-test in an environment where it was previously working i.e.
using Linux on my NSLU2. I attached the FHZ1300 PC to the NSLU2 and
started FHEM. As if by magic everything stated working. The three
FHT80Bs became paired and all of them now accepted and processed
commands sent from the FHEM web interface. So I now know that all the
FHT80Bs are OK :-)
I closed down the NSLU2 and re-attached the FHZ1300 PC to the Windows
7 PC. All devices are reporting their values but they won't accept
commands. So it seems to me that something must be different with the
Windows 7 PC when transmitting commands to the FHT80Bs such that they
ignore them. I am confused as to what to do next to debug this issue.
Any suggestions would be welcome :-)
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
Further feedback on this issue (which I still haven't solved) - in
case anyone has any suggestions or can help :-)
I have now got to the point where all FHT80Bs are seen and monitored
and graphs can be produced for the temperatures / actuators etc. The
only thing I can't do is set any values in the FHT80Bs e.g. desired
temperature.
I thought that it might be a problem with the FHZ 1300 PC not
transmitting commands but I think I have disproved this as I have a
FS20 device (switch) that is accepting and acting on 'ON' | 'OFF'
commands that I send from FHEM - so the FHZ 1300 PC is transmitting
OK.
It is just the FHT80Bs that don't seem to be receiving commands (or
ignoring them). However, as soon as I run FHEM on my NSLU2 (Ubuntu) it
works fine and the FHT80Bs behave themselves.
I am now beginning to wonder if it is some sort of software problem
with FHEM working on Windows - a setting not correct (rather like an
earlier problem I had with FHEM not handling windows back slashes -
changing them to forward slashes solved the issue).
Is there any log that is available to see what FHEM is trying to
transmit to the FHT80Bs?
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
Originally posted by: <email address deleted>
I have today (finally) resolved this problem :-)
I was searching this group and came across this thread
http://groups.google.com/group/fhem-users/browse_thread/thread/cb7befc398e358a
= Upgraded to 5.1, lost "mon-from" messages from FHT80b
I changed the fhtsoftbuffer setting in my .cfg file to be 0 (it was
1).
So it now seems to work OK AFAIK.
Thought I would update the thread in case other users experience the
same problem :-)
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com
> I changed the fhtsoftbuffer setting in my .cfg file to be 0 (it was
> 1).
The fhtsoftbuffer attribute was removed from the CUL in release 1059 (about 2
months ago).
--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com