It automatically creates a new device representing my temp sensor, and I can name it and assign a room, but it doesn’t ever actually SHOW anything either in the dashboard, or in the Devices view.
Settings, Advanced, and Device Options for this device are all blank.
If I go into the Advanced tab for the main Motion Sensor device, I can see the field where it’s reporting the temperature, so it’s actually working, it’s just not showing up in the iDoorContact device.
Am I missing some configuration step?
I’ve tried uninstalling an reinstalling the iDoorContact plugin, and rebooting the Veralite and nothing has changed.
I’m running it on Ui7 (7.04 on a Vera 3) with 3 of the Monoprice sensors. You do have to add the sensor ID’s to the plugin and set a Wakeup interval time.
In the idoorplugin:
Settings
Set the Wakeup interval to 1800
Advanced
On the Variables tab, in the iDoorContacts field (Add it if it is not there via New Variable - it is case sensitive) enter the device numbers of the MonoPrice PIR sensors separated by commas, eg 57,93,64
Reload the LUUP engine and it will create the devices. Wait a few hours and it should retrieve the temperatures and put them on the devices.
I too am having the same result as the OP. There just is no new additional devices added after idoor . The app says there is, but it does not show in devices. I need both temp and motion for these devices to work for me.
Does anyone know why this might not add a new device. Until that happens, I can not add the device numbers of the MonoPrice PIR sensor.
I just checked my setup. The ‘Additional temperature’ device that was on my devices page is no longer there. That device is where you add the ID’s. Me thinks one of the firmware upgrades since 7.04 may have broken this plugin. GetVera would have to look into this I fear…
Attached are two files that are needed to fix the “Additional Temperature Device” under UI7…
The plugin does not specify a json file for the device… and newer versions of UI7 will not show the device without a json file. The attached files are a generic json file and the device file that specifies this new json file…
I just downloaded the files and pushed them to my Vera. After a LUUP reload, the device is now again visible.
And yes, I did this from work. I trust Cybrmage’s capabilities.
This should hopefully fix everyone’s issues.
Download the files attached to Cybrmage’s post to your computer.
On your UI7 Vera, go to APP → Develop Plugin and click the UPLOAD button and upload these two files. Then restart LUUP
Files are downloaded.
UI7 Vera, go to APP → Develop Plugin and click the UPLOAD button and uploaded the two files. Verified files exist. Restarted LUUP.
Device still does not show under devices. Restarted veralite. No joy. I tried deleting the app and re installing thinking that if the files were now in veralite that any issue not creating the generic device would no longer happen. No luck.
Note: Sensors are functioning and reporting including temp from the the advance variables CurrentTemperature’. This is a new veralite (parents house) and the sensors are new to it. I previously never had idoorcontact ever working. I say this thinking that my issue might not be solved the same way as BOFH. I am gathering that BOFH’s generic device was already in the system.
Thank you all for any help. Am I missing a step? Is there anything else that I can do?
To add: In addition to the two files that I added, there is also I_iDoorContact.xml.
Further Discovery. I went out and purchased an Aeotec Multisensor 6-1 (I really needed that temp) and when I paired it, the ‘Additional temperatu’ (limited chars in UI7) showed up. Totally not what I was expecting. I am guessing that I should have tried to pair the motion sensor again after installing iDoorContact? I have added the device id to the iDoorContacts variables. Nothing showing up yet, but hopes are high. I have since excluded the 6-1. Pretty slick sensor, but I want to keep things simple for now.
Just wanted to add to the thread that this did work after the ‘Additional temperatu’ showed up and the new iDoor device appeared. The mobile iOS app shows C rather than what is correctly displayed on the web gui. But that is another issue.
Thank you all for the help.
Also note that when a “iDoor #45 XXX” device is created, you can’t rename it, otherwise the code won’t work. It assumes that the name starts with “iDoor #%d”"
Im having a hell of a time to get the temp to work. First off, it appears that some field changed since this thread. I have updated the xml and json file. I do see my motion sensor device (id#9), additional temporature device (#10). I selected the additional temp device, went to advanced, then variables and put in 9 in the IDoorContacts variable, to match my motion sensor device.
Then I go to settings->z-wave settings->advanced->reload engine. After it loads up I do see a new device, iDoor #9 temp sensor. However this sensor does not display anything but 0F.
In the motion sensor (#9) advanced variables, i have tried putting in 9, 10, or 11 in the iDoorContacts variable. None of these seem to do anything to the temperature. I know Im close and must be missing something. If a picture helps, please let me know, i would upload one. Also the #9 device has wakeupIterval of 1800 set. I do see the temp in the variables of the motion sensor (#9) device
[quote=“dbldown768, post:15, topic:185354”]Im having a hell of a time to get the temp to work. First off, it appears that some field changed since this thread. I have updated the xml and json file. I do see my motion sensor device (id#9), additional temporature device (#10). I selected the additional temp device, went to advanced, then variables and put in 9 in the IDoorContacts variable, to match my motion sensor device.
Then I go to settings->z-wave settings->advanced->reload engine. After it loads up I do see a new device, iDoor #9 temp sensor. However this sensor does not display anything but 0F.
In the motion sensor (#9) advanced variables, i have tried putting in 9, 10, or 11 in the iDoorContacts variable. None of these seem to do anything to the temperature. I know Im close and must be missing something. If a picture helps, please let me know, i would upload one. Also the #9 device has wakeupIterval of 1800 set. I do see the temp in the variables of the motion sensor (#9) device
Sent from my Nexus 5 using Tapatalk[/quote]
Did you ever find a solution to this? I am having the same issue.
Nope. Was just going to ask, if anyone has any suggestions or comments, it would be much appreciated. Right now this thing is sitting on my counter as I really wanted the temp part of this sensor.
I manually created a temperature sensor device and created a scene to poll the temperature from the motion sensor every 5 minutes. I found this somewhere in this forum. Didn’t need any plugging to do this. If interested, maybe do a search on Vision Motion sensor. I would have to look it up.
I’ve been seeing a lot of posts where people can’t get the Additional Temperature Device plugin configured properly…
So, I automated the device configuration… updated implementation file is attached…
To use this:
Install the plugin, if you haven’t already.
Once your Vera has finished reloading, find the “Additional Temperature Device” that was created in the dashboard.
Go to the device settings/advanced page and change the impl_file attribute to “I_iDoorContact-auto.xml”
Go to Apps/Develop Apps/Luup files… Make sure “restart luup after upload” is checked, and upload the L_iDoorContact-auto.xml" file to your Vera.
When your Vera reloads, the new implimentation will create a temperature sensor device for each installed device that:
A) Is a Z-Wave device
B) reports that it supports COMMAND_CLASS_SENSOR_MULTILEVEL
C) contains a populated “CurrentTemperature” variable.
NOTE 1: When you initially add a Z-Wave device with temperature sensor (such a a vision, monoprice,etc) to your Vera, the “CurrentTemperature” variable may not be populated immediately… If the additional temperature device does not appear immediately, wait 30 minutes and try again.
NOTE 2: The default name given to the created temperature sensors can be changed without affecting the operation of the plugin.
cybrmage, thanks for the update. I tried you latest auto setup. It seems to have the same result when i tried manually. Maybe i have to unpair the sensor and start all over again? i took some screenshot of what i see. let me know if more information would help
Is the author available to update the plugin? I would be willing to do the testing if needed.