misterhouse-users Mailing List for MisterHouse: Home Automation with Perl

Thanks Serge, I think my problem for outputs is that the weeder IO board I have outputs voltage, so I either need relays, or to pick up the weedtech relay board.

I noticed that their cases are sold out and not for sale anymore. Does anyone on the list have a CASE-SM that they don’t need and want to sell? I’ll have to find a DB9 serial cable and a WTSSR-M

> On Aug 22, 2023, at 6:36 PM, Serge Martel (smartel) <sm...@sm...> wrote:
> 
> I moved away from MH for a while now, so it's not so fresh in my memory, but I used to have a weeder board, it was very solid and reliable, I dived in my code file and found this, for my inputs, as you can see I chaged the default On, OFF to ferme and ouvert, or arme and desarme and it worked.
> 
> # Digital  items
> $portes_garage       = new  Serial_Item('AAH', 'ferme', 'weeder');        #A
> $portes_garage      -> add             ('AAL', 'ouvert', 'weeder');
> $portes_garage      -> add             ('ASA', 'init', 'weeder');
> $portes_garage      -> add             ('ARA', 'read', 'weeder');
> 
> 
> $alarme_status           = new  Serial_Item('ABH', 'desarme', 'weeder');        #B
> $alarme_status           -> add             ('ABL','arme', 'weeder');
> $alarme_status           -> add             ('ASB', 'init', 'weeder');
> $alarme_status           -> add             ('ARB', 'read', 'weeder');
> 
> 
> 
> and this for my outputs:
> 
> $AFX_Arm      = new Serial_Item('AHN', ON      , 'weeder');         #N
> $AFX_Arm     -> add     
> ('ALN', OFF     , 'weeder');
> $AFX_Arm     -> add     
> ('ARN', 'status', 'weeder');
> 
> 
> I did not reset every day but on every restart like so:
> 
> 
> $weeder_io_control=new Serial_Item('A!','reset','weeder');
> $start_timer = new Timer;
> 
> if ($Startup or (state_now $weeder_io_control eq 'reset')or $Reload ) {
> 
> net_mail_send to => 'me...@vm... <mailto:me...@vm...>', text =>' MrHouse restarted';
>         print_log " MrHouse restarted";
> 
> set $start_timer 30;
> 
> 
> for my $resetboard2 (
> $portes_garage,
> $alarme_status,
> $mom_unlock_garage,
> $cabanon_status,
> $Alarme_AC_fail,
> $Alarme_Maison,
> $sump_pump_b,
> $bedroom_motion_b,
> $IR_frigo,
> $IR_garage,
> $IR_atelier,
> $IR_poteau) {
> set $resetboard2 'init';
> select(undef, undef, undef, 0.025);
> 
> 
> Hope it helps you, it has been a while I used it, and I am no programmer, so don't expect me to understand everything😊
> 
> Good luck!
> 
> From: H Plato <hp...@gm... <mailto:hp...@gm...>>
> Sent: August 22, 2023 2:35:33 PM
> To: misterhouse list
> Subject: [mh] Weeder users?
>  
> I use Insteon IOlincs to sense and control my garage doors. They are also a bit unreliable, I had to disconnect one of the contacts from the opener as it was opening at night, and the sensors are missing about 1 in 10 open/close events.
> 
> I’ve run parallel wires to the magnetic open/close sensors to my weeder, and that seems to be more robust. However, it was a real challenge getting a few issues ironed out.
> 
> Looking at the code samples, it recommends initializing the weeder ports every night. This worked well for a single Serial_Item object, however when I added more, those objects were stuck at init. It seems like sending all the inits in one loop causes problems. I’ve been able to successfully reset all the ports using set_with_timer:
> 
> if ($New_Day) {
>             set_with_timer $front_doorbell_button 'init',1;
>             set_with_timer $back_doorbell_button 'init', 2;
>             set_with_timer $garage_door_S1 'init', 3;
>             set_with_timer $garage_door_S2 'init', 4; 
>             set_with_timer $garage_door_S3 'init', 5;
>             set_with_timer $garage_door_S4 'init', 6;
> }
> 
> So, here are my issues. I’m hoping that someone with some weeder experience might be able to help spot something I’m doing wrong
> 
> 1. I have $garage_door_S1 and $garage_door_S3 states set to open and close, however when the init happens, for whatever reason they come back as on and off. I used to have them on and off, but recently changed the code to be open and closed. I can’t see anywhere else in the code, or in Serial_Item.pm where something would be set to ON or OFF.
> 
> $garage_door_S1 = new Serial_Item( 'AEH', 'open', 'weeder' );
> $garage_door_S1->add( 'AEL', 'closed',     'weeder' );
> $garage_door_S1->add( 'ARE', 'read',  'weeder' );
> $garage_door_S1->add( 'ASE', 'init',  'weeder' );
> 
> $garage_door_S3 = new Serial_Item( 'AGH', 'open', 'weeder' );
> $garage_door_S3->add( 'AGL', 'closed',     'weeder' );
> $garage_door_S3->add( 'ARG', 'read',  'weeder' );
> $garage_door_S3->add( 'ASG', 'init',  'weeder' );
> 
> If I press the read button on the web interface nothing happens. However if the door opens or closes, it gets set to the proper state. I could put in a line that if the state is on then turn it to open, but that seems like a kludge and I might not have something properly configured.
> 
> 2. I want to wire the contacts of my opener to the weeder so I can send it a control signal. I could do this with the IOlinc to close a contact. I _think) it would be setting the port to low for a second, but would be great to hear if someone has done this:
> 
> $garage_door_S2 = new Serial_Item( 'AIH', ‘inactive', 'weeder' );
> $garage_door_S2->add( 'AIL', ‘active',     'weeder' );
> $garage_door_S2->add( 'ALI1000', ’toggle',     'weeder' );
> $garage_door_S2->add( 'ARI', 'read',  'weeder' );
> 
> 3. I use a proxy for my W800 for wireless motion sensors. It’s been pretty good. Could having the weeder serial and insteon serial in the same instance be adding to the problems? Would another proxy instance be a better solution?
> 
> 
> 
> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>

Master has been updated.

> On Aug 22, 2023, at 3:38 PM, Dave Neudoerffer <da...@ne...> wrote:
> 
> Howard:  I have submitted a pull request.  It includes one fix in particular whereby the check_for_data code for mqtt will now process all pending mqtt messages, rather than 1 per call.  I had a situation where there were 1000s of retained messages in a large mqtt environment, and it took MH 10-15 minutes processing these 1 at a time at startup until it would process regular MQTT messages.  I have seen no MH issues with this mqtt message processing change, and the 1000s of messages are processed at startup sub second.
> 
> Stephen:  mqtt_item is the original mqtt code.  It lines a separate mqtt_item object up with each mqtt message.  I implemented a separate module, mqtt_items.pm <http://mqtt_items.pm/>, that lines objects up with an mqtt device -- the normal MH way to do things.  I think if you try out the mqtt_RemoteItem it will do more what you are looking for.
> 
> Dave
> 
> On Tue, Aug 22, 2023 at 4:56 PM <mis...@si... <mailto:mis...@si...>> wrote:
> I'll be diving into MQTT in the next month or two. From this discussion I gather that there is an MH-native MQTT implementation, and apparently another approach that Giles is using. I've seen https://github.com/hollie/misterhouse/wiki/Items-mqtt <https://github.com/hollie/misterhouse/wiki/Items-mqtt> (though not yet studied it in-depth), but it doesn't apparently talk about what Giles is doing.
> 
> Can someone please give me a very superficial explanation of the differences, or else point me to an article somewhere. 
> 
> Thanks in advance for any enlightenment.
> 
>                       -Brian M
> 
> On 8/22/23 11:08, Giles Godart-Brown wrote:
>> I also have a lot of MQTT devices using the native MH code with no major issues.
>> Giles
>> 
>> On 22/08/2023 17:50, H Plato wrote:
>>> On an unrelated note, is the insteon MQTT code more reliable than the native MH support? Why did you switch?
>>> 
>>> I don’t have 120 devices, but probably 50 or so devices and it’s pretty good for reliability with the odd device exception. I have a challenge with some keypadlincs getting them to sync. the MH code seems to give up after a period of time, so I end up uninstalling the KPLs from the walls and into a temporary plastic electrical box that I can plug into the same outlet as the PLM.
>>> 
>>> Dave if you submit a PR I can merge it in. There’s been a bunch of changes over the past year or so, might be good to capture a release soon. Unfortunately my git skills have atrophied so every time I think about doing this I get frustrated with some git situation and figure I’ll do it later….
>>> 
>>>> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw... <mailto:st...@sw...>> wrote:
>>>> 
>>>> I'm probably running an old version of MH, so if this has been fixed in the past 1-2 years, then please tell me to update. :)
>>>> 
>>>> I created an integration that has MH listening to the mosquito broker for some light commands, and for the most part, it's working.                     However, it seems that random lights do not work when I send a MQTT command to the broker. I can see the command hit the broker, but it won't trigger an event in MH for all lights. I see no difference between the lights that work and those that do not.
>>>> 
>>>> Mosquito Broker:
>>>> insteon/living_room_lamp on
>>>> insteon/living_room_lamp/state on
>>>> 
>>>> insteon/living_room_fan_light on
>>>> caddx/motion/binary_sensor.living_motion/state on
>>>> insteon/living_room_lamp off
>>>> caddx/motion/binary_sensor.living_motion/state off
>>>> insteon/living_room_lamp/state off
>>>> 
>>>> 
>>>> MH:
>>>> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
>>>> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
>>>> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>>>> 
>>>> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
>>>> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
>>>> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
>>>> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
>>>> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
>>>> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>>>> 
>>>> You  can see MH is listening to the broker, sending messages successfully, etc. The living_room_fan_light  event was not picked up from the broker by MH. I don't see why. Here's the code snippets:
>>>> 
>>>> 
>>>> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', "", "", 120);
>>>> 
>>>> $MQTT_insteon_living_room_fan_light_set = new mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light");
>>>> $MQTT_insteon_living_room_fan_light_state = new mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light/state", 1, 1);
>>>> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>>>>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>>>>     set $living_room_fan_light $state;
>>>> }
>>>> if($state = state_now $fl_liv_fanlight) {
>>>>     $state = ON if $state == '100%';
>>>>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>>>>     set $MQTT_insteon_living_room_fan_light_state $state;
>>>> }
>>>> 
>>>> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon, "insteon/living_room_lamp");
>>>> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon, "insteon/living_room_lamp/state", 1, 1);
>>>> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>>>>     print_log("[MQTT_RECV] living_room_lamp: $state");
>>>>     set $living_room_lamp $state;
>>>> }
>>>> if($state = state_now $ll_liv_lamp1) {
>>>>     $state = ON if $state == '100%';
>>>>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>>>>     set $MQTT_insteon_living_room_lamp_state $state;
>>>> }
>>>> 
>>>> 
>>>> Mind you, I have about 120 lights in my code, all listening to $MQTT_insteon. Could there be a memory issue? I appreciate any input with ideas on this.
>>>> 
>>>> Thank you!
>>>> 
>>>> -- 
>>>> Best regards,
>>>> Steve Switzer
>>>> 
>>>> ---
>>>> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!
>>>> http://www.sbsROC.com <http://www.sbsroc.com/>________________________________________________________
>>>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>>> 
>>> 
>>> 
>>> 
>>> 
>>> ________________________________________________________
>>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>>> 
>> 
>> 
>> 
>> 
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
>> 
> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users <https://lists.sourceforge.net/lists/listinfo/misterhouse-users>
> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
> 

I've moved almost totally over to Tasmota devices because it supports 
both http and MQTT and can be flashed to most devices that contain an 
esp8266 chip.

For switches I use the native MH HTTP implementation because you get 
immediate confirmation that it worked e.g. in Items.mht;
TASMOTA_HTTP_SWITCH,       192.168.100.81, Immersion_heater,         
POWER1, Roof|Stay_off_when_out|Tasmota

I use MQTT for sensors, here are a few of examples; the broker is set up 
in items.mht as follows;
MQTT_BROKER,     mqtt_1

I have a Wemos D1 connected to a string of DS18B20 1-wire temperature 
sensors that is defined in items.mht as follows;
MQTT_DEVICE,     Roof_1_temperatures,     MQTT_tempertures|Roof,     
mqtt_1,     tele/Roof_1_temperatures/SENSOR

Tasmota supports a huge number of devices, however some are not in the 
supplied binaries, but are in their library, so you may need to do your 
own build using their library code and a configuration file telling it 
what modules to include.  This is pretty easy if you use github, if 
anyone wants more on this please email me.  For example the MFRC522 
RFID  reader is one such device that is supported by their library but 
not in the supplied binaries so once you have flashed Tasmota with your 
build, it can be set up in MH items.mht as follows;
MQTT_DEVICE,     Back_hall_RFID,     Back_hall|tasmota_RFID, mqtt_1,     
tele/Back_hall_RFID/SENSOR

