What channel types are supported by wich netatmo device

Sound good. If we provide you an unstable .jar file for this binding can you install it manually and test it?

Of course! :wink:

@RolandS To speed up this process maybe you could provide us the response of your “Try it module” which can be found here: https://dev.netatmo.com/resources/technical/reference/weatherstation/getstationsdata. Please make sure you post only the anonymized JSON part for the key modules. Thanks.

This is all information I get with this function for the module.

_id: "03:xx:xx:xx:xx:xx"
type: "NAModule4"
last_message: 1502449482
last_seen: 1502449469
▼dashboard_data:
	time_utc: 1502449469
	Temperature: 20.8
	temp_trend: "down"
	Humidity: 61
	CO2: 427
	date_max_temp: 1502431475
	date_min_temp: 1502442190
	min_temp: 19.9
	max_temp: 26.2
▼data_type:
	"Temperature"
	"CO2"
	"Humidity"
module_name: "xxx"
last_setup: 1437413143
battery_vp: 5067
battery_percent: 48
rf_status: 69
firmware: 44

Thanks. Nice. It comfirms that the NAModule4 supports the new channels MinTemp, MaxTemp, etc.

No Problem. I have now 4 Netatmo stations under control with all available modules (main station, outdoor, indoor, rain and wind). If you need further help, just ask. Also for testing a new binding version!

@RolandS new channels are added to NAModule4 and PR is merged. You are able to test it with the upcoming snapshot.

Hi @cweitkamp,

Thank you for improving the Netatmo binding.
Since my upgrade to snapshot #1020, I have the following error message when starting OpenHAB.log:

2017-08-21 21:19:47.965 [WARN ] [pse.smarthome.core.items.GenericItem] - failed notifying listener '[org.eclipse.smarthome.core.persistence.internal.PersistenceManagerImpl@2a31d596, Netatmo_EV_MasterBedroom_Luchtvochtigheid, null]' about state update of item {}: {}
java.lang.NullPointerException: null
	at org.mapdb.DataOutput2.writeUTF(DataOutput2.java:147) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.openhab.persistence.mapdb.internal.MapDBitemSerializer.serialize(MapDBitemSerializer.java:45) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.openhab.persistence.mapdb.internal.MapDBitemSerializer.serialize(MapDBitemSerializer.java:1) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.BTreeMap$NodeSerializer.serialize(BTreeMap.java:397) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.BTreeMap$NodeSerializer.serialize(BTreeMap.java:288) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.Store.serialize(Store.java:154) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.StoreWAL.update(StoreWAL.java:371) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.Caches$HashTable.update(Caches.java:270) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.EngineWrapper.update(EngineWrapper.java:63) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.BTreeMap.put2(BTreeMap.java:707) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.mapdb.BTreeMap.put(BTreeMap.java:643) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.openhab.persistence.mapdb.internal.MapDBPersistenceService.store(MapDBPersistenceService.java:161) [198:org.openhab.persistence.mapdb:1.11.0.201708190109]
	at org.openhab.core.persistence.internal.PersistenceServiceDelegate.store(PersistenceServiceDelegate.java:55) [195:org.openhab.core.compat1x:2.2.0.201708201100]
	at org.eclipse.smarthome.core.persistence.internal.PersistenceManagerImpl.handleStateEvent(PersistenceManagerImpl.java:119) [103:org.eclipse.smarthome.core.persistence:0.9.0.201708151402]
	at org.eclipse.smarthome.core.persistence.internal.PersistenceManagerImpl.stateChanged(PersistenceManagerImpl.java:420) [103:org.eclipse.smarthome.core.persistence:0.9.0.201708151402]
	at org.eclipse.smarthome.core.items.GenericItem$1.run(GenericItem.java:229) [98:org.eclipse.smarthome.core:0.9.0.201708151402]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]

I have this error message for many of my Netatmo-items.
I didn’t had them before.

This is the item definition:

Number Netatmo_EV_MasterBedroom_Luchtvochtigheid		"Bedroom [%d %%]"								<humidity>			(gEV_MasterBedroom, gNetatmo, gAlexa, gClimate)	[ "CurrentHumidity" ]	{channel="netatmo:NAModule4:99274317:03000004d19e:Humidity"}	

Since the upgrade, when I load PaperUI, my values are not loaded anymore:

Any idea what the cause could be? And more importantly: how to solve it?

Hey Dries,

thanks for reporting. Now that you say it: I remembered that I saw something similiar like this in my logs before. So I looked into them and found the same NPE from time to time. My productive environment runs openHAB 2.1.0 - release build - and the warning looks like this:

2017-08-21 12:32:14.893 [WARN ] [pse.smarthome.core.items.GenericItem] - failed notifying listener '[org.eclipse.smarthome.core.persistence.internal.PersistenceManagerImpl@165b978, netatmoOutdoorTempTrend, null]' about state update of item java.lang.NullPointerException: {}

But I guess this is only a partial error of the Netatmo binding. I am going to report an error in the ESH repo and do some investigations in the binding itself.

// EDIT: issue #4104

Thanks a lot! I’ve seen already a lot of things happening/being discussed in the Github issue. :slight_smile:

Fix for binding is submitted:

Wow, that is incredibly efficient! :slight_smile:

I don’t understand the full process of fixed on Github being merged into a snapshot. But I guess it needs to be reviewed/approved first? And then it will be in the next snapshot that is build?

Yes, that’s right. The PR will be reviewed and merged afterwards. After merging it takes only couple of days to be part of the nightly snapshot.

I just updated to "openHAB 2.2.0~20170822201204-1 (Build #1023)"
But in PaperUI I can’t find the new channels for the additional module. I recognized only many more german translations.
Do I have to configure it manually? I didn’t test this up to now, I will do this later…
Changing the location now works, this was impossible before because of the wrong MAC address patterns

About the “failed to notify listener blablabla” I found this error many times since I use the HTTP binding for reading out some values from websites - so I think this is not netatmo-dependent.

If channels were added to a thing type, you have to delete your thing of this type and create it again to see the new channels.

1 Like

@cweitkamp
Seems to work fine! :slightly_smiling_face:

Thanks to @Lolodomo for the hint with deleting and addding again.

Nice, I am glad to hear. Did you miss anything else (e.g. data measured by rain gauge or wind gauge)?

I only translated the Things and Channels for the Indoor-Modul(s) and the Outdoor-Modul to German because I am not able to test the rest. I am thinking about aquire some more modules on my own.

We was able to retrace the NPE “failed to notify listener blablabla” and found it located in the madb persistence. Issue is already posted. I hope someone could help solving it.

I didn’t found any other problems up to now - except the logging of events or openhab itself is not working anymore at all. since I upgraded 2 days ago.

Hey Roland,

to get rid of the logging issue you want to look here:

1 Like

Great! Thx. I didn’t have time to search for the solution up to now.