Closed GoogleCodeExporter closed 9 years ago
This issue was closed by revision r981.
Original comment by uAle...@gmail.com
on 11 Jan 2015 at 8:41
Hello
I want to send next pull request but i have info: Your client has issued a
malformed or illegal request. That’s all we know.
I dont know what is a problem. Please help me.
Original comment by Piotr.Ku...@gmail.com
on 11 Jan 2015 at 8:52
I don't understand the message/error? The svn checkout and updates works are
working fine here, I normally use:
svn checkout http://open-zwave.googlecode.com/svn/trunk/ open-zwave-read-only
Original comment by uAle...@gmail.com
on 11 Jan 2015 at 9:02
But i send pull request by web by edit file...
Original comment by Piotr.Ku...@gmail.com
on 11 Jan 2015 at 9:03
Ok i try again and now send new Issue 433
Original comment by Piotr.Ku...@gmail.com
on 11 Jan 2015 at 9:05
Ok, you can't submit a patch via this website i think ... Best is to open a new
"issue".
BTW: can you also attach here your FGRGBWM441 manual? I couldn't fix the added
parameter on the Fibaro site?
Original comment by uAle...@gmail.com
on 11 Jan 2015 at 9:11
Ok but it is only in Polish language.
Original comment by Piotr.Ku...@gmail.com
on 11 Jan 2015 at 9:13
Attachments:
This changes was implement to Domoticz but i still not show parameter 62 on
config Fibaro device ... WHy?
Original comment by Piotr.Ku...@gmail.com
on 18 Jan 2015 at 3:06
If you remove the zwcfg*xml and let it rediscover the device it should show up,
IF you or Domoticz applied the latest open-zwave revision. If this isn't the
case, please contact the Domoticz team.
Original comment by uAle...@gmail.com
on 18 Jan 2015 at 3:17
You think about zwcfg.xsd ? Not zwcfg.XML. ..
Original comment by Piotr.Ku...@gmail.com
on 18 Jan 2015 at 4:42
The open-zwave create a file named zwcfg_<homeid>.xml, e.g.
zwcfg_0xdc3c305a.xml. This contains the information of your Z-Wave network.
To use the new configuration item, it is easiest to remove this file and let
the open-zwave rediscover your devices/network.
Original comment by uAle...@gmail.com
on 18 Jan 2015 at 4:49
Original issue reported on code.google.com by
Piotr.Ku...@gmail.com
on 11 Jan 2015 at 3:57Attachments: