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!
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?
Hey everyone, I'm currently working on developing a bed sensor that can detect when you're out of bed. It could be used to trigger other smart home gadgets, like lights or blinds, temperature etc.
The sensors are placed under the legs of your bed post. Should look and feel like "smart furniture pads" with size 2 inches in diameter and 1/4 inch thick.
Before we go any further, I'd love to get your thoughts on this - would a bed sensor like this be something you'd find useful? We're still in the early stages of development, so any feedback you have would be greatly appreciated. Thanks in advance!
@DesT, fenced code blocks display differently after the upgrade.
abc defThe above should display as abc and def on two separate lines. This works. But this fails:
verbose: true config: data: "auto"The above should display as three lines, verbose: true, config: and data: "auto", but this fails. In order to make it display properly, I now have to open the fenced code block with ```text (specify language, generic text). This displays without highlighting. The words yml and yaml (and the all-caps versions) don't seem to be recognized. I can also use js to get JavaScript highlighting, but this isn't great for YAML. Here's the same block with the language (text) specifier added (no other changes):
verbose: true config: data: "auto"Sure, we can start adding language specifiers to our new posts, but I suspect if we start digging around old posts, we're going to find a lot of broken display of the fenced code blocks (plain ``` at the start with no language specifier) in the thousands of old posts in these forums, upon which people still rely for answers and information.
Log file snippets also get similarly brutalized:
[###BUILDVERSION###]2023-04-26T19:41:51.683Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs added file logger to zwavejs.log [###BUILDVERSION###]2023-04-26T19:41:51.747Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_cfg, which is not consistent with the recommended naming [###BUILDVERSION###]2023-04-26T19:41:51.747Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_mfg_spec, which is not consistent with the recommended naming [###BUILDVERSION###]2023-04-26T19:41:51.747Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_device_ver, which is not consistent with the recommended naming [###BUILDVERSION###]2023-04-26T19:41:51.747Z <ZWaveJSController:WARN> zwavejs_capabilities defines x_zwave_values, which is not consistent with the recommended naming [###BUILDVERSION###]2023-04-26T19:41:51.837Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs connecting to ws://192.168.0.10:3000 [###BUILDVERSION###]2023-04-26T19:41:51.874Z <ZWaveJSController:NOTICE> ZWaveJSController#zwavejs connected [###BUILDVERSION###]2023-04-26T19:41:51.874Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs sending connection initialization [###BUILDVERSION###]2023-04-26T19:41:51.931Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs greeting from server: [Object]{ "type": "version", "driverVersion": "10.16.0", "serverVersion": "1.28.0", "homeId": 3631280043, "minSchemaVersion": 0, "maxSchemaVersion": 28 } [###BUILDVERSION###]2023-04-26T19:41:51.932Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing initial inventory [###BUILDVERSION###]2023-04-26T19:41:52.325Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs manufacturer-specific data for 134 (AEON Labs) from package ver 22315.1 [###BUILDVERSION###]2023-04-26T19:41:52.328Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs configuring node 1 endpoint 0 (entity "1-0") [###BUILDVERSION###]2023-04-26T19:41:52.339Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs manufacturer-specific data for 543 (Elexa Consumer Products Inc.)I think this is going to be a problem. Is there a way in NodeBB to configure the default language for fenced code block markdown for the entire forum so that these display more as they did before the upgrade?
EDIT: Examples below of old posts with corrupt formatting now:
https://smarthome.community/topic/1101/dynamic-groups-controller-filter-expressions
https://smarthome.community/post/11362
This last old post is interesting, because the first block displays incorrectly, but the second block is OK. In playing around, there seem to be triggering character sequences, suggesting that the markdown processor is trying to "guess" the language but not getting it right, perhaps:
Hi guys,
we are doing a survey in IT privacy and security and we want to analyze the user perception of privacy concerns in smart homes. It will only take 5-10 min to fill out the survey 🙂
i would be very thankful if you could take part and help us to get as many responses as possible.
Thank you!
Can anyone help with the MIOS UI5 weblink? Not the getvera one.
Still running UI5 on a couple of sensors & lights and need to tweak PLEG but for the life of me I can't remember the link to tunnel back to the trusty machine....
The wifi on my router is turned off, and wifi around the house is provided using a mesh - 3 units altogether (one connected directly to the router) that are spread around the house.
I would like to start automating certain tasks around the house and intend to try adding a few smart sockets to my setup.
The mesh system I have supports both 2.4GHz and 5GHz, and does not provide me with the option to control them - i.e. turn one or both on/off, give each a different SSID, etc.
The devices I wish to purchase/use only support 2.4GHz.
Will turning the mesh units off and temporarily turning the 2.4GHz wifi on the router to allow me to set them up be enough? Will I then be able to return to my usual setup and everything will work as it should?
Many thanks in advance
ChatGPT samples:
Me:
Tell me about an iot program called openLuup.
It:
OpenLuup is an open source home automation system that is built on the VeraLuup platform. It is designed to be easy to install and configure, and provides users with a powerful and versatile way to control their home automation devices. OpenLuup offers a wide range of features, including support for many popular home automation devices, scheduling, scripting, and integration with other services. OpenLuup is designed to be customizable, allowing users to create their own home automation systems. It is an excellent choice for those looking to create their own home automation system without spending a lot of money.
Me:
Write an iot program using openLuup.
It:
--openLuup IoT Program-- -- Initialize Variables -- local device_id = "MyHomeDevice" local temperature_sensor_id = "MyTemperatureSensor" local temperature_threshold = 75 -- Create Devices -- luup.create_device("OpenLuup Temperature Sensor", 0, device_id, "D_GenericSensor1.xml", "I_GenericSensor1.xml", "S_TemperatureSensor1.xml", "") luup.variable_set("urn:upnp-org:serviceId:TemperatureSensor1", "CurrentTemperature", 0, device_id) -- Start Timer -- luup.call_delay("check_temperature", 10, "", false) --Function to Check Temperature-- function check_temperature() local current_temperature = luup.variable_get(temperature_sensor_id, "CurrentTemperature", 0) --Check Temperature Threshold-- if current_temperature >= temperature_threshold then --Send Alert-- luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "SendTextMessage", {PhoneNumber="1234567890", Message="ALERT! Temperature exceeded threshold!"}, 0) end --Reset Timer-- luup.call_delay("check_temperature", 10, "", false) endMe:
Write an iot program using openLuup.
It:
Write an iot program using openLuup. -- openLuup IOT Program -- -- Variables local lampState = false local lampTime = 0 -- Functions function lampTimer() if lampTime > 0 then lampTime = lampTime - 1 if lampTime == 0 then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 0, lampDeviceID) lampState = false end end end -- Setup luup.call_delay('lampTimer', 60, 0) -- Main Loop while true do -- Check for motion if luup.variable_get('urn:micasaverde-com:serviceId:MotionSensor1', 'Tripped', motionSensorDeviceID) == '1' then if not lampState then luup.variable_set('urn:upnp-org:serviceId:SwitchPower1', 'Status', 1, lampDeviceID) lampState = true -- Set lamp timer to 5 minutes lampTime = 300 end end luup.sleep(1) endWhat??
luup.sleep(1)Not good - looks like I still have some semblance of a job to fulfill.
Me:
An iot program called openLuup was written by akbooer. Who is akbooer?
It: (note: answer redacted and as I understand it, also incorrect re: AltUI):
akbooer is the pseudonym of the software developer and home automation enthusiast. He is the creator of the openLuup home automation software, which is an open-source version of the Vera home automation system. He is also the creator of the AltUI graphical user interface for openLuup.
Me:
Who created of the AltUI graphical user interface for openLuup.
and
Me:
Who created of the AltUI graphical user interface for the home automation system Vera.
Names two different people - mmmm.
Regardless very impressive - give it a few more years.
...which I'd like to do. I know I go about these things all wrong (namely think of something I'd like to do, then try and work out what I need to know) but that's me 🙂
Just looking for some pointers on what I should google for really:
What I'd like is to provide a selection of (basically two word) phases which I can select from randomly (or even pseudo randomly) and pass to Alexa to be spoken. There are 10 such phrases only.
So what should I be reading up on to get me started?
TIA for any guidance
C
Hi,
I am a student and recently i am working on smart home project and writing a seminar paper about the way users handle and manage IoT devices. I you have 3 min, please fill below survey. Its really short.
Thank you in advance, I really appreciate everyone's help.
For what it's worth, I've been putting the finishing touches on a much-updated version of my DP Apps spreadsheet -- specifically intended for HE users, at least for now -- and invite you all to take a gander http://bit.ly/hedb23 at the PDF one-page version.
Corrections and edits welcome (esp. for the HOMEKIT column, just added yesterday)! Thanks in advance, especially because I'm not a big dashboard user myself, but somehow accepted this role as "keeper of the list" as it were.
Hello guys,
I would like to achieve two different things with lights, but I am not sure it could be done. I am starting with smart things, and I am far from any electrician knowledge, wo any help is really appreciated.
I have dumb switches in my hall, controlled from 3 places. I understood that installing one smart module before first switch will make them "hybrid", both smart controlled and dumb controlled.
I would like to buy ceiling light with two bulb sockets. What I would like to achieve is I would like to have one bulb for normal daily usage (lets say cold white full brightness), and second for night time (aprox from 10pm till morning) with some red/orange - minimum brightness.
So question are:
Is there a way to keep both bulbs turning-on separated? So only one will be on during day, and then only second during night?
And could that be done with pressing dumb switch? What would I need to achieve it? (maybe another module into the ceiling lights)
Thank you in advance
Z-Wave Classes & Commands
-
Considering how long I’ve been using HA systems, where I was a relatively early adopter of z-wave, I’ve never really explored the Z-Wave Classes and Commands.
Don’t get me wrong I understand (well at least I think I do) the overall objective and the design of the classes and the command, but my exposure to it has always been hidden behind a software/application layer.. No bad thing your might say, but the more I got to know the Lua language , the more I wanted to know more about the Z-wave Classes and Command - and how I could interact with them a little more directly.
FYI - I’m still very much in the learning phase, and welcome any insight/advice from those more experienced than me.
For this particular ‘How To’, I’m going to start off with a link to all the recorded z-wave classes and commands, this is a great place to see the length and breadth of what z-wave supports.
My first objective is to see if I can request a battery report from a device.. (Make sure your device support this class)
To do that I need to look up the
Commands_Class
for Battery, and note down it’s associated value, which in this case is0x80
COMMAND_CLASS_BATTERY 0x80 Management Active
After that, I then need to get the value associated with the specific command I want to send, which in this case is the
Battery Get
one from the following list..BATTERY_GET 0x02 controlling supporting BATTERY_REPORT 0x03 supporting controlling BATTERY_HEALTH_GET 0x04 controlling supporting BATTERY_HEALTH_REPORT 0x05 supporting controlling
Those two looks up have now provided me with the following two item values …
Battery Command Class = 0x80 BATTERY_HEALTH_GET Command = 0x04
Next I need to send them to my Vera/Z-wave controller , specifying the z-wave ‘node’ I want to target (make sure it is the node number (alt.I’d, NOT the Device No.) , which in this case is node 3 (device no. 64) - using a command like the following....
luup.call_action('urn:micasaverde-com:serviceId:ZWaveNetwork1','SendData',{Node='3',Data='0x80 0x04'},1)
Or externally..
http://192.168.1.10/port_3480/data_request?id=action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Node=3&Data=0x80-0x04
Any/all feedback welcome..
-
Very well constructed. A couple of details I'd point out:
- A subtle mistake users often make in this procedure is sending the
SendData
command to the device. It cannot be stressed enough that theSendData
action is always and only sent to device #1, the ZWave Network device (i.e. the last parameter ofcall_action()
forSendData
is always1
). A lot of users will get the node ID parameter set correctly, construct the data string correctly, and then send the action to the device they want to control rather than the ZWave Network device #1, and then puzzle over why it doesn't work. - The hex may be abbreviated, for example,
x80
(the leading zero is not required), and any value may also be given in decimal form, and you can mix decimal and hex (e.g.x70 4 10 1 15
sets configuration parameter decimal 10 to the one-byte decimal value 15 on the target device). - Many ZWave commands require multi-byte values. For example, to send a 16-bit integer (range 0-65535 unsigned or -32768 to 32767 signed), you must send two bytes. To send 4096, for example, you cannot just put
4096
or0x1000
in your data string, as these are not valid byte values (which are 0-255/0x00-0xff range). If you look at the hex representation of 4096 --0x1000
-- you see four hexadecimal digits; split them into pairs and send them like this:0x00 0x10
. Notice the order of the two bytes has been reversed. This is referred to as little endian in network communications: the least significant byte is sent first, followed by progressively more significant bytes. A four-byte (32 bit) value, for example 0x12345678, would be sent as0x78 0x65 0x34 0x12
. Notice that the order of bytes is reversed, but within the bytes, there is no reversal of bits (that is 0x78 does not become 0x87). If the command you are using requires a byte count, remember to account for this splitting in your number of bytes (the 0x1000 example adds 2 to the length of the command because it takes two bytes to represent the one 16-bit number). Always send leading zeroes to get the expected number of bytes: if a 16-bit integer is expected for the command and you need to send 0, you must send0 0
or0x00 0x00
. - There is no easy way on Vera to intercept any data that may be a reply to the request/command. If you issue a command that replies with a packet that Luup does not understand, it will be logged but not otherwise handled, or available. This is a big short-coming of Vera in terms of allowing third-party support of ZWave devices. Hubitat, for example, has solved this problem, and third party ZWave device drivers are quite common, and not difficult to use, write or support.
- There is no way that I am aware of to do this on eZLO hubs with current firmware (there is no documented equivalent to
SendData
). I have pointed this out; the reply thus far has been deafening silence, not even so much as an acknowledgement that it may be added to a list for future consideration..
- A subtle mistake users often make in this procedure is sending the
-
All a bit tricky. The OpenZWave people spent ages reverse engineering the protocol. The logViewer plugin I wrote - it's for Vera/OpenWRT only - was subsequently augmented by @gengen. Putting the logging into verbose mode invokes his "ZShark". It allows a good view of the ZWave interchanges. Definitely don't leave your Vera in the logging verbose mode fo any length of time.
-
I have a Qubino ZMNHBD1 that I'm trying to reconfigure without messing with device numbers, but it's not really working.
I'm sending param 13 2-byte device to 0, but it doesn't seem to work (this will disable auto-off after 1 sec, since in 7.32 beta there's a bug preventing auto-off from being updated, so I've repurposed all my devices doing this, attaching external relays, or using Shellies).
luup.call_action("urn:micasaverde-com:serviceId:ZWaveNetwork1", "SendData", { Node='128', Data= "x70 4 13 2 0"}, 1 )
Any hints? Device is set to auto configure to off. Next step is to remove, reset the device and pair again, but I'd like to try this route first.
-
The first thing that stands out is latter part of my point #3 above: you are saying in the codes that parameter 13 is coming with a 2-byte value, but you are only sending one byte after the count. Try sending
x70 4 13 2 0 0
so that you are sending the upper and lower bytes of the two-byte value. Remember thatSendData
sends bytes, not values. It's up to you to "decompose" your values into the correct number and sequence of bytes that represents the value.One thing I also forgot to mention in my missive above for Vera in particular, is that the refresh and data validity around the "Device Options" in the UI is almost non-existent, and the values shown are often wrong. You have to do the following in order to see correct values:
- Set to
monitor only
any parameter in Device Options that you intend to control viaSendData
. If you don't do this, every Luup restart will reconfigure the device and clobber your values, and all you will ever see is what Luup wants to set or has set. - Some users turn off auto-reconfigure, and it is often recommended quite casually in the other forums. IMO, this is probably the worst advice I see being given in that community today, at least when given casually. It should only be used as a last resort for devices that errantly destroy and create children and wreak havoc with your device numbering, scenes and automations. But in any case, if you turn it off, the UI will never show you correct Device Option parameter values. Because...
- When inspecting values, the device must be reconfigured in order for the value to be picked up by Device Options, as during ZWave startup is the only time Luup sets or fetches these values. So if you are looking at the Device Options UI after a
SendData
, it will be wrong, and even after a hard refresh, it will be wrong (relative to your expectations), unless and until you reload Luup, or, reconfigure the device. Sometimes, you can get away with hitting "Configure Now", but I find that sometimes, for reasons I fear I will ever understand, attempting to just say "Configure Now" fails when configuration during a Luup reload works, an inexplicable dilemma (they should be one and the same function and work identically). And after either reload or "Configure Now", you must hard-refresh your browser, because the UI does not see changes in the state variables they use for these values reliably.
Also keep in mind that some devices will not keep the value you send, they will only act on it. For example, some of my Aeotec devices will reset their parameters to factory default if you set the value of a parameter to 255. When looking at the value, it is always reported as 0, never as 255, even though it gets the value when sent and does in fact reset itself as directed. Likewise my siren will accept the number of a melody to play in a parameter, but that parameter always reports as 0, even after playing melody 1, 10, 77, ....
- Set to
-
@toggledbits said in Z-Wave Classes & Commands:
Try sending x70 4 13 2 0 0 s
that did the trick. I really didn't paid attention to this detail. it works this way, in fact. I'm not really monitoring the params, but I know the relay will not do a second click after 1 sec after sending on, so I'm know it's working well. I'm not messing so much with parameters these days, since the system is almost stable and I've added many new devices (I still have 3-4 added but not already deployed, but that's another story). Thanks, as always!
-
@toggledbits Would it be possible to add a function to MSR that returns the parameters of a Z-Wave device?
Vera comes close but you need to know the parameter to be able to find the setting of it, punching in 254 values one at a time is very laborious and time consuming, especially if you find that there are no further parameters......FWIW .Homeseer doesn't have this ability at all, perhaps someone can comment of HASS or other HA platforms in use?
Some will question why do you need to do this?
Apart from discovering any unknown parameters just because they are there, Z-Wave device manufacturers do not publish all parameters that are used in a device - generally because they have been added after the device has been certified and publishing it renders Certification void.
Would it be useful? Yes, as an example a Device we had in a Z-Wave net didn't behave as expected. An email exchange between the manufacturer divulged a "hidden parameter" which when switched on caused the device to behave correctly. If we had known that there was an extra Parameter then we would have tested it to find out what it did. It may or may not have worked but we would have had the opportunity to try it beforehand.
Anyway, it's useful to know when engaging with manufacturers, it gives you the upper hand...... -
At this stage, probably not, just for the lack of consistency. The issues:
- Vera, we know, keeps the data in state variables, and we get what we get. You can get that today -- just look at the attribute on the entity in MSR and see as much information as it could publish. On a Vera ZWave device, look for
x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet
. - On Hass, not only does the API not tell you what integration drives an entity, but even if you forced that association by declaring the ZWave service, the service itself doesn't publish any attributes/data from the integration through the API. So the configuration variables aren't visible at all. Nor is the device's manufacturer info, model number, or even its ZWave node ID. Mind you, Hass has all of this information, it must in order to function, it just doesn't publish any of it through its APIs.
- On Hubitat, pretty much the same story as Hass: the API doesn't tell you what driver supplies the device, so you don't even know it's ZWave, and there's no data available attached to the device that's published through the API related to ZWave, anyway.
- On eZLO, they do identify the device by its parent "protocol" (zwave), and give you the ZWave node ID and a couple of flags, but no other useful information that I've seen. There aren't even API commands available for single-node things like poll a node or set a config value, only network-wide commands for things like start/stop inclusion or reset the Zwave chip and delete the entire network (i.e. not things you usually want to do in an automation). Since I'm probably the only person who cares if those other things exist and I'm persona non grata over there, they're probably not getting done any time soon, whether I report them or not. I haven't used any devices on my eZLO system that have configuration parameters, so I can't tell if or how it publishes those. If someone has included on their eZLO system a device that normally uses configuration parameters, like an Aeotec Multisensor, etc., please send me via PM your
logs/ezlo_data_list.json
file. I'd love to see if it has anything.
Very low on my priorities (particularly with the big changes to the core/Engine of late) has been direct integration with ZWave-JS. That would expose all the right information, I'm sure. But that's really no small task, and in essence, transforms MSR from an automation tool into the realm of being a hub itself. Maybe that's not bad.
- Vera, we know, keeps the data in state variables, and we get what we get. You can get that today -- just look at the attribute on the entity in MSR and see as much information as it could publish. On a Vera ZWave device, look for