The Tasmota Zigbee gateway is really useful to convert zigbee messages 
to MQTT.  You need to flash a device like the Sonoff Zigbee bridge with 
Tasmota, then you can get these to interface with MH.  The device is 
defined in items.mht as follows;
MQTT_DEVICE,     Back_hall_zigbee_gateway, Back_hall|zigbee_gateway ,    
mqtt_1, tele/Back_hall_zigbee_gateway/SENSOR
CODE,          $Back_hall_zigbee_gateway->{address} = "192.168.100.101";
CODE,  $Back_hall_zigbee_gateway->{states_casesensitive} = 1;
Attached are a couple of screen grabs from the Zigbee gateway. Note the 
records starting MQT: are the records it sends via MQTT.

There was an omission in the first release of the MH interface that did 
not support wildcards which we fixed and I now believe is in the current 
build.  I make extensive use of the MQTT  Last Will and Testament (LWT) 
feature to detect when devices are powered up and when they die, for 
this I use a wildcard for all LWT messages then decode the topic to find 
the actual name of the device whose state changed.  items.mht is defined 
as follows;
MQTT_DEVICE,     MQTT_LWT, ,     mqtt_1,     tele/+/LWT
or for IP status messages
MQTT_DEVICE,     MQTT_status5_handler, ,     mqtt_1, stat/+/STATUS5
Note that the MH MQTT handler messes with the case, if you want the case 
of the messages to be unchanged when you get them in MH,  add this line;
CODE,          $MQTT_status5_handler->{states_casesensitive} = 1;

I hope this helps
Giles
p.s. Many years ago I met Andy Stanford-Clark who led the team at IBM 
that developed MQTT, at the time I didn't get what he was so passionate 
about, now I get it.

