Homeseer/Hubitat sending commands duplicated times

[mik3]

So this happen. I'm not sure if it's even related to Homeseer or the plugin.

The event action will be sent multiple times.

If I inititate an ON or and OFF from the Device Management page, it does the same thing.


Homeseer Log

Nov-03 8:04:27 AM

Event

Event Trigger "Bathroom Upstairs Bathroom Motion ON"

Hubitat Log

dev:4822019-11-03 08:04:29.211 am infoBathroom Upstairs Light was turned on
dev:12019-11-03 08:04:29.094 am inforcvd: OUTPUT,23,1,100.00
dev:4822019-11-03 08:04:29.056 am infoBathroom Upstairs Light was turned on
dev:12602019-11-03 08:04:29.028 am infoUpstairs Hallway MS is active
dev:4822019-11-03 08:04:28.984 am infoBathroom Upstairs Light was turned on
dev:12019-11-03 08:04:28.876 am inforcvd: OUTPUT,23,1,100.00
dev:4822019-11-03 08:04:28.836 am infoBathroom Upstairs Light was turned on

[Michael McSharry]

The debug log in /Dsta/habitat will show how many times a command is sent to hubitat.

[mik3]

The debug log in /Dsta/habitat will show how many times a command is sent to hubitat.

Here you go.

Hubitat Plugin Log:

11/3/2019 10:25:47 AM 49770 | Message received: {"source":"DEVICE","name":"motion","displayName":"Upstair s Hallway MS","value":"active","unit":null,"deviceId":1260,"hubId":nul l,"locationId":null,"installedAppId":null,"descriptionText": "Upstairs Hallway MS is active"}
11/3/2019 10:25:48 AM 50950 | Message received: {"source":"DEVICE","name":"motion","displayName":"Bathroo m Upstairs MS","value":"active","unit":null,"deviceId":995,"hubId":null ,"locationId":null,"installedAppId":null,"descriptionText":" Bathroom Upstairs MS is active"}
11/3/2019 10:25:48 AM 50968 | SetIOMulti triggered, checking CAPI 'On' on device 898 controlValue 255
11/3/2019 10:25:48 AM 50977 | http://###IP###/apps/api/675/devices/482/on?###Token###
11/3/2019 10:25:48 AM 50978 | SetIoMulti Failure response when setting 898
11/3/2019 10:25:48 AM 51191 | Message received: {"source":"DEVICE","name":"switch","displayName":"Bathroo m Upstairs Light","value":"on","unit":null,"deviceId":482,"hubId":null, "locationId":null,"installedAppId":null,"descriptionText":"B athroom Upstairs Light was turned on"}
11/3/2019 10:25:48 AM 51209 | HubitatDevice:{"id":"482","name":"Bathroom Upstairs Light","label":"Bathroom Upstairs Light","attributes":[{"name":"switch","currentValue":"off","dataType":"ENUM","val ues":["on","off"]}],"capabilities":["Switch",{"attributes":[{"name":"switch","dataType":null}]},"Refresh","Actuator"],"commands":["flash","off","on","refresh"]}
11/3/2019 10:25:48 AM 51380 | Message received: {"source":"DEVICE","name":"switch","displayName":"Bathroo m Upstairs Light","value":"on","unit":null,"deviceId":482,"hubId":null, "locationId":null,"installedAppId":null,"descriptionText":"B athroom Upstairs Light was turned on"}
11/3/2019 10:25:49 AM 51446 | Message received: {"source":"DEVICE","name":"switch","displayName":"Bathroo m Upstairs Light","value":"on","unit":null,"deviceId":482,"hubId":null, "locationId":null,"installedAppId":null,"descriptionText":"B athroom Upstairs Light was turned on"}
11/3/2019 10:25:49 AM 51556 | Message received: {"source":"DEVICE","name":"switch","displayName":"Bathroo m Upstairs Light","value":"on","unit":null,"deviceId":482,"hubId":null, "locationId":null,"installedAppId":null,"descriptionText":"B athroom Upstairs Light was turned on"}
11/3/2019 10:25:50 AM 52788 | Message received: {"source":"DEVICE","name":"motion","displayName":"Basemen t MS","value":"inactive","unit":null,"deviceId":1000,"hubId":n ull,"locationId":null,"installedAppId":null,"descriptionText ":"Basement MS is inactive"}
11/3/2019 10:25:56 AM 59052 | Message received: {"source":"DEVICE","name":"schedule","displayName":"Orbit Garden","value":"on","unit":null,"deviceId":993,"hubId":null ,"locationId":null,"installedAppId":null,"descriptionText":n ull}
11/3/2019 10:25:56 AM 59053 | Hubitat Device not in Device Map: schedule
^C

Hubitat Log:

dev:12602019-11-03 10:26:23.498 am infoUpstairs Hallway MS is inactive
dev:9952019-11-03 10:26:23.169 am infoBathroom Upstairs MS is inactive
dev:10002019-11-03 10:26:11.450 am infoBasement MS is active
dev:10002019-11-03 10:25:51.334 am infoBasement MS is inactive
dev:4822019-11-03 10:25:50.111 am infoBathroom Upstairs Light was turned on
dev:12019-11-03 10:25:50.034 am inforcvd: OUTPUT,23,1,100.00
dev:4822019-11-03 10:25:50.000 am infoBathroom Upstairs Light was turned on
dev:4822019-11-03 10:25:49.925 am infoBathroom Upstairs Light was turned on
dev:12019-11-03 10:25:49.800 am inforcvd: OUTPUT,23,1,100.00
dev:4822019-11-03 10:25:49.735 am infoBathroom Upstairs Light was turned on
dev:9952019-11-03 10:25:49.495 am infoBathroom Upstairs MS is active


Homeseer Log:

Nov-03 10:25:48 AM

Event

Event Trigger "Bathroom Upstairs Bathroom Motion ON"

[Michael McSharry]

I am interested in the log created by plugin at /Data/hubitat. Debug checkbox on plugin config page needs to be checked. Better to post the file or email the file as attachment

[mik3]

I am interested in the log created by plugin at /Data/hubitat. Debug checkbox on plugin config page needs to be checked. Better to post the file or email the file as attachment

I posted it above .... debug is turned on

[Michael McSharry]

Sorry I missed it on first glance. The log does confirm that only one command was sent to Hubitat so duplicate entries in the hubitat log are due to something inside of hubitat.

[mik3]

Sorry I missed it on first glance. The log does confirm that only one command was sent to Hubitat so duplicate entries in the hubitat log are due to something inside of hubitat.

The hubitat data log shows 4 light on executions, which then reflects under the Hubitat log.

[Michael McSharry]

I do not believe there is anything I can do about what happens inside Hubitat. The single command that was sent was as shown below with the personal data redacted.

http://###IP###/apps/api/675/devices/482/on?###Token###

If it is a problem then the Hubitat Community forums is the place to pursue.

[mik3]

I do not believe there is anything I can do about what happens inside Hubitat. The single command that was sent was as shown below with the personal data redacted.

http://###IP###/apps/api/675/devices/482/on?###Token###

If it is a problem then the Hubitat Community forums is the place to pursue.

Weird, I wonder if it's just my Homeseer install to be honest.

I may do a reinstall..

Nobody else has reported this, correct?

[Michael McSharry]

From the HS side there would be no reason to suspect anything since the repeated status updates do not change the HS device status so it could be happening with others but just never investigated. I do not think there is any value in doing any reinstall on the HS side. HS sends one command as it should and it services each status update from Hubitat as it should.

[dbmet]

Only time I have gotten duplicate entries its been a Hubitat thing and that was before I even added this plugin in HomeSeer.

[mik3]

Only time I have gotten duplicate entries its been a Hubitat thing and that was before I even added this plugin in HomeSeer.

I have all sorts of weird behaviour.

i have a feeling it’s do to Linux.

[dbmet]

I'm running HomeSeer on Ubuntu 18.04 here.

I think you also had weird slow lighting problems too if I remember right from the Forums...

I have all sorts of weird behaviour.

i have a feeling it’s do to Linux.