Hi All
Hopefully this place looks like a helpful forum as I’m quite new to all this!
I’ve had a few devices all working separately /through their proprietary apps but we’re just finishing off a large house extension and this has added to the list.
I’d ideally like to be able to view/switch a number of different devices on one screen/head end but have no idea where to start.
The devices we have/will have shortly are as follows;
Zigbee Smart Sockets
Zigbee smart switches (for lights)
Heatmiser Neo Underfloor Heating (this runs from a Samsung ASHP but that part is automatic)
Samsung VRF air conditioning (currently using Smart Things App)
Hive (2xLTHW heating circuits in the existing house and Hot Water)
Ring (doorbell!)
Hik Vision PoE CCTV
We have lots of appliances (Neff N70) which we can control remotely but not too fussed about controlling those at the
Moment)
Any help/recommendations would be appreciated!
Thanks
Adrian
I have a legacy home automation set-up running on Windows XP. the computer and software have now died.
I have written a very nice Excel VBA program to replace the software and it can run on any modern Windows system.
My only remaining problem is to output the correct signal to a USB port to trigger the wireless switches.
Has anybody done a similar exercise. Please help.
Hi All,
Kind of new to Home Automation. Started off Using Amazon Echo units and added a Samsung SmartThings hub. I have mostly been using plug in modules for turning lights on and off. I live in a very rural area where the internet goes out a lot. I eventually want to change to to a non internet Hub so things will work without needing an internet connection. But I will post with those questions at a later date.
So, the task at hand is this: I have flood lights at each corner of my house. They are currently controlled by switches at the front and back doors. I would like to add Security Cameras to each corner also. I can easily find small Wifi switches to put into the electrical box where the flood lights are located, then I can terminate the leads together behind the Decora switch to have constant power. Then I can use the constant power up at the lights electrical box to power the security cameras. I would also like to have a wireless switch to take the place of the Decora switch to be able to turn the lights off and on.
I cannot seem to find a product like this. It seems I can find the small wired in switch boxes that will also come with external smart wall switches, but the wall switches are an external box that does not fit in or cover the existing Wall switch electrical box. I can also find Wireless Decora switches that come with a remote wired in small switch box , but they all seem to be RF and do not integrate with a Smart Hub.
I am hoping someone here knows of a product that matches what I am looking for. Any help would be appreciated.
Also any recommendations for Wireless Security cameras are welcome.
Thanks for any help.
Dear Forum,
I am just starting a smart home system. I've wanted to do this for 10 years at most and really would like to get a start. What I have are a couple of SONOFF wifi relays, some 433 (Hz/mHz) switches ( not wifi ) a couple of wifi lightbulbs, and I'd like to expand wifi thermostat, leak/water detectors, garage door openers and what ever else I can think of.
In the SONOFF items I have it's a particular app, the wifi bulbs are another app, and if I do a thermostat there might be another app. My wife is not a Luddite but she damn sure doesn't want to have to trouble shoot if/why a particular app breaks down.
So in what I do understand about smart home things is that I need/want a HUB. I spent 15 years doing some programming so I do have some computer ability, though I'd prefer to stay away from HAVING to line command operate the hub.
I would like a list of HUB's that people have found to be the best. Even better are links to let's say Amazon for that hub.
Regards from Noob Smart Home,
Barry
Hello lovely people. Long time and all that. Hope you're all doing OK.
Bit of a left field one here, looking for extra eyes more than an answer and you're the most logical bunch I know 🙂
Part of our HA system is a Logitech Elite hub and remote control.
This is programmed to control my Cyrus Stereo, our TV, and HDMI switch and our Virgin V6 box.
I've been away for a couple of days. Got back this evening to (eventually) work out that the V6 box appears to be not accepting any commands from the Logitech.
Everything has been rebooted.
Logitech uses IR to control
Cyrus: Fine
TV: Fine
HDMI: Fine
Remote control uses Bluetooth to control Hub.
All commands from the Remote to the hub are executed (one might assume correctly) as the activity LED responds, and if you're controlling (say) the Cyrus, all works fine.
iOS App can be used to control Hub over the WLAN:
All commands from the App re executed (one might assume correctly) as the activity LED responds, and if you're controlling (say) the Cyrus, all works fine.
Native remote (that uses as far as I know bluetooth) to control the V6 box works fine.
V6 box refuses to acknowledge any command other than from the native remote. Remote or app provoke absolutely zero response from the V6 box.
This is annoying, but damned if I can think of any logical reason. One might assume a firmware update on the V6 box, but given that the Hub simply emulates the native remote, that seems unlikely.
I'm struggling to think of where even to start troubleshooting this, so any random thoughts would be appreciated.
My initial approach is to buy another hub in case there's a different radio set that's failed in the hub...
TIA!
C
I currently have an HVAC system in the attic - for heating and A/C. 120v is supplied to the unit to run the gas heating. A/C uses 240v. I have an ecobee thermostat...which sometimes goes offline....not often. When it goes offline, I need to turn the 120v power to the HVAC system off and then back on (the ecobee gets its power from the HVAC system). That resets the ecobee and all is fine. I spend the summer away from this house and if the ecobee goes offine..I have no current method to reset the HVAC 120v power remotely. My idea is to replace the current 120v plug in the attic with a smart plug...then I can remotely turn the 120v power off and the ecobee will reset and come back online. I use Wyze and Lutron Casita in the house currently and was hoping I could find an in-wall smart plug from Wyze or Lutron. Obviously, I don't need diming, etc...just the ability to turn the plug power on/off. I've seen some options...but one problem I have is the attic can reach up to 135F in the summer...many of the smart plugs I've seen are not rated for that temperature. Might any of you have any thoughts on a smart plug I might want to look at? I don't want to invest in anything that would require a new hub - so either WiFi based or Casita HUB based. I need 120v and 15amp ratings. Thanks in advance.
I am trying to run a reaction that turns on lights if a sensor has not been tripped for 2 minutes. Basically, when a garage door is open, turn on inside lights if nothing has been sensed for 2 minutes. My question has to do with the expression/variable for "Last Seen". The variable never gets updated over time since the last seen event never changes.
Screenshot 2024-09-02 191632.png
In the screenshot above, the reaction checks for any garage door as well as the variable called "GarageLastEntry". The expression for this variable is displayed below:
Screenshot 2024-09-02 191651.png
The problem that I am experiencing is that the variable never changes over time. I understand that this is because the "last seen" variable does not change over time when there is no activity. In this screenshot, the value shows 0.029... This can also be seen as the current value in the original reaction screenshot above. After 10 minutes, this value should be 10. However, when a garage door is opened, the variable does not get updated and thus the rule does not become true since .029 is less than 2.
When I go to the variable and click on the > icon, the variable then gets updated as expected as seen below:
Screenshot 2024-09-02 191711.png
So the ultimate question is, how do I use a rule that can use a variable such as "last seen"? Do I need to create another variable or reaction that multiplies this by 1 every minute? From what I read in the manual, a variable is evaluated every time it is included in a reaction. But this is not what I am seeing.
I also want to ask another question related to this variable. It seems like Reactor continuously deletes this variable and I have to keep recreating it? I have never experienced this with MSR so wanted to ask if this is a common problem or if my definition is causing this.
Any info is appreciated!!!
BACKGROUND
I have been using 4 x Yale Contactless Connected Door Locks for several years (they use either a rfid tag or code to enter)
I have also been using 1 x Yale L1 Door Lock on the main front door and this connects via Yale Software
Yale contacted me to advise the L1 Lock software was being withdrawn and I needed to install a Yale Access Module into the existing lock and a Wi-Fi Bridge to link it with the newly released software
ALL of the above was working just fine.
RECENT
Yale emailed to advise I should add a Yale Access Module to each of the 4 other locks as this would link with the updated software via the Wi-Fi Bridge.
They offered a deal of just £4 each for these Modules so I got them.
THE PROBLEM
I found that only 2 of these modules would slot easily into the locks - two of them bent the pins and one of those snapped the female part in a lock (I do have a spare lock but thats not the point).
Anyway, I began to set-up the two fitted Modules with the Wi-Fi Bridge and I eventually found (thanks Google, NOT Yale) that I now need 1 x Wi-Fi Bridge PER LOCK (£50 each).
QUESTION
Does anyone know of a compatible Wi-Fi Bridge which works with Yale AND can handle multiple connections (ie 5 all 5 of my locks) ?
THANK YOU
Hello,
I had an iCOMEN boiler switch that worked for many years. And I used iCOMEN app on my phone to manage it. Short time ago app started to have an error message that it cannot connect to the server, and after some time the device also stopped working.
Some of you may know that I took at shot at building an alternate geofencing solution for Vera. The core of it was system agnostic, using the OwnTracks application and AWS lambdas to track devices and keep a central data, then disseminate that to the Vera via a websocket-based plugin. It worked with other apps as well, including Tasker and GPSLogger, but of the dozen people that were testing it, most used OwnTracks.
A lot was learned in the process, not the least of which is that the success of any such solution is highly dependent on the phone and its settings. Phone manufacturers love to set things up for the longest battery life, of course, but that's usually very anti-geofencing behavior. In the case of at least one brand, it was unusable and the settings could not be modified. It was also cost-prohibitive to maintain on Amazon, as AWS grabs a dime here and a dollar there and before you know it, it added $100/month to my AWS bill, which my wife deducted from my Scotch budget. Unacceptable.
But it's quite reasonable to use OwnTracks to a local endpoint, and I could pretty easily replicate the functionality as a local application, or maybe even as an additional endpoint built into MSR's API (still separate port and process, but in the package).
So the question really is... would you do it, or would you be too concerned about the security risks associated (e.g., dynamic DNS and NAT mapping in the firewall necessary for the phone to contact the service when not on LAN)?
Hello forum instigators.
Not sure who host/runs the forum software but a couple of challenges:
The chat is not currently usable, as the scrolling is all not right and it's not possible to read chats or send chats reliably.
There are a lot of female members that should perhaps be on another forum; where they can advertise their skills more appropriately. Note: I agree it's a job, like any other.
Whoever you are - thank you for your invaluable work.
I run a B&B and am looking for a way to turn the lights off whenever a room is unoccupied for X amount of time. The guest should still be able to turn the lights on and off manually, but should not be able to disable the auto turn off feature if the room is unoccupied.
I guess I am looking for a light switch with a built in presence sensor? I guess a presence sensor would be better as if it is a motion sensor, the lights may go off unwanted if the guest fails to make sufficient movement e.g. if the guest is lying down watching a film.
Are there any products on the market that would work for my application?
Hello,
I am in search of a device capable of using Bluetooth to connect with a smartphone and serve as its primary sound source on demand. This device should function similarly to conventional Bluetooth headphones, which automatically become the phone's sound output upon activation. However, this device should differ in that it transmits the audio signal to an amplifier via a jack, SPDIF, or similar connection. Alternatively, it could be an integrated amplifier that directly sends the signal to passive speakers.
The control of this process should be manageable through an API such as MQTT, REST, MODBUS, or similar. Are you aware of any devices that operate in this manner?
The concept is as follows: upon entering the bathroom, I would press a wall-mounted switch. This switch would send a signal to the Bluetooth device, prompting it to connect to my smartphone and seamlessly continue playing the audiobook I am currently listening to. Instead of using the phone's speakers, it would seamlessly start playing through ceiling-mounted speakers.
Many thanks 🙂
Hi folks,
I currently have some cheap Zigbee hub and some Amazon Alexas running my smart home which mostly consists of Zigbee power strips and Zigbee battery powered switches.
It all worked OK originally, but now whenever I press a Zigbee switch the light in the corresponding plug switches on then immediately off again.
If I ask Alexa to turn the light on it works fine. Likewise if I switch it on from my phone.
Any ideas what the issue could be?
I've tried unplugging the hub a number of times but that doesn't seem to fix it.
I was thinking about getting a Homey Pro 2023 to speed things up (tmas the Zigbee hub seems to be really slow now as well, for some reason) but I'm not sure about that either.
Any suggestions greatly appreciated!
Looking for a recommendation:
Locksmith is trying to talk me into the Yale Assure Lock Touchscreen with Wi-Fi and Bluetooth - the original 1st generation because they said it's built better than the Assure Lock 2. Any thoughts on this? Which would you recommend?
I see Mul T Lock makes a cylinder (KW-KIDYRL) for Yale Smart Locks. Would this fit the 1st gen Assure Lock, as well as Assure Lock 2? Has anyone tried replacing the cylinder with this on either lock?
Other smart lock I was considering is the Schlage Encode Plus.
Thanks!
Hi. So when I had my house build I ran a bunch of stuff, one of which being two pairs of speaker wires to each bedroom and to 4 spots around my living room… Over the years I have used them here and there with different success.. But today they sit in my walls just unused.
I converted all the cat6 or 5e (I don’t remember) over to basically eithernet jacks. The cable coaxial well it’s there but now unused. But I was thinking there has got to be some use for two pairs of speaker wires to each room. Can I make them usb plugs? Not sure so looking for ideas.
Thanks in advance for your thoughts on this.
Kevin
Hey guys...
We are replacing the heat pump and furnace this week and I will also need to replace my nest thermostat at the same time 'cause Nest is ending the cloud thing end of the month.
Anyway, I'm looking to use the
That's what the heat pump installer recommend BUT, using Nest I was also using it to control the home humidifier using a single wire connected to nest... but no low voltage thermostat is able to do that, I checked all of them...
So I need some help on how I can do that, to connect the home humidifier using zwave also....
Hi
We are looking for a solution where we can detect presence of a «thing» (people , car , dog, cat, and more..
We need:
fast detections, 1-3 seconds in range from 0 to 20 m from «base» fysical «client» , chip , transmitter , unit. base , receiver placed at a door, gate, house, etc uniq Identifying wirelessThe client:
no need for pressing any thing (no buttons) battery , hoply 2-5 years battery time.Have someone done anything like this?
What technologi will be best?
MQTT – setup and use
-
@akbooer Wow, that was fast! Thanks, works like a charm.
May I bother you with my next issue? Every time I restart Homebridge my sensor values and current state of bridged devices are lost to mqttthing and shows 0 or OFF until there is an update from the device. Is there a way to retain the values from openLuup/update? -
-
In my own broker I have a Vera/VeraID/update message causing an update from the bridge on demand. I find it useful when subscribing from my windows app, so I get all the updates. It’s similar to what Shelly or tasmota is doing. Maybe it’s easier to implement than retained messages.
-
Thanks for that! I think the challenge in this case is that we are somewhat constrained by what the mqttthing is able to handle. It has some configurability, but I’m not sure whether we can use this approach. We will see.
-
I have a Shelly plug and a Tasmota sensor.
I installed the latest OpenLuup version (21.4.28c)
I have the Shelly and Tasmota bridges that appear automatically, but I don't have the child devices.
Error message in the logs:2021-04-29 15: 02: 20.795 openLuup.context_switch :: ERROR: [dev # 75] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 20.795 openLuup.mqtt :: ERROR publishing application message for mqtt: tele / piscine / SENSOR: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.216 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.217 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / relay / 0 / power: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.219 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.219 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / relay / 0 / energy: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.221 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.221 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / relay / 0: ./openLuup/api.lua:148: attempt to index field '? ' (a nil value) 2021-04-29 15: 02: 21.223 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.223 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / temperature: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.225 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.225 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / temperature_f: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.227 openLuup.context_switch :: ERROR: [dev # 76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 15: 02: 21.227 openLuup.mqtt :: ERROR publishing application message for mqtt: shellies / shellyplug-s-20E453 / overtemperature: ./openLuup/api.lua:148: attempt to index field '?' (a nil value) -
MQTT setting :
luup.attr_set ("openLuup.MQTT.Port", 1885) luup.attr_set ("openLuup.MQTT.Username", "*******") luup.attr_set ("openLuup.MQTT.Password", "*******") luup.attr_set ("openLuup.MQTT.PublishDeviceStatus", "0") luup.attr_set ("openLuup.MQTT.PublishVariableUpdates", true) -- publish every variable update luup.attr_set ("openLuup.MQTT.PublishDeviceStatus", 2) -- publish a single device status every N seconds (0 = never)Devices 75 et 76
21 2021-04-29 14:56:51.444 75 Done 0.000 21 plugin: Tasmota OK 22 2021-04-29 14:56:51.444 76 Done 0.000 22 plugin: Shelly OKContext after StartLuup
2021-04-29 16:53:44.403 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/command tcp{client}: 0x184a658 2021-04-29 16:53:44.404 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/shellyplug-s-20E453/command tcp{client}: 0x184a658 2021-04-29 16:53:44.404 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/shellyplug-s-20E453/relay/0/command tcp{client}: 0x184a658 2021-04-29 16:53:44.404 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.404 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/online : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.405 luup.shelly:76: New Shelly announced: shellyplug-s-20E453 2021-04-29 16:53:44.405 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.405 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.405 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.405 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/announce : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0/power : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0/energy : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.406 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0 : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/temperature : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/temperature_f : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.context_switch:: ERROR: [dev #76] ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.407 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/overtemperature : ./openLuup/api.lua:148: attempt to index field '?' (a nil value) 2021-04-29 16:53:44.661 openLuup.server:: request completed (515424 bytes, 33 chunks, 272 ms) tcp{client}: 0x22f6cf8 -
Thanks – that shows exactly what I needed to see. The first incoming message from the Shelly is not an announcement, so the device doesn't yet exist. I knew this happened, but thought I had handled the condition. A recent change has made it appear again. I'll work on it...
-
Okay
Thank you for your work that I am with interest -
Can you tell me what Shelly devices you are using here? Thanks.
-
Could you try the latest development version (21.4.29b) and see if that fixes the issue? Thanks.
-
Shelly Plug
I installed the last version but still the same problem
2021-04-29 20:31:35.495 openLuup.io.server:: MQTT:1885 connection from 192.168.1.149 tcp{client}: 0x1808020 2021-04-29 20:31:35.500 openLuup.server:: request completed (1304 bytes, 1 chunks, 6470 ms) tcp{client}: 0x1a2dc08 2021-04-29 20:31:35.515 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/command tcp{client}: 0x1808020 2021-04-29 20:31:35.516 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/shellyplug-s-20E453/command tcp{client}: 0x1808020 2021-04-29 20:31:35.517 openLuup.mqtt:: shellyplug-s-20E453 SUBSCRIBE to shellies/shellyplug-s-20E453/relay/0/command tcp{client}: 0x1808020 2021-04-29 20:31:35.518 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.518 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/online : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.519 luup.shelly:76: New Shelly announced: shellyplug-s-20E453 2021-04-29 20:31:35.520 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:226: attempt to index field '?' (a nil value) 2021-04-29 20:31:35.520 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./L_ShellyBridge.lua:226: attempt to index field '?' (a nil value) 2021-04-29 20:31:35.521 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.521 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/announce : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.522 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.522 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0/power : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.523 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.524 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0/energy : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.525 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.525 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/relay/0 : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.526 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.526 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/temperature : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.527 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.527 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/temperature_f : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.528 openLuup.context_switch:: ERROR: [dev #76] ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) 2021-04-29 20:31:35.528 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/shellyplug-s-20E453/overtemperature : ./L_ShellyBridge.lua:343: attempt to index field 'hadevice' (a nil value) -
logs/LuaUPnP_startup.log
178 lines, 1 error, max gap 0s @ 2021-04-30 08:45:58.9362021-04-30 08:45:57.409 :: openLuup STARTUP :: /etc/cmh-ludl 2021-04-30 08:45:57.409 openLuup.init:: version 2021.04.08 @akbooer 2021-04-30 08:45:57.437 openLuup.scheduler:: version 2021.03.19 @akbooer 2021-04-30 08:45:57.462 openLuup.io:: version 2021.03.27 @akbooer 2021-04-30 08:45:57.462 openLuup.mqtt:: version 2021.04.28b @akbooer 2021-04-30 08:45:57.464 openLuup.wsapi:: version 2019.08.12 @akbooer 2021-04-30 08:45:57.464 openLuup.servlet:: version 2021.04.28c @akbooer 2021-04-30 08:45:57.464 openLuup.client:: version 2019.10.14 @akbooer 2021-04-30 08:45:57.465 openLuup.server:: version 2020.03.26 @akbooer 2021-04-30 08:45:57.473 openLuup.scenes:: version 2021.04.28 @akbooer 2021-04-30 08:45:57.477 openLuup.chdev:: version 2020.21.27 @akbooer 2021-04-30 08:45:57.477 openLuup.userdata:: version 2021.03.14 @akbooer 2021-04-30 08:45:57.477 openLuup.requests:: version 2021.02.20 @akbooer 2021-04-30 08:45:57.478 openLuup.gateway:: version 2020.03.08 @akbooer 2021-04-30 08:45:57.481 openLuup.smtp:: version 2018.04.12 @akbooer 2021-04-30 08:45:57.485 openLuup.historian:: version 2021.02.03 @akbooer 2021-04-30 08:45:57.486 openLuup.luup:: version 2021.04.27 @akbooer 2021-04-30 08:45:57.487 openLuup.pop3:: version 2018.04.23 @akbooer 2021-04-30 08:45:57.488 openLuup.compression:: version 2016.06.30 @akbooer 2021-04-30 08:45:57.488 openLuup.timers:: version 2019.05.03 @akbooer 2021-04-30 08:45:57.488 openLuup.logs:: version 2018.03.25 @akbooer 2021-04-30 08:45:57.488 openLuup.json:: version 2020.05.20 @akbooer 2021-04-30 08:45:57.488 openLuup.init:: using openLuup.json.Lua.decode() for JSON decoding (Cjson not installed) 2021-04-30 08:45:57.545 luup.create_device:: [1] D_ZWaveNetwork.xml / I_ZWave.xml / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1) 2021-04-30 08:45:57.561 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json (openLuup) 2021-04-30 08:45:57.561 openLuup.init:: loading configuration user_data.json 2021-04-30 08:45:57.571 openLuup.userdata:: loading user_data json... 2021-04-30 08:45:57.846 luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0 2021-04-30 08:45:57.846 openLuup.userdata:: loading rooms... 2021-04-30 08:45:57.846 openLuup.userdata:: room#1 'MiOS-45003471' 2021-04-30 08:45:57.846 openLuup.userdata:: room#2 'VeraEdge_Exterieur' 2021-04-30 08:45:57.846 openLuup.userdata:: room#3 'VeraEdge_Essai' 2021-04-30 08:45:57.846 openLuup.userdata:: room#4 'VeraEdge_Température' 2021-04-30 08:45:57.846 openLuup.userdata:: room#5 'VeraEdge_Piscine' 2021-04-30 08:45:57.846 openLuup.userdata:: room#6 'VeraEdge_System' 2021-04-30 08:45:57.846 openLuup.userdata:: room#7 'VeraEdge_Securité' 2021-04-30 08:45:57.846 openLuup.userdata:: room#8 'ZWay-31415926' 2021-04-30 08:45:57.846 openLuup.userdata:: room#9 'OpenLuup' 2021-04-30 08:45:57.847 openLuup.userdata:: ...room loading completed 2021-04-30 08:45:57.847 openLuup.userdata:: loading devices... 2021-04-30 08:45:57.850 luup.create_device:: [1] D_ZWaveNetwork.xml / X / (urn:schemas-micasaverde-com:device:ZWaveNetwork:1) 2021-04-30 08:45:57.859 luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json (urn:schemas-upnp-org:device:AltAppStore:1) 2021-04-30 08:45:57.868 luup.create_device:: [5] D_VeraBridge.xml / I_VeraBridge.xml / D_VeraBridge.json (VeraBridge) 2021-04-30 08:45:57.903 luup.create_device:: [15] D_Switchboard1.xml / I_Switchboard1.xml / D_Switchboard1_UI7.json (urn:schemas-toggledbits-com:device:Switchboard:1) 2021-04-30 08:45:57.957 luup.create_device:: [18] D_Reactor.xml / I_Reactor.xml / D_Reactor_UI7.json (urn:schemas-toggledbits-com:device:Reactor:1) 2021-04-30 08:45:57.994 luup.create_device:: [19] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:57.999 luup.create_device:: [20] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.004 luup.create_device:: [25] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.110 openLuup.scheduler.sandbox:: device 26 defined 'string.starts' (a function value) 2021-04-30 08:45:58.110 openLuup.scheduler.sandbox:: device 26 defined 'string.altui_split' (a function value) 2021-04-30 08:45:58.110 openLuup.scheduler.sandbox:: device 26 defined 'string.template' (a function value) 2021-04-30 08:45:58.111 openLuup.scheduler.sandbox:: device 26 defined 'string.trim' (a function value) 2021-04-30 08:45:58.111 luup.create_device:: [26] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json (urn:schemas-upnp-org:device:altui:1) 2021-04-30 08:45:58.158 luup.create_device:: [27] D_VirtualSensor1.xml / I_VirtualSensor1.xml / D_VirtualSensor1.json (urn:schemas-toggledbits-com:device:VirtualSensor:1) 2021-04-30 08:45:58.165 luup.create_device:: [28] D_GenericSensor1.xml / / D_GenericSensor1.json (urn:schemas-micasaverde-com:device:GenericSensor:1) 2021-04-30 08:45:58.210 luup.create_device:: [29] D_MString.xml / I_MString.xml / D_MString.json (urn:schemas-upnp-org:device:VContainer:1) 2021-04-30 08:45:58.214 luup.create_device:: [32] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.219 luup.create_device:: [33] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.281 luup.create_device:: [35] D_ZWay.xml / I_ZWay2.xml / D_ZWay.json (ZWay) 2021-04-30 08:45:58.300 openLuup.scheduler.sandbox:: device 36 defined 'string.fliprsplit' (a function value) 2021-04-30 08:45:58.300 openLuup.scheduler.sandbox:: device 36 defined 'string.template' (a function value) 2021-04-30 08:45:58.300 openLuup.scheduler.sandbox:: device 36 defined 'string.trim' (a function value) 2021-04-30 08:45:58.301 luup.create_device:: [36] D_FLIPR.xml / I_FLIPR.xml / D_FLIPR_UI7.json (urn:schemas-upnp-org:device:flipr:1) 2021-04-30 08:45:58.319 luup.create_device:: [40] D_MString.xml / I_MString.xml / D_GenericSensor1_Ph.json (urn:schemas-upnp-org:device:VContainer:1) 2021-04-30 08:45:58.338 luup.create_device:: [41] D_MString.xml / I_MString.xml / D_GenericSensor1_mVolts.json (urn:schemas-upnp-org:device:VContainer:1) 2021-04-30 08:45:58.356 luup.create_device:: [42] D_MString.xml / I_MString.xml / D_GenericSensor1_Tpiscine.json (urn:schemas-upnp-org:device:VContainer:1) 2021-04-30 08:45:58.385 luup.create_device:: [46] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.407 luup.create_device:: [49] D_BinaryLight1.xml / I_VirtualBinaryLight1.xml / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.411 luup.create_device:: [50] D_ReactorSensor.xml / / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.425 luup.create_device:: [51] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.437 luup.create_device:: [54] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.450 luup.create_device:: [55] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.463 luup.create_device:: [56] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.480 luup.create_device:: [57] D_VeraAlexa1.xml / I_VeraAlexa1.xml / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.489 luup.register_handler:: global_function_name=Tasmota_MQTT_Handler, request=mqtt:tele/# 2021-04-30 08:45:58.489 luup.register_handler:: global_function_name=Tasmota_MQTT_Handler, request=mqtt:tasmota/tele/# 2021-04-30 08:45:58.490 luup.create_device:: [75] D_TasmotaBridge.xml / I_TasmotaBridge.xml / D_TasmotaBridge.json (TasmotaBridge) 2021-04-30 08:45:58.494 luup.register_handler:: global_function_name=Shelly_MQTT_Handler, request=mqtt:shellies/# 2021-04-30 08:45:58.494 luup.create_device:: [76] D_ShellyBridge.xml / I_ShellyBridge.xml / D_ShellyBridge.json (ShellyBridge) 2021-04-30 08:45:58.501 luup.create_device:: [10002] D_SceneController1.xml / X / D_SceneController1.json (urn:schemas-micasaverde-com:device:SceneController:1) 2021-04-30 08:45:58.505 luup.create_device:: [10003] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.509 luup.create_device:: [10006] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.513 luup.create_device:: [10012] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.522 luup.create_device:: [10016] D_InfoViewer1.xml / X / D_InfoViewer1.json (urn:schemas-a-lurker-com:device:InfoViewer:1) 2021-04-30 08:45:58.544 luup.create_device:: [10034] D_DeusExMachinaII1.xml / X / D_DeusExMachinaII1_UI7.json (urn:schemas-toggledbits-com:device:DeusExMachinaII:1) 2021-04-30 08:45:58.606 luup.create_device:: [10040] D_MiLightRGBWBOX2.xml / X / D_MiLightRGBW.json (urn:schemas-dcineco-com:device:DimmableLightRGBW:1) 2021-04-30 08:45:58.610 luup.create_device:: [10046] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.614 luup.create_device:: [10047] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.617 luup.create_device:: [10048] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.625 luup.create_device:: [10059] D_LuaView1.xml / X / D_LuaView1.json (urn:schemas-toggledbits-com:device:LuaView:1) 2021-04-30 08:45:58.643 luup.create_device:: [10060] D_ZiBlueGateway1.xml / X / D_ZiBlueGateway1.json (urn:schemas-upnp-org:device:ZiBlueGateway:1) 2021-04-30 08:45:58.644 luup.create_device:: [10061] D_SerialPortRoot1.xml / X / (urn:micasaverde-org:device:SerialPortRoot:1) 2021-04-30 08:45:58.654 luup.create_device:: [10062] D_SerialPort1.xml / X / (urn:micasaverde-org:device:SerialPort:1) 2021-04-30 08:45:58.659 luup.create_device:: [10069] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.664 luup.create_device:: [10070] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.667 luup.create_device:: [10071] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.669 luup.create_device:: [10072] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.672 luup.create_device:: [10075] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.675 luup.create_device:: [10076] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.683 luup.create_device:: [10082] D_DelayLight.xml / X / D_DelayLight_UI7.json (urn:schemas-toggledbits-com:device:DelayLight:1) 2021-04-30 08:45:58.695 luup.create_device:: [10089] D_WindSensor1.xml / X / D_WindSensor1.json (urn:schemas-micasaverde-com:device:WindSensor:1) 2021-04-30 08:45:58.698 luup.create_device:: [10095] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.718 luup.create_device:: [10097] D_VSwitch.xml / X / D_VSwitch_UI7.json (urn:schemas-upnp-org:device:VSwitch:1) 2021-04-30 08:45:58.723 luup.create_device:: [10099] D_VSwitch.xml / X / D_VSwitch_UI7.json (urn:schemas-upnp-org:device:VSwitch:1) 2021-04-30 08:45:58.726 luup.create_device:: [10102] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.730 luup.create_device:: [10103] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.733 luup.create_device:: [10104] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.735 luup.create_device:: [10105] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.738 luup.create_device:: [10106] D_Reactor.xml / X / D_Reactor_UI7.json (urn:schemas-toggledbits-com:device:Reactor:1) 2021-04-30 08:45:58.743 luup.create_device:: [10107] D_Switchboard1.xml / X / D_Switchboard1_UI7.json (urn:schemas-toggledbits-com:device:Switchboard:1) 2021-04-30 08:45:58.747 luup.create_device:: [10110] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.751 luup.create_device:: [10114] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.753 luup.create_device:: [10115] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.759 luup.create_device:: [10118] D_DoorSensor1.xml / X / D_DoorSensor1.json (urn:schemas-micasaverde-com:device:DoorSensor:1) 2021-04-30 08:45:58.761 luup.create_device:: [10124] D_SmartHomeHelper.xml / X / (urn:schemas-upnp-org:device:GoogleHome:1) 2021-04-30 08:45:58.767 luup.create_device:: [10131] D_MotionSensor1.xml / X / D_MotionSensor1.json (urn:schemas-micasaverde-com:device:MotionSensor:1) 2021-04-30 08:45:58.774 luup.create_device:: [10132] D_LightSensor1.xml / X / D_LightSensor1.json (urn:schemas-micasaverde-com:device:LightSensor:1) 2021-04-30 08:45:58.778 luup.create_device:: [10133] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.784 luup.create_device:: [10138] D_GenericIO1.xml / X / D_GenericIO1.json (urn:schemas-micasaverde-com:device:GenericIO:1) 2021-04-30 08:45:58.788 luup.create_device:: [10139] D_MotionSensor1.xml / X / D_MotionSensor1.json (urn:schemas-micasaverde-com:device:MotionSensor:1) 2021-04-30 08:45:58.792 luup.create_device:: [10143] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.796 luup.create_device:: [10145] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.799 luup.create_device:: [10146] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.802 luup.create_device:: [10147] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.808 luup.create_device:: [10165] D_SmokeSensor1.xml / X / D_COSensor1NoTamper.json (urn:schemas-micasaverde-com:device:SmokeSensor:1) 2021-04-30 08:45:58.815 luup.create_device:: [10166] D_FloodSensor1.xml / X / D_FloodSensor1.json (urn:schemas-micasaverde-com:device:FloodSensor:1) 2021-04-30 08:45:58.820 luup.create_device:: [10172] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.825 luup.create_device:: [10173] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.831 luup.create_device:: [10177] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.836 luup.create_device:: [10178] D_ALTUI.xml / X / D_ALTUI_UI7.json (urn:schemas-upnp-org:device:altui:1) 2021-04-30 08:45:58.841 luup.create_device:: [10181] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.848 luup.create_device:: [10182] D_VirtualSensor1.xml / X / D_VirtualSensor1.json (urn:schemas-toggledbits-com:device:VirtualSensor:1) 2021-04-30 08:45:58.852 luup.create_device:: [10183] D_TemperatureSensor1.xml / X / D_GenericSensor1_Tpiscine.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.857 luup.create_device:: [10184] D_GenericSensor1.xml / X / D_GenericSensor1_mVolts.json (urn:schemas-micasaverde-com:device:GenericSensor:1) 2021-04-30 08:45:58.861 luup.create_device:: [10185] D_GenericSensor1.xml / X / D_GenericSensor1_Ph.json (urn:schemas-micasaverde-com:device:GenericSensor:1) 2021-04-30 08:45:58.865 luup.create_device:: [10186] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.871 luup.create_device:: [10187] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.875 luup.create_device:: [10189] D_MString.xml / X / D_MString.json (urn:schemas-upnp-org:device:VContainer:1) 2021-04-30 08:45:58.880 luup.create_device:: [10190] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.882 luup.create_device:: [10192] D_VeraAlert.xml / / () 2021-04-30 08:45:58.882 openLuup.chdev:: ERROR: unable to read XML file D_VeraAlert.xml 2021-04-30 08:45:58.886 luup.create_device:: [10193] D_ReactorSensor.xml / X / D_ReactorSensor_UI7.json (urn:schemas-toggledbits-com:device:ReactorSensor:1) 2021-04-30 08:45:58.894 luup.create_device:: [10195] D_FloodSensor1.xml / X / D_FloodSensorWithTamper1.json (urn:schemas-micasaverde-com:device:FloodSensor:1) 2021-04-30 08:45:58.898 luup.create_device:: [10196] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.902 luup.create_device:: [10197] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.906 luup.create_device:: [10198] D_VeraAlexa1.xml / X / D_ComboDevice1.json (urn:bochicchio-com:device:VeraAlexa:1) 2021-04-30 08:45:58.909 luup.create_device:: [10199] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.913 luup.create_device:: [10200] D_BinaryLight1.xml / X / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.916 luup.create_device:: [10201] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.919 luup.create_device:: [10202] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.922 luup.create_device:: [10203] D_TemperatureSensor1.xml / X / D_TemperatureSensor1.json (urn:schemas-micasaverde-com:device:TemperatureSensor:1) 2021-04-30 08:45:58.925 luup.create_device:: [10204] D_HumiditySensor1.xml / X / D_HumiditySensor1.json (urn:schemas-micasaverde-com:device:HumiditySensor:1) 2021-04-30 08:45:58.928 luup.create_device:: [30040] D_BinaryLight1.xml / / D_BinaryLight1.json (urn:schemas-upnp-org:device:BinaryLight:1) 2021-04-30 08:45:58.932 luup.create_device:: [30070] D_DoorSensor1.xml / / D_DoorSensor1.json (urn:schemas-micasaverde-com:device:DoorSensor:1) 2021-04-30 08:45:58.933 openLuup.userdata:: loading scenes... 2021-04-30 08:45:58.933 openLuup.userdata:: [10014] Alarme Température Congel/frigo 2021-04-30 08:45:58.933 openLuup.userdata:: [10010] Gestion_SmartLed 2021-04-30 08:45:58.933 openLuup.userdata:: [10009] essai_clavier 2021-04-30 08:45:58.934 openLuup.userdata:: [10001] Eclairage_Allee(Manu) 2021-04-30 08:45:58.934 openLuup.userdata:: number of scenes = 4 2021-04-30 08:45:58.934 openLuup.userdata:: ...scene loading completed 2021-04-30 08:45:58.934 openLuup.userdata:: loading installed plugin info... 2021-04-30 08:45:58.934 openLuup.userdata:: [openLuup] openLuup (21.4.29b) 2021-04-30 08:45:58.934 openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30) 2021-04-30 08:45:58.934 openLuup.userdata:: [VeraBridge] VeraBridge (21.1.3) 2021-04-30 08:45:58.934 openLuup.userdata:: [8246] ALTUI (2.53b.) 2021-04-30 08:45:58.934 openLuup.userdata:: [Z-Way] Z-Way (21.1.19) 2021-04-30 08:45:58.934 openLuup.userdata:: [Arduino] MySensors (not.installed) 2021-04-30 08:45:58.934 openLuup.userdata:: [9194] Switchboard (GitHub.GitHub.stable) 2021-04-30 08:45:58.935 openLuup.userdata:: [9086] Reactor (GitHub.stable) 2021-04-30 08:45:58.935 openLuup.userdata:: [9031] Virtual Sensor (1.11) 2021-04-30 08:45:58.935 openLuup.userdata:: [9281] Virtual HTTP Devices (GitHub.master) 2021-04-30 08:45:58.935 openLuup.userdata:: [AlexaTTS] VeraAlexa (GitHub.master) 2021-04-30 08:45:58.935 openLuup.userdata:: ...user_data loading completed 2021-04-30 08:45:58.935 openLuup.init:: running _openLuup_STARTUP_ 2021-04-30 08:45:58.936 luup_log:0: startup code completed 2021-04-30 08:45:58.936 openLuup.init:: init phase completed 2021-04-30 08:45:58.936 :: openLuup LOG ROTATION :: (runtime 0.0 days) -
@crille said in MQTT – setup and use:
May I bother you with my next issue? Every time I restart Homebridge my sensor values and current state of bridged devices are lost to mqttthing and shows 0 or OFF until there is an update from the device. Is there a way to retain the values from openLuup/update?
In the latest testing branch release (v21.4.30) the MQTT server now subscribes to the topic
openLuup/query. If you publish a message with the format:devNo.serviceId.variable, for example,- topic: openLuup/query
- message: 2.openLuup.Memory_Mb
it will force an immediate update message:
- topic: openLuup/update/2/openLuup/Memory_Mb
- message: 8.7 (or whatever)
You should be able to use this to get an initial value for any mqttthing.
Notice the formatting difference between the message and the returned topic ('.' instead of '/') this is intentional because it is in line with openLuup's existing dev.srv.var notation and it reminds you that it's not a part of the query topic, but it goes in the message, and avoids the need for openLuup to use a wildcard subscription.
-
@christian_fabre I added my Shelly 1PM today to OpenLuup v21.4.29b.
At first it did not work, and I could not figure out why. Then I found a post on the Shelly forum that said that there in some cases (or for some devices) could be a problem with the latest Shelly firmware and Mqtt.
I had the latest v1.10.3 in my 1PM. After I downgraded the Shelly to v1.9.4 it worked.
Check what firmware you have in your plug and if you have the latest you can try to downgrade and see if it works.
Go to https://www.shelly-support.eu/index.php?shelly-firmware-archive/ and enter your IP address, select the right plug variant (there are a few to choose from) and firmware release. Then you copy the url that is generated into a browser.
If you have blocked the Shelly in your router from Internet access you probably have to open it temporary for the downgrade.I also added my Shelly Button to OpenLuup and for some reason I could not downgrade it, but I managed to get it working anyway after a few attempts.
(A bit strange since the post I found on the forum was on problems with the Button and v1.10.3.)Another tip is to use MqttExplorer if you do not already use it and see if the Shelly shows up there. If it does, then at least the Mqtt part of the Shelly most likely works.
-
Excellent diagnosis. Let's hope that's the root cause.
Entirely exaplins why I couldn't reproduce this ... my Shelly 2.5s are on 1.9.4, but telling me there's a 1.10.3, so I'll be sure NOT to do that!
I don't follow the Shelly forum much, so please pass on when it's safe again to upgrade.
@rafale77 Shellies are manual update... a good choice, as I'm sure you'll agree!
-
@akbooer said in MQTT – setup and use:
I don't follow the Shelly forum much, so please pass on when it's safe again to upgrade.
@rafale77 Shellies are manual update... a good choice, as I'm sure you'll agree!
Ha! Indeed, There is an ongoing train wreck on the QNAP forum with people humorously (to me at least, maybe not to them) finding out the firmware autoupdate being enabled on the new firmware which itself has a lot of connectivity problems forcing many to downgrade... sounds familiar? No one is immune to a problematic upgrade or a use case where something breaks. And this came as a knee jerk reaction to a security breach for which the firmware upgrade itself does nothing because the exposure comes from an app.
-
@akbooer I routinely updated the two new Shellies and then I got v1.10.3, bad decision as it turnes out.
My two older Shellies are on v1.9.0 and worked directly when I enabled Mqtt.Manual update is better, automatic is a pain, Win 10 is a good example on that. I assume I will get it on my Qnap when I update it.
I have also blocked the Shellies and Tasmotas in the the router
