search

OpenZWave / open-zwave

a C++ library to control Z-Wave Networks via a USB Z-Wave Controller.
http://www.openzwave.net/
GNU Lesser General Public License v3.0
1.05k stars 912 forks source link

**TODO: handle request for 0xa8** Please report this message. #739

Closed slawekgh closed 8 years ago

slawekgh commented 8 years ago

White USB Sigma for EU The same message for Danfoss Z and Fibaro Wall Plug

Effect is a) there is no Power and Energy for FWP and b) there is no heating for danfoss

I can check also for termometers, motion detectors etc but imho doesnt make any sense - smth wrong with white USB ?

the same devices (danfoss+fibaro_wall_plug) with black AEON USB Stick - everything works fine

slawekgh commented 8 years ago

I made additional tests (to simplify I just run MinOZW only, nothing more):

For openzwave-1.0.791 and white Sigma USB Dongle: a) without any devices (only one001) - OK, no MinOZW bad messages
b) with Danfoss - MinOZW message: "Info, TODO: handle request for 0xa8 Please report this message." c) with Fibaro Wall Plug - "Info, _TODO: handle..." d) with Everspring Thermometer - "Info, _TODO: handle..." e) with all of them - "Info, **TODO: handle..."

Exactly the same situation for: openzwave-1.2.919 openzwave-1.4.0 openzwave-1.4.1

My system is Ubuntu 12.0 , I can also made some test on RaspberryPi with Raspbian

sl

slawekgh commented 8 years ago

Any ideas?

Fishwaldo commented 8 years ago

No Idea. I don't know what message 0xa8 is at all. Could you send a complete log file to the mailing list?

I have a Sigma UZB stick (Gen 5) and it works fine.

slawekgh commented 8 years ago

I ordered new USB Sigma stick , it is on the way , so please dont close this ticket, i will repeat tests asap and provide additional details , i think my USB stick could be damaged etc

Fishwaldo commented 8 years ago

any update?

slawekgh commented 8 years ago

I have just received new (2nd one) white USB from sigma, I start to make tests...

slawekgh commented 8 years ago

the same: "2016-02-16 21:55:56.144 Info, TODO: handle request for 0xa8 Please report this message." . tested on openzwave-1.2.919 , I can also make tests for openzwave-1.4.0, openzwave-1.4.1 and ozw-1.0.791 but I think it doesnt make any sense, result will be for 100% the same

Fishwaldo commented 8 years ago

Could you provide a full log please?

I have updated UZB sticks and I don't see that message (ever!)

slawekgh commented 8 years ago

MINOZW.txt

slawekgh commented 8 years ago

previous log file was for OZW 1.0.791 , now I send for OZW=1.4.1 MINOZW_1.4.1.txt

openzwave-dev-watcher commented 8 years ago

El jueves, 18 de febrero de 2016, 9:03:27 (UTC+1), Justin Hammond escribió:

Could you provide a full log please?

I have updated UZB sticks and I don't see that message (ever!)

— Reply to this email directly or view it on GitHub https://github.com/OpenZWave/open-zwave/issues/739#issuecomment-185588076 .

How did you update your UZB?

Which tool do you use?

sennet-software commented 8 years ago

I have the same problem like you, could you tell me if you have find the solution to work with lastest UZB?

Thanks.

slawekgh commented 8 years ago

No, I didnt find solution, now I'm waiting for 5 new usb sticks and I plan to check it again on new sticks

IOOOTAlan commented 8 years ago

I also have the same problem here with a SD5303 SoC and openzwave 1.4.78. I reported the issue also on the OpenZWave Google Group. Guess this 0xA8 is a new kind of class in recent zwave controllers?

Fishwaldo commented 8 years ago

Hi, This is a message from the SerialAPI portion of the protocol, which is lower than the CC. Unfortunately we don't know what it means yet.

I'm thinking it's either related to two things: initialization sequence isn't working for these newer chips, or maybe related to the new S2 Security support. I hope to investigate this further soon.

IOOOTAlan commented 8 years ago

@Fishwaldo thanks for the info!

Fishwaldo commented 8 years ago

Any way any of you can check what Firmware is loaded on the Z-Wave Chip?

Fishwaldo commented 8 years ago

Hi, This message is from Bridge Firmware loaded on your Chip/Controller. Currently OZW doesn't support Bridge Firmware.

We only work with Static Controller Firmware. I'll see about adding a check in OZW to bail out if its not a Static Controller.

IOOOTAlan commented 8 years ago

Good to know, thanks for the analysis!

jeffsf commented 7 years ago

Unfortunate that this has been closed as it is still a problem with a just-received UZB3-U-BRG from Sigma Design's authorized eval-kit distributor.

Logs available, if needed.

Posts strongly that the BRG is a superset of the STA

From http://forum.z-wavepublic.com/t/uzb-static-versus-bridge/1041

Hi, can someone explain the difference between ACC-UZB3--STA and ACC-UZB3--BRG. From the description, I see that the difference is static and bridge. Does that mean that bridge model will act as a repeater for all traffic and the static model will not? Thanks. Answered with:

The bridge controller allows the creation of virtual nodes. It is identical with the static controller in any other aspect.

Confirmed in http://forum.z-wavepublic.com/t/bridge-controller-uzb/22/2

Regarding your questions: 1) Both are supported and have the same performance, while there is a slight difference in components. 2) While it is technically possible to update the static controller UZBs, however the firmware images and tools are not publicly available. 3) Z/IP Gateway, the core software component relies on the bridge functionality for session handling and IP associations.

The onboard SAW filter has been replaced to match our latest recommendation for hardware designers.The Z-wave SoC is unchanged; the SD3503.

Fishwaldo commented 7 years ago

We don't support Bridge Firmware. As the SerialAPI is not released by Sigma, not much we can do there unless someone wants to reverse engineer it.