-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Hey Alladdin,
thanks at first for your great work here!
As far as I know @codmpm / Patrik already contacted you about the issue regarding messages not coming through in the latest Loxone beta.
I think I already found the issue:
The Loxone MS is throwing a HTTP 500 on jdev/sps/ios/// since the first beta.
I already contacted Loxone about this, but did not get any response yet.
I did a little workaround for now, by just switching to /io/ commands for now within
node-lox-ws-api/lib/Auth/Hash.js
Line 18 in 0d9721b
| var prefix = 'jdev/sps/ios/'+this._hmac_hash+'/'; |
- var prefix = 'jdev/sps/ios/'+this._hmac_hash+'/';+ var prefix = 'jdev/sps/io/;
After this is works like a charm again for now.
One thing got my attention when reading the Loxone docs about it. In the "Hashing" section of https://www.loxone.com/dede/wp-content/uploads/sites/2/2016/08/loxone-communicating-with-the-miniserver.pdf they write "encode the hash back to hex".
As far as I could see the /authenticate/ still works fine without encoding it back. So I assume it's just a working issue in the docs. I also just tried to hex-encode it back within the command, with no luck.
So I strongly assume it's just a bug and they need to fix it.
Kind regards
Björn