
RPerrault
Members-
Posts
279 -
Joined
-
Last visited
Everything posted by RPerrault
-
Can multiple Zwave commands be sent at the same time?
RPerrault replied to peterathans's topic in ZMatter
oh - and i send individual commands to my 3 blinds now with about 8 second delay between commands should have used lutron - sigh -
Can multiple Zwave commands be sent at the same time?
RPerrault replied to peterathans's topic in ZMatter
open the event viewer and try it my guess is that associations are the way z-wave does what you want - and you won't get much help here with that i have not thrown in the towel yet - going to get a zooz stick and download the silicone labs software - then see how my devices install with that (i suspect i will have the association capabilities) - set my 3 devices in a z-wave group association (not z-wave scene association) - and see if i can control all 3 with one command and have them all respond at the same time i don't use z-wave for lighting and such i am guessing the implementation is similar to multicasting - when your pc joins a multicast group, your network adapter begins listening for traffic on a second ip address for this, dimmer 1 has an address of 7f - dimmer 2 has an address of 6f - an association group of 2f contains both 7f and 6f - so both devices will respond to a command sent to 2f - no need to send individual commands to the dimmers just a guess - but be careful, understanding the concept is not welcome here - just rote memorization of steps and scolding to use search -
looks like my first step is to find out why my devices install without the additional entries for association during the include (or 'interview'), what needs to be passed to the eisy for it to add those entries?
-
it would be interesting to know what command class supports associations - and what z-wave version - and what device types then if it supports the beam or flirs or wakeup call to the device then its on to return routes i think the article on that uses a zooz software (controller and zooz usb radio) which would be z-wave centered - notsomuch with the eisy
-
i asked the device manufacturer before starting this thread. and seeing little help here. this is what they said: iBlidns supports Associaton, but there is a catch: the Associated controlling device needs to support beaming (have the ability to send a special command to wake up the iblidns motor). It's also important that the Z-Wave hub follows the correct process when making the Z-Wave associations. We've noticed that most hubs don't. Here's an article written by Dr.Zwave: https://drzwave.blog/2021/02/01/controlling-flirs-via-associations/ the cited article is a little over my head, but it seems that if supporting the 'flirs' is part of the standard but not supported here. i am thinking that my step 1 is getting any kind of association set up. i see where others have done it here but they have an option under the dropdown menu (when in an insteon scene) for some z-wave options. nothing on my system has any z-wave option. which is why i posted the manufactures specs on what it should support and the xrays on how the iesy did install. i was hoping that might identify if the devices are installing correctly. that was the way my pointy head reasoned out the problem. i don't use much z-wave but before i began, installed 4 repeaters. aeotec v6. ordered the same brand in v7 so i can rule out z-wave versions as being a problem. they should arrive tomorrow. thanks for the reply
-
aha - huge step forward how did you get the association set up - that caused the entry names 'basic assoc 2' or 3
-
its z-wave - each command is slow and waits for nack/ack - tried lots of things if i could assign the devices to a common association group, one command to that group should operate all the devices at one time but i cannot find a way in the eisy to assign devices to a association group when a discussion gets close to asking, the thread is ghosted and closed thought i'd try the direct question incidentally - i can create an eisy scene and add the z-wave blind - add a keypad button - and it works - and it works with alexa gets more complicated with 3 blinds with one button these are opened/closed at sunrise/sunset - rarely any other way - you have to add a 5-8 second delay between z-wave commands but still - association groups are the closest thing to insteon scenes - and i suspect lots of people here would pee their panties if we could implement them - lots of people want virtual 3-way switches and this should accomplish that for them the web link above is the easiest explanation of associations, groups and scenes in the z-wave world that i have found i contacted the iblinds seller and he said the blinds had the capability - and should work IF the controller can handle it - so i posted the specs of how the devices install and the command sets the devices support - and some of the xray screen shots of how they installed on my eisy i don't see any way to do it in the eisy unless it is setting some parameters' i suspect it does not support it - which is why the replies stop i also suspect others have other controllers then swap controllers to primary or use zooz sticks then transfer - none of which i an interested in doing i have resisted a deep dive into z-wave - and so far been successful be nice to have an answer without having to learn the internals of z-wave - if i understand it correctly, z-wave is not an open system and could be why people are not free to discuss it online
-
should have done lutron
-
i set up my eisy using 5.6.4 just updated to 5.7.0 i only use z-wave for water detection, smoke/co2 detectors and blinds i have 4 repeaters installed i want to have 3 blinds open or close at the same time - these are iblinds z-wave motors they install to the eisy as either of these two device types Z-Wave Command Classes iblinds Supported Command Classes – cc:5E,85,59,86,72,5A,73,26,25,80,70 Command Class Association Group Info V2 Command Class Association V2 Command Class Basic V2 Command Class Battery Command Class Device Reset Locally Command Class Manufacturer Specific V2 Command Class Powerlevel Command Class Switch Binary Command Class Switch Multilevel V4 Command Class Version V2 Command Class Z-Wave+ Info V2 iblinds V2 Product Details Z-Wave Specific Device Type: Window Covering – Endpoint and Position Aware, CLASS_B_MOTOR_CONTROL Z-Wave Generic Device Type: Multilevel Switch Z-Wave Role Type: Listening Sleeping Slave Manufacturer ID: 0287 Product Type ID: 0x0003 Product ID: 0x000D and Z-Wave Command Classes SWITCH_BINARY SUPERVISION ASSOCIATION V2 FIRMWARE UPDATE MD V5 ASSOSCIATION GROUP INFO BATTERY TRANSPORT SERVICE V2 MULTILEVEL SWITCH VERSION V2 CONFIGURATION MANUFACTURER SPECIFIC INDICATOR V3 DEVICE RESET LOCALLY Z-WAVE PLUS INFO V2 POWERLEVEL MULTI CHANNEL ASSOCIATION V3 SECURITY V2 WINDOW COVERING V1 iblinds V3 Product Details Z-Wave Specific Device Type: Window Covering – Endpoint and Position Aware, CLASS_C_MOTOR_CONTROL Z-Wave Generic Device Type: Multilevel Switch Z-Wave Role Type: Listening Sleeping Slave Manufacturer ID: 0287 Product Type ID: 0x0004 Product ID: 0x0071, 0x0072 reading this https://www.vesternet.com/en-us/pages/z-wave-groups-scenes-associations i should be able to use a group to open/close all 3 blinds with one command i have individual blinds in an insteon scene with a keypad button and that seems to work adding 3 blinds to an insteon scene does not the blinds will open /close with alexa the manufacturer said it should work, depending on the controller i have not seen a direct answer here when asked about setting up associations, groups or z-wave scenes - other than 'if it supports it there will be an option in the drop down menu in the scene' - and not sure anyone has seen that on any device x-ray node definition <nodeDefs> <nodedef nls="119" id="ZY066_1"> <sts> <st editor="_51_0_R_0_101_N_IX_DIM_REP" id="ST"/> <st editor="_51_0_R_0_100" id="BATLVL"/> <st hide="T" editor="ZY_ERR" id="ERR"/> </sts> <cmds> <sends> <cmd id="DON"/> <cmd id="DOF"/> <cmd id="FDUP"/> <cmd id="FDDOWN"/> <cmd id="FDSTOP"/> </sends> <accepts> <cmd id="DON"> <p optional="T" editor="ZY_DIM_PERCENT" init="ST" id=""/> <p optional="T" editor="ZY_RR" id="RR"/> </cmd> <cmd id="DOF"/> <cmd id="DFON"/> <cmd id="DFOF"/> <cmd native="F" id="BRT"/> <cmd native="F" id="DIM"/> <cmd id="FDUP"> <p optional="T" editor="ZY_DIM_PERCENT" init="ST" id="STARTLEVEL"/> <p optional="T" editor="ZY_RR" id="RR"/> </cmd> <cmd id="FDDOWN"> <p optional="T" editor="ZY_DIM_PERCENT" init="ST" id="STARTLEVEL"/> <p optional="T" editor="ZY_RR" id="RR"/> </cmd> <cmd id="FADE"> <p editor="ZY_MLS_DIR" id="DIR"/> <p optional="T" editor="ZY_DIM_PERCENT" init="ST" id="STARTLEVEL"/> <p optional="T" editor="ZY_RR" id="RR"/> <p optional="T" editor="ZY_MLS_DIR" id="DIR2"/> <p optional="T" editor="ZY_RR" id="STEP2"/> </cmd> <cmd id="FDSTOP"/> <cmd id="QUERY"/> <cmd id="CONFIG"> <p editor="_107_0_R_0_255" id="NUM"/> <p editor="ZY_CONFIG" id="VAL"/> </cmd> <cmd id="WDU"/> </accepts> </cmds> <links> <ctl/> <rsp> <link gid="ASSOC" linkdef="ASSOC"/> <link gid="ASSOC" linkdef="ASSOC_MC"/> <link gid="BASIC" linkdef="BASIC"/> <link gid="BASIC" linkdef="BASIC_MC"/> <link gid="MLSW" linkdef="MLSW"/> <link gid="MLSW" linkdef="MLSW_MC"/> </rsp> </links> </nodedef> </nodeDefs> associations All Assocations for node 66 (0x42) Assocation version=2 groups=1 | Group 1 : max=1 [01] device object Z-Wave Database for uid=66.0 (0x42.00) Isy Primary Node: id=226 addr=[ZY066_1] ZW-Type: 4.17.0 (0x04.0x11.0x00) Mfg Specific: mid=647 tid=3 pid=13 ZWave+ RoleType=0 NodeType=0 Flags: initialized=T agi=F alwaysAwake=F Security: No Security --- 12 Command Classes --- 32 x20 V2 I S BASIC 37 x25 V2 I S SWITCH_BINARY 38 x26 V4 I S SWITCH_MULTILEVEL 89 x59 V2 I S ASSOCIATION_GROUP_INFO 90 x5a V1 I S DEVICE_RESET_LOCALLY 94 x5e V2 I S ZWAVEPLUS_INFO 112 x70 V0 I S CONFIGURATION 114 x72 V2 I S MANUFACTURER_SPECIFIC 115 x73 V1 I S POWERLEVEL 128 x80 V1 I S BATTERY 133 x85 V2 I S ASSOCIATION 134 x86 V2 I S VERSION --- 2 AGI --- grp= 1 cc=0x80.03 profile=0x00.01 maxRsp=1 /1 BATTERY grp= 1 cc=0x5A.01 profile=0x00.01 maxRsp=1 /1 DEVICE_RESET_LOCALLY --- Status Map (3 records) --- [ 0] 0x26/SWITCH_MULTILEVEL recId=1 sgid=119 ST uom=51 prec=0 namemap=27 | min=0 max=101 [ 1] 0x25/SWITCH_BINARY recId=1 sgid=147 ST uom=78 prec=0 namemap=0 | predef=2 [ 2] 0x80/BATTERY recId=1 sgid=119 BATLVL uom=51 prec=0 namemap=0 | min=0 max=100 --- Control Map (0 records) --- --- Responder Map (10 records) --- [ 0] sgid=119 ASSOC ASSOC (1, 1) [ 1] sgid=119 ASSOC ASSOC_MC (1, 51) [ 2] sgid=119 BASIC BASIC (2, 2) [ 3] sgid=119 BASIC BASIC_MC (2, 52) [ 4] sgid=147 BSW BSW (3, 3) [ 5] sgid=147 BSW BSW_MC (3, 53) [ 6] sgid=119 MLSW MLSW (4, 4) [ 7] sgid=119 MLSW MLSW_MC (4, 54) [ 8] sgid=259 SCENE SCENE_RSP (5, 6) [ 9] sgid=259 SCENE SCENE_RSP_MC (5, 56) --- Status Callbacks --- [ 0] 0x25/SWITCH_BINARY id=0 path="level" [ 1] 0x26/SWITCH_MULTILEVEL id=0 path="level" [ 2] 0x80/BATTERY id=0 path="last" --- Control Callbacks --- device/channel database object Z-Wave Database for uid=66.0 (0x42.00) Isy Primary Node: id=226 addr=[ZY066_1] ZW-Type: 4.17.0 (0x04.0x11.0x00) Mfg Specific: mid=647 tid=3 pid=13 ZWave+ RoleType=0 NodeType=0 Flags: initialized=T agi=F alwaysAwake=F Security: No Security --- 12 Command Classes --- 32 x20 V2 I S BASIC 37 x25 V2 I S SWITCH_BINARY 38 x26 V4 I S SWITCH_MULTILEVEL 89 x59 V2 I S ASSOCIATION_GROUP_INFO 90 x5a V1 I S DEVICE_RESET_LOCALLY 94 x5e V2 I S ZWAVEPLUS_INFO 112 x70 V0 I S CONFIGURATION 114 x72 V2 I S MANUFACTURER_SPECIFIC 115 x73 V1 I S POWERLEVEL 128 x80 V1 I S BATTERY 133 x85 V2 I S ASSOCIATION 134 x86 V2 I S VERSION --- 2 AGI --- grp= 1 cc=0x80.03 profile=0x00.01 maxRsp=1 /1 BATTERY grp= 1 cc=0x5A.01 profile=0x00.01 maxRsp=1 /1 DEVICE_RESET_LOCALLY --- Status Map (3 records) --- [ 0] 0x26/SWITCH_MULTILEVEL recId=1 sgid=119 ST uom=51 prec=0 namemap=27 | min=0 max=101 [ 1] 0x25/SWITCH_BINARY recId=1 sgid=147 ST uom=78 prec=0 namemap=0 | predef=2 [ 2] 0x80/BATTERY recId=1 sgid=119 BATLVL uom=51 prec=0 namemap=0 | min=0 max=100 --- Control Map (0 records) --- --- Responder Map (10 records) --- [ 0] sgid=119 ASSOC ASSOC (1, 1) [ 1] sgid=119 ASSOC ASSOC_MC (1, 51) [ 2] sgid=119 BASIC BASIC (2, 2) [ 3] sgid=119 BASIC BASIC_MC (2, 52) [ 4] sgid=147 BSW BSW (3, 3) [ 5] sgid=147 BSW BSW_MC (3, 53) [ 6] sgid=119 MLSW MLSW (4, 4) [ 7] sgid=119 MLSW MLSW_MC (4, 54) [ 8] sgid=259 SCENE SCENE_RSP (5, 6) [ 9] sgid=259 SCENE SCENE_RSP_MC (5, 56) --- Status Callbacks --- [ 0] 0x25/SWITCH_BINARY id=0 path="level" [ 1] 0x26/SWITCH_MULTILEVEL id=0 path="level" [ 2] 0x80/BATTERY id=0 path="last" --- Control Callbacks --- are these devices installing correctly? how can i create a group with all 3 blinds to respond to an open/close command from my eisy?
-
elk if you have it your choice of devices that actually work
-
sockets discard new work arriving when their buffers are full - might be that nodelink is firing off new connections - in fact, it sounds like it is and the isy side is creating new sockets to hold the work arriving from nodelink - the question is why nodelink is doing that if disabling that heartbeat is possible, i'd do it to see if nodelink stops creating new connections
-
its all my nodes that have to be reconnected
-
i have the same problem - i found that when the internet connection to the isy drops and recovers, the nodes are not communicating - have to restart the nodes to get it working again annoying
-
until alexa has the ability to know the fan by the alexa location, i don't use it to operate fans it can become formulaic speech with 'guest bedroom fan to low' instead of 'fan to low' i whined to michel to give alexa location awareness until alexa routines gave me that with lights ('turn the lights off' instead of 'turn the guest bedroom lights off') but i do have a ton of pedestals with keypads and remotes to operate fans
-
and - scenes work with or without the isy
-
oh - i never use the isy to control devices from its interface its not practical for me and i never met a wife that uses the isy interface either my philosophy of home automation is not like most here - i try to make it easy to do what you want to do - not guess what you want done
-
is there a reason you need programs to do this? i accomplish it without them
-
what are the standard commands/messages for a zigbee light bulb?
-
the resistance to open standards is strongest here - if that matters
-
be sure insteon support is still checked on the config - it has been known to become unchecked during a plm restore
-
careful - you'll get a private nastygram then he will lock the thread after you are called a drunk so you won't reply i do think there is a missed opportunity on documentation - especially conceptual overviews - people that have been here a decade do not understand the concepts, especially since polynode whatever - but i will say its not easy to find someone that understands the concepts and has the ability to effectively write those concepts for the audience
-
How to use Alexa AV to control receiver volume?
RPerrault replied to landolfi's topic in Amazon Echo
my comment was to say this homeseer has had some form of voice control for a long time in response to the comment on local based voice control and what hardware might be necessary to drive it -
How to use Alexa AV to control receiver volume?
RPerrault replied to landolfi's topic in Amazon Echo
homeseer -
email is an interesting beast - i recently moved a municipality from an exchange server to microsoft 365 - learned some things but i am in no way an expert microsoft 365 has some rudimentary filtering but i chose to add barracuda for extra protection - and its good - has fended off attacks successfully - so far internal email is not parsed - only incoming and outgoing external email of course it does not deliver viruses - but that is not all that is not delivered if a sender's dkim or spf key has a problem, not delivered - this is not uncommon even among technology companies (check your dns entry) - some will overlook those errors (microsoft 365 will), barracuda (by default) does not ignore those errors 'intent' is another reason email is not delivered this one was interesting - 'reputation' - caused me some grief if barracuda (not a small player) deems you to have a bad reputation (spammer, for example), your emails are not delivered - you can check if a company is on barracuda's naughty list here https://www.barracudacentral.org/lookups interesting to know, if someone is on the naughty list, it will be blocked from delivery if that company is referenced in the email content - if someone forwards an email to me that refers to that company, not delivered - this can even be in a signature block for example, if barracuda considers instagram to be naughty, an email to me with an icon linking to their instagram account - even in their signature block - no delivery it will not pass if i send that email with the signature block, remove the signature, its delivered as best i can tell, those notifications you get are from the email provider - if barracuda rejects delivery, i am unsure if you get a notification so email is not absolute - if it sends to one account successfully, that gives you some information but is not proof that it should send to all computers suck not back to my first sd-wan conversion - wish me luck