Fibaro motion sensor FGMS-001

[Geir Eilertsen]

Hi,

I'm thinking about buying a FGMS-001, has anybody actually received one and got it working with openHAB?

Geir

[Chris Jackson]

I have one, and I know some others do as well. I've included it into my network but haven't really used it 'properly' yet. It initialises correctly and HABmin gives it the 'green light' :)

It's very nice - small, and easily able to be positioned/pointed. Others might be able to comment more on its use. It's clearly meant for indoor use as it's not bolted to anything - the sensor itself is about the size of a golfball, and it just 'slots' in to a holder that grips the 'ball'. This allows it to be rotated/pointed in any direction, but also means you can just pull it out easily (of course that will trigger the tamper alarm which uses an accelerometer).

If there are any issues with this sensor, given I have one I would like to think it can be rectified :)

Cheers

Chris

[wolffromthenorth]

I have one to but can't get it included using the z-wave stick 2 , does anyone here have a valid config to use this sensor ?

kind regards

ps: maybe i could help debug 

[Chris Jackson]

I included mine with no problem. I just pressed the (new) Include button on the HABmin toolbar, then pressed the button on the motion sensor 3 times and it included fine.

Chris

[christophe xxx]

OK i'll try again tonight with latest binding from habmin. Do you also use a z-stick ?
Kind regards

Op 14-mei-2014 15:23 schreef "Chris Jackson" <ch...@cd-jackson.com>:

I included mine with no problem. I just pressed the (new) Include button on the HABmin toolbar, then pressed the button on the motion sensor 3 times and it included fine.

Chris

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/bb9bB71zgsM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Chris Jackson]

Do you also use a z-stick ? 

Yes.

Chris

[wolffromthenorth]

This morning , i did a reset of the z-stick 2 in the z-wave zensys tool

started from scratch in openhab and tried to add the fibaro FGMS-001 without succes.

the following happens --> controler goes into learning mode --> then i tripple click the B button --> theye goes Blue and fades out.

i can see a new node added in habmin but with no product specs or name

when i do heal and triple click the B-button again it updates itself in habmin as Fibaro FGMS-001 with some command enz ....

but the node stays gray whatever i do , this has been a problem from the beginning i had this node.

the other ones i have at home work fine ( rgbw controller , relay switch all fibaro )

i also tried other software and the get info and batt status work but still the node has not joined the network when i recheck in habmin or the zensystool, what am i doing wrong ?

kind regards 

[Chris Jackson]

Note that you don't need to do a heal, but you do need to press the button a few times. This is because by default the wakeup period is something like 6 hours, and it takes 1 tor 2 wakeup periods to complete initialisation (at least the first time). I normally set my wakeup period down to 1 hour...

Which version of the binding are you using? If you're not using the latest from the HABmin site, then I'd recommend using it as I found a bug last week that was preventing the FGSS from completing initialisation and it is possibly the same thing.

Alternatively, if you're using the latest binding, please send me a log with debug enabled and I'll take a look.

Cheers

Chris

[wolffromthenorth]

Hi chris,

Can i ask you how i can set down the wake time for initial connect as i can't do anything with the node ?

Remember i had the same issue before with the node rgbw controller .

i'm using the latest master from habmin, downloaded this morning , i saw indeed some new buttons added for z-stick control so i assume as i not had them before it is the latest.

before i used other soft like homegenie or the zensystool to bind the nodes and then all went swell , but this happens in seconds, except with this one.

somethings up with this fibaro motion sensor.

I don't understand that for example we need to wake  the node 2,3,4 times as i tried that allready or wait like 8 hours ? what do you mean ? i have to let openhab and habmin run for 16 hours to accept the node ?

As i am still testing openhab and have not implemented it yet in house it's not running all day yet.

i do see a difference as stated in the intial bind that after the second wakeup of the node ( by quickly pressing the B-button 3 times ) it its recognized as Fibaro FGMS-001

Also when i take a look in the zensys tool, i see that all my other nodes are in lisening mode , and this is not (maybe till the bind is complete )

I can't imagine that people with a home center 2 or any other domotica brain suffer from the same troubles ?

