Hi @alien8er does your GT125 is getting his IP address via DHCP ? or you did set a static IP ?
If it is via DHCP check on your DHCP server, your router or computer depending on your setup. The server should list all devices connected with there IP address and MAC address. I think that the MAC address of the GT125 start with 00:1E:C0 because of the communication chip it use.
Two-network have been merged in release v1.1.5. Thanks for testing
1 Like
Hi Claudegel,
Yes, normally I would find my device in my router settings, but I donât see either bridge when I plug them in. Thatâs whatâs got me so perplexed. I have a Google WiFi router which isnât the best for managing devices, but I havenât had a problem in the last 3 years with a specific device not showing up or connecting when plugged in. I checked all the devices connected and their mac addresses and none of them start with that sequence. I am going to take my GT125 to a friends house at some point to plug into their network to see if it turns on the Web light at least. I canât figure out what else to do.
Ok so today my new GT-125 is working and is showing on my router with an IP address. I was able to get everything set up again. I spoke with tech support and my new best friend there wasnât sure what happened and was going to speak with his tech team to see if they pushed anything out. My old device still isnât coming online, but at least I have the new one going. I can now sleep again knowing that everything is back online.
For sure it will increase your WAF (wife acceptance factor) 
Did Sinopé had to connect to your GT125 to fix something or you did a full reset ?
The WAF was already good for 5 years. With it going out, I started getting back into the bad books haha.
The tech at Sinope said he wasnât sure if level 2 had done anything or not. He was looking into it and was going to get back to me in a week or so. They are pretty shorthanded at the moment, but he mentioned there were a bunch of people hired on. I would really love to know what the resolution was as this was such a weird one!
Let us know if Sinope find the exact problem. Do they perform an update that didnât work ?
Just to keep you in touch: the automation trigger as expected but parameters must be adjusted
Regards
Hello Claude,
About the improvement of the early start of the thermostat.
Of corse, it will be better if Synope can improve the firmware of the thermostat with a better early start algorithme.
If not (Synope doesnât respond to my mail addressed to the support).
The improvement can be implanted in the Home Assistant Neviweb driver. In this driver the setting point, the actual and the history are all disponible. The outside temperature is disponible too. The driver can âlearnâ the behaviour of the room and calculate the starting point. Of corse too, normally it is not the responsibility of a driver to correct the behaviour of a device !
With my knowledge, I write an automation with the values I get.
This automation donât get the setting point so if I decide to change the setting point I have to modify my automation: not very good.
But for now, the behaviour is correct, my wife can dring a cafe with 21 degré in the room.
Just a latest question:
Sometimes the temperature getting from the thermostats is âunknowâ.
In the automation in the test comparing the actual temperature, if the temperature is unknow it is considered below the reference:
{% set t = states('sensor.time') %}
{% set temp = states('sensor.kitchen_temp')|float %}
{{ (t == '07:00' and temp < 19.5) or
What is the float value of âunknowâ ?
is that correct to write:
{% set t = states('sensor.time') %}
{% set temp = states('sensor.kitchen_temp')|float %}
{{ (t == '07:00' and temp < 19.5 and temp != 0) or
Thanks a lot for all your help !
Regards
Do you have the log when you get «unknown» for room temperature ?
I donât think there is a way for the driver to learn the behavior of the room. The driver donât keep data itâ HA that keep them. But I think you can setup sensor for each parameters and an automation that compute the result for heating performance in each room.
Iâll put a patch in my git for the unknown temp in branch «wrong-temp». This will tell the driver to keep the old temps if it receive an unknown temp from the device or the device just donât answer. Are you using the latest version of my Sinope-gt125 ?
Hello,
Itâs a good idea to keep the latest value.
Where can I find the version of the neviweb component ?
I open the climate.py and find 268 lines, the same as github.
This nignt, my automation running well, but I have logs on the server:
Logger: custom_components.neviweb.climate
Source: custom_components/neviweb/climate.py:134
Integration: Sinope Neviweb (documentation)
First occurred: 08:24:24 (1 occurrences)
Last logged: 08:24:24
Cannot update neviweb climate Cuisine: {'error': {'code': 'DVCCOMMTO', 'data': {'retry': 2}}}. Device is busy or does not respond quickly enough.
and another type of error:
Logger: custom_components.neviweb.light
Source: custom_components/neviweb/light.py:108
Integration: Sinope Neviweb (documentation)
First occurred: 22 novembre 2020 Ă 22:14:16 (23 occurrences)
Last logged: 08:59:17
Cannot update neviweb dimmer chambre: {'error': {'code': 'DVCCOMMTO', 'data': {'retry': 2}}}. Device is busy or does not respond quickly enough.
Cannot update neviweb dimmer Salon: {'error': {'code': 'DVCCOMMTO', 'data': {'retry': 2}}}. Device is busy or does not respond quickly enough.
Cannot update neviweb dimmer Salle de bain m: {'error': {'code': 'DVCCOMMTO', 'data': {'retry': 2}}}. Device is busy or does not respond quickly enough.
Best regards
Thierry
Ho your using the neviweb custom_component not the sinope-gt125. So Iâll make the patch for this one too. The error you get are from Neviweb. This is because Neviweb do not get response from your devices fast enough. Maybe the device is busy sending other data.
In that case you get an unknown value that disturb your automations.
By keeping the previous value if Neviweb do not send data during an update it will prevent that unknown value.
Go to my git claudegel / sinope-1 switch to branch «wrong-temp» and copy climate.py over the one you have in your setup.
Let me know if it solve those unknown temp
@claudegel. I have noticed that when Iâm not placing any call for a while let say overnight, my first call will take a while to execute. For instance, turning a light one could take 15 second. Once the first call as been placed, everything works rather quickly. As if one pieces of the puzzle goes to sleep and needs to wake up which causes the delay. Do you have any idea of why Iâm experiencing such delay ?
Hello,
I reinstall the component from hac. Version 1.25 ?
Is this component neviweb or sinope-gt125?
What is the difference between the two components?
Is that possible to know what is the next setting point and when?
Best regards
Hi @BenCour, normally HA is polling the devices every 3 minutes depending on your scan_interval setting for Sinope so the GT125 and HA never sleep. If you add some debug in HA for custom_components sinope you can see in the log how long it take for each update.
logger:
default: warning
logs:
custom_components.sinope: debug
look for [homeassistant.components.climate] Updating sinope climate âŠ
itâs the same for light and dimmer.
Light and dimmer are pretty fast to update but thermostat are slower. In my case I have 10 thermostats on my GT125 and it is frequently over 3 minutes to update all of them.
On the other hand I donât know if the devices themselves goes to sleep. In that case it could be the cause. Could you check if it is always the same devices that wake up slowly .
There is three custom_components:
- neviweb to manage your devices via neviweb
- sinope-gt125 to manage your devices directly via the GT125, no need of Neviweb
- neviweb130 to manage you zigbee devices and wifi devices via Neviweb
@claudegel , I can confirm that itâs not always the same device. Iâm mainly experiencing this issue when trying to turn a light or a dimer on. Iâm going from Apple Home -> Home Kit -> HA -> GT125. Iâm still new to all of this, and Iâm not sure I was able to reproduce the issue when using it direclty from HA.
Ok, appened again, in the log I see:
2020-11-25 19:37:47 ERROR (SyncWorker_53) [custom_components.neviweb130] Session expired. Set a scan_interval lessthan 10 minutes, otherwise the session will end.
2020-11-25 19:37:47 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.neviweb130_climate_th1123zb fails
And my scan_interval is 360.
Hi @Leicas it is possible that Sinopé reduced the delay before closing the connection.
On my side I have scan_interval 360 and no Session expired . I have two session openned. neviweb for the devices connected to GT125 and neviweb130 for the GT130 both have a scan_interval of 360
@BenCour the timeout could be caused by Apple Home that is sleeping. Do you control other devices than the Sinopé with that Apple Home. If yes you can check if you get the same timeout in the morning. There are some discussion on the web about apple home kit loosing time to find the best wifi band if you have a dual band wifi. It could take up to 20 seconds to find the fastest band before talking to the devices. Disabling one band could be a good test to see if it improve next morning.
1 Like