Hi Claude, thermostats made it to the walls but I am in the process of moving Hass into a container which will likely happen over the weekend at some point. I’ll keep you informed of how it all goes.
Happy Thanksgiving and appreciate the work you’ve done on this.
I think you’ll see a rise of WiFi thermostat users. They’re now on the shelves at Costco for a reasonable price.
I hope someone can provide model number of the 3000 and 4000w wifi thermostats. That’s the only parameter missing to include those thermostats in HA
I also need model number of thelow voltage wifi thermostats.
But I check on Costco website and there is nothing about Sinopé
I’ve seen them at my local costco
You mean TH1123WF AND TH1124WF?
That’s them!
Yes I need model number for TH1123WF, TH1124WF and TH1400WF to add them to the neviweb130 custom_components. I already have it for the TH1300WF wifi floor thermostat. I need that to handle specific attributes of each thermostats
I’m not sure what else you need? Tell me how to identify that for you.
Once you have installed the custom_components neviweb130 in HA and that you have added your wifi thermostats to Neviweb in the same network then your other zigbee devices connected to the GT130, not the network for the GT125. If you don’t have GT130 then create a new network in Neviweb and add it to you configuration.yaml for the neviweb130 custom_component:
neviweb130:
username: «Neviweb user name»
password: «Neviweb password»
network: «your Neviweb network for the wifi thermostats»
scan_interval: 360
Than restart HA and check in your log for the following line:
[custom_components.neviweb130] Received signature data: {'signature': {'model': 737, 'modelCfg': 0, 'softBuildCfg': 0, 'softVersion': {'minor': 9, 'middle': 0, 'major': 1}
model: 737 is for zigbee floor thermostat.
I need your model number for the wifi thermostats you have. Then I 'll tell you where to add that model number in the climate.py file and make a new release to add them permanently to neviweb130
The model for the 3000w is 1510. I have two 4000w on the way that were on backorder so I’ll have them shortly.
I spent a bit of time frigging around with the old sinope-1 install before going this route with the neviweb130.
Thank you.
to support the 3000W change line 57 from
DEVICE_MODEL_WIFI = []
to
DEVICE_MODEL_WIFI = [1510]
save and restart HA. Your thermostat will appear in the devices list. Have fun
I’ve created a branch wifi-support with the changes to climate.py
And there’s the meltdown
‘’’
2020-10-10 15:44:40 DEBUG (MainThread) [custom_components.neviweb130.climate] Setting up neviweb130 climate Main: {‘id’: 129422, ‘identifier’: '2462abfffee7$
2020-10-10 15:44:41 DEBUG (SyncWorker_8) [custom_components.neviweb130.climate] Updating neviweb130 climate Basement (1.013 sec): {‘setpointMode’: ‘auto’, '$
2020-10-10 15:44:41 ERROR (MainThread) [homeassistant.components.climate] neviweb130: Error on device update!
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 346, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 471, in async_device_update
await self.hass.async_add_executor_job(self.update) # type: ignore
File “/usr/local/lib/python3.8/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/neviweb130/climate.py”, line 150, in update
self._wattage = device_data[ATTR_WATTAGE]
KeyError: ‘loadConnected’
2020-10-10 15:44:42 DEBUG (SyncWorker_10) [custom_components.neviweb130.climate] Updating neviweb130 climate Main (1.324 sec): {‘setpointMode’: ‘auto’, 'roo$
2020-10-10 15:44:42 ERROR (MainThread) [homeassistant.components.climate] neviweb130: Error on device update!
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 346, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 471, in async_device_update
await self.hass.async_add_executor_job(self.update) # type: ignore
File “/usr/local/lib/python3.8/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/neviweb130/climate.py”, line 150, in update
self._wattage = device_data[ATTR_WATTAGE]
KeyError: ‘loadConnected’
‘’’
Ok probably that sinopé use the same attribute for wifi thermostat then for wifi floor thermostat.
To be sure you need to open Neviweb in a browser like firefox and open the debug console to get the attribute received from Neviweb for your wifi thermostat.
zigbee thermostat use attribute «loadConnected»
wifi thermostat probably use something like «loadWatt»
I’ve updated my branch wifi-support for neviweb130. You only need to copy climate.py
If you can check for what is sent by Neviweb in the firefox debug console it will help.
Claude, I “think” this is what you’re looking for:
@claudegel Yeah, that’s it. It’s calling for loadwatt. I updated in const.py and it ran through. I can see the entities now.
I’ve updated my branch wifi-support. please test
there is changes in const.py and climate.py
can’t open your link. Please tell me the exact spelling is it loadWatt with a capital W
“loadWatt”
OK c’est ca que j’ai mi dans ma branch wifi-support. J’attends juste des nouvelles d’un autre utilisateur qui a un wifi floor thermostat pour qu’il test de son coté au cas où j’aurais bousiller quelques chose pour les wifi floor. Si tout va bien je fais une mise a jour ce soir.
Il me manque juste le model number pour les wifi 4000w et wifi low voltage. A qui la chance? 
Ready to merge that branch. Just waiting for some testing with wifi floor thermostat. If everuthing is ok I’ll merge tonight.
Still missing model number for TH1124WF and TH1400WF