-
Not sure this is in quite the right place (again) but I have a device that exists in z-way that I simply cannot remove. It seems to be a zombie. I have no idea what it was. It claims to be a routing binary sensor that has not woken up since August I go through the 'Only do this if your device is broken' and it simply will not go. Any ideas (apart from ignore it)? Cheers C
-
Hi all Possibly a long shot - but does anyone know of a way, (maybe you have some code or know of an app) that can help you discover the IR codes of a device when you’ve lost the remote? Looking online there seems to be a growing number of IR banks, yet I can’t find anything on the market that could cycle through a huge set of different codes (e.g just the power on/off) to let me know which ones are compatible ? When you consider so many things these days are made in the same place, and often thing can just be re/badges versions of other items - it’s likely that a sets of codes for one branded product will work in the most part with another ..
-
Since one member asked at one point about the "front end" and "back end", I drew this showing the controller from the base to the tip along with what I have found to be the best options from my testing. Almost every controller will try to integrate all elements, especially commercial ones but... they all have strengths and weaknesses so if one can have a medley of the best ones...
-
Hi all. Looking for some guidance as ever This luup.inet.wget('https://api.telegram.org/bot1225075966:AAHS5rwhCpOx0hwq3mOnNjtCSKiDeAS6B4/sendMessage?chat_id=@Coalport58&text=House mode is home') Works fine This luup.inet.wget('https://api.telegram.org/bot1225075966:AAHS5rwhCpOx0hwq3mOnNjtCSKiDeAS6B4/sendMessage?chat_id=@Coalport58&text=House mode is Home') Throws a 400 error: openLuup.client:: WGET error status: 400 I have munged the bot key to post here, but just changing the 'h' to 'H' breaks it. Any ideas why? C
-
We are a smart home startup based in England, we are looking for a co-founder/advisor who is good at iot software development. Many thanks
-
What are the projects you're working on? Summer is over, and that (unfortunately) means more time indoor and (luckily) more time to build things. I have almost nothing in my backlog and it's boring I appreciate a couple of (crazy) ideas.
-
Is there one? I know TTS is working but suddenly woke up at 0300.... ...or does it just use Vera. That seems unlikely from what I know of the architecture TIA C
-
So, I'm trying to execute the same code I had for years to mount my synology NAS for datamine (I know, old stuff), but I'm getting this: mount -o user=vera,pass=pass //192.168.1.26/Backups/Vera/datamine /datamine mount: mounting //192.168.1.26/Backups/Vera/datamine on /datamine failed: No such device It used to work until 3 days ago, then I had to factory reset my Vera Plus and now this. Packages are OK: opkg update opkg --force-depends install kmod-fs-cifs opkg --force-depends install kmod-nls-utf8 kmod-nls-base kmod-crypto-hmac kmod-crypto-md5 kmod-crypto-misc I've already trying anything, with no luck. Any ideas?
-
My quest to build a central usb to serial server (hub) continues The goal is to make a core set of usually local devices available to other HA controllers over the network to use (via Ser2net). Current list includes .. Current Cost Energy Monitor Rfxtrx433 Transceiver Bluegiga BLED112 Bluetooth Next up is a Z-Wave Module ZMEEUZB1 What other devices do people think would be a good to add to the ‘hub’ ?
-
https://www.google.co.uk/url?sa=i&url=https%3A%2F%2Fpanic.com%2Fblog%2Fpanic-status-board-2013-edition%2F&psig=AOvVaw1ERsyah34ZkmLnpWaYLgu-&ust=1600418906446000&source=images&cd=vfe&ved=0CAIQjRxqFwoTCODol5Xn7-sCFQAAAAAdAAAAABAE I’ve always liked the idea of having a screen, located somewhere in the house that would allow me to see the status of pretty much everything. (Hardware wise I’m just think of a basic Rasp Pi, fixed to a vesa mount, screwed to the back of an old monitor screen) I’ve tried a number of tools/apps over the years, one of which was PanicBoard (where the above image comes from) - which seemed to have some potential, but the owners stopped developing/investing in that a while back. What are people using ? Is there something, perhaps a single tool/app that this community would collectively support/promote, one that no matter what HA you used, you could submit information to and have it displayed ? **** Just to be clear, I’m referring to status/information boards, not a touch based, control board where you can turn things on/off etc..***
-
I just noticed from other forums that IFTTT has started some serious payment plans with a very restrictive free tier. IFTTT Plans - IFTTT Find the right plan for Pros, Developers and Businesses. This was writing on the wall from the beginning and why I tested it for the entirety of 5mins and requested to delete my account back 3 years ago. The idea to me was mind boggling: Having a multitude of platform API integrated by them in the cloud so every signal and command would go through them. This outside dependency, could not remain free and would offer poor reliability security/privacy and performance by design and is intrinsically inefficient. Now if you want to continue using it, you get to pay for it.. What a waste of time and energy...
-
Sorry for the long title After building, for the want of a better term, a “Ser2net Server” in order to share various USB/Serial devices With Vera/Node-Red etc. I’ve recently added Bluegiga’s BLED112 Bluetooth (https://www.silabs.com/wireless/bluetooth/bluegiga-low-energy-legacy-modules/device.bled112) with the goal that I can integrate all the personal bluetooth devices worn in the house (i.e fitness trackers etc.) into some sort of presence awareness set-up. All my other usb/serial devices, such as a Current Cost energy monitor, DSC Alarm Panel and a RFCOM Rfxrtx433 transceiver which are connected are all working well, and with the ability to share each device I’ve been able to integrate them into the different HA solutions I use. So getting back to the point of my post, and with the BLED112 connected, I can access it via the pi no problem and using this .py script (. https://github.com/jrowberg/bglib/blob/master/Python/Examples/bled112_scanner.py) - so I can do a few things when logged into the pi, but what I’m struggling with at the moment is how to get clean information out via ser2net. Currently everything looks jumbled/corrupted and I’ve tried to change the Ser2net serial/connection settings for it but that hasn’t resulted in any noticeable improvements . Ser2net .conf settings. 4004:raw:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT max-connections=4 Is anyone on this forum using the BLED112 in any capacity today ? Ideally with Vera/OpenLuup ? Screenshot below of what’s seen via telnet (Remoter is the iOS app I’m using , but the N065H is a model of fitness band my wife has. And attached below is what seen from the pi when the python script is run.. Within the above you have the MAC of the Bluetooth device, plus the strength of the signal, so the makings of some good presence/range automation capabilities 🤩
-
General Information - I thought some of the regulars would like to register. Links down the bottom,Interesting that they are looking into the failures....wonder if there will be any mention of you know what..... Z-Wave Works With Amazon, Google, Samsung, Apple, Comcast Virtual Conference by DrZWave Silicon Labs is hosting what was intended to be an in-person conference in Austin Texas but is now a virtual online conference on IoT ecosystems - the Works With Smart Home Developer Event September 9-10. The best part is it is now FREE to attend any of the in-depth technical sessions and you don't have to wear a mask. The downside is that we don't get to experience all that great music down in Austin - well, there's always next year! Virtual IoT Works With EcoSystems from Google, Amazon, Apple for Z-Wave development engineers Works With Smart Home Developer Event - Silicon Labs Attend Works With Smart Home Developer Event virtually to learn how to work with ecosystem partners to connect devices, platforms and protocols. Live or on-demand. I am hosting the Z-Wave track and will be making several presentations including a detailed look at Silicon Labs latest release of Simplicity Studio V5 which just came out yesterday. We'll also have presentations on developing Z-Wave Smart Hubs and Z-Wave Certification. I'll also be describing some IoT failures - you learn more from your failures than your successes. We have speakers and engineers from all of the ecosystem partners, not just Silicon Labs folks. Learn from the experts from across the industry! What is Works With 2020? The smart home developer’s virtual event where you will have the opportunity to interact with our ecosystem partners from Amazon, Google, Samsung, and Z-Wave to connect devices, platforms and protocols and be able to immerse yourself in keynotes, a panel discussion on Project CHIP, hands-on, and technical sessions led by smart home engineers who are building the latest advanced IoT devices. The Works With event is live, all-online, free of charge, and you can join from anywhere around the world. Works With Z-Wave Apple, Google, Amazon, Samsung IoT SmartHome conference 2020 Click here to Register Today and feel free to forward to the rest of your team. Here’s an overview of what you won’t want to miss: Specialized Engineer-Led Tracks – Educational sessions and technical training designed for engineers, executives, developers, business development and product managers. Hands-On Workshops More than 12 workshops and hands-on sessions to give you experience, knowledge and confidence to develop and accelerate smart home development. One-on-One Developer Meetings – Schedule a meeting with Silicon Labs or an ecosystem partner to get 1:1 technical guidance. Join me in September and learn how to smoothly get your IoT device plugged into any and all of the ecosystem partners. Register today, it's totally free and you can join from anywhere in the world. See you September! DrZWave | July 30, 2020 at 8:22 pm | Tags: WorksWith | Categories: 700 series, Best Practice, Coding Guides, News, Presentations, Summit, Z-Wave Controllers, Z-Wave Developers, Z-Wave Mesh, Z-Wave Network, Z-Wave Slaves, Z-Wave Users | URL: https://wp.me/p6tsK6-o5 Comment See all comments Unsubscribe to no longer receive posts from DrZWave. Change your email settings at Manage Subscriptions. Trouble clicking? Copy and paste this URL into your browser: DrZWave / Jul 30 Z-Wave Works With Amazon, Google, Samsung, Apple, Comcast Virtual Conference Works With Amazon, Google, Apple and more Smart Home EcoSystem vendors. Learn how to design your product to work with these 800 pound gorillas
-
Derick Schweppe Mycroft – Open Source Voice Assistant - Mycroft Mycroft is an open source voice assistant, that can be installed on Linux, Raspberry Pi, or on the Mark 1 hardware device. Our opensource skills are written in Python and we have a very friendly developer community. Come join us! I have been following this project with great interest and am thinking about testing it. Eventually, I believe this is the way to go and will eliminate all the GH and Echo ecosystems.
-
I picked up a new WD SSD for practically next to nothing (wow, have prices on storage dropped) and want to replace the SDC in omy HS4 Pi that I added Node Red to. I know that a thread existed on this, perhaps on the Vera forum before it was censored. I can't find it here can anyone point me in the right direction. Thks
-
In the pseudo code below settimeout always times out after ten seconds. I can set the timeout to any value and it always times out when it reaches the set value. But why? The transmit is fine and the data is rx'ed OK exactly as expected. ie the expected data is always the length expected. There are no partial results. The only way to get it to work is to set the timeout to zero. ie no timeout delay and use socket.select to become a defacto timeout. It works great after that. -- Socket library version is: LuaSocket 3.0-rc1 m_tcp = socket.tcp() m_tcp:settimeout(10) -- set to zero when using socket.select fix m_tcp:connect('ip_address', port) repeat -- send request local txMsg('Data request. Hi what is the hardware status? (ongoing)') m_tcp:send(txMsg) -- THIS fixs the problem as long as m_tcp:settimeout() is set to zero -- Wait on the socket for 50 msec for rx data. -- The rx data will arrive in the rx buffer in less than this time. -- *** local rxlist, _, selectStatus = socket.select ({m_tcp}, nil, 0.05) -- get the response to the request -- get the 16 byte data header, that contains the length of the payload local expectedLength = 16 local s, status, partial = m_tcp:receive(expectedLength) if (status == "timeout") then print('timeout') end -- the returned data amount varies but we know what it is from the header just rx'ed expectedLength = s[1] s, status, partial = m_tcp:receive(expectedLength) -- do this every 0.5 sec; -- we're regularly updating the status of a hardware device luup.sleep(500) until false
-
Is there anyone out there that has contact with the admin(s) at the Z-wave.me forum? I registered about three weeks or so ago and did not get a authorization email and I have tried contacting the admin several times with no response. I have a question about my RaZberry I need to post. Regards.
-
Something interesting, Jul 2 Best Z-Wave dongle for Raspberry Pi 4 There is very little in the way of new “features” for controllers with the 700 Stick. Most of the “enhancements” are going to be around devices. So I don’t think you gain very much with 700 series controllers. I have had a zwave700 dongle to play with for some time and have eventually stopped as its firmware and API was not fully developed for controllers. Back then I was the first one to introduce it to the old place's devs. Now, looking closer into it, I have come to the same conclusion as this post I have linked above. Because the main benefits of the 700 series are range and power consumption, I understand now that it mostly benefits client devices and that controllers won't see much of any significant improvement if any. This would explains why silabs didn't really focus on developing a controller sdk/stack for these new chips. PS: fishwaldo is the author of openzwave and is considered a more than credible expert and authority in zwave.
-
Some of my favorite projects I have been using on my setup for over 5 years: Bridge the vera or openluup to amazon echo through a local hue emulator. A much faster solution than the vera native bloatware as the only cloud service is used by this alternative is the voice recognition. It was initiated for vera control but later expanded to many other platforms like the logitech Harmony and other controllers. No cloud to cloud so no need for mios servers: bwssytems/ha-bridge Home automation bridge that emulates a Philips Hue light system and can control other systems such as a Vera, Harmony Hub, Nest, MiLight bulbs or any other system that has an http/https/tcp/udp int... The equivalent for Apple Siri: Hackworth/VeraHomeKitBridge Contribute to Hackworth/VeraHomeKitBridge development by creating an account on GitHub. Alternative SONOS TTS implementation from all the plugin versions applicable for any platform since it is an API you can call. It is run also locally on a MacOS desktop in my case but can run on anything running nodeJS. For the TTS to be fully local though, you will need a mac or bear with the robotic voice of maryTTS. I have been hesitant to move my TTS to the amazon echos (project by @therealdb), but the echos lack synchronization and are cloud dependent which causes a 3-5s delay I do not have with this local solution, so this remains my choice: jishi/node-sonos-http-api An HTTP API bridge for Sonos easing automation. Hostable on any node.js capable device, like a raspberry pi or similar. - jishi/node-sonos-http-api Use my fork if you need to install on Catalina because some fixes are needed and my pull request from months ago has not yet been merged.
Reactor Oddity
-
Morning. As posted elsewhere, I've killed all my scenes and moved to Reactor.
One thing that is not quite working is my morning alarm. The idea (and the scene) was that the alarm clock device changes state, then triggers reactor to os.execute a script which curls to my volumio player. No biggy been working for years. Reactor seems unhappy and damned if I can see why:Specific screen shot:
Shows that the sensor has been false since 0530 June 11, but the log shows:
06 06/12/20 6:00:00.110 Device_Variable::m_szValue_set device: 141 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1591849810 now: 1591938000 #hooks: 0 upnp: 0 skip: 0 v:0xd04870/NONE duplicate:0 <0x74c87520> 06 06/12/20 6:00:00.121 Device_Variable::m_szValue_set device: 141 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 1 #hooks: 1 upnp: 0 skip: 1 v:0xd055a8/NONE duplicate:0 <0x74c87520> 08 06/12/20 6:00:00.363 JobHandler_LuaUPnP::HandleActionRequest device: 141 service: urn:upnp-org:serviceId:VClock1 action: GetAlarmTime <0x75287520> 06 06/12/20 6:01:32.490 Device_Variable::m_szValue_set device: 141 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: ArmedTripped was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0x12d0c38/DL_ARMEDTRIPPED duplicate:0 <0x76f73520> 06 06/12/20 6:01:32.491 Device_Variable::m_szValue_set device: 141 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: LastTrip was: 1591938000 now: 1591938092 #hooks: 0 upnp: 0 skip: 0 v:0x12d0a80/NONE duplicate:0 <0x76f73520> 06 06/12/20 6:01:32.492 Device_Variable::m_szValue_set device: 141 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 1 now: 0 #hooks: 0 upnp: 0 skip: 1 v:0x12d0950/NONE duplicate:0 <0x76f73520>That it tripped (as expected) at 0600 June 12th.
Any thoughts as to what I'm missing? I've tried with ArmedTripped as well, and that also didn't fire.
Logic summary
*************************************************** REACTOR LOGIC SUMMARY REPORT *************************************************** Version: 3.6 config 20070 cdata 20045 ui 20130 pluginDevice 109 LuaXP 1.0.2enh System: Vera version 1.7.4833 (7.30) on Sercomm G450 ID 36 (Vera Plus); loadtime 1591938067/1591938091; systemReady 1591938096; ALTUI v2.49 Env: Lua 5.1; JSON dkjson 1.2; UnsafeLua=1/true Local time: 2020-06-12T06:43:40+0100; DST=1; Harlow, England United Kingdom; formats %Y-%m-%d %H:%M:%S House mode: plugin 1; system 1; tracking on Sun data: { "source": "int", "civdawn": 1591930374, "nautdawn": 1591925888, "sunset": 1591993087, "nautdusk": 1592000446, "stamp": 2020164, "latitude": 51.76253, "astrodusk": null, "longitude": 0.134391, "civdusk": 1591995960, "astrodawn": null, "sunrise": 1591933248 } Geofence: not running RS: 1591734364,1591735539,1591737519,1591738125,1591766191,1591770523,1591770640,1591786032,1591786144,1591938091 NS: 0:X,1589293080:U,1589395800:D,1589395860:U,1590934920:D,1590935220:U ************************************************************************************************************************************ Bedroom Keypad (#132) Version 19082.114 06/11/20 06:05:02 Message/status: Not tripped Condition group "Master Bedroom Keypad" (AND) false as of 03-29.02:00:01 <root> &-F-group "Single press on button one (DAY)" (AND) false as of 04-19.07:43:04 <grpgsop1aj> | &-?-comment "Sets the house up for morning when the sun is up. 13 minute delay for showering" <condlcz902i> | &-F-group "Has Alexa triggered the shower" (OR) false as of 06-09.11:47:45 <grpso06xoi> | | |-F-service Shower_Trigger (257) urn:upnp-org:serviceId:SwitchPower1/Status = 1 [0 at 06-09.11:47:45; F/F as of 06-09.11:47:45/06-09.11:47:45] <condso07vu3> | | |-F-group "Or has button one been pressed" (AND) false as of 06-09.11:47:45 <grpso07bdg> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 1 [9 => 13 at 06-09.12:59:21; F/F as of 04-19.07:43:04/04-19.07:43:04] <condgsopmmy> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update ; output follow, delay reset for 30s [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:51] <condgsopzzi> | &-T-service Day or Night (26) urn:rts-services-com:serviceId:DayTime/Status = 1 [0 => 1 at 04:55:29; T/T as of 04:55:29/04:55:29] <condgsoqhi9> &-F-group "Single press on button one (NIGHT)" (AND) false as of 06-10.21:24:50 <grpgniuphh> | &-?-comment "Sets the house up for the morning when the sun has not risen. 13 minute delay for showering" <condlcz9wih> | &-F-group "Has Alexa triggered the shower" (OR) false as of 06-09.11:47:45 <grpso0a7si> | | |-F-service Shower_Trigger (257) urn:upnp-org:serviceId:SwitchPower1/Status = 1 [0 at 06-09.11:47:45; F/F as of 06-09.11:47:45/06-09.11:47:45] <condso0b46s> | | |-F-group "Or has button one been pressed" (AND) false as of 06-09.11:47:45 <grpso0af3p> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 1 [9 => 13 at 06-09.12:59:21; F/F as of 04-19.07:43:04/04-19.07:43:04] <condgniuzpf> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update ; output follow, delay reset for 30s [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:51] <condgnivjlq> | &-F-service Day or Night (26) urn:rts-services-com:serviceId:DayTime/Status = 0 [0 => 1 at 04:55:29; F/F as of 04:55:29/04:55:29] <condgniw190> &-F-group "Single press on button two or Alexa: Time to get up (DAY)" (AND) false as of 06:28:24 <grpgr2s3wv> | &-?-comment "Sets the house up for the morning when the sun has risen" <condqj3av4l> | &-F-group "grpqj3anz5" (OR) false as of 06:28:24 <grpqj3anz5> | | |-F-service Morning_Trigger (244) urn:upnp-org:serviceId:SwitchPower1/Status = 1 [1 => 0 at 06:28:24; F/F as of 06:28:24/06:28:24] <condqj3ceq3> | | |-F-group "grpqj3h1hl" (AND) false as of 04-16.15:58:09 <grpqj3h1hl> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 5 [9 => 13 at 06-09.12:59:21; F/F as of 04-18.08:23:33/04-18.08:23:33] <condgr2s5sn> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:21] <condgr2s6us> | &-T-service Day or Night (26) urn:rts-services-com:serviceId:DayTime/Status = 1 [0 => 1 at 04:55:29; T/T as of 04:55:29/04:55:29] <condgr2sais> &-F-group "Single press on button two or Alexa: Time to get up (NIGHT)" (AND) false as of 03-29.02:00:01 <grpgr2u86a> | &-?-comment "Sets the house up for the morning when the sun has not risen" <condqk6823b> | &-F-group "grpqj3o1cv" (OR) false as of 06:28:24 <grpqj3o1cv> | | |-F-service Morning_Trigger (244) urn:upnp-org:serviceId:SwitchPower1/Status = 1 [1 => 0 at 06:28:24; F/F as of 06:28:24/06:28:24] <condqj3oo8j> | | |-F-group "grpqj3o71s" (AND) false as of 04-16.16:03:39 <grpqj3o71s> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 5 [9 => 13 at 06-09.12:59:21; F/F as of 04-18.08:23:33/04-18.08:23:33] <condgr2u9lp> | | | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:21] <condgr2ubyr> | &-F-service Day or Night (26) urn:rts-services-com:serviceId:DayTime/Status = 0 [0 => 1 at 04:55:29; F/F as of 04:55:29/04:55:29] <condgr2ucpa> &-F-group "Single press on button three" (AND) false as of 06-09.12:59:16 <grpsnwx0ou> | &-?-comment "Starts the Volumio in the master bedroom" <condsnwxjp9> | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 9 [9 => 13 at 06-09.12:59:21; F/F as of 06-09.12:59:21/06-09.12:59:21] <condsnwy7uc> | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:21] <condsnwyyoc> &-F-group "Single press on button 4" (AND) false as of 06-09.12:59:21 <grpsnwxb2q> | &-?-comment "Stops the Volumio in the master bedroom" <condsnwzhlj> | &-T-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 13 [9 => 13 at 06-09.12:59:21; T/T as of 06-09.12:59:21/06-09.12:59:21] <condsnwzx12> | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:21] <condsnx0hfc> &-F-group "Single press on button eight" (AND) false as of 03-29.02:00:01 <grplcyu4s7> | &-?-comment "This will turn the house off" <condlcyu60p> | &-?-comment "Note the House virtual switch runs the Good Night scene in the Master Bedroom" <condlcz2fmh> | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene = 29 [9 => 13 at 06-09.12:59:21; F/F as of 03-29.02:00:01/03-29.02:00:01] <condlcyvekq> | &-F-service Master_Bedr_ZRC-90 (7) urn:micasaverde-com:serviceId:SceneController1/sl_CentralScene update [1591786135 => 1591938068 at 06:01:32; F/F as of 06-09.12:59:21/06-09.12:59:21] <condlcyx74m> &-F-group "Alarm Clock" (AND) false as of 06-11.05:30:10 <grpsnxo66j> | &-?-comment "Not part of the keypad, but removing the Alarm Clock scene" <condsnxofxi> | &-F-service Alarm_Clock (141) urn:micasaverde-com:serviceId:SecuritySensor1/Tripped = 1 [1 => 0 at 06-11.05:30:10; F/F as of 06-11.05:30:10/06-11.05:30:10] <condsnxox6c> Activity grpsnwx0ou.true Run Lua: 1: os.execute ("/BedroomPlay") Activity grpsnwxb2q.true Run Lua: 1: os.execute("/BedroomStop") Activity grpgr2u86a.true Device Kettle_Plug (153) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Kitchen_Lights (15) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Standard_Lamp (57) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Table Lamp (37) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Security (235) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Device Morning_Trigger (244) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Activity grpsnxo66j.true Run Lua: 1: os.execute ("/BedroomWakeup >/dev/null 2>&1 <&- &") Activity grpgsop1aj.true Run Lua: 1: os.execute ("/BathroomPlay") Delay 720 inline Device Kettle_Plug (153) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Security (235) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Activity grplcyu4s7.true Device House (152) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Activity grpgr2s3wv.true Device Kettle_Plug (153) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Security (235) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Device Morning_Trigger (244) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Activity grpgniuphh.true Delay 720 inline Run Lua: 1: os.execute ("/BathroomPlay") Device Kettle_Plug (153) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Kitchen_Lights (15) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Standard_Lamp (57) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Table Lamp (37) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="1" ) Device Security (235) action urn:upnp-org:serviceId:SwitchPower1/SetTarget( newTargetValue="0" ) Events 2020-06-12 06:01:31: Reactor startup (Luup reload) 2020-06-12 06:01:31: Starting (Luup Startup/Reload) 2020-06-12 06:01:32: Sensor update starting 2020-06-12 06:01:32: Sensor update completed; 0.170s 2020-06-12 06:28:10: Device Morning_Trigger (#244) urn:upnp-org:serviceId:SwitchPower1/Status changed from "0" to "1" 2020-06-12 06:28:10: Sensor update starting 2020-06-12 06:28:10: Condition condqj3ceq3 test state changed from false to true 2020-06-12 06:28:10: Condition condqj3ceq3 evaluation state changed from false to true 2020-06-12 06:28:10: Group grpqj3anz5 test state changed from false to true 2020-06-12 06:28:10: Group grpqj3anz5 evaluation state changed from false to true 2020-06-12 06:28:10: Group Single press on button two or Alexa: Time to get up (DAY) test state changed from false to true 2020-06-12 06:28:10: Group Single press on button two or Alexa: Time to get up (DAY) evaluation state changed from false to true 2020-06-12 06:28:10: Condition condqj3oo8j test state changed from false to true 2020-06-12 06:28:10: Condition condqj3oo8j evaluation state changed from false to true 2020-06-12 06:28:10: Group grpqj3o1cv test state changed from false to true 2020-06-12 06:28:10: Group grpqj3o1cv evaluation state changed from false to true 2020-06-12 06:28:10: Preparing Single press on button two or Alexa: Time to get up (DAY).true (grpgr2s3wv.true) activity 2020-06-12 06:28:10: Launching scene/activity grpgr2s3wv.true 2020-06-12 06:28:10: Starting "grpgr2s3wv.true" group 1 2020-06-12 06:28:24: Device Morning_Trigger (#244) urn:upnp-org:serviceId:SwitchPower1/Status changed from "1" to "0" 2020-06-12 06:28:24: Activity "grpgr2s3wv.true" finished 2020-06-12 06:28:24: Stopping activity "grpgr2s3wv.true" 2020-06-12 06:28:24: Sensor update completed; 13.702s 2020-06-12 06:28:24: Sensor update starting 2020-06-12 06:28:24: Condition condqj3ceq3 test state changed from true to false 2020-06-12 06:28:24: Condition condqj3ceq3 evaluation state changed from true to false 2020-06-12 06:28:24: Group grpqj3anz5 test state changed from true to false 2020-06-12 06:28:24: Group grpqj3anz5 evaluation state changed from true to false 2020-06-12 06:28:24: Group Single press on button two or Alexa: Time to get up (DAY) test state changed from true to false 2020-06-12 06:28:24: Group Single press on button two or Alexa: Time to get up (DAY) evaluation state changed from true to false 2020-06-12 06:28:24: Condition condqj3oo8j test state changed from true to false 2020-06-12 06:28:24: Condition condqj3oo8j evaluation state changed from true to false 2020-06-12 06:28:24: Group grpqj3o1cv test state changed from true to false 2020-06-12 06:28:24: Group grpqj3o1cv evaluation state changed from true to false 2020-06-12 06:28:24: Sensor update completed; 0.054s Devices ZWave (1) urn:schemas-micasaverde-com:device:ZWaveNetwork:1 (19/0); parent 0; plugin -; mfg model ; dev D_ZWaveNetwork.xml impl Switchboard Plugin (117) urn:schemas-toggledbits-com:device:Switchboard:1 (1/-1); parent 0; plugin 9194; mfg model ; dev D_Switchboard1.xml impl I_Switchboard1.xml Table Lamp (37) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg model ; dev D_BinaryLight1.xml impl Master_Bedr_ZRC-90 (7) urn:schemas-micasaverde-com:device:SceneController:1 (14/0); parent 1; plugin -; mfg Remotec model ZRC-90; dev D_SceneController1.xml impl Standard_Lamp (57) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 1; plugin -; mfg Everspring model ; dev D_BinaryLight1.xml impl House (152) urn:schemas-upnp-org:device:BinaryLight:1 (3/3); parent 117; plugin -; mfg rigpapa model Switchboard Virtual Binary Switch; dev D_BinaryLight1.xml impl Alarm_Clock (141) urn:schemas-upnp-org:device:VClock:1 (0/-1); parent 0; plugin 2838; mfg model ; dev D_VClock.xml impl I_VClock.xml Kettle_Plug (153) urn:schemas-upnp-org:device:BinaryLight:1 (3/3); parent 1; plugin -; mfg model ; dev D_BinaryLight1.xml impl Day or Night (26) urn:schemas-rts-services-com:device:DayTime:1 (0/-1); parent 0; plugin 3166; mfg model ; dev D_DayTime.xml impl I_DayTime.xml Security (235) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 117; plugin -; mfg rigpapa model Switchboard Virtual Binary Switch; dev D_BinaryLight1.xml impl Kitchen_Lights (15) urn:schemas-upnp-org:device:DimmableLight:1 (2/3); parent 1; plugin -; mfg Fibaro model FGD-212; dev D_DimmableLight1.xml impl Shower_Trigger (257) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 117; plugin -; mfg rigpapa model Switchboard Virtual Binary Switch; dev D_BinaryLight1.xml impl Morning_Trigger (244) urn:schemas-upnp-org:device:BinaryLight:1 (3/0); parent 117; plugin -; mfg rigpapa model Switchboard Virtual Binary Switch; dev D_BinaryLight1.xml impl Watches Device #244 Morning_Trigger service urn:upnp-org:serviceId:SwitchPower1 variable Status Device #141 Alarm_Clock service urn:micasaverde-com:serviceId:SecuritySensor1 variable Tripped Device #7 Master_Bedr_ZRC-90 service urn:micasaverde-com:serviceId:SceneController1 variable sl_CentralScene Device #26 Day or Night service urn:rts-services-com:serviceId:DayTime variable Status Device #257 Shower_Trigger service urn:upnp-org:serviceId:SwitchPower1 variable Status Device #132 Bedroom Keypad service urn:toggledbits-com:serviceId:ReactorSensor variable TestTime Device #132 Bedroom Keypad service urn:toggledbits-com:serviceId:ReactorSensor variable cdata Device #132 Bedroom Keypad service urn:toggledbits-com:serviceId:ReactorSensor variable TestHouseMode Special Configuration UseReactorScenes = 1 Retrigger = 0 FailOnTrouble = 0 ContinuousTimer = 0Cheers
C
-
Hmm, just tested this and it worked perfectly. I think this was a contemporaneous Luup reload possibly, or possibly not, caused by logs rotating
I shall watch with interest
C
-
I think you are onto something but the log should show that luup has reloaded. Did it not?
-
It did, and it appears to be logging out of order, which is pretty much the only way I caught it...
ESC[7;36m2020-06-12 06:01:07 - LuaUPnP Terminated with Exit Code: 137ESC[1;00m 03 06/12/20 6:01:07.909 LuaUPNP: starting bLogUPnP 0 <0x77a04320> 02 06/12/20 6:01:07.918 ESC[33;1mJobHandler_LuaUPnP::Run: pid 12479 didn't exitESC[0m <0x77a04320> 02 06/12/20 6:01:08.153 ESC[33;1mUserData::TempLogFileSystemFailure start 1ESC[0m <0x77a04320> 02 06/12/20 6:01:08.293 ESC[33;1mUserData::TempLogFileSystemFailure 8700 res:1 -rw-r--r-- 1 root root 33 Nov 28 2019 /etc/cmh/HW_Key -rw-r--r-- 1 root root 31 Apr 14 2017 /etc/cmh/HW_Key2 -rw-r--r-- 1 root root 9 Nov 28 2019 /etc/cmh/PK_AccessPoint -rw-r--r-- 1 root root 7 Apr 20 2019 /etc/cmh/PK_Account -rw-r--r-- 1 root root 452 Jun 12 06:00 /etc/cmh/alerts.json -rw-r--r-- 1 root root 0 Dec 20 2017 /etc/cmh/cameras -rw-r--r-- 1 root root 457 Nov 28 2019 /etc/cmh/cmh.conf -rw-r--r-- 1 root root 0 Nov 28 2019 /etc/cmh/devices -rw-r--r-- 1 root root 16383 Jul 31 2018 /etc/cmh/dongle.4.5.dump.0 -rw-r--r-- 1 root root 16383 Jun 1 2018 /etc/cmh/dongle.4.5.dump.1 -rw-r--r-- 1 root root 16383 Apr 7 2018 /etc/cmh/dongle.4.5.dump.2 -rw-r--r-- 1 root root 16383 Mar 4 2018 /etc/cmh/dongle.4.5.dump.3 -rw-r--r-- 1 root root 16383 Feb 1 2018 /etc/cmh/dongle.4.5.dump.4 -rw-r--r-- 1 root root 16383 Jan 30 2018 /etc/cmh/dongle.4.5.dump.5 -rw-r--r-- 1 root root 16383 Jun 12 02:00 /etc/cmh/dongle.6.1.dump.0 -rw-r--r-- 1 root root 16383 Jun 11 02:00 /etc/cmh/dongle.6.1.dump.1 -rw-r--r-- 1 root root 16383 Jun 10 07:35 /etc/cmh/dongle.6.1.dump.2 -rw-r--r-- 1 root root 16383 Jun 10 03:00 /etc/cmh/dongle.6.1.dump.3 -rw-r--r-- 1 root root 16383 Jun 10 02:00 /etc/cmh/dongle.6.1.dump.4 -rw-r--r-- 1 root root 16383 Jun 9 02:00 /etc/cmh/dongle.6.1.dump.5 -rw-r--r-- 1 root root 41 Dec 3 2018 /etc/cmh/ergy_key -rw-r--r-- 1 root root 0 Nov 28 2019 /etc/cmh/first_boot -rw-r--r-- 1 root root 1 Nov 28 2019 /etc/cmh/ip_mode -rw-r--r-- 1 root root 48 Apr 14 2017 /etc/cmh/keys -rw-r--r-- 1 root root 3 Jan 1 2000 /etc/cmh/language -rw-r--r-- 1 root root 2 Nov 28 2019 /etc/cmh/language_id -rw-r--r-- 1 root root 10 Jun 11 09:46 /etc/cmh/last_backup -rw-r--r-- 1 root root 10 Mar 22 01:01 /etc/cmh/last_reboot -rw-r--r-- 1 root root 11 Jun 11 12:58 /etc/cmh/last_report -rw-r--r-- 1 root root 71 Jun 9 20:46 /etc/cmh/lighttpd_failures -rw-r--r-- 1 root root 10 Feb 23 2019 /etc/cmh/lock_log_levels -rw-r--r-- 1 root root 36316 Nov 28 2019 /etc/cmh/network_pnp.lua -rw-r--r-- 1 root root 12 Jan 1 2000 /etc/cmh/platform -rw-r--r-- 1 root root 458 Nov 28 2019 /etc/cmh/ra_key -rw-r--r-- 1 root root 0 Nov 28 2019 /etc/cmh/rebrand -rw-r--r-- 1 root root 10 Apr 24 14:03 /etc/cmh/reupgraded.firmware -rw-r--r-- 1 root root 0 Nov 28 2019 /etc/cmh/scenarios -rw-r--r-- 1 root root 2043 Dec 13 17:01 /etc/cmh/servers.conf -rw-r--r-- 1 root root 2007 Nov 28 2019 /etc/cmh/servers.conf.catman -rw-r--r-- 1 root root 1520 Nov 28 2019 /etc/cmh/servers.conf.default -rw-r--r-- 1 root root 1520 Apr 19 2019 /etc/cmh/servers.conf.default.orig -rw-r--r-- 1 root root 2014 Feb 28 2019 /etc/cmh/servers.conf.orig -rw-r--r-- 1 root root 20 Dec 13 17:01 /etc/cmh/servers.conf.timestamp -rw-r--r-- 1 root root 181 Nov 28 2019 /etc/cmh/servers_whitelist -rw-r--r-- 1 root root 1604 Jun 11 12:58 /etc/cmh/services.conf -rw-r--r-- 1 root root 20 Apr 14 2017 /etc/cmh/sync_kit -rw-r--r-- 1 root root 20 Apr 14 2017 /etc/cmh/sync_rediscover -rw-r--r-- 1 root root 2 Jan 1 2000 /etc/cmh/ui -rw-r--r-- 1 root root 2 Nov 19 2019 /etc/cmh/ui_man -rw-r--r-- 1 root root 5 Nov 28 2019 /etc/cmh/ui_skin -rw-r--r-- 1 root root 504 Nov 28 2019 /etc/cmh/user_data.json.luup.lzo -rw-r--r-- 1 root root 138744 Jun 12 06:01 /etc/cmh/user_data.json.lzo -rw-r--r-- 1 root root 138736 Jun 12 06:01 /etc/cmh/user_data.json.lzo.1 -rw-r--r-- 1 root root 138389 Jun 12 05:58 /etc/cmh/user_data.json.lzo.2 -rw-r--r-- 1 root root 138393 Jun 12 05:52 /etc/cmh/user_data.json.lzo.3 -rw-r--r-- 1 root root 138371 Jun 12 05:46 /etc/cmh/user_data.json.lzo.4 -rw-r--r-- 1 root root 138373 Jun 12 05:40 /etc/cmh/user_data.json.lzo.5 -rw-r--r-- 1 root root 44240 Jan 15 2019 /etc/cmh/user_data.json.lzo.bak -rw-r--r-- 1 root root 29078 Apr 21 2017 /etc/cmh/user_data.json.lzo.modified -rw-r--r-- 1 root root 29049 Apr 21 2017 /etc/cmh/user_data.json.lzo.orig -rw-r--r-- 1 root root 28512 Apr 21 2017 /etc/cmh/user_data.json.lzo.working -rw-r--r-- 1 root root 53 Apr 20 2019 /etc/cmh/users.conf -rw-r--r-- 1 root root 20 Apr 20 2019 /etc/cmh/users.conf.timestamp -rw-r--r-- 1 root root 3 Nov 28 2019 /etc/cmh/vera_model -rw-r--r-- 1 root root 9 Jan 1 2000 /etc/cmh/version -rw-r--r-- 1 root root 9 May 21 16:15 /etc/cmh/version.latest -rw-r--r-- 1 root root 5 Nov 28 2019 /etc/cmh/version.short -rw-r--r-- 1 root root 9 Jun 10 21:16 /etc/cmh/version_latest -rw-r--r-- 1 root root 5 Apr 14 2017 /etc/cmh/zigbee_version -rw-r--r-- 1 root root 8 Jun 12 05:58 /etc/cmh/zwave_house_id -rw-r--r-- 1 root root 3 Apr 20 2019 /etc/cmh/zwave_locale -rw-r--r-- 1 root root 53 Jun 10 11:48 /etc/cmh/zwave_version /etc/cmh/orig: -rw-r--r-- 1 root root 0 Nov 28 2019 devices -rw-r--r-- 1 root root 0 Nov 28 2019 first_boot -rw-r--r-- 1 root root 0 Nov 28 2019 fresh_install -rw-r--r-- 1 root root 0 Nov 28 2019 scenarios -rw-r--r-- 1 root root 558 Nov 28 2019 user_data.json.lzo /etc/cmh/persist: /etc/cmh/wan_failover: -rw-r--r-- 1 root root 31 Nov 28 2019 check_internet.hosts df -h Filesystem Size Used Available Use% Mounted on rootfs 54.4G 152.8M 51.5G 0% / /dev/root 10.0M 10.0M 0 100% /rom tmpfs 124.8M 1.6M 123.1M 1% /tmp /dev/sda2 54.4G 152.8M 51.5G 0% / tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 487.8M 21.7M 436.5M 5% /tmp/log/cmh /dev/mtdblock10 50.0M 1.5M 48.5M 3% /storage /dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-firmware /dev/mtdblock10 50.0M 1.5M 48.5M 3% /etc/cmh-backup /dev/mtdblock9 9.8M 9.8M 0 100% /mios logread Fri Jun 12 05:56:01 2020 cron.info crond[2731]: crond: USER root pid 13594 cmd /usr/bin/Rotate_Logs.sh Fri Jun 12 05:57:01 2020 cron.info crond[2731]: crond: USER root pid 13781 cmd /usr/bin/Rotate_Logs.sh Fri Jun 12 05:58:01 2020 cron.info crond[2731]: crond: USER root pid 13993 cmd /usr/bin/Rotate_Logs.sh Fri Jun 12 05:59:01 2020 cron.info crond[2731]: crond: USER root pid 14191 cmd /usr/bin/Rotate_Logs.sh Fri Jun 12 06:00:01 2020 cron.info crond[2731]: crond: USER root pid 14410 cmd /usr/bin/Rotate_Logs.shYou can see from the last 5 lines
C
-
Hmm, Alarm clock went off this morning. Luup restarted. I suspect there's a nastiness in the way my script responds to Reactor. I shall break it up and do it all in Reactor
C
-
No Luup reload this morning. Random alarm late last night but that's totally different!
Reactor FTW!
C