Hi Jürgen,
I’ve analyzed your latest upload, but sadly there’s no Phone call logged.
There is only TV/VIDEO and KMA on the 261/263 IDs for about 70 seconds;

First item: 2016-12-17 14:53:46
Last item: 2016-12-17 14:54:58

(thats about how long the log takes to reach 7500 rows)
Maybe the log just missed the call (in timing).

The 665 messages was send every second with consistent data again. Though the message is different than a few days ago. (I’ve read somewhere this could be data about your phones battery and reception details.)

Last week: 61 38 00 AA CA AA 2A
Saterday: 61 25 00 AA 9A AA 2A

Looking forward to your new logs 🙂

Kind regards,
Jeroen

Hi Jürgen,

Now the 265 and 267 show up:

The 665 messages also show a sequentiality of which we might get starting to make assumptions with 🙂
I’ll mail the full log to you, but the 665 seem to to have the following meaning;

665#61 passif (no FSE FIS content)
665#77 active (ANRUF …..)
665#67 ending (first ANRUF BEENDED)
665#63 FIS content, no calling (ANRUF BEENDED)

(265 and 267 both twice send a message full of zero’s)

665#61 passif (no FSE FIS content)

I hope the 665#67xxx triggers Rns-e to stop silence mode.
I’ll try to recode my plugin with the 665#67xxx and with the 665#63xxx message and see if it shows any result.

With al this info I think I’ll need to add an (ugly) override to the default 665#61 FSE sends regulairly every second.

Summarized; the FSE says every second “I’m not doing anything, any FIS line 1 and 2 (265/267) won’t set visible, but the regulair 261/263 TV/VIDEO or PHONE content will be visible. The raspberry at the same time says every second “Ok, Phone active, let me send content to 265/267. This “argue” explains the flickering.

We might be able to reduce this to a minimum if we can catch the exact timestamp of the FSE message and directly follow it up with a raspberry 665#63xxx message. (To keep the flicker back to TV/VIDEO as short as possible, our hopefully just invisable or unnoticable) 😀

If this ugly workaround does not turn out to be effective there might be a way to reject FSE acceptance in the device “Ring” (There is a follow up order between IDs 428 – 436 – 43A) It could be possible to break this ring, make FSE stop sending anything. Question is if it’s possible to “reconnect” FSE and have KI to accept FSE again…. Hopefully the first workaround does the trick!!

I hope to be able to upload a new version of the plugin with this function built in before end of this week.
You’ll be able to download it from the homepage (and send you an update about it ofcourse.)

Kind regards,
Jeroen

Hi Jürgen,

Have you checked which pins the canbus hardware uses?
If this does not interfere (or the Relais Module could be used on another pin) it seems to be potentionally possible 🙂

Do you already own the module?
I’ll try to find some time maybe at the end of this week. (I’m expecting my second child and I am currently busy to create an extra bedroom 🙂 )

Kind regards,
Jeroen

Hi Jürgen,

Thanks for the electric scheme!
As for now I’ll continu to write in English if you don’t mind. I have a little less trouble finding the correct expressions than in German.
I actually have lived near the German border for a few years, which still makes me thing I speak some German sometimes, but it just stays hard to find the right words. (In school we’ve been taught perfect grammer though! – Der Die Das Des Dem Den :))

I’ll try to add some (plain) python (like your example link) to the plugin which you could use to test on.
Als the FSE project seems to stall a bit. I’ll add a ‘Kill FSE’ option, which tells the FSE to stop writing to the FIS.
It’s not the end result we want, but if it does stop sending to the FIS it might be a something!

Kind regards,
Jeroen

Hi Jürgen,

I changed ‘sleep’ 100 ms to 75 ms. Maybe the whole script (loop) just takes a little longer than 100 ms.
Same download-link.

Kind regards,
Jeroen