I will try again this evening and will run it also in debug so i can send you the log file, i think with the newer fibaro modules something is different or changed.

you also have a motion eye , do you have the american or EU version ? and what firmware ?

Also could you implent a firmware check for the z-stick 2 so we can see on what firm it's running on ?

kind regards 

[Chris Jackson]

Can i ask you how i can set down the wake time for initial connect as i can't do anything with the node ?

In theory the change I made late last week should allow the node to complete without changing the wkeup conifuguration. However, you do need to wake the device up - this is done simply by pressing the button 3 times quickly.

 

Remember i had the same issue before with the node rgbw controller .

The RGBW is on my list to look at - I bought one last week so have it at home but haven't had the time to look at it yet. Lots of people have had problems with that device for some reason so I thought I'd get one to try and find out why (if I can!).

 

I don't understand that for example we need to wake  the node 2,3,4 times as i tried that allready or wait like 8 hours ? what do you mean ? i have to let openhab and habmin run for 16 hours to accept the node ?

For the node to show green in HABmin, which means it's finished it's initialisation staging, it needs to wake up one or two times - this is inevitable no matter what software you use, although some software may not show this. Basically, when the software starts, it tries to communicate with the device, and it can't do this until the device wakes up - and until this time, HABmin won't show the device as green.  Whenever you want to talk to the device, you must either wake it up, or wait for the device to wake up by itself (which can be many hours - I know Ben sets his wakeup time to 1 day!). However, this doesn't mean that the device is not working, or that if it detects motion openHAB won't be notified - it's just the way zwave battery devices work.

 

i do see a difference as stated in the intial bind that after the second wakeup of the node ( by quickly pressing the B-button 3 times ) it its recognized as Fibaro FGMS-001

Just to explain a bit more...  When the binding starts and it doesn't know about a device, it needs to request a lot more information (including the device type, which is why you see the device name show up after waking it up). Once the initialisation is completed, the binding will save all this information in an XML file and when the binding starts next, it reloads and doesn't ask the device for this information again.

In your case, the initialisation is not completing, so the XML file is never saved so you always have this situation.

 

Also when i take a look in the zensys tool, i see that all my other nodes are in lisening mode , and this is not (maybe till the bind is complete )

I don't know this tool so I'm not sure what this means...

 

I can't imagine that people with a home center 2 or any other domotica brain suffer from the same troubles ?

Well, you should have a read of (say) the MCV Vera forum and you'll see this is the case - at least to some degree. I agree there are still issues to resolve in the binding to make it more streamlined, and there may still be a bug here, but battery devices in zwave are problematic, and this is the same for an HC2, or a Vera or any other device. As I said above, these controllers may present the information differently - I know Vera doesn't show initialisation state, but it still has to go through the same steps as I mentioned above - it just doesn't tell you, but the device may still not work until it's completely initialised.

 

I will try again this evening and will run it also in debug so i can send you the log file, i think with the newer fibaro modules something is different or changed.

