Yes it does … very wierd it doesn’t want to accept the manual routing … I will try next week with 1 routing, maybe that makes a difference :
Well ive given this another shot. i pulled it off from the garage.
brought it inside, attempted exclusion. i got “removed unknown device” on veralite.
so had to manually delete parent object, which cleared the child objects. i then performed a reset of the device, as instructed in the manual.
i then screwed the sensor down to block of wood so the under TMP button is pressed, as it would be when mounted on garage wall.
i then proceeded to include, which it did, after finding the device, i hit reload and it began configuring the device. 3 icons appeared. i left it to finish configuring, it found neighbours, shows version, bla bla bla.
i then went into generic_IO device, added tempsensor files into their respective fields, and saved.
the motion is now being successfully detected, and temperature began reporting few mins ago, however, its still higher than it should be. its currently 22c degrees in the house, this device first showed 25c. 5 mins later its showing 24c. which is still 2 degrees above what im expecting.
so either the sensor is faulty, which i doubt, else it wouldnt work at all. or this device just isnt capable of giving accurate temp readings to vera, which is more likely.
i’ll attempt to put this thing back on the garage and monitor from there, but my last solution is to use it as a binary input, and never buy one again.
Feedback appreciated if im doing something wrong
Just one more thing ive just noticed:
after renaming the newly added deviceand placing them in the “garage” room, the old ones that i force deleted came back??? with the same status of “waiting for wakeup to configure”
I’ve just deleted them again and they went away.
Im thinking because they werent removed properly, they are orphaned somewhere that i cant see them.
Is there some way to check and force delete them? perhaps via ssh?
OK, last consecutive post i swear
I hope this helps someone, with devices losing connectivity, or unknown devices when removing. I still havent solved my temp reporting higher than it should be issue:
so what was happening was everything was working on my bench. when removing magnet, it showed in vera as tripped, etc.
but when i went to put it on the garage, i was putting the magnet in place first, then attaching the device to the wall, then inserting the battery. then testing the garage door opening. This process simulates the procedure required to reset the device. so everytime i was installing it, the device was getting reset.
so to avoid this, i installed the device first, then inserted battery (led blinked once), then put on the cover, (led blinked quickly to show tamper switch activated), when the led stopped blinking, i put the magnet in its place, led blinked once to show contact with magnet and vera showed bypassed.
and now when garage opens and closes, it reports correctly.
Now if something happens after today and its stops working, its going in the creek across the road
How long does it take to replace new battery?
I have managed to get Veralite to include my Fibaro door sensor (i have also installed the temp sensor), i now have 1 motion sensor in my UI5, nothing more, but maybe i have to be more patient ? It is still waiting for wakeup to configure device, so i am hoping it will all show up once it has been configured. But it has been like that for nearly 2 hours… Does it normally take that long ? Dont know what the wakeup frequency is, and what i should change it to (poll frequency in settings)
You must click on the “tmp” switch to wake the sensor up. It will allow communication between the sensor and veralite. When it’s done and the UI will reload (or click on “reload”) and the temp sensor should appear…
No that doesnt work. It seems to wake up as the blue led is flashing, but nothing changes at the sensor device. If i try pressing configure node, tit cannot reach node, when i try polling, it says unable to get any information on node. I have added an appliance module about 12 feet away with direct line of sight, just in case to help communication, but that hasnt helped either. I have tried the temp switch a few times and pressing updating nodes, polling, reloading… its not working
Update: the sensor is now shown without any error message in devices, manufacturer info has been filled in, so part success. Still no temperature device or any other new device, and when i open/close the door it doesnt trigger, no light blue light on the led, the green man in the sensor device does not change to red either. When i have the cover of the sensor and open the door, the blue light flashes, but no change in the sensor device
Mikee, i have found that for better success i kept the bottom TMP button pressed always. I mounted it onto a piece of wood first, ensured the button was pressed in.
If i were you i would exclude it first, takes 2 mins, press exclude on vera, hold device within half a meter, press inside tmp button 3 times quickly, then again 3 times quickly, until vera excludes the device. Then hit reload and ensure device is gone.
start the inclusion process, same as the exclusion above, when vera detects the sensor, put the cover back onto the sensor and keep magnet near also, wait 2 mins, then hit reload. Its after this reload that vera configures the device, and starts adding the the other 2 child devices. leave this for 5 mins or so, i found it adds the child devices, then appears to do nothing, then starts configuring devices. At this stage you can open the parent device, go to settings and check it shows configured date, has neighbors, etc.
lastly, open the generic_io device, change the fields to temp sensors, close and save and after the reload, wait 5 mins for first temp reading. then your good to go.
the entire process from inclusion to being able to read temp and see motion triggered with magnet is 20 mins tops
let me know if your getting anything different than the above
thanks, will try that tomorrow and report back
[quote=“oTi@, post:76, topic:173593”]So if you remove the manual routing, the device configures fine (again)?
Is the Lua engine rebooting after you wake up the device / are you sure the manual route is correct? (One way to get something like you describe, is when the manual route is not correct. This appears to cause a reload of the Lua engine, and so Vera will want to attempt to configure the device again, causing the ‘waiting for wake-up’ message to appear; then when you wake up the device, the engine reloads, and so on.)
Regarding parameter 14, I would leave it at 0. I think the device would need to be treated as a scene controller and a mapping must be added to Vera, to allow support for the 'scene activation' feature.I now have one of these devices and verified this a bit. It can be shown to work that way. In a test environment, I have a single click toggle S1 on an FGS221, a double click turn on S2 and a triple click turns S2 off.
For this to become a feature, MCV will have to decide how to handle these ‘hybrid’ devices (e.g. give user the option of whether it should be treated as a door/window sensor, or a scene controller); and they need to fix the scene handling.
I think i might have found the problem, i think the sensor is faulty. When i first got it it only occasionally responded with a flash of the LED whatever i did, sometimes it did not respond at all, now it is completely dead, not reacting to anything, so either its faulty or the battery is dead, althought that had 58% yesterday. So its going back as it is only a week old, then try again…
does anyone know … if there is any chance to get the sensor deliver more acurate temperatures ?
since the hardware does support 0,25 Degree steps.
[quote=“nullx8, post:94, topic:173593”]does anyone know … if there is any chance to get the sensor deliver more acurate temperatures ?
since the hardware does support 0,25 Degree steps.[/quote]
vera doesnt support this (yet)
vera doesnt support this (yet)[/quote]
yeah … in datamine it looks really ugly (since room temperature does not really change much)
hopefully MCV will incorporate this in the next firmware as it is indeed nice to have it shown in 2 decimals behind the comma for measurements and stuff like that.
does anyone have a pic how to add the temp sensor, whenever I do it, my sensor does not respond anymore (no blue light)
I can’t take a picture at the moment but when you use the ‘can’ device the flat face of the can should be facing away from the terminal block when you bend the leads at a right angle to fit it into housing. Dont forget to exclude and reset the device before trying to re-include with the DS18B20 attached.
thx, at the moment I am struggling to get it working without the temp device. One sensor was installed in 10 secs, this one keeps on blinking