Issue with 253, not sure.
11 November, 2010 - 09:41
Hi Guys,
As you know I do most of my controlling HAH through my Joggler and xapflash.
Now upto 253 I pretty much had a basic config working no problem, controlling devices and picking up info.
After upgrading I had to obviously change all the uids in xapflash to point to the new xap devices.
Now the buttons don't work or rather they do work but when I press a button on I get an immediate off to match it.
If it's on and I press it I get an off and an immediate on so effectively the buttong doesn't work.
Any ideas? Should I re-learn the rf devices perhaps?
Cheers
Gary
11 November, 2010 - 14:54
#2
More debug
Gary can you provide some debug information about what is happening? Some xap packet traces maybe running the programs that are causing you issues with -d and supply those debug logs. As Im not on the beta program I can't test this behavior your seeing. So I need to rely on others to pin point the issues.
Brett
11 November, 2010 - 19:42
#4
Its a matter of the broadcast
I got the xAPFlash app from Kevin, installed it on my joggler and traced the issue.
The xFX viewer and the HAH both broadcast on the LAN subnet broadcast, for me this is 192.168.1.255
The xFx Viewer will also honour packets sent to 255.255.255.255.
The iServer broadcasts on 255.255.255.255.
The HAH will only honour packets sent on its subnet broadcast, for me 192.168.1.255.
Therefore the HAH cannot see the iServer packets.
The iServer should be using the LAN's broadcast. This is a bug with iServer. I could work around it by making the xap-hub honour its broadcast but I don't feel this is the right way to do the thing. Talks with Kevin H in progress.
Brett
12 November, 2010 - 03:12
#6
iServer fix posted
I have posted iServer beta 12 that reduces iServer xAP broadcasts to a single subnet so this is fixed on both sides :-) Available from here.
http://www.ukusa.demon.co.uk/iServerF_b12.exe
We have some people using iServer in a corporate role (not with xAP Flash but for it's xAP internet routing capacity) and I suspect they might have several subnets or use a class B subnet. Not sure if the xAP messages naturally traverse internal routers when using a 255.255.255.255 broadcast address but reducing the broadcast to x.x.x.255 may impact them. Eventually I'll make this configurable via the iServer settings file.
K
PS 24 hour turnaround on bug fixes from two developers , two different products, two different continents .. both unpaid - "We can'na go any faster Jim.."
Hi Gary,
I'm not sure why you are seeing this change of behaviour. When I use the HAH UI to control the RF switches, I get consistent and reliable operation. Have you tried this?
Also, perhaps use xap-snoop or xFx Viewer and see what messages are being generated by which endpoints.
I don't think that re-learning the RF devices would make any difference. The code in the AVR micro that pumps out the RF signal hasn't changed in 253.
On the xapFlash front, both Brett and I have Jogglers ... but aren't on the xapFlash beta programme. Once xapFlash Beta5 is publically released, we should be able to better shape the HAH roadmap to do good things with the Joggler. We do keep in touch with Kevin (who has a HAH).
Cheers,
Derek