forum

We are proud to announce new release version. Compared to previous v1.7.0 it has stability improvements and few new features.

Next in our schedule is to improve and make new modules, finish TV UI, do thermostat, security and notifications.

ChangeLog

Fixes and improvements:
- Fix memory leak in http.request().
- Fix issues with too many threads created by many http.request().
- Make v8 debugger not to crash on ZXmlNode objects and on CC access.
- Minor fix of UserCode clear.
- Delivery statistics not recorder for encapsulated packets (only for physicaly sent).
- z-cfg-update can now convert from very config starting from v1.2.
- Improve experience with modern secure door locks inclusion.
- Limited callbacks count on DataHolder from JS not to overkill the server from JS and to easily find bugs in JS code.
- DataHolder callback with notifications for child events fixed.

New features:
- Experimental: v8 remote debugging!

Debugger:
The debugger is enabled by setting V8_DEBUG environment variable and uses port 8183 (base port + 100).
Then you can connect either with d8 (./d8 --remote_debugger --debugger_port=8183) or with node-inspector --debug-port 8183.

I would add that now port 8084 is working even on raspberry where apache is working.
Well done

Yes, this was fixed Thanks for the report.

Did the firmware update from 1.7.1-rc2 using the Z-Way configuration Interface. Everything went smooth. My automation settings survived the update. So congratulations for this great update! Things are getting easier for the casual user.

I applied the update to my 1.7.1 rc 2 installation, as well. No problems so far!
Good job, thanks!

My usual problem with updates that the whole old install gets moved somewhere else and the whole new installation takes place. It means my custom modules stop working at once and I have to manually copy them back. It is very inconvenient.

alexey.zimarev wrote:My usual problem with updates that the whole old install gets moved somewhere else and the whole new installation takes place. It means my custom modules stop working at once and I have to manually copy them back. It is very inconvenient.

Place them into userModules folder – installer restores its content after update.

pofs wrote:Place them into userModules folder – installer restores its content after update.

See what PoltoS said here: viewtopic.php?f=3422&t=20455&p=51370#p51360 about problem of placing it in userModules

pz1 wrote:

pofs wrote:Place them into userModules folder – installer restores its content after update.

See what PoltoS said here: viewtopic.php?f=3422&t=20455&p=51370#p51360 about problem of placing it in userModules

I believe @alexey.zimarev wants to place legit modules there, so there's no problem with that.

I am not sure if others are seeing the same issue. Since upgrade to 1.7.1, some additional sensors appear for my Fibaro wall plugs and the only way to get rid of them is re-interview. See device 4 and 7 in the attached screen shot. Edit: Even Aeon 4in1 Multi Sensors (node 2) and Fibaro Motion Sensor (node 30) are reporting one extra sensor?