Version 3.4.x.x

[Pete]

Opened garage door...and leaving it open for a bit...

Console shows:

12:26:00 MQT: /GarageDoor1/Door1 = CLOSED
12:26:00 MQT: /GarageDoor1/Door1 = INDETERMINATE
12:26:11 MQT: /GarageDoor1/Door1 = OPEN
12:28:12 MQT: /GarageDoor1/STATE = {"Time":"2018-08-18T12:28:12", "
12:28:12 MQT: /GarageDoor1/Door1 = OPEN

Looking at associations and do not see the MQT change.

Shouldn't this show OPEN ?

[Michael McSharry]

There are two messages. One the JSON STATE. The other is the DOOR. The DOOR message will track door position and the STATE is periodic. I associate only the DOOR message to HS device.

[Michael McSharry]

Another thought is LWT for the door sonoff. Has the unit been visible to broker this entire period?

[Pete]

Yes only associating the door message and not the state message. IE:



Has the unit been visible to broker this entire period?

Yes see the temperature updates all of the time. (Sub: /GarageDoor1/SENSOR:TempUnit) and API state is constantly updating.

The RPi2 broker is on 24/7 and I never touch it.

I have second identically configured SonOff in the house (door #2) not connected to anything except temperature sensor and left GPIO wires such that I can test the open and close stuff. For testing just looking at the console and it show open and closed and intermediate and see the same relating to the associations.

Looking at SonOff MQTT configuration again:

client = GarageDoor1
topic=GarageDoor1
fulltopic=/%topic%/

Watching statistics not seeing it change the way I used to.

I cannot edit out the below so will do screen pics.

Disabled and re-enabled plugin. These numbers are not climbing like they used to.
The lightning sensor keeps updating but only occassionally see the SonOff temperature sensor...very rarely though...

[Pete]

Disabled the lightning sensor broadcast and changed the times for the combo temperature / humidity sensors from every 10 seconds to every 10 minutes.

Here have two Node Red RPi devices doing OWFS Mosquitto messages. One is in the attic with multiple combo sensors and the HB lightning counter. Second one is in the basement just doing a bunch of combo sensors.

Now watching the stats do occassionally see the sonoff garage door 1 and 2 device.

Last Received Topic Accepted /GarageDoor2/SENSOR
Last Received Payload Accepted {"Time":"2018-08-18T14:18:41", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18B20", "Address":"280D7E5B04000049", "Temperature":72.5}}, "TempUnit":"F"}
Last Received Timestamp 2018-08-18 14:19:04

Disabling both Node Red / OWFS RPi's for testing purposes.

[Pete]

OK now have two Node Red OWFS RPis disabled and Sonoff #2 disabled.

See only Sonoff #1 broadcasts in stats.

Last Published Topic ICS-HS3Pro/mcsMQTT/LWT
Last Published Payload Online
Last Received Topic /GarageDoor1/SENSOR
Last Received Payload {"Time":"2018-08-18T15:13:14", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18B20", "Address":"282F515C04000080", "Temperature":94.0}}, "TempUnit":"F"}
Last Received Topic Accepted /GarageDoor1/SENSOR
Last Received Payload Accepted {"Time":"2018-08-18T15:13:14", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18B20", "Address":"282F515C04000080", "Temperature":94.0}}, "TempUnit":"F"}
Last Received Timestamp 2018-08-18 15:13:14

Opening Garage Door 3 feet to watch the stats. Working now.

Last Published and Received

Last Published Topic ICS-HS3Pro/mcsMQTT/LWT
Last Published Payload Online
Last Received Topic /GarageDoor1/Door1
Last Received Payload INDETERMINATE
Last Received Topic Accepted /GarageDoor1/Door1
Last Received Payload Accepted INDETERMINATE
Last Received Timestamp 2018-08-18 15:24:11

See variable as DOOR1

INDETERMINATE Door1 Today 3:29:03 PM

See mosquitto on console:

15:24:12 MQT: /GarageDoor1/Door1 = INDETERMINATE

Closed door:

See Association just fine:

Sub: /GarageDoor1/Door1 CLOSED 2018-08-18 15:32:29

and HS variable fine:

Enabling Sonoff #2. Powering it on.

Last Published Topic ICS-HS3Pro/mcsMQTT/LWT
Last Published Payload Online
Last Received Topic /GarageDoor2/SENSOR
Last Received Payload {"Time":"2018-08-18T15:47:26", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18B20", "Address":"280D7E5B04000049", "Temperature":69.1}}, "TempUnit":"F"}
Last Received Topic Accepted /GarageDoor2/SENSOR
Last Received Payload Accepte {"Time":"2018-08-18T15:47:26", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18B20", "Address":"280D7E5B04000049", "Temperature":69.1}}, "TempUnit":"F"}
Last Received Timestamp 2018-08-18 15:47:25

Opened Garage door

Last Published Topic ICS-HS3Pro/mcsMQTT/LWT
Last Published Payload Online
Last Received Topic /GarageDoor1/Door1
Last Received Payload OPEN
Last Received Topic Accepted /GarageDoor1/Door1
Last Received Payload Accepted OPEN
Last Received Timestamp 2018-08-18 15:53:45

Console shows:
15:53:46 MQT: /GarageDoor1/Door1 = OPEN

HS3 Variable shows:

OPEN Door1 Today 3:53:45 PM

Wondering if the two NodeRed OWFS broadcasts are too chatty kathy?

It seems to me that the NodeRed OWFS stuff is preventing the plugin from seeing the SonOffs?

[Michael McSharry]

I don't know the relationship of your nodes, but when broker sends messages to mcsMQTT they are queued and worked off FIFO. Your statistics posted show a small max queue depth so not an overload situation. If it was overloaded then you would see delay, but not dropped messages.

My point about LWT is not that sonoff does not connect to broker, but that it may be disconnecting and reconnecting and for a period when disconnected it would not be able to have door event traffic. I just click the LWT message payload to see if all ways online or if there are periods when offline. It shows graphically very easily.

[Pete]

Thank you Michael.

Yes will check on the LWT message payload. Association shows it off line.

Been using BLLan doing pings and it hasn't shown the Sonoff's going off line.


Accepted the GarageDoor/LWT device today.

Last Published and Received

Last Published Topic ICS-HS3Pro/mcsMQTT/LWT
Last Published Payload Online
Last Received Topic GarageDoor1/LWT
Last Received Payload Offline
Last Received Topic Accepted GarageDoor1/LWT
Last Received Payload Accepted Offline
Last Received Timestamp 2018-08-19 18:19:13

Redid the garage door open HS3 garage door open event yesterday.

It triggers the open door tts whether partially open or totally open. Tested it to work fine and fast this afternoon.

I have not yet enabled the two Node Red / OWFS RPi's.

When I went to the SonOff device web page this morning it took some 3 tries to see the web page and console.


For the new Sonoff SV board testing with current release of Sonoff Tasmota firmware. IE: Sonoff-Tasmota 6.1.1 by Theo Arends

I have left it enabled since yesterday. I was able to get to the web interface quick this morning. The web interface is very 'snappy'.

The two LED lamps go on and off with the push button of the relay. The WLAN indicator LED doesn't show the blinking any more.

This happened with the update of firmware using Tamota firmware (mcsTasmota and Tasmota). Doesn't really matter anyhow as the device will be in a metal box anyhow.

[Pete]

Event here is still not triggering. Have I configured something wrong?

I have deleted and re-entered event a few times now.

I saw the garage door open in the console this morning for a bit and did not see any logs of my HS3 trigger and event.

[petez69]

Pete, when you say in the console, that tasmota or HS console ? If you saw it in Tasmota I would suggest to roll back to 5.12. As mentioned I had super weirdness with 6.1.1 on 5 basic units

Pete

[Michael McSharry]

When I look at my HS Event setup the Device in the event is from pulldown that has both location and name. Yours appears to have only name. "Changes and becomes" in your post is "Open" while my option if "OPEN" in the pulldown. The mcsMQTT form shows the payload to be OPEN/CLOSED/INDETERMINATE. The event evaluation by HS is likely case-sensitive.

[Pete]

Thank you Pete and Michael.

when you say in the console, that tasmota or HS console

It is the webgui mcsTasmota console that I see the messages.

The current version that I am using is working with garage door sensors, button and 1-wire temperature sensor.

Can you please post the version of firmware you are using?


The mcsMQTT form shows the payload to be OPEN/CLOSED/INDETERMINATE. The event evaluation by HS is likely case-sensitive.

The drop down for the trigger only shows Open, Closed and Indeterminate rather than OPEN, CLOSED and INTERMINATE.

IE:

Reference ID 2303
Status 0 = OFF
Value 0 = "Closed"
String CLOSED



I see what I did. I edited the values in the properties to Open and Closed versus using OPEN and CLOSED.

[Pete]

Still not working....MCSTasmota console is showing:

06:22:22 MQT: /GarageDoor1/Door1 = CLOSED
06:22:23 MQT: /GarageDoor1/Door1 = INDETERMINATE
06:22:34 MQT: /GarageDoor1/Door1 = OPEN
06:23:00 MQT: /GarageDoor1/Door1 = INDETERMINATE
06:23:11 MQT: /GarageDoor1/Door1 = CLOSED
06:23:11 MQT: /GarageDoor1/Door1 = INDETERMINATE
06:23:11 MQT: /GarageDoor1/Door1 = CLOSED
06:23:18 MQT: /GarageDoor1/STATE = {"Time":"2018-08-22T06:23:18",....
06:23:18 MQT: /GarageDoor1/Door1 = CLOSED
06:23:18 MQT: /GarageDoor1/SENSOR = {"Time":"2018-08-22T06:23:18", "....
06:28:18 MQT: /GarageDoor1/STATE = {"Time":"2018-08-22T06:28:18", ....
06:28:18 MQT: /GarageDoor1/Door1 = CLOSED

Nothing in the logs that the trigger / event occurred.

The payload is changing accordingly.



The trigger / event stuff is now configured with all caps and still doesn't trigger.



Will change it to a value of one for open to see what happens.



Never see the VSP value change of the device...IE: 0, 1, 2 .



Changed the trigger / event to using the MQTT topic-payload. I did not see this in the drop down until I changed the above HS Device MISC Properties to SHOW_VALUES and STATUS_ONLY.



OK so now the event triggers but the variable status graphic does not change - well cuz the number value doesn't change

[Pete]

PM status

Created some new events using MQTT messages recieved for Open, Intermediate and Closed and graphics for open, closed and partially open.

Works great now.

Dunno why I did not see the numeric values not change earlier today.

And why I couldn't get status of OPEN, INDETERMINATE and CLOSED working using a trigger based on status.

IE: the status changed but the event wouldn't trigger based on the changed status.

Following events are working now and status values are changing with the graphics.

MQTT Topic "/GarageDoor1/Door1" received with Payload "OPEN" status value=1 graphic garage open
MQTT Topic "/GarageDoor1/Door1" received with Payload "INDETERMINATE" value=2 graphic partially open
MQTT Topic "/GarageDoor1/Door1" received with Payload "CLOSED" value=0 and graphic garage closed

[Michael McSharry]

Select the type to be Button or List rather than text. Text maps into DeviceString. Button or List map into DeviceValue. HS Triggers are based upon DeviceValue.