Rpi+COC+FHEM

[Guest]

Originally posted by: <email address deleted>

I have a RPi, COC and FHEM running with 10 x FHT80B and 8 x DS18B20 on a
one wire bus.

Instead of using OWX, I use the Homematic emulation in the CULFW  (set COC
raw OHo) - this works well but I still have the same problem as many with
the COC reporting unknown messages that appear to be coming from the one
wire bus.

Eventually I wrote a 'notify' that resets the COC and restarts FHEM
whenever an unidentified device was found:

1  Disable Autocreate
2  define LogUndef notify global:UNDEFINED.* set COC raw B00;;shutdown
restart

Not very pretty, but it works

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[rudolfkoenig]

                                                   

> 2  define LogUndef notify global:UNDEFINED.* set COC raw B00;;shutdown
> restart

The COC does not implement B00, you have to reboot it via setting some GPIO
bits.

fhem> get CUL_0 raw
CUL_0 raw => ? (B00 is unknown) Use one of m C F i A Z O G M R T V W X e f l t u x

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

My COC appears to support it !  And it works, so thats OK.

2012.11.09 09:10:57 2: COC: unknown message ON
2012.11.09 09:10:57 0: Server started (version Fhem 5.3 (DEVELOPMENT), $Id: fhem.pl 2085 2012-11-05 07:32:55Z rudolfkoenig $, pid 4871)
2012.11.09 09:10:56 1: Including /var/log/fhem/fhem.save
2012.11.09 09:10:54 3: set COC raw OHo
2012.11.09 09:10:54 3: COC: Possible commands: mBCFAZOGMRTVWXefltux
2012.11.09 09:10:51 3: COC device opened
2012.11.09 09:10:51 3: Setting COC baudrate to 38400
2012.11.09 09:10:51 3: Opening COC device /dev/ttyAMA0
2012.11.09 09:10:50 3: HOMEtablet: port 8086 opened
2012.11.09 09:10:50 3: WEBtablet: port 8085 opened
2012.11.09 09:10:50 3: WEBphone: port 8084 opened
2012.11.09 09:10:50 3: WEB: port 8083 opened
2012.11.09 09:10:50 3: telnetPort: port 7072 opened
2012.11.09 09:10:48 1: Including /etc/fhem.cfg
2012.11.09 09:10:45 0: Server shutdown
2012.11.09 09:10:45 3: set COC raw B00





Am Freitag, 9. November 2012 09:34:15 UTC schrieb Rudolf Koenig:
>
> > 2  define LogUndef notify global:UNDEFINED.* set COC raw B00;;shutdown
> > restart
>
> The COC does not implement B00, you have to reboot it via setting some
> GPIO
> bits.
>
>
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Erstaunlich.

Very strange - I have the same firmware version and it says

COC raw => ? (B is unknown) Use one of m C F A Z O G M R T V W X e f l t u
x

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

There must be something else involved beside the COC itself.

During the last days I updated my test system with RPi & COC nearly every
day by using the fhem update command.
What I can see from here is, that it takes only some hours for the COC for
getting mad. This behaviour is new. Before I had phases where the system
war running fine for at least a couple of days.

What I try to say: it seems to me that there's more than one contributor to
the problem, which might make it complex identifying the cause for all of
this.

BR
Ralf

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

Please post the version of the COC firmware obtained with get COC raw V

pah

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com

[Guest]

Originally posted by: <email address deleted>

COC raw => V 1.47 CSM868



Am Freitag, 9. November 2012 11:17:02 UTC schrieb Prof. Dr. Peter A.
Henning:
>
> Please post the version of the COC firmware obtained with get COC raw V
>
> pah
>

--
To unsubscribe from this group, send email to
fhem-users+unsubscribe@googlegroups.com