Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp3079763ybv; Sat, 15 Feb 2020 10:27:59 -0800 (PST) X-Google-Smtp-Source: APXvYqwXAKai0Q4QcAVMV3/4JytA4PNFGjyAK79wGrwu/KLtSKqcWnZbjfdxB3pFavVzSkZ5h0v9 X-Received: by 2002:a9d:649a:: with SMTP id g26mr6481751otl.15.1581791279219; Sat, 15 Feb 2020 10:27:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581791279; cv=none; d=google.com; s=arc-20160816; b=puUD1eTdfpFeVNS1QziRwFhGz5IcH2TdEd7b9EYwpuxmfkL7CMHqryI52d/eszTzHZ YbeNn7LC9O1xjlO/LVgLemtsbAUTjUC2810odF3MJTwej+SEODTrX1YMaV2jytnE4Rs9 ac7qG4xoTeDw6q+AgRWpMhfx38o7HeL8Hc3SfCm514DSPdPk7CpZoyJ9Cl8ZLSvs9b4u jNga70OJlsGCDByvVJvsgqKrlmLrefcCkLKNSqGpSU4DSYMJwzvk0mz/G2SL1KVJqpRm Q2noIv/hBMpbqGjbtzC69SpYcnUA2GTURG8UAd09ZCvbJpwiMdsRxb4oCGRqEWZ6zl23 GIDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:mime-version:user-agent:date:message-id:subject :from:to:dkim-signature; bh=sqR6jvCezxifu6HIZJks15S/qgDB2yExmYTkNf8OAXo=; b=kgDDli6soh2rdo/MZ5TPjHCwgLL6OUMyKcbhOB/JoCnc0hniz4sBp8/2uAoejPVwe6 hR0n9V6I7TgLeZhzCebEPCbCzVqa+bZaTgmaPPK3b+hMfpplEKRMnkNqymfgxFBM2FZt UU49figPX0j4ligzldmZSN5XnOL3eu4uFAnqLfDWmtOs35G1gFrYxhfDk4RytaD0y1az mfYoxMf9+vLSx39v7CnJ4MzquPPWNhovQaC4pRdEOnsJS4WvGpTatdNr0Ukk8WcTiMtl QvQuS2TwgWsR4Y10DYL5U9A1bSa+osFwm8ObBQXWSFHD2knMje4yhgD/+whKkjqCCRrf tB4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mnmoran.org header.s=dkim header.b="LKxUN/hi"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s9si4338451oij.78.2020.02.15.10.27.26; Sat, 15 Feb 2020 10:27:59 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@mnmoran.org header.s=dkim header.b="LKxUN/hi"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726307AbgBOS1I (ORCPT + 99 others); Sat, 15 Feb 2020 13:27:08 -0500 Received: from hoster906.com ([192.252.156.27]:51986 "EHLO hoster906.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726299AbgBOS1I (ORCPT ); Sat, 15 Feb 2020 13:27:08 -0500 X-Greylist: delayed 400 seconds by postgrey-1.27 at vger.kernel.org; Sat, 15 Feb 2020 13:27:07 EST DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=mnmoran.org; h=to:from :subject:message-id:date:mime-version:content-type :content-transfer-encoding; s=dkim; bh=SczR5boP5q313A2eeaqYX6vkL Kl8DsseGursjaTbMUY=; b=LKxUN/hi1rjxiXf3yXusz0Tl87+sof6CUW+1vnktH R+v1fSTFd/r0JZp/zUSVJSwkKCaH6d3k1wtp9hjDK9sY0+/x6Ui1tcxtLuMHtfD1 AAY7Y01NiVdLWJ1166zC2FAB3q1F3dI3ovKvuSXtTik6SX8CQmy29yFB9zwqruNY MM= Received: (qmail 15385 invoked by uid 503); 15 Feb 2020 18:20:27 -0000 Received: from unknown (HELO ?192.168.254.100?) (pop-before-smtp@162.39.210.60) by hoster906.com with ESMTPA; 15 Feb 2020 18:20:27 -0000 To: linux-bluetooth@vger.kernel.org From: "Michael N. Moran" Subject: mesh: Send mesh model message to group address Message-ID: <848c1b0b-83c6-41a3-fc66-1359fa9a72bb@mnmoran.org> Date: Sat, 15 Feb 2020 13:20:21 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi, I'm new to the mailing list, so please be patient. I've been using meshctl to provision/configure a group of mesh nodes. There does not seem to be a mechanism in meshctl to send model messages to group addresses or virtual addresses. As an example, consider the simple OnOff model. I can configure the subscription for an OnOff model with a group address. However, the meshctl onoff command will not work with a group address set for the onoff target. I have modified the cmd_set() function in onoff-model.c by removing the node_find_by_addr(target) check and this works fine. Obviously, that only works for the OnOff model. I'd happily submit a patch for that model, but that doesn't seem to be a very good general solution. So is meshctl the right (only) tool to use on Linux? Is there a newer tool that is planned or under development? regards, mike