I don't think this will be an issue with the Fibaro - I'm using it ok at home. Since it is repeatable I think it will be easy to find, and I suspect that it is the same issue that I found with the smoke detector last week. This isn't a problem with the Fibaro though - it's a binding issue. Hopefully I can easily find it with your log (I suspect I didn't completely solve the problem last week so I will look there first).

 

you also have a motion eye , do you have the american or EU version ? and what firmware ?

EU I guess - I'm in the UK. The device has only just come out a few weeks back so I assume there aren't too many versions.

 

Also could you implent a firmware check for the z-stick 2 so we can see on what firm it's running on ?

I'll check when I get home, but I think this is already available in HABmin. I added some controller information a few weeks back - if you look in the controller node (normally node 1) there should be a 'controller' folder and I think it shows version in there. I'll check when I get home, but that's where it should be...

I am confident that with the log file (with debug please - or better still TRACE information) I will be able to find the problem.

Cheers

Chris

[wolffromthenorth]

hi chris,

 

i'll run it in debug and try to play with the wakeup function.

 what you say about battery powerd devices sounds correct to me as it is the first battery device i am testing at home.

so that would explain the hard binding and wakeups as it needs to save it battery.

about the zensystool, i found this on a forum a few days back cause i was searching for a way to reset the z-stick2 and this tool is ideal for testing nodes and resetting, it features some basic on / off function for z-wave devices.

i made post about it yesterday at the request for someone who asked how to reset the stick.

http://www.moonlitzwave.com/zensys-tools.zip

you can have a look at the link above if you like.

i'll run the diag this evening , i'm testing on windows for now but the end product @ home is going to be raspberry pi  + z-wave 2 stick

allready many thanks for the efforts, let's see how far we get with the tests.

kind regards

[wolffromthenorth]

hi all,

after following the advice on the fibaro sensor with the wakeup timings i decided to let the binding and fibario motion detector run all night just to see if it binds and stages correctly.

this is what i did.

i added the node in habmin and the node was grey and unrecognized, then i activated the motion sensor by tripple clicking the little B button inside.

The node was identified as the fibaro fgms.

after restarting openhab i saw it was getting commands like battery status and ......

i just let the binding run for 12 hours, when i woke up the magical green icon appeard next to the node confirming its in the network.

i'll post / will send the logfiles to chris so he can take a look at it.

@chris  you are right about the battery powerd devices and wakeup timings just weard that they do not state that in the manual, quite confusing.

kind regards 

[wolffromthenorth]

btw,

Is there anyone who has allready created an item file for this sensor and rules for example cause looks to me that this is not going to be a easy one.

kind regards 

[Chris Jackson]

> @chris you are right about the battery powerd devices and wakeup timings just weard that they do not state that in the manual, quite confusing.

Yes, battery devices in zwave are really not so simple - or not so well understood at least, and it certainly leeds to some confusion :(

I’m pleased to see things are generally working :)

Cheers
Chris

[marian...@gmail.com]

Hi All,

i have the same setup and the same problem but i can't get it to run. 

4 * FGMS-001 (V2-6 EU)

1 * Aeon Laps z-wave stick S2

OpenHab 1.5.0

z-wave binding (1.5.0 & 1.5.1) 

Habmin (1.5.0-SNAPSHOT)

1. Pairing the devices with the Z-Stick (directly with the stick): works (devices listed grey in openhab, the stick is listed green)

2. after triple clicking the B Button on the motion sensor the devices are identified as the right devices but the still marked as grey.

> i just let the binding run for 12 hours, when i woke up the magical green icon appears next to the node confirming its in the network.

I am waiting for that little green button already a week without success :( 

And the zwave debug log gives no related messages as well.

Do someone have any idea what i do wrong?

kind regards 

marian

[Alex Karls]

if my stick is in the post today i´ll try it this evening

[mad...@gmail.com]

Did you associate all 3 association groups with you z-wave controller node?
If I remember correctly that's what solved the problem for me.

Op maandag 7 juli 2014 11:43:39 UTC+2 schreef marian...@gmail.com:

[Chris Jackson]

Did you associate all 3 association groups with you z-wave controller node?

I don't think you need to associate all 3 groups - but you MUST associate group 3. This group is kept as for notifications to the controller - I only have this group, and I'm pretty sure that I get all notifications.

Chris

[Divine Threepwood]

OK, i thought that every main controller is associated with group 3. How can I establish this association? Because there are no config params reachable via HABmin for the S2. Exists there a wiki howto? I wasn't able to find one.

I don't understand why the other components like the FibaroReedSwitche or the FibaroPlug are successfully registered if the controller is not in group 3?

Is it just necessary for the Motion sensor? Makes no sense for me :( 

[Chris Jackson]

> OK, i thought that every main controller is associated with group 3. How can I establish this association? Because there are no config params reachable via HABmin for the S2. Exists there a wiki howto? I wasn't able to find one.

Sorry - I’m not sure I understand what you mean by this :( What is “the S2”?

> I don't understand why the other components like the FibaroReedSwitche or the FibaroPlug are successfully registered if the controller is not in group 3?
> Is it just necessary for the Motion sensor? Makes no sense for me :(

Normally, with Fibaro devices they have 3 groups - I’m not sure if this is the case for every device, but for most, and I think for all the ones I have. The first group is often linked to the main device specific function, the second group to another function, and the third groups is associated to the controller for an ‘all updates’ type notification. Group 3 normally only has the option to set 1 device, so if you have more than 1 controller, then you need to pick which one is your main controller.

For example, with the door/window sensor, group 1 is the door sensor, group 2 is the tamper button, and group 3 is for the controller, and it will receive both tamper and door sensor updates. The motion sensor is the same - group 1 is motion, group 2 is tamper, group 3 is the controller.

So, you can achieve the same thing by setting group 1 and group 2 as you can for group 3. If you set all 3 groups, it might end up reporting twice which would reduce battery life (although I’ve not tested this so I’m not sure). So, maybe you have group 1 set in other devices, and you think it’s working fine (which it is) but with this configuration you won’t get all notifications - maybe this doesn’t matter though…

I hope that helps - apologies if I’ve not answered all the question.

Cheers
Chris

[christophe xxx]

Hi all,

Same config here no issues wake the units up a few times and it will be green had the same issue here. I also adjusted the wakeup time and gold the sensor to report Evert change in temp and lux

Op 7-jul.-2014 18:16 schreef "Chris Jackson" <ch...@cd-jackson.com>:

So, you can achieve the same thing by setting group 1 and group 2 as you can for group 3. If you set all 3 groups, it might end up reporting twice which would reduce battery life (although I've not tested this so I'm not sure). So, maybe you have group 1 set in other devices, and you think it's working fine (which it is) but with this configuration you won't get all notifications - maybe this doesn't matter though...

I hope that helps - apologies if I've not answered all the question.

Cheers
Chris

[Divine Threepwood]

Hey I got the green button :)

Thanks a lot chris for your useful hints! The problem was definitely the missing association of the fibaro devices with group 3. 

This association was not established by default and MUST be manually set via HABmin! (Tested in two different setups.)

1. Include devices in the zwave network via the S2 Stick (Aeon Labs USB Z-Stick S2). 

2. Start HABmin and navigate to the zwave device overview and triple click the B Button on the Fibaro Motion Sensor till the Sensor is identifiered as FGMS01 Motion Sensor.

3. Restart openHab (sometimes necessary to update the device tree in HABmin, otherwise the configuration or the association settings are not reachable)

4. Navigate with HABmin to the FGMS01 -> Association Groups -> Controller Updates 

5. Mark controller (e.g. Node 1)  as member of this group. (Value is marked yellow until the configuration is transmitted, )

6. Triple click the B button to submit the configuration and verify that the correct node is registered as member.

7. Triple click the B button multiple times again (or wait multiple sensor wakeups) till the device button in HABmin switches from grey to green.

Cheers

Marian

[Chris Jackson]

Thanks a lot chris for your useful hints! The problem was definitely the missing association of the fibaro devices with group 3. 

This association was not established by default and MUST be manually set via HABmin! (Tested in two different setups.)

I'm glad it's working :)

The intention is that this can be automated in future and I defined a flag in the XML files that allows this support... It's just a case of time to implement it, but for now it's manual :) 

Cheers

Chris

[Alex Karls]

Thanks to Marian i got mine finally included :) Could you pls provide your item-config?

--

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/bb9bB71zgsM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

--
mit freundlichen Grüßen,
Alexander Karls

[daniel....@gmail.com]

My working config:

Contact item_name  "Bewegungsmelder [%s]"  <pir>  { zwave="19:1:command=SENSOR_BINARY" }

Number item_name  "Temperatur [%.2f °C]"  <temperature> {zwave="19:1:command=SENSOR_MULTILEVEL,sensor_type=1,refresh_interval=900" }

Number item_name  "Helligkeit [%.0f Lux]" <sun>  { zwave="19:1:command=SENSOR_MULTILEVEL,sensor_type=3,refresh_interval=900" }

[Divine Threepwood]

For sure, here is my working config:

Number  Movement_A_Living16 "SensorID 22:  [MAP(movement.map):%s]"    <present>    (Fibaro,Motion)        { zwave="22:1:command=sensor_binary" }

Number  Alarm_A_Fibaro16 "SenosrID 22:  [MAP(earthquake.map):%s]" <fire>          (Fibaro,Alarm)         { zwave="22:1:command=sensor_alarm" }

Number  Lux_A_Fibaro16       "SensorID 22:  [%.2f Lux]"                    <sun>        (Fibaro,Lux)            { zwave="22:1:command=sensor_multilevel,sensor_type=3" }

Number  Bat_A_Fibaro16          "SensorID 22:  [%d %%]"                         <energy>        (Fibaro,Bat)                { zwave="22:1:command=battery" }

Number  Temp_A_Fibaro16         "SensorID 22:  [%.1f °C]"                       <temperature>   (Fibaro,Temp)               { zwave="22:1:command=sensor_multilevel,sensor_type=1" }

have a nice weekend!

Marian

Am Freitag, 11. Juli 2014 11:24:31 UTC+2 schrieb Alex Karls:

[Alex Karls]

i got it working for once in my testsetup today. now, in my live system, it won`t work at all:

WARN  o.o.b.z.i.c.ZWaveConverterHandler[:256]- No command class found for item = ZWaveTestMotion, command class name = sensor_binary“}

[aaron...@gmail.com]

This is the answer to everything. I had been struggling for hours and hours with my Fibaro motion sense and Z-Stick. Everything looked like it should work but nothing was being reported and the item was grey in Habmin. I was about to smash it all to pieces when I saw this post. For some reason the association wasn't set by default and the manual didn't really explain how important it was.

As soon as I made the association between the sensor and the Z-Stick, everything started working. This should be in big red letters on OpenHAB's page.

[Martin Naughton]

Hey,
       Does anyone find that after they setup the Fibaro FGMS-001 that it stops reporting after a while? I set it up to report motion and temperature to the controller. Tested that it sent motion to openhab and left it. Few hours later it stops sending motion even though the light on the sensor turns blue.  This is the second time that i configured it and it stopped reporting. I just configured the controller would be in group 3 and the temperature report would be sent every 0.5c degrees.


I will configure it again. This time i will not configure the temperature control. See if it will only send motion information for more than a day. The sensor is with in line of sight of the zwave stick so that is not the problem. Would be interesting to see if anyone else had this problem.

Martin

[Ben Jones]

I am using the Fibaro Motion sensor, and have motion and temp reporting enabled. It works just fine, in fact my sensor is far from the controller and has to be routed thru intermediate nodes but it never misses a beat.

Sorry, not much help, but confirmation that it works as expected with openHAB. 

NOTE: it took a while to get setup correctly, due to the routing. It took me a few goes to get the routing table setup correctly, I had to move the sensor close enough to the controller so it could tx/rx directly as it wouldn't initialise and do neighbour updates otherwise. Then once I got that sorted I moved it back to the current location and it successfully routed all messages via the intermediate nodes.

[Jon Evans]

Exactly my experience. I have two Fibaro motion sensors. I find that they work fine for up to a week, then they lose their association to Node 1 in the Controller Updates group. Another ing which seems to remove the association is just to restart the OpenHAB process. Initialisation seems to adversely affect the nodes.

[Chris Jackson]

On Monday, 8 December 2014 14:23:54 UTC, Jon Evans wrote:

Another ing which seems to remove the association is just to restart the OpenHAB process. Initialisation seems to adversely affect the nodes.

The binding shouldn't touch the associations during initialisation - the current binding doesn't even send any association class messages. The new one that I'm working on reads back the associations on startup if the device state is not restored from file, but it doesn't change them.

I'm happy to look at a logfile of the initialisation to see if there's something going on.

Chris

[Norman Sand]

Hi all,

thank you very much for this thread because it helped me lot. But I am stuck in the middle of the configuration process of adding my Fibaro Motion Sensor S2 (this one).

I'm using a Mac Mini (mid 2011) with Mac OS X 10.10 and of openHAB and habmin with org.openhab.binding.zwave-1.7.0-SNAPSHOT.jar. My Z-Stick S2 Z-Wave Controller from Aeon Labs works (as far as I can tell) without any problems and I can see my Motion Sensor on the devices-pane in habmin. As you can see in the attached picture, my Motion Sensor still is "grey". I waited now over a week, tripple-pressed the Backbutton of the sensor multiple times, hoping the configuration process comes to an end - but nothing happens. I have no idea what went wrong. 

I also attached a logfile of the starting process of openHAB and some triggered events of the sensor. It seems that these events (tamper alarm) comes through, but has no endpoint - although I think I configured the endpoint as it should be (node 1).

I would be very glad, if someone could have a look at my logfile and could give me a hint, what I can do. 

Thank you very much!

Cheers

Norman

[Chris Jackson]

Hi Norman,

Thanks for the information and log.  I think you’ve probably come across a corner case bug with the initialisation sequence…

This sensor the only device in your network (other than the controller) and I think the wakeup class isn’t currently configured and the initialisation sequence relies on this for battery devices. This means the initialisation sequence doesn’t get a wakeup, so doesn’t progress...  I’ll try and find a solution for this issue today or tomorrow.

Chris

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

<zwave.log><habmin.png>

[Chris Jackson]

Hi Norman,
I’ve put a new test version on the HABmin site - please give this a go and see if it helps. If it doesn’t complete initialisation, please send me the logs…

Thanks
Chris

[Norman Sand]

Hi Chris,

I'm impressed! Thank you very much for your fast reaction! I used the new test version and it helped partly: The motion sensor appears now with the yellow dot next to the item. According to the habmin-website this means, that the sensor should work in general. But even after waking up the sensor multiple times it won't work as it should. I don't receive any sensor data and according to the logfile, something goes wrong I guess. I attached a new logfile and a new screenshot. (The node has now the number 8, because I started fresh, but it's the same sensor.) 

 

Should I just wait a while, is there something else to do or is this a bug?

Thank you very much!

Norman

[Chris Jackson]

Hi Norman,
I’ll take a look at the log. Normally, the yellow dot means that initialisation is complete, but maybe comms is ‘difficult’ - either the node has been dead in the past 24 hours, or the number of retries is higher than (from memory) 5%. There should be information in the status area for this node - it will give packet stats etc. Maybe you can grab a screenshot with the Status ‘folder’ expanded?

Chris

[Chris Jackson]

Quick look at the log shows the sensor is working, but the item configuration is probably wrong. How have you got this configured - can you post your item configuration strings?

[Norman Sand]

Hi Chris,

of course!

My item-configuration (first is motion):

Contact schlafzimmerbewegung  "Bewegungsmelder [%s]"  <pir>  { zwave="8:1:command=SENSOR_BINARY" }

Number  schlafzimmertemperatur  "Temperatur [%.2f °C]"  <temperature> {zwave="8:1:command=SENSOR_MULTILEVEL,sensor_type=1,refresh_interval=900" }

Number  schlafzimmerhelligkeit  "Helligkeit [%.0f Lux]" <sun>  { zwave="8:1:command=SENSOR_MULTILEVEL,sensor_type=3,refresh_interval=900" }

and one simple rule:

rule "corLightOn"
when  
Item schlafzimmerbewegung changed from OFF to ON

then  

        sendCommand(Lampe_Wohnzimmer_Ecke, ON)

            Lampe_Wohnzimmer_Ecke_Licht.sendCommand("50,50,70")

end

[Norman Sand]

The hue-lamps are working fine, so there should not be any problem within the "then"-part of the rule.

I attached another screenshot with the status open. The package statistic seems not to be very good...

[Chris Jackson]

I think you need to remove the :1 in your item definitions (e.g. user “8:command=SENSOR_BINARY”).

If you look in the log, you’ll see the following messages -:

2014-12-14 12:51:17.065 WARN  o.o.b.z.i.ZWaveActiveBinding[:459]- NODE 8: No item bound for event, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 51, ignoring.

This indicates that the binding can’t find an item linked to this sensor - you’ll find this also for the alarms…

This has been a common issue since the endpoint changes - I’ll add this to the wiki…

Cheers

Chris

[Norman Sand]

That's it! Thank you very much for your help! The sensor is now working as it should. It controls the lights now, I can see the temperature and the brightness in the room. Your help was very appreciated. :)

Norman