Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Vera/openLuup plugins
  4. External Temp Sensor w/ Thermostat
Logic Programming
akbooerA
Topic thumbnail image
Vera/openLuup plugins
Fork Mios VERASECURE
R
How to launch an API code on the VERASECURE? The current scripts are obsolete (SMSCODE). Is there a firmware FORK for the VERASECURE?
Vera/openLuup plugins
Virtual HTTP Devices plug-in: slight start up bug
A
On start up the log indicates the following: 2023-12-19 10:17:12.588 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","",209) old value "" 2023-12-19 10:17:12.589 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelTarget","",209) old value "" 2023-12-19 10:17:12.589 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelStatus","",209) old value "" 2023-12-19 10:17:12.589 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","LoadLevelLast","",209) old value "" 2023-12-19 10:17:12.589 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","TurnOnBeforeDim","",209) old value "" 2023-12-19 10:17:12.590 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:upnp-org:serviceId:Dimming1","AllowZeroLevel","",209) old value "" 2023-12-19 10:17:12.590 luup_log:209: VirtualDevices[3.0-beta7@209](setVar@104):setVar("urn:bochicchio-com:serviceId:VirtualBinaryLight1","SetBrightnessURL","",209) old value "" 2023-12-19 10:17:12.590 luup_log:209: VirtualDevices[3.0-beta7@209](initializeMqtt@421):initializeMqtt(209,{ PowerStatusOff={ Value="0", Service="urn:upnp-org:serviceId:SwitchPower1", Variable="Status" }, BrightnessValue={ Variable="LoadLevelStatus", Service="urn:upnp-org:serviceId:Dimming1" }, PowerStatusOn={ Value="1", Service="urn:upnp-org:serviceId:SwitchPower1", Variable="Status" } }) - openLuup: true 2023-12-19 10:17:12.591 luup_log:209: VirtualDevices[3.0-beta7@209](subscribeToMqtt@414):subscribeToMqtt(209,nil,{ deviceID=209, opts={ Value="0", Service="urn:upnp-org:serviceId:SwitchPower1", Variable="Status" } }) 2023-12-19 10:17:12.591 openLuup.context_switch:: ERROR: [dev #209] ./L_VirtualLibrary.lua:415: attempt to concatenate field 'topic' (a nil value) 2023-12-19 10:17:12.591 openLuup.scheduler:: job aborted : ./L_VirtualLibrary.lua:415: attempt to concatenate field 'topic' (a nil value) The MQTT variables are all set to "skip": MQTT_BrightnessValue MQTT_PowerStatusOff MQTT_PowerStatusOn However it looks like the code doesn't check for "skip" and executes the functions initializeMqtt() and subscribeToMqtt() disappearing into the weeds at that point as there is nothing to subscribe to. It would also be good if the code treated an empty string in the same way as it uses the key word "skip". It's not obvious that "skip" needs to be explicitly used.
Vera/openLuup plugins
RulesEngine
DesTD
@akbooer not sure if it's related to openLuup or ALTUI... But since a couple of update (both openLuup and ALTUI), some basic function in RulesEngine are not working, like "saving" a rule after an edit and also "deleting" a rule... It's probably "javascript" related
Vera/openLuup plugins
SiteSensor > how to fill in Value Expressions (json data) SOLVED !
M
I still use Vera controllers in combination with ReactorSensors. I have several Reactor sensors in use to retrieve weather data from Wunderground (i have a personal weather station), my smartmeter etc. Recently I installed solar panels with a SolarEdge inverter. SolarEdge has an API to retrieve my power production data from their cloud. Output is in json. So I created a new Reactor Sensor. Connection is working (query okay). But I encounter problems at the Value Expressions. Either I get ""query okay" but no data or I get "query okay but 1 expressions failed" This is the json output {"overview":{"lastUpdateTime":"2023-05-12 10:45:57","lifeTimeData":{"energy":476310.0,"revenue":216.577},"lastYearData":{"energy":433001.0},"lastMonthData":{"energy":433001.0},"lastDayData":{"energy":8262.0},"currentPower":{"power":5647.0},"measuredBy":"INVERTER"}} So it has different layers/levels. I tried to put in the Value Expressions field several combinations to get the energy data of today (8262.0), like: response.lastDayData.energy response.overview.lastDayData.energy response.overview.lastUpdateTime.lastDayData.energy all fail... Who can help me with this ?
Vera/openLuup plugins
When turning off the dimmer, set the LoadLevelLast to 100%
E
Topic thumbnail image
Vera/openLuup plugins
Netatmo – Oath2 login
akbooerA
Just seen notification to Netatmo developers that the current password-based login is being disabled as from October. Oath2 is now a requirement for apps needing access to Netatmo. This will require some changes to my venerable plug-in. I’m not sure how easy this will be with the current libraries in use. Does anyone out there use the Netatmo plug-in? Does anyone have any advice on using Oath2?
Vera/openLuup plugins
Alexa TTS volume does not update as expected
CatmanV2C
Topic thumbnail image
Vera/openLuup plugins
Vera Alexa down?
CatmanV2C
Anyone else seeing issues with Vera TTS? All was working fine. I assumed the cookie had expired, but even having replaced it, and seeing that the .alexa.login file is aging (as I'd expect) No speech. I seem to be getting an odd timeout but no idea from where. Debian Bullseye, bare metal Good call from this morning: 2023-01-18 08:22:51.657 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a2345e8 2023-01-18 08:22:51.667 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e89df13d8 2023-01-18 08:22:51.668 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=31085221&MinimumDelay=50&output_format=json&_r=1674030171666 HTTP/1.1 tcp{client}: 0x563e89df13d8 2023-01-18 08:22:58.223 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a4ab388 2023-01-18 08:22:58.223 openLuup.server:: GET /data_request?Text=Rachel%20has%20arrived%20at%20Washtec&Language=en-GB&GroupZones=Everywhere&Volume=50&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action= Say&output_format=json&_r=1674030178221 HTTP/1.1 tcp{client}: 0x563e8a4ab388 2023-01-18 08:22:58.224 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.Say 2023-01-18 08:22:58.224 luup_log:22: VeraAlexa: addToQueue: added to queue for 22 2023-01-18 08:23:09.379 luup.variable_set:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.LatestResponse was: sending cmd:speak:<s><lang xml:lang="en-UK"><amazon:domain name="conversational">The temperature outside is -3 degr... now: sendi ng cmd:speak:<s>Rachel has arrived at Washtec</s><break time="0s" /> to dev:Everywhere type:A3C9PE6TNYLTCH ser... #hooks:0 2023-01-18 08:23:09.381 openLuup.server:: request completed (29 bytes, 1 chunks, 11156 ms) tcp{client}: 0x563e8a4ab388 2023-01-18 08:23:09.391 luup.variable_set:: 25001.urn:micasaverde-com:serviceId:SecuritySensor1.Tripped was: 0 now: 1 #hooks:0 2023-01-18 08:23:09.391 luup.variable_set:: 25001.urn:micasaverde-com:serviceId:SecuritySensor1.LastTrip was: 1674030032 now: 1674030189 #hooks:0 2023-01-18 08:23:09.394 openLuup.server:: request completed (1389 bytes, 1 chunks, 31782 ms) tcp{client}: 0x563e897eefd8 2023-01-18 08:23:09.395 openLuup.server:: request completed (1389 bytes, 1 chunks, 31662 ms) tcp{client}: 0x563e8a7c5248 2023-01-18 08:23:09.396 openLuup.server:: request completed (1389 bytes, 1 chunks, 17728 ms) tcp{client}: 0x563e89df13d8 2023-01-18 08:23:09.396 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a4ab388 2023-01-18 08:23:09.411 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.412 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.412 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e89df13d8 2023-01-18 08:23:09.413 openLuup.server:: GET /data_request?newTargetValue=1&DeviceNum=20330&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ASwitchPower1&action=SetTarget&output_format=json&_r=1674030189410 HTTP/1.1 tcp{client}: 0x563e 8a13f3c8 2023-01-18 08:23:09.413 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=31085224&MinimumDelay=50&output_format=json&_r=1674030189411 HTTP/1.1 tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.413 luup.call_action:: 20330.urn:upnp-org:serviceId:SwitchPower1.SetTarget 2023-01-18 08:23:09.413 luup.call_action:: action will be handled by parent: 37 2023-01-18 08:23:09.413 luup.variable_set:: 20330.urn:upnp-org:serviceId:SwitchPower1.Target was: 1 now: 1 #hooks:0 2023-01-18 08:23:09.449 openLuup.server:: request completed (35 bytes, 1 chunks, 36 ms) tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.461 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a13f3c8 2023-01-18 08:23:09.564 openLuup.server:: request completed (819 bytes, 1 chunks, 151 ms) tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.569 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x563e8a79f3c8 2023-01-18 08:23:09.581 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x563e8a32bf28 Bad request from just now: 2023-01-18 18:29:26.695 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557239889e58 2023-01-18 18:29:26.696 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66503545&MinimumDelay=50&output_format=json&_r=1674066566691 HTTP/1.1 tcp{client}: 0x557239889e58 2023-01-18 18:29:26.799 openLuup.server:: request completed (833 bytes, 1 chunks, 2249 ms) tcp{client}: 0x557239a62f78 2023-01-18 18:29:26.911 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66503545&Timeout=60&MinimumDelay=1500&_=1674030721531 HTTP/1.1 tcp{client}: 0x5572385f78d8 2023-01-18 18:29:27.028 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x557238b98c58 2023-01-18 18:29:27.029 openLuup.server:: GET /data_request?Text=Testing...1...2...3&Language=en-GB&GroupZones=Everywhere&Volume=50&DeviceNum=22&id=action&serviceId=urn%3Abochicchio-com%3AserviceId%3AVeraAlexa1&action=Say&output_format=json&_r=1674066567027 HTTP/1.1 tcp{client}: 0x557238b98c58 2023-01-18 18:29:27.029 luup.call_action:: 22.urn:bochicchio-com:serviceId:VeraAlexa1.Say 2023-01-18 18:29:27.029 luup_log:22: VeraAlexa: addToQueue: added to queue for 22 2023-01-18 18:29:43.149 openLuup.server:: error 'closed' sending 4 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 29 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: error 'closed' sending 5 bytes to tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.150 openLuup.server:: ...only 0 bytes sent 2023-01-18 18:29:43.150 openLuup.server:: request completed (29 bytes, 1 chunks, 16121 ms) tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: device is not a sensor or if a sensor; is not coded for 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: veraId: 64, blId: a0:43:b0:8b:e0:e5, altId: a0:43:b0:8b:e0:e5_ir 2023-01-18 18:29:43.153 luup_log:63: BroadLink_Mk2 debug: RM3 Mini - IR 1: urn:schemas-micasaverde-com:device:IrTransmitter:1 2023-01-18 18:29:43.154 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=66503545&Timeout=60&MinimumDelay=1500&_=1674066518681 HTTP/1.1 tcp{client}: 0x557239a62f78 2023-01-18 18:29:43.155 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557238b98c58 2023-01-18 18:29:43.157 openLuup.server:: request completed (591 bytes, 1 chunks, 16460 ms) tcp{client}: 0x557239889e58 2023-01-18 18:29:43.161 openLuup.io.server:: HTTP:3480 connection closed openLuup.server.receive closed tcp{client}: 0x557239889e58 2023-01-18 18:29:43.175 openLuup.io.server:: HTTP:3480 connection from 192.168.70.249 tcp{client}: 0x5572399f30e8 2023-01-18 18:29:43.176 openLuup.server:: GET /data_request?id=status&Timeout=15&DataVersion=66503545&MinimumDelay=50&output_format=json&_r=1674066583172 HTTP/1.1 tcp{client}: 0x5572399f30e8 2023-01-18 18:29:57.979 luup.variable_set:: 20380.urn:upnp-org:serviceId:TemperatureSensor1.CurrentTemperature was: 22 now: 21 #hooks:0 Any thoughts? Cheers C
Vera/openLuup plugins
Windows script/application to trigger Zwave devices
V
Hello, I'm looking for a way to create a script/executable file I can launch from my Loupedeck controller that will trigger outlets on a Zwave power strip. Can anyone point me to some info on how to do this? I'm using a VeraPlus controller Thanks
Vera/openLuup plugins
SiteSensor: get data from Wunderground suddenly stopped
M
Topic thumbnail image
Vera/openLuup plugins
Virtual HTTP Devices plug-in - light bulb status
A
Virtual HTTP Devices plug-in: I wanted to try this out. Installed the plugin and created one device, which came up as a light bulb. So far so good. In AltUI I clicked on the On/Off slider on the page. The log shows that the Target is set to one. Likewise for the Variable list in AltUI. However the Status never gets set to one and the light bulb icon doesn't go yellow. In some plugins you set the Target and then the plugin checks the physical device actually went on by checking an actual status report from the device, which can be used to set the variable Status. In other cases a plugin will send a message to the physical device but that device will have no status feedback mechanism available. So the Status variable has to be set locally when the Target is set and everybody hopes the physical device all worked. Not to sure what Virtual HTTP Devices plug-in does in this regard? Does the above go in anyway to explaining what I'm seeing? Is the plugin looking for status feedback?
Vera/openLuup plugins
Device issues in Open Luup
CatmanV2C
I have a couple of issue with Openluup ATM. I'm going to work through them in the order that they appeared if that's OK OpenLuup on bare metal (Debian Bullseye) running Z-way server and Z-wave.me Issue: I deleted a (I think) virtual switch in OpenLuup Now when I call up all devices I have this in a 'tile' Error displaying device 0-20510 - urn:schemas-upnp-org:device:BinaryLight:1 nil is not defined And below (in room 101) ReferenceError: nil is not defined at eval (eval at evaluateConditions (http://192.168.70.249:3480/J_ALTUI_verabox.js:960:18), :1:1) at Object.evaluateConditions (J_ALTUI_verabox.js:960:18) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_verabox.js:1642:37) at Object._evaluateConditions [as evaluateConditions] (J_ALTUI_multibox.js:629:89) at Object. (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2572:23) at Function.each (https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js:2:2976) at _getDeviceIconPath (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2569:10) at _deviceIconHtml (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2739:18) at _internalDeviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2765:19) at _deviceDraw (http://192.168.70.249:3480/J_ALTUI_uimgr.js:2840:4) Any ideas from anyone? Full reboot has been done.... Cheers C
Vera/openLuup plugins
I need help with Reactor for VERA.
B
I've been trying to figure out Reactor but I'm not very good at programming. I have two scenes in VERA. One scene should only run during the DAY and then stop running. One scene should only run during the NIGHT and then stop running. My scenes start off at the right times, but they do not turn off. I created a Sunrise/Sunset Reactor trigger and added it as a condition to each of my scenes. However, the Reactor trigger when tripping or untripping does not prevent my Vera scenes from running. It will start them correctly the first day, but after that, both scene stay running and fight with each other. What am I doing wrong? Thanks for any help! If you are interested, here are the actions I wish to perform with each scene. FARM STAND - DAY (runs at Sunrise) Turn ON a device called LETTUCE LAMP 2a) Every 60 min, turn ON a device called LETTUCE PUMP 2b) Wait 15 min then turn OFF a device called LETTUCE PUMP FARM STAND - NIGHT (runs at Sunset) Turn OFF a device called LETTUCE LAMP 2a) Every 135 min, turn ON a device called LETTUCE PUMP 2b) Wait 15 min then turn OFF a device called LETTUCE PUMP This sounds simple, but I cannot figure out how to disable these scenes when the theyre not supposed to run.
Vera/openLuup plugins
Anyone with Reactor experience? Will this work?
B
Topic thumbnail image
Vera/openLuup plugins
Reactor 3.9develop-21009.1600 ALTUI Error
PablaP
Topic thumbnail image
Vera/openLuup plugins
Latest ALTUI version brakes Reactor
M
FYI. Recently a new ALTUI version got pushed out, release 2553. After the update Reactor is no longer showing any of the Control panels in a sensor. looking at the ALTUI changes they seem minimal so in J_ReactorSensor_UI7.js I upped the _MAX_ALTUI_VERSION to 2553 and all seems to be working again.
Vera/openLuup plugins
Broadlink setup
CatmanV2C
Good evening, all. Is there a simple readme to set up and use a Broadlink device with OpenLuup? The readme on github points to a thread on the old forum, and thence to a rabbit hole. Is it just a case of adding IP address of the device? Or does it need the MAC? Then how do I fire commands? It looks like I need to find the codes and send via Lua? TIA C
Vera/openLuup plugins
Virtual Sensor Polling
B
Hi Patrick, A quick question about your virtual sensor plugin. I saw that the child sensors rely on polling for sensor data updates. Was there a reason not to use a watch on the underlying (source) state variable as opposed to polling. I'm asking in the sense that I need a fairly rapid response to a rise in humidity, but am unsure how to set sensor polling without adding additional io drag to openLuup. I currently use the state humidity variable directly in a reactor sensor (the data is captured via a bluetooth device with multiple humidity variables), however, these state humidity variables have a generated name making it difficult to determine what is what in group of approximately 10 state humidity variables. So a virtual sensor solves the naming problem, while creating some trigger delay due to polling. Thx
Vera/openLuup plugins
Reactor - Unable to update device information database
Z
@toggledbits I have Reactor running under openLuup (which is running inside vwout's Docker container). On the activities tab, it tells me I should update to a newer version of the device information database. When I go to the Tools tab, for a fraction of a second I can see the green "Update Device Info" button along with the Troubleshooting & Support and Device Spy sections. But after that fraction of a second, they disappear and I only see the Test Tools and Update Device Information Database sections, to just above where the Green button used to be. I've tried this on both Edge and Firefox with the same behavior (with extensions both on and off). Any suggestions?
Vera/openLuup plugins

External Temp Sensor w/ Thermostat

Scheduled Pinned Locked Moved Vera/openLuup plugins
19 Posts 3 Posters 1.2k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #1

    Hello all, I have a thermostat in a hallway that controls the whole upstairs floor and my room seems to get way warmer than the hallway its located in. I am not able to move the thermostat, neither are there any external temperature probes available that connect directly to the thermostat.

    I had an extra Z wave temp sensor lying around so thought I'd place that in my room and use that somehow in place of the internal temp sensor in the hallway.

    I can't seem to think of a good way to go about this, my original plan was to use either the AVT plugin or the Virtual Devices plugin but to my knowledge they won't work they way I intend them to. So I resorted to using Reactor, but that may become very tricky since I will need to put in a lot of fail safes to make sure the heating/cooling turns on/off when expected.

    Does anyone have any ideas on how to go about this? Every time I come up with a possible solution, I always find a way that it could fail and either not turn the a/c off/on.

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      You're unlikely to get the thermostat to directly honor your external sensor. I would think about using the external sensor to manipulate the setpoint on the thermostat to force heating to run (or not). Also, if the differential between the hallway and the room is consistent, even across season, a "behavior" change on the part of the humans (different setpoint) may be all that's needed.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      1 Reply Last reply
      0
      • PablaP Offline
        PablaP Offline
        Pabla
        wrote on last edited by
        #3

        I was thinking of creating a virtual thermostat which uses the external temp sensor as its own temp sensor, and then have the setpoints on the virtual thermostat manipulate the set points on the physical hallway thermostat.

        For example if the room temperature is at 23 degrees, and the hallway is at 19, I would set the virtual thermostat to 20 degrees then with some Reactor trickery I could set the setpoint on the hallway thermostat to something absurdly cold so that it an trigger the a/c on (regardless of hallway ambient temp) until the room reaches the desired temp. From there then set the hallway thermostat back to either its pervious setpoint so that the a/c can turn off. I think that may be a possible solution, I can't think of any issues unless the hallway temp gets as low as the setpoint, but the temperature differential isn't that much.

        therealdbT 1 Reply Last reply
        0
        • PablaP Pabla

          I was thinking of creating a virtual thermostat which uses the external temp sensor as its own temp sensor, and then have the setpoints on the virtual thermostat manipulate the set points on the physical hallway thermostat.

          For example if the room temperature is at 23 degrees, and the hallway is at 19, I would set the virtual thermostat to 20 degrees then with some Reactor trickery I could set the setpoint on the hallway thermostat to something absurdly cold so that it an trigger the a/c on (regardless of hallway ambient temp) until the room reaches the desired temp. From there then set the hallway thermostat back to either its pervious setpoint so that the a/c can turn off. I think that may be a possible solution, I can't think of any issues unless the hallway temp gets as low as the setpoint, but the temperature differential isn't that much.

          therealdbT Offline
          therealdbT Offline
          therealdb
          wrote on last edited by
          #4

          @pabla I think you could just use the temperature in general, if you’re using a time schedule (very common in Europe, not so common in US/Canada, from my previous trips). We usually have our thermostats set to both temperature and time windows. Maybe a simpler approach like this could also work.

          A more fancy one is to watch for temperatures, make an average and lower the set point, so you’ll get a better feeling. I will not lower it too much, to avoid the feeling of being in a freezer 🥶

          --
          On a mission to automate everything.

          My MS Reactor contrib
          My Luup Plug-ins

          1 Reply Last reply
          0
          • PablaP Offline
            PablaP Offline
            Pabla
            wrote on last edited by
            #5

            The issue with scheduling is that with our weather here its sometimes 28 degrees then the next day it will be 9 degrees so some days a/c isn't even needed.

            I think I have figured out how to go about this:

            -Create a virtual thermostat
            -Tie the temp reading to the room temp sensor (if that's possible)
            -Set a Reactor condition to turn on cooling when the set point of the virtual thermostat is below the room temp

            The only issue I am running into is creating the virtual thermostat, I created it but I cannot change the thermostat's mode. Would I need to create a custom device file type to create a functional virtual thermostat?

            therealdbT 1 Reply Last reply
            0
            • PablaP Pabla

              The issue with scheduling is that with our weather here its sometimes 28 degrees then the next day it will be 9 degrees so some days a/c isn't even needed.

              I think I have figured out how to go about this:

              -Create a virtual thermostat
              -Tie the temp reading to the room temp sensor (if that's possible)
              -Set a Reactor condition to turn on cooling when the set point of the virtual thermostat is below the room temp

              The only issue I am running into is creating the virtual thermostat, I created it but I cannot change the thermostat's mode. Would I need to create a custom device file type to create a functional virtual thermostat?

              therealdbT Offline
              therealdbT Offline
              therealdb
              wrote on last edited by
              #6

              @pabla yes, you’ll need an implementation file. I have one for heaters, but I’ve never found the motivation to do a cooler. It should be easy to do.

              --
              On a mission to automate everything.

              My MS Reactor contrib
              My Luup Plug-ins

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                Well, you can use AVT for that. There are state variables in AVT when heating and cooling are called that you can react to in Reactor. And AVT will use your external temp sensor, of course.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                PablaP 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Well, you can use AVT for that. There are state variables in AVT when heating and cooling are called that you can react to in Reactor. And AVT will use your external temp sensor, of course.

                  PablaP Offline
                  PablaP Offline
                  Pabla
                  wrote on last edited by
                  #8

                  @toggledbits that was the plan but the only issue with AVT is it doesn’t work through the mobile app well.

                  1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #9

                    Yeah, but it's open source, so you could take the code and just the standard device type and static JSON rather than the custom versions. I can't do that with the plugin because it would break existing users, but there's nothing stopping you from using it. No need to start from scratch.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    PablaP 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      Yeah, but it's open source, so you could take the code and just the standard device type and static JSON rather than the custom versions. I can't do that with the plugin because it would break existing users, but there's nothing stopping you from using it. No need to start from scratch.

                      PablaP Offline
                      PablaP Offline
                      Pabla
                      wrote on last edited by
                      #10

                      @toggledbits Okay so I took the original AVT device and changed the device type to urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1 , device file toD_HVAC_ZoneThermostat1.xml and device json to D_HVAC_ZoneThermostat1.json . The device now shows up like a regular thermostat but no longer can change its mode from off to anything else

                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #11

                        Are you on Vera or openLuup?

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        1 Reply Last reply
                        0
                        • PablaP Offline
                          PablaP Offline
                          Pabla
                          wrote on last edited by
                          #12

                          Vera 7.32 beta

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by toggledbits
                            #13

                            OK. I took a dig in myself, and it still needs some additional support because so much of the "logic" is actually hard-coded in UI7.

                            I've put together just a prototypical modification to AVT that makes AVT itself a master device (interface only) that creates a single child device that is a dual-setpoint native thermostat type. If and only if you are not using AVT currently, you can install this hacked version and I'll help you get it running and stabilized. Do not run this version if you use AVT otherwise, as it will break all existing AVT devices.

                            To install:

                            1. Click link for "devicetype" branch of the project on Github: https://github.com/toggledbits/AutoVirtualThermostat/tree/devicetype
                            2. Click the green "Code" button and choose "Download ZIP"
                            3. Unzip the downloaded archive to a spot on your local system.
                            4. Open the uploader at Apps > Develop apps > Luup files
                            5. Drag the unzipped files (not the folder) as a group to the "Upload" button. Wait for the upload and Luup reload to complete.
                            6. Now, for first-time install, go to Apps > Develop apps > Create Device
                            7. Enter AVT Plugin or something in the "Description" field.
                            8. Enter (exactly--use copy/paste) in the "Upnp Device Filename" field: D_AutoVirtualThermostat1.xml
                            9. Hit the "Create device" button.
                            10. Go the Apps > Develop apps > Test Luup code (Lua) and run luup.reload()
                            11. There will be two reloads, one that you just initiated, and another by the plugin when it creates the child device. Wait for these to complete.
                            12. Hard refresh your browser. You should then see a "AVT Plugin" (or whatever you called it above) device, and a "Generic Virtual Thermostat', which is the generic-typed child.

                            Now, you need to configure the child device ("Generic Virtual Thermostat") with your temperature sensor. There is no UI for this version of AVT. Go into the Generic Virtual Thermostat's control panel, to Advanced > Variables and find TempSensors. Put the temperature sensor device number in there (if you have more than one you are going to use/average, put them in comma-separated). Then... reload Luup again.

                            The built-in (Vera UI7) web UI for the generic type dual setpoint thermostat has some bugs, but generally works well enough. The mode you are in determines which setpoints are settable (e.g. in "Auto" both, in "Heat" heat only). Setting the setpoint via the up-down controls works, but editing them by clicking on the setpoint and editing the value does not (that's a UI7 bug--it doesn't send an event when you exit the field, so the edit never takes); no workaround possible.

                            On the Vera Mobile app side, setting the temperature while in AUTO mode presents only one setpoint control and doesn't work, so to set the heat setpoint, go into Heat mode and set it, and to set the cooling setpoint, go into Cool mode and set it. Then go back to Auto mode if that's what you want. I'll play with that the mobile app thinks its doing and see if I can come up with a sensible workaround.

                            Finally, one other restriction, since I was running fast to make these changes, only one child device is supported at the moment.

                            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                            PablaP 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              OK. I took a dig in myself, and it still needs some additional support because so much of the "logic" is actually hard-coded in UI7.

                              I've put together just a prototypical modification to AVT that makes AVT itself a master device (interface only) that creates a single child device that is a dual-setpoint native thermostat type. If and only if you are not using AVT currently, you can install this hacked version and I'll help you get it running and stabilized. Do not run this version if you use AVT otherwise, as it will break all existing AVT devices.

                              To install:

                              1. Click link for "devicetype" branch of the project on Github: https://github.com/toggledbits/AutoVirtualThermostat/tree/devicetype
                              2. Click the green "Code" button and choose "Download ZIP"
                              3. Unzip the downloaded archive to a spot on your local system.
                              4. Open the uploader at Apps > Develop apps > Luup files
                              5. Drag the unzipped files (not the folder) as a group to the "Upload" button. Wait for the upload and Luup reload to complete.
                              6. Now, for first-time install, go to Apps > Develop apps > Create Device
                              7. Enter AVT Plugin or something in the "Description" field.
                              8. Enter (exactly--use copy/paste) in the "Upnp Device Filename" field: D_AutoVirtualThermostat1.xml
                              9. Hit the "Create device" button.
                              10. Go the Apps > Develop apps > Test Luup code (Lua) and run luup.reload()
                              11. There will be two reloads, one that you just initiated, and another by the plugin when it creates the child device. Wait for these to complete.
                              12. Hard refresh your browser. You should then see a "AVT Plugin" (or whatever you called it above) device, and a "Generic Virtual Thermostat', which is the generic-typed child.

                              Now, you need to configure the child device ("Generic Virtual Thermostat") with your temperature sensor. There is no UI for this version of AVT. Go into the Generic Virtual Thermostat's control panel, to Advanced > Variables and find TempSensors. Put the temperature sensor device number in there (if you have more than one you are going to use/average, put them in comma-separated). Then... reload Luup again.

                              The built-in (Vera UI7) web UI for the generic type dual setpoint thermostat has some bugs, but generally works well enough. The mode you are in determines which setpoints are settable (e.g. in "Auto" both, in "Heat" heat only). Setting the setpoint via the up-down controls works, but editing them by clicking on the setpoint and editing the value does not (that's a UI7 bug--it doesn't send an event when you exit the field, so the edit never takes); no workaround possible.

                              On the Vera Mobile app side, setting the temperature while in AUTO mode presents only one setpoint control and doesn't work, so to set the heat setpoint, go into Heat mode and set it, and to set the cooling setpoint, go into Cool mode and set it. Then go back to Auto mode if that's what you want. I'll play with that the mobile app thinks its doing and see if I can come up with a sensible workaround.

                              Finally, one other restriction, since I was running fast to make these changes, only one child device is supported at the moment.

                              PablaP Offline
                              PablaP Offline
                              Pabla
                              wrote on last edited by
                              #14

                              @toggledbits First off thanks for helping me out, this is great!

                              Everything went smoothly until I set the TempSensors variable. I set it to 53 which is the room temperature sensor and did multiple reloads and hard refreshes but the inside temp on the generic thermostat still shows 0 degrees.

                              1 Reply Last reply
                              0
                              • toggledbitsT Offline
                                toggledbitsT Offline
                                toggledbits
                                wrote on last edited by
                                #15

                                If you look in the log, it will log what it thinks about the sensor. Look for the strings "Found 1 valid sensors" and "No valid sensors". I suspect you're getting the latter, and that's usually because your sensor hasn't updated within the "sanity" check periods (in case of dead battery). Handling that is documented in the regular README for AVT at the link given in step 1 above.

                                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                PablaP 1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  If you look in the log, it will log what it thinks about the sensor. Look for the strings "Found 1 valid sensors" and "No valid sensors". I suspect you're getting the latter, and that's usually because your sensor hasn't updated within the "sanity" check periods (in case of dead battery). Handling that is documented in the regular README for AVT at the link given in step 1 above.

                                  PablaP Offline
                                  PablaP Offline
                                  Pabla
                                  wrote on last edited by Pabla
                                  #16

                                  @toggledbits that looks like what is happening. I guess I will wait for the sensor to update

                                  50 06/10/21 10:39:31.102 luup_log:69: AutoVirtualThermostat: Sensor "53" ("Master Bedroom Temperature") ineligible, last battery report 1623306414 (time 23:26:54) is more than 7200 ago <0x748aa520>

                                  01 06/10/21 10:39:31.103 luup_log:69: AutoVirtualThermostat: No valid sensors. <0x748aa520>

                                  1 Reply Last reply
                                  0
                                  • PablaP Offline
                                    PablaP Offline
                                    Pabla
                                    wrote on last edited by
                                    #17

                                    Since this is a battery operated sensor, I can't have it update every 2 hours. Is it possible to override the 7200 second fail safe? The actual temperature in my past experience updates more often than battery dates since I think battery dates only update with a wake up.

                                    1 Reply Last reply
                                    0
                                    • toggledbitsT Offline
                                      toggledbitsT Offline
                                      toggledbits
                                      wrote on last edited by
                                      #18

                                      Yes, the docs linked from the README describe this.

                                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                      1 Reply Last reply
                                      0
                                      • PablaP Offline
                                        PablaP Offline
                                        Pabla
                                        wrote on last edited by
                                        #19

                                        Duh, the docs have all the info I need. Looks like everything is now up and running thanks!!!

                                        1 Reply Last reply
                                        1
                                        Reply
                                        • Reply as topic
                                        Log in to reply
                                        • Oldest to Newest
                                        • Newest to Oldest
                                        • Most Votes


                                        Recent Topics

                                        • Limit HA Entity in MSR
                                          toggledbitsT
                                          toggledbits
                                          0
                                          5
                                          47

                                        • Reactor (Multi-System/Multi-Hub) Announcements
                                          toggledbitsT
                                          toggledbits
                                          5
                                          121
                                          35.2k

                                        • Disaster recovery and virtualisation
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          5
                                          584

                                        • Remote access of Zwave stick from Z-wave server
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          3
                                          306

                                        • Organizing/ structuring rule sets and rules
                                          G
                                          gwp1
                                          0
                                          5
                                          348

                                        • Moving MSR from a QNAP container to RP 5 - some issues
                                          G
                                          gwp1
                                          0
                                          5
                                          296

                                        • Widget deletion does not work and landing page (status) is empy
                                          G
                                          gwp1
                                          0
                                          4
                                          266

                                        • Need help reducing false positive notifications
                                          T
                                          tamorgen
                                          0
                                          7
                                          461

                                        • Deleting widgets
                                          toggledbitsT
                                          toggledbits
                                          0
                                          4
                                          440

                                        • MQTT configuration question
                                          tunnusT
                                          tunnus
                                          0
                                          11
                                          592
                                        Powered by NodeBB | Contributors
                                        Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                        • Login

                                        • Don't have an account? Register

                                        • Login or register to search.
                                        • First post
                                          Last post
                                        0
                                        • Categories
                                        • Recent
                                        • Tags
                                        • Popular
                                        • Unsolved