Hi all,
this is my test report for using MQTT with HomeGenie.
Setup:
Win7 pro box running in vmware workstation upgraded with latest HG r447 (394 didn't have MQTT)
Don't forget to backup, the windows installer forces you to uninstall and everything gets lost unless
you have a backup.
Enabled MQTT and forgot to recompile.
Did some other stuff and noticed the webbrowser indicated a restart of HG once in a minute or so.
After recompiling MQTT HG was stable.
When both boxes were configured and some restarts/recompiles/etc. of HG were done (don't remember the
exact order) events arrived and the module was added.
RPi B+ box with downloaded HG image revision 431, I modified all raspberry-sharp IO binaries
Tried to disable all modules that could cause events.
Disabled interconnections, enabled MQTT and yes you really need to recompile before it connects.
Enabled the FakeTemperatureSensorCluster with only one sensor sending one event per second.
CPU utilization was about 5% peeks to 30% (I need a graphical tool)
End Setup
So I started testing...
I throwed away every html/threadpoollimit/overfloodprotection thing I could think of...
In other words:
Closed all browsers and deleted all widgets, checked if the interconnection were still disabled.
Disabled all polling sensors except for one sensor generating an event every second.
Booted RPi and Win7 box to get a clean start.
Facts:
RPi is logging every event, tail of the homegenie.log is attached as RPiboxHomeGenieLog.txt
Win7 misses events in the homegenie.log, attached as Win7boxHomeGenieLog.txt
That's the end of test day 1
When I came home next day and started testing, the http server on the RPi was down.
(SSH)Putty was working and top didn't show mono anymore, obviously HG had died.
Copied(WinSCP) the tail of the homegenie.log into RPiHttpServerDown.txt which is attached.
This was the first time in weeks HG died on RPi, normally it's rocksolid.
Rebooted the RPi and everything was fine again.
So, what am I going to do now?
Find out what's causing the nasty mqtt exception in de logs.
Install the mqtt client app to see if the events are arriving at the mqtt broker.
Let win7 box send events to see if there's anything different.
Debug code in win7 box if it has the same problem
Update boxes to last revision.
Don't know what and in what order I should test, still a newbie.
Any pointers are welcome.
Think curiosity wins and mqtt client app gets installed first, results will be posted.
Best regards,
Wibo.