the version update script should look into packages/node_modules/@enocean-js/* and update the package.json of all packages to the same version

the readme need some polish. if you want to help, this is a good starting point. ask me what to do and how to do it here.

https://github.com/RafaelKa/node-serialport-enocean-parser

for my TCM at least it returns RET_WRONG_PARAM (address outside range of values)
for an address that is otherwise perfectly readable. In that case i would expect it to return RET_OPERATION_DENIED when i have no write access... we should have a look at this...

convert strings in EEP descriptions that are Number to numbers...

should we use es6 modules style export?
I do think so. what i don't like is the --experimantal-modules flag.
lets test esm.js

there should be a way to express enum or value meaning based on other datafields.

implement a setBits() function that can set one or more bits in a ByteArray given an offset in bytes and or bits, and a bit-stream length.

The payload of 4BS telegrams my contain data that is spread across 8bit Byte boundaries.

CVAR should be an enum. it has a range.max:"100,255" the only sensor i found so far with multible values in this field, in fact in any field. in other places arrays are used.

the sematics are totally wrong here because the second max value (255) defines a single value not a range. enums howerver support a mixture of single values and ranges. this is even used in the same eep. (FANSP)

The dependency esm was updated from 3.2.0 to 3.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

esm is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

parsing and creation like it's done for common command.

https://www.enocean-alliance.org/wp-content/uploads/2018/04/EnOcean_over_IP_Specification_v0.9.pdf

looks interresting. though chunked transfer encoding seems a bit outdated... would be nice to have a server with http/2 compatibility ...

implement ref scale like it's done in a5-12-0x for those not using it.

https://www.enocean-alliance.org/wp-content/uploads/2018/04/EnOcean_Alliance_Generic_Profiles.pdf

let us know about your usecase. what app do you want to write? what information do you need? where do you need it? or any other ideas what could be useful or fun?

let the caller parse the response

The devDependency mocha was updated from 6.0.2 to 6.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

https://www.npmjs.com/package/mocha-headless-chrome ?

https://enocean-js.slack.com

like the parser and the transformer i'm thinking about implementing the memory/teach in part as a transformable stream that acts as a kind of filter that unifies teach in telegrams and emits the needed information like eep and senderId and then have configurable backends for storing/retrieving the actual data.
that could be: filesystem, leveldb, redis,mysql or even cloud storrages like elastic search etc.
there should be an api for retrieving and storing not only for teach in but also for sensor data.
naming scheme could be something like enocean-js-memory-*

if you want to help, please let me know here. I'll help you getting started.
There is so much to do, any help is greatly appreciated.

https://codeclimate.com/

I have EnOcean devices with UTE teach in - so it would be great to be able to learn them!

Hello team EnOcean-JS,

I purchased EnOcean modules expecting to use them with Node-RED, only to find out the latest version of Node-Red and the latest version of node-red-contrib-enocean aren't compatible, as the Node-Red module isn't using the new enocean-js library.

I've seen some messages from last December saying this should be available "soon" (a week was mentioned in enocean-js/nrce-deprecated#12).

Is there any news on that? Is there a way to donate/contribute to the project to make this happen faster?

Best regards,
S.

use Arrays instead of Uint8Arrays for compatibility and speed. Someday Uint8Arrays might be optimized but for now they are slower that regular Arrays. But most importantly mobile browsers don't support Uint8Array..

we need a publishing script that goes into each package folder and does an npm publish there...

the logo was created by @huwylphi see enocean-js/node-enocean#27

it's graet to have it as an svg. I'm not a big fan of inskapes output though. in fact i'm not a fan of nay editors output. it would be nice to recreate the logo as clean and small as possible as handwritten svg.

the parsing of values is way better
But is it possible to recognize unused values?
rawValue:0 seems to be a propper value - so its correct to scale it to -64 ... but its really not that cold here ;-)

  OUTT:
   { name: 'Outdoor Air Temperature',
     rawValue: 69,
     value: 5,
     range: { min: '0', max: '127' },
     scale: { min: '-64', max: '63' },
     unit: '°C' },
  SPLYT:
   { name: 'Supply Air Temperature',
     rawValue: 77,
     value: 13,
     range: { min: '0', max: '127' },
     scale: { min: '-64', max: '63' },
     unit: '°C' },
  INT:
   { name: 'Indoor Air Temperature',
     rawValue: 0,
     value: -64,
     range: { min: '0', max: '127' },
     scale: { min: '-64', max: '63' },
     unit: '°C' },

there are a few things not implemented yet in in common command in common command. mostly because my USBs do not implement things like secure CO_WR_SECUREDEVICE_ADD or even CO_WR_LEARNMODE so i can not test this functionality. I only have old TCM 300 modules here... i will order a TCM310 and TCM320 for testing...

We should at least having it the functionality implemented, and tested on a theoretical level. If we get Bugs in real applications, we can fix them later.