Address validation error

[keukenrol]

Hi

the BME280 shows me an address validation error. NaN is not defined, despite the number being filled (0x76).

Any idea? Tried deleting the node and putting in a new one, but the issue persists.

[maga-1]

This is probably the same error I have fixed in this pull request: #10

[keukenrol]

Ok thanks, will this new fixed version be released via npm?

[ludiazv]

Yes I try to publish it during this week.

[keukenrol]

Updated today.
Now showing error: Invalid properties: Invalid number
-> when sea pressure is not filled in
Rest works OK!

[SirReal-surreal]

Hi!
I updated to the latest node.js version (from 12 to 18) and got the same issue. As this error don't stop the code, it is still working.
However, the issue is the NaN vs. Nan typo which is fixed on 1.1.0, right? However, npm doesn't update my node to 1.1.0, it stays on 1.0.0.
I did manually edit the HTML to correct the code and it works well, now. But there is an issue with updating the node via npm.

[hasenradball]

@SirReal-surreal
Hi I have the same error....
What do I need to do?
how can I get the v 1.1.0?

[SirReal-surreal]

@SirReal-surreal Hi I have the same error.... What do I need to do? how can I get the v 1.1.0?

The update didn't work - so I edited the HTML source manually. You need to find the HTML source for the node BME280 on your raspberry and you change the "n" to a capital "N" and that's it.

The path is something like this (if default is used):
/home/pi/.node-red/node_modules/node-red-contrib-bme280
and the file is called:
bme280.html
Line 38 (in my case).

[hasenradball]

Ah for the NAN....

understood Thank you!

[hasenradball]

But I would say if the update doesn‘ t work is a big problem.

[ludiazv]

Hi guys,
This issue is quite strange. The fix for the typo in was merged in this PR #10. And the version was published to npmjs check it out: https://www.npmjs.com/package/node-red-contrib-bme280

I just checked the package installing it from npm and the NaN issue is fixed. I doubt it the problem has any relation with the node version or npm as isNaN is std javascript function. So something fishy is going on.

I'm will be busy for the next two week. So I can't do proper test. If someone is able to test why this happening pleas let me know.

[SirReal-surreal]

Hi @ludiazv !
On my YouTube channel I got several guys facing this problem. All fixed it manually by changing the HTML on their own.
So, yes, it seems to be fixed in 1.1.0 but this update is not taken by npm. Not sure why, but somehow the released version is not seen as an update.
As this bug was not seen before on the older node.js versions, I can only assume that we all used 1.0.0 since a while but the older node.js version didn't complain about a missing capital N.

[hasenradball]

@ludiazv
@SirReal-surreal
Please look to this Ticket answer I created:
node-red/node-red#4210 (comment)

Problem should be solved.

This is because the author of the module never requested its entry on the Flow Library to be updated to the latest version.

When logged into the Flow Library there is a 'check for updates' button in the sidebar of every page. I have just clicked that button and the entry has been updated to the latest release.

The Palette Manager catalog will be updated by an automated process in the next hour.

[keukenrol]

Solved over here with updater using palette.

[SirReal-surreal]

Great - I can see the update now:

[hasenradball]

Then I Think we can close this issue now.

[ludiazv]

Thanks @hasenradball for solving the issue.

[hasenradball]

you are welcome
😊