On 22/08/2023 21:30, mis...@si... wrote:
> I'll be diving into MQTT in the next month or two. From this 
> discussion I gather that there is an MH-native MQTT implementation, 
> and apparently another approach that Giles is using. I've seen 
> https://github.com/hollie/misterhouse/wiki/Items-mqtt (though not yet 
> studied it in-depth), but it doesn't apparently talk about what Giles 
> is doing.
>
> Can someone please give me a very superficial explanation of the 
> differences, or else point me to an article somewhere.
>
> Thanks in advance for any enlightenment.
>
>                       -Brian M
>
> On 8/22/23 11:08, Giles Godart-Brown wrote:
>> I also have a lot of MQTT devices using the native MH code with no 
>> major issues.
>> Giles
>>
>> On 22/08/2023 17:50, H Plato wrote:
>>> On an unrelated note, is the insteon MQTT code more reliable than 
>>> the native MH support? Why did you switch?
>>>
>>> I don’t have 120 devices, but probably 50 or so devices and it’s 
>>> pretty good for reliability with the odd device exception. I have a 
>>> challenge with some keypadlincs getting them to sync. the MH code 
>>> seems to give up after a period of time, so I end up uninstalling 
>>> the KPLs from the walls and into a temporary plastic electrical box 
>>> that I can plug into the same outlet as the PLM.
>>>
>>> Dave if you submit a PR I can merge it in. There’s been a bunch of 
>>> changes over the past year or so, might be good to capture a release 
>>> soon. Unfortunately my git skills have atrophied so every time I 
>>> think about doing this I get frustrated with some git situation and 
>>> figure I’ll do it later….
>>>
>>>> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw...> 
>>>> wrote:
>>>>
>>>> I'm probably running an old version of MH, so if this has been 
>>>> fixed in the past 1-2 years, then please tell me to update. :)
>>>>
>>>> I created an integration that has MH listening to the mosquito 
>>>> broker for some light commands, and for the most part, it's 
>>>> working. However, it seems that random lights do not work when I 
>>>> send a MQTT command to the broker. I can see the command hit the 
>>>> broker, but it won't trigger an event in MH for all lights. I see 
>>>> no difference between the lights that work and those that do not.
>>>>
>>>> Mosquito Broker:
>>>> insteon/living_room_lamp on
>>>> insteon/living_room_lamp/state on
>>>>
>>>> insteon/living_room_fan_light on
>>>> caddx/motion/binary_sensor.living_motion/state on
>>>> insteon/living_room_lamp off
>>>> caddx/motion/binary_sensor.living_motion/state off
>>>> insteon/living_room_lamp/state off
>>>>
>>>>
>>>> MH:
>>>> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
>>>> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
>>>> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>>>>
>>>> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
>>>> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
>>>> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
>>>> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
>>>> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
>>>> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>>>>
>>>> You  can see MH is listening to the broker, sending messages 
>>>> successfully, etc. The living_room_fan_light  event was not picked 
>>>> up from the broker by MH. I don't see why. Here's the code snippets:
>>>>
>>>>
>>>> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', 
>>>> "", "", 120);
>>>>
>>>> $MQTT_insteon_living_room_fan_light_set = new 
>>>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light");
>>>> $MQTT_insteon_living_room_fan_light_state = new 
>>>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light/state", 1, 1);
>>>> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>>>>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>>>>     set $living_room_fan_light $state;
>>>> }
>>>> if($state = state_now $fl_liv_fanlight) {
>>>>     $state = ON if $state == '100%';
>>>>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>>>>     set $MQTT_insteon_living_room_fan_light_state $state;
>>>> }
>>>>
>>>> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon, 
>>>> "insteon/living_room_lamp");
>>>> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon, 
>>>> "insteon/living_room_lamp/state", 1, 1);
>>>> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>>>>     print_log("[MQTT_RECV] living_room_lamp: $state");
>>>>     set $living_room_lamp $state;
>>>> }
>>>> if($state = state_now $ll_liv_lamp1) {
>>>>     $state = ON if $state == '100%';
>>>>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>>>>     set $MQTT_insteon_living_room_lamp_state $state;
>>>> }
>>>>
>>>>
>>>> Mind you, I have about 120 lights in my code, all listening to 
>>>> $MQTT_insteon. Could there be a memory issue? I appreciate any 
>>>> input with ideas on this.
>>>>
>>>> Thank you!
>>>>
>>>> -- 
>>>> Best regards,
>>>> Steve Switzer
>>>>
>>>> ---
>>>> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!
>>>> http://www.sbsROC.com  <http://www.sbsroc.com/>
>>>> ________________________________________________________
>>>> To unsubscribe from this list, go to: 
>>>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>>
>>>
>>>
>>>
>>> ________________________________________________________
>>> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>
>>
>>
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

Howard:  I have submitted a pull request.  It includes one fix in
particular whereby the check_for_data code for mqtt will now process all
pending mqtt messages, rather than 1 per call.  I had a situation where
there were 1000s of retained messages in a large mqtt environment, and it
took MH 10-15 minutes processing these 1 at a time at startup until it
would process regular MQTT messages.  I have seen no MH issues with this
mqtt message processing change, and the 1000s of messages are processed at
startup sub second.

Stephen:  mqtt_item is the original mqtt code.  It lines a separate
mqtt_item object up with each mqtt message.  I implemented a separate
module, mqtt_items.pm, that lines objects up with an mqtt device -- the
normal MH way to do things.  I think if you try out the mqtt_RemoteItem it
will do more what you are looking for.

Dave

On Tue, Aug 22, 2023 at 4:56 PM <mis...@si...> wrote:

> I'll be diving into MQTT in the next month or two. From this discussion I
> gather that there is an MH-native MQTT implementation, and apparently
> another approach that Giles is using. I've seen
> https://github.com/hollie/misterhouse/wiki/Items-mqtt (though not yet
> studied it in-depth), but it doesn't apparently talk about what Giles is
> doing.
>
> Can someone please give me a very superficial explanation of the
> differences, or else point me to an article somewhere.
>
> Thanks in advance for any enlightenment.
>
>                       -Brian M
>
> On 8/22/23 11:08, Giles Godart-Brown wrote:
>
> I also have a lot of MQTT devices using the native MH code with no major
> issues.
> Giles
>
> On 22/08/2023 17:50, H Plato wrote:
>
> On an unrelated note, is the insteon MQTT code more reliable than the
> native MH support? Why did you switch?
>
> I don’t have 120 devices, but probably 50 or so devices and it’s pretty
> good for reliability with the odd device exception. I have a challenge with
> some keypadlincs getting them to sync. the MH code seems to give up after a
> period of time, so I end up uninstalling the KPLs from the walls and into a
> temporary plastic electrical box that I can plug into the same outlet as
> the PLM.
>
> Dave if you submit a PR I can merge it in. There’s been a bunch of changes
> over the past year or so, might be good to capture a release soon.
> Unfortunately my git skills have atrophied so every time I think about
> doing this I get frustrated with some git situation and figure I’ll do it
> later….
>
> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw...> wrote:
>
> I'm probably running an old version of MH, so if this has been fixed in
> the past 1-2 years, then please tell me to update. :)
>
> I created an integration that has MH listening to the mosquito broker for
> some light commands, and for the most part, it's working. However, it seems
> that random lights do not work when I send a MQTT command to the broker. I
> can see the command hit the broker, but it won't trigger an event in MH for
> all lights. I see no difference between the lights that work and those that
> do not.
>
> Mosquito Broker:
> insteon/living_room_lamp on
> insteon/living_room_lamp/state on
>
> insteon/living_room_fan_light on
> caddx/motion/binary_sensor.living_motion/state on
> insteon/living_room_lamp off
> caddx/motion/binary_sensor.living_motion/state off
> insteon/living_room_lamp/state off
>
>
> MH:
> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>
> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>
> You  can see MH is listening to the broker, sending messages successfully,
> etc. The living_room_fan_light  event was not picked up from the broker by
> MH. I don't see why. Here's the code snippets:
>
>
> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', "", "",
> 120);
>
> $MQTT_insteon_living_room_fan_light_set = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_fan_light");
> $MQTT_insteon_living_room_fan_light_state = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_fan_light/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>     set $living_room_fan_light $state;
> }
> if($state = state_now $fl_liv_fanlight) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>     set $MQTT_insteon_living_room_fan_light_state $state;
> }
>
> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_lamp");
> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_lamp/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>     print_log("[MQTT_RECV] living_room_lamp: $state");
>     set $living_room_lamp $state;
> }
> if($state = state_now $ll_liv_lamp1) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>     set $MQTT_insteon_living_room_lamp_state $state;
> }
>
>
> Mind you, I have about 120 lights in my code, all listening to
> $MQTT_insteon. Could there be a memory issue? I appreciate any input with
> ideas on this.
>
> Thank you!
>
> --
>
> Best regards,
> Steve Switzer
>
> ---
> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!http://www.sbsROC.com <http://www.sbsroc.com/>
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

I'll be diving into MQTT in the next month or two. From this discussion 
I gather that there is an MH-native MQTT implementation, and apparently 
another approach that Giles is using. I've seen 
https://github.com/hollie/misterhouse/wiki/Items-mqtt (though not yet 
studied it in-depth), but it doesn't apparently talk about what Giles is 
doing.

Can someone please give me a very superficial explanation of the 
differences, or else point me to an article somewhere.

Thanks in advance for any enlightenment.

                       -Brian M

On 8/22/23 11:08, Giles Godart-Brown wrote:
> I also have a lot of MQTT devices using the native MH code with no 
> major issues.
> Giles
>
> On 22/08/2023 17:50, H Plato wrote:
>> On an unrelated note, is the insteon MQTT code more reliable than the 
>> native MH support? Why did you switch?
>>
>> I don’t have 120 devices, but probably 50 or so devices and it’s 
>> pretty good for reliability with the odd device exception. I have a 
>> challenge with some keypadlincs getting them to sync. the MH code 
>> seems to give up after a period of time, so I end up uninstalling the 
>> KPLs from the walls and into a temporary plastic electrical box that 
>> I can plug into the same outlet as the PLM.
>>
>> Dave if you submit a PR I can merge it in. There’s been a bunch of 
>> changes over the past year or so, might be good to capture a release 
>> soon. Unfortunately my git skills have atrophied so every time I 
>> think about doing this I get frustrated with some git situation and 
>> figure I’ll do it later….
>>
>>> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw...> 
>>> wrote:
>>>
>>> I'm probably running an old version of MH, so if this has been fixed 
>>> in the past 1-2 years, then please tell me to update. :)
>>>
>>> I created an integration that has MH listening to the mosquito 
>>> broker for some light commands, and for the most part, it's working. 
>>> However, it seems that random lights do not work when I send a MQTT 
>>> command to the broker. I can see the command hit the broker, but it 
>>> won't trigger an event in MH for all lights. I see no difference 
>>> between the lights that work and those that do not.
>>>
>>> Mosquito Broker:
>>> insteon/living_room_lamp on
>>> insteon/living_room_lamp/state on
>>>
>>> insteon/living_room_fan_light on
>>> caddx/motion/binary_sensor.living_motion/state on
>>> insteon/living_room_lamp off
>>> caddx/motion/binary_sensor.living_motion/state off
>>> insteon/living_room_lamp/state off
>>>
>>>
>>> MH:
>>> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
>>> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
>>> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>>>
>>> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
>>> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
>>> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
>>> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
>>> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
>>> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>>>
>>> You  can see MH is listening to the broker, sending messages 
>>> successfully, etc. The living_room_fan_light  event was not picked 
>>> up from the broker by MH. I don't see why. Here's the code snippets:
>>>
>>>
>>> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', 
>>> "", "", 120);
>>>
>>> $MQTT_insteon_living_room_fan_light_set = new 
>>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light");
>>> $MQTT_insteon_living_room_fan_light_state = new 
>>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light/state", 1, 1);
>>> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>>>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>>>     set $living_room_fan_light $state;
>>> }
>>> if($state = state_now $fl_liv_fanlight) {
>>>     $state = ON if $state == '100%';
>>>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>>>     set $MQTT_insteon_living_room_fan_light_state $state;
>>> }
>>>
>>> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon, 
>>> "insteon/living_room_lamp");
>>> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon, 
>>> "insteon/living_room_lamp/state", 1, 1);
>>> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>>>     print_log("[MQTT_RECV] living_room_lamp: $state");
>>>     set $living_room_lamp $state;
>>> }
>>> if($state = state_now $ll_liv_lamp1) {
>>>     $state = ON if $state == '100%';
>>>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>>>     set $MQTT_insteon_living_room_lamp_state $state;
>>> }
>>>
>>>
>>> Mind you, I have about 120 lights in my code, all listening to 
>>> $MQTT_insteon. Could there be a memory issue? I appreciate any input 
>>> with ideas on this.
>>>
>>> Thank you!
>>>
>>> -- 
>>> Best regards,
>>> Steve Switzer
>>>
>>> ---
>>> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!
>>> http://www.sbsROC.com  <http://www.sbsroc.com/>
>>> ________________________________________________________
>>> To unsubscribe from this list, go to: 
>>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>
>>
>>
>>
>> ________________________________________________________
>> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

I use Insteon IOlincs to sense and control my garage doors. They are also a bit unreliable, I had to disconnect one of the contacts from the opener as it was opening at night, and the sensors are missing about 1 in 10 open/close events.

I’ve run parallel wires to the magnetic open/close sensors to my weeder, and that seems to be more robust. However, it was a real challenge getting a few issues ironed out.

Looking at the code samples, it recommends initializing the weeder ports every night. This worked well for a single Serial_Item object, however when I added more, those objects were stuck at init. It seems like sending all the inits in one loop causes problems. I’ve been able to successfully reset all the ports using set_with_timer:

if ($New_Day) {
	    set_with_timer $front_doorbell_button 'init',1;
	    set_with_timer $back_doorbell_button 'init', 2;
	    set_with_timer $garage_door_S1 'init', 3;
	    set_with_timer $garage_door_S2 'init', 4; 
	    set_with_timer $garage_door_S3 'init', 5;
	    set_with_timer $garage_door_S4 'init', 6;
}

So, here are my issues. I’m hoping that someone with some weeder experience might be able to help spot something I’m doing wrong

1. I have $garage_door_S1 and $garage_door_S3 states set to open and close, however when the init happens, for whatever reason they come back as on and off. I used to have them on and off, but recently changed the code to be open and closed. I can’t see anywhere else in the code, or in Serial_Item.pm where something would be set to ON or OFF.

$garage_door_S1 = new Serial_Item( 'AEH', 'open', 'weeder' );
$garage_door_S1->add( 'AEL', 'closed',     'weeder' );
$garage_door_S1->add( 'ARE', 'read',  'weeder' );
$garage_door_S1->add( 'ASE', 'init',  'weeder' );

$garage_door_S3 = new Serial_Item( 'AGH', 'open', 'weeder' );
$garage_door_S3->add( 'AGL', 'closed',     'weeder' );
$garage_door_S3->add( 'ARG', 'read',  'weeder' );
$garage_door_S3->add( 'ASG', 'init',  'weeder' );

If I press the read button on the web interface nothing happens. However if the door opens or closes, it gets set to the proper state. I could put in a line that if the state is on then turn it to open, but that seems like a kludge and I might not have something properly configured.

2. I want to wire the contacts of my opener to the weeder so I can send it a control signal. I could do this with the IOlinc to close a contact. I _think) it would be setting the port to low for a second, but would be great to hear if someone has done this:

$garage_door_S2 = new Serial_Item( 'AIH', ‘inactive', 'weeder' );
$garage_door_S2->add( 'AIL', ‘active',     'weeder' );
$garage_door_S2->add( 'ALI1000', ’toggle',     'weeder' );
$garage_door_S2->add( 'ARI', 'read',  'weeder' );

3. I use a proxy for my W800 for wireless motion sensors. It’s been pretty good. Could having the weeder serial and insteon serial in the same instance be adding to the problems? Would another proxy instance be a better solution?

I also have a lot of MQTT devices using the native MH code with no major 
issues.
Giles

On 22/08/2023 17:50, H Plato wrote:
> On an unrelated note, is the insteon MQTT code more reliable than the 
> native MH support? Why did you switch?
>
> I don’t have 120 devices, but probably 50 or so devices and it’s 
> pretty good for reliability with the odd device exception. I have a 
> challenge with some keypadlincs getting them to sync. the MH code 
> seems to give up after a period of time, so I end up uninstalling the 
> KPLs from the walls and into a temporary plastic electrical box that I 
> can plug into the same outlet as the PLM.
>
> Dave if you submit a PR I can merge it in. There’s been a bunch of 
> changes over the past year or so, might be good to capture a release 
> soon. Unfortunately my git skills have atrophied so every time I think 
> about doing this I get frustrated with some git situation and figure 
> I’ll do it later….
>
>> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw...> wrote:
>>
>> I'm probably running an old version of MH, so if this has been fixed 
>> in the past 1-2 years, then please tell me to update. :)
>>
>> I created an integration that has MH listening to the mosquito broker 
>> for some light commands, and for the most part, it's working. 
>> However, it seems that random lights do not work when I send a MQTT 
>> command to the broker. I can see the command hit the broker, but it 
>> won't trigger an event in MH for all lights. I see no difference 
>> between the lights that work and those that do not.
>>
>> Mosquito Broker:
>> insteon/living_room_lamp on
>> insteon/living_room_lamp/state on
>>
>> insteon/living_room_fan_light on
>> caddx/motion/binary_sensor.living_motion/state on
>> insteon/living_room_lamp off
>> caddx/motion/binary_sensor.living_motion/state off
>> insteon/living_room_lamp/state off
>>
>>
>> MH:
>> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
>> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
>> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>>
>> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
>> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
>> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
>> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
>> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
>> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>>
>> You  can see MH is listening to the broker, sending messages 
>> successfully, etc. The living_room_fan_light  event was not picked up 
>> from the broker by MH. I don't see why. Here's the code snippets:
>>
>>
>> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', 
>> "", "", 120);
>>
>> $MQTT_insteon_living_room_fan_light_set = new 
>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light");
>> $MQTT_insteon_living_room_fan_light_state = new 
>> mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light/state", 1, 1);
>> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>>     set $living_room_fan_light $state;
>> }
>> if($state = state_now $fl_liv_fanlight) {
>>     $state = ON if $state == '100%';
>>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>>     set $MQTT_insteon_living_room_fan_light_state $state;
>> }
>>
>> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon, 
>> "insteon/living_room_lamp");
>> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon, 
>> "insteon/living_room_lamp/state", 1, 1);
>> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>>     print_log("[MQTT_RECV] living_room_lamp: $state");
>>     set $living_room_lamp $state;
>> }
>> if($state = state_now $ll_liv_lamp1) {
>>     $state = ON if $state == '100%';
>>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>>     set $MQTT_insteon_living_room_lamp_state $state;
>> }
>>
>>
>> Mind you, I have about 120 lights in my code, all listening to 
>> $MQTT_insteon. Could there be a memory issue? I appreciate any input 
>> with ideas on this.
>>
>> Thank you!
>>
>> -- 
>> Best regards,
>> Steve Switzer
>>
>> ---
>> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!
>> http://www.sbsROC.com  <http://www.sbsroc.com/>
>> ________________________________________________________
>> To unsubscribe from this list, go to: 
>> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>
>
>
>
> ________________________________________________________
> To unsubscribe from this list, go to:https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

