The segment below shows Topic homeseer/house/security_system with payload of 100 received. It was associated with Device 20. CAPI control was performed and HS updated status for Device 20 and mcsMQTT published this topic with payload 100. For this sequence the publish and subscribe topics must have been different for HS device 20. Looking at the database posted yesterday I confirmed that there was no subscribe topic for this device in the database for one of the three instances of device 20. There should have been only one instance.
In another area I see several expired web pages. This may help explain why things do not appear to stick. mcsMQTT maintains individual user sessions for browser pages. A two-second heartbeat is setup with the browser and this tell mcsMQTT that the user still has the page open. If this heartbeat stops then mcsMQTT assumes the session has been ended by the user and any subsequent action on that session is ignored. A 5 minute timeout is used. This was done to protect from multiple open windows stomping on each other when filters may be different on each.
What I think I will do is provide feedback with a clock/counter/blink or something to let the user know the session is still active. To minimize issues in this area keep only one browser window in use.
The debug did not contain anything about why multiple copies of topics are being recorded. I will now try to replicate to understand. Most of my use is with subscribed topics and have no instances in use of using existing HS devices so have only looked at it when I was doing testing in the past.
Code:
6/19/2018 9:28:11 AM 138594986 | Update Accepted 20 to 100 StatusType=0 6/19/2018 9:28:11 AM 138594991 | Command nonPlugin Device 20 to 100 6/19/2018 9:28:11 AM 138594991 | Command 20 to 100 ControlValue=0, Range=Nothing, ControlType=Button, ControlString=, Label=Off, ControlUse=Not_Specified 6/19/2018 9:28:11 AM 138594992 | Command numeric, but no CAPI matches value or range 6/19/2018 9:28:11 AM 138594992 | Command 20 to 100 ControlValue=100, Range=Nothing, ControlType=Button, ControlString=, Label=On, ControlUse=Not_Specified 6/19/2018 9:28:11 AM 138594994 | HSEvent Do= True VALUE_CHANGE for Device 20 6/19/2018 9:28:11 AM 138595046 | HSEvent Add VALUE_CHANGE | 20 6/19/2018 9:28:11 AM 138595046 | DoHsEvent Topic=homeseer/house/security_system, Payload=100, Template=
What I think I will do is provide feedback with a clock/counter/blink or something to let the user know the session is still active. To minimize issues in this area keep only one browser window in use.
Code:
6/19/2018 9:34:37 AM 138981145 | Removed expired web page 6/19/2018 9:38:38 AM 139221510 | Removed expired web page 6/19/2018 9:45:51 AM 139654616 | Command nonPlugin Device 87 to 0 6/19/2018 9:46:01 AM 139664540 | Sort > 0 6/19/2018 9:47:56 AM 139779596 | Command nonPlugin Device 20 to 100 6/19/2018 9:48:03 AM 139786535 | Sort > 0 6/19/2018 9:49:57 AM 139900459 | Command nonPlugin Device 20 to 0 6/19/2018 9:51:49 AM 140012687 | Removed expired web page 6/19/2018 9:53:59 AM 140142885 | Removed expired web page 6/19/2018 9:55:49 AM 140253052 | Removed expired web page 6/19/2018 9:59:58 AM 140501294 | Sort > 0 6/19/2018 10:25:22 AM 142025752 | Removed expired web page
Comment