On an unrelated note, is the insteon MQTT code more reliable than the native MH support? Why did you switch?

I don’t have 120 devices, but probably 50 or so devices and it’s pretty good for reliability with the odd device exception. I have a challenge with some keypadlincs getting them to sync. the MH code seems to give up after a period of time, so I end up uninstalling the KPLs from the walls and into a temporary plastic electrical box that I can plug into the same outlet as the PLM.

Dave if you submit a PR I can merge it in. There’s been a bunch of changes over the past year or so, might be good to capture a release soon. Unfortunately my git skills have atrophied so every time I think about doing this I get frustrated with some git situation and figure I’ll do it later….

> On Aug 20, 2023, at 1:32 PM, Stephen Switzer <st...@sw...> wrote:
> 
> I'm probably running an old version of MH, so if this has been fixed in the past 1-2 years, then please tell me to update. :)
> 
> I created an integration that has MH listening to the mosquito broker for some light commands, and for the most part, it's working. However, it seems that random lights do not work when I send a MQTT command to the broker. I can see the command hit the broker, but it won't trigger an event in MH for all lights. I see no difference between the lights that work and those that do not.
> 
> Mosquito Broker:
> insteon/living_room_lamp on
> insteon/living_room_lamp/state on
> 
> insteon/living_room_fan_light on
> caddx/motion/binary_sensor.living_motion/state on
> insteon/living_room_lamp off
> caddx/motion/binary_sensor.living_motion/state off
> insteon/living_room_lamp/state off
> 
> 
> MH:
> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
> 
> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
> 
> You  can see MH is listening to the broker, sending messages successfully, etc. The living_room_fan_light  event was not picked up from the broker by MH. I don't see why. Here's the code snippets:
> 
> 
> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', "", "", 120);
> 
> $MQTT_insteon_living_room_fan_light_set = new mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light");
> $MQTT_insteon_living_room_fan_light_state = new mqtt_Item($MQTT_insteon, "insteon/living_room_fan_light/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>     set $living_room_fan_light $state;
> }
> if($state = state_now $fl_liv_fanlight) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>     set $MQTT_insteon_living_room_fan_light_state $state;
> }
> 
> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon, "insteon/living_room_lamp");
> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon, "insteon/living_room_lamp/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>     print_log("[MQTT_RECV] living_room_lamp: $state");
>     set $living_room_lamp $state;
> }
> if($state = state_now $ll_liv_lamp1) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>     set $MQTT_insteon_living_room_lamp_state $state;
> }
> 
> 
> Mind you, I have about 120 lights in my code, all listening to $MQTT_insteon. Could there be a memory issue? I appreciate any input with ideas on this.
> 
> Thank you!
> 
> -- 
> Best regards,
> Steve Switzer
> 
> ---
> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!
> http://www.sbsROC.com <http://www.sbsroc.com/>________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
> 

Hi Stephen,

I have done quite a bit of work on the mqtt support. I also have some
pending changes that may help with your issues.  I will try and get that
submitted in the next couple days.

Dave

On Sun, Aug 20, 2023, 4:41 PM Stephen Switzer <st...@sw...> wrote:

> I'm probably running an old version of MH, so if this has been fixed in
> the past 1-2 years, then please tell me to update. :)
>
> I created an integration that has MH listening to the mosquito broker for
> some light commands, and for the most part, it's working. However, it seems
> that random lights do not work when I send a MQTT command to the broker. I
> can see the command hit the broker, but it won't trigger an event in MH for
> all lights. I see no difference between the lights that work and those that
> do not.
>
> Mosquito Broker:
> insteon/living_room_lamp on
> insteon/living_room_lamp/state on
>
> insteon/living_room_fan_light on
> caddx/motion/binary_sensor.living_motion/state on
> insteon/living_room_lamp off
> caddx/motion/binary_sensor.living_motion/state off
> insteon/living_room_lamp/state off
>
>
> MH:
> 08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
> 08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
> 08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on
>
> 08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
> 08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
> 08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
> 08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
> 08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
> 08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off
>
> You  can see MH is listening to the broker, sending messages successfully,
> etc. The living_room_fan_light  event was not picked up from the broker by
> MH. I don't see why. Here's the code snippets:
>
>
> $MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', "", "",
> 120);
>
> $MQTT_insteon_living_room_fan_light_set = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_fan_light");
> $MQTT_insteon_living_room_fan_light_state = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_fan_light/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
>     print_log("[MQTT_RECV] living_room_fan_light: $state");
>     set $living_room_fan_light $state;
> }
> if($state = state_now $fl_liv_fanlight) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] fl_liv_fanlight: $state");
>     set $MQTT_insteon_living_room_fan_light_state $state;
> }
>
> $MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_lamp");
> $MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon,
> "insteon/living_room_lamp/state", 1, 1);
> if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
>     print_log("[MQTT_RECV] living_room_lamp: $state");
>     set $living_room_lamp $state;
> }
> if($state = state_now $ll_liv_lamp1) {
>     $state = ON if $state == '100%';
>     print_log("[MQTT_SEND] ll_liv_lamp1: $state");
>     set $MQTT_insteon_living_room_lamp_state $state;
> }
>
>
> Mind you, I have about 120 lights in my code, all listening to
> $MQTT_insteon. Could there be a memory issue? I appreciate any input with
> ideas on this.
>
> Thank you!
>
> --
>
> Best regards,
> Steve Switzer
>
> ---
> Get world-class business I.T. services and a phone system with awesome features that won't challenge your budget!http://www.sbsROC.com
>
> ________________________________________________________
> To unsubscribe from this list, go to:
> https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>
>

I'm probably running an old version of MH, so if this has been fixed in the
past 1-2 years, then please tell me to update. :)

I created an integration that has MH listening to the mosquito broker for
some light commands, and for the most part, it's working. However, it seems
that random lights do not work when I send a MQTT command to the broker. I
can see the command hit the broker, but it won't trigger an event in MH for
all lights. I see no difference between the lights that work and those that
do not.

Mosquito Broker:
insteon/living_room_lamp on
insteon/living_room_lamp/state on

insteon/living_room_fan_light on
caddx/motion/binary_sensor.living_motion/state on
insteon/living_room_lamp off
caddx/motion/binary_sensor.living_motion/state off
insteon/living_room_lamp/state off


MH:
08/20/23 03:21:57 PM [MQTT_RECV] living_room_lamp: on
08/20/23 03:21:59 PM [LIGHTS] $ll_liv_lamp1 is 100%
08/20/23 03:21:59 PM [MQTT_SEND] ll_liv_lamp1: on

08/20/23 03:22:06 PM [MQTT] MQTT_living_motion: on
08/20/23 03:22:07 PM [MOTION] Motion sensed in Living.
08/20/23 03:22:10 PM [MQTT_RECV] living_room_lamp: off
08/20/23 03:22:12 PM [MQTT] MQTT_living_motion: off
08/20/23 03:22:12 PM [LIGHTS] $ll_liv_lamp1 is off
08/20/23 03:22:12 PM [MQTT_SEND] ll_liv_lamp1: off

You  can see MH is listening to the broker, sending messages successfully,
etc. The living_room_fan_light  event was not picked up from the broker by
MH. I don't see why. Here's the code snippets:


$MQTT_insteon = new mqtt('mqtt_1', '127.0.0.1', 1883, 'insteon/#', "", "",
120);

$MQTT_insteon_living_room_fan_light_set = new mqtt_Item($MQTT_insteon,
"insteon/living_room_fan_light");
$MQTT_insteon_living_room_fan_light_state = new mqtt_Item($MQTT_insteon,
"insteon/living_room_fan_light/state", 1, 1);
if(my $state = state_changed $MQTT_insteon_living_room_fan_light_set) {
    print_log("[MQTT_RECV] living_room_fan_light: $state");
    set $living_room_fan_light $state;
}
if($state = state_now $fl_liv_fanlight) {
    $state = ON if $state == '100%';
    print_log("[MQTT_SEND] fl_liv_fanlight: $state");
    set $MQTT_insteon_living_room_fan_light_state $state;
}

$MQTT_insteon_living_room_lamp_set = new mqtt_Item($MQTT_insteon,
"insteon/living_room_lamp");
$MQTT_insteon_living_room_lamp_state = new mqtt_Item($MQTT_insteon,
"insteon/living_room_lamp/state", 1, 1);
if(my $state = state_changed $MQTT_insteon_living_room_lamp_set) {
    print_log("[MQTT_RECV] living_room_lamp: $state");
    set $living_room_lamp $state;
}
if($state = state_now $ll_liv_lamp1) {
    $state = ON if $state == '100%';
    print_log("[MQTT_SEND] ll_liv_lamp1: $state");
    set $MQTT_insteon_living_room_lamp_state $state;
}


Mind you, I have about 120 lights in my code, all listening to
$MQTT_insteon. Could there be a memory issue? I appreciate any input with
ideas on this.

Thank you!

-- 

Best regards,
Steve Switzer

---
Get world-class business I.T. services and a phone system with awesome
features that won't challenge your budget!http://www.sbsROC.com

Hello,

  I have a weeder WTDIO-M which does a pretty good job of notifying me when a switch closes. I’d also like to use it to trigger a NO switch. Looking at the document, I _think_ I can do this by setting it to a high state:

HIGH, H chn time, Make channel chn an output and set high for time x10 microseconds. chn = A-N, time = 1 to 65535. If time omitted, chn remains high.(Note 3)

However looking at the MH code, I’m not sure the serial configuration. This is my button:

$button = new Serial_Item( 'AAH', OFF, 'weeder' );
$button->add( 'AAL', ON,     'weeder' );
$button->add( 'A!',  'reset', 'weeder' );
$button->add( 'ASA', 'init',  'weeder' );

So close a contact I need to send an H and microseconds, 

$contact = new Serial_Item( 'ABH50000', ON, 'weeder' );

So set $contact ON should send a high level with a half second duration. I think this will close the contact, however that will leave the $contact in an ON state, is this correct?

Anyone use a weeder board to close contacts?