putting your command nothing happens;
Really strange. Have you something working on MQTT ?
Have setup the MQTT integration AND the MQTT Broken Add-on. ?
Do you have some existing topic using MQTT Explorer : http://mqtt-explorer.com
v0.0.4 available !
- Added debug mode with option debug: true/false
1 Like
could it be due to this?
Logger: homeassistant.config_entries
Source: components/somfy/init.py:113
First occurred: 21:28:39 (1 occurrences)
Last logged: 21:28:39
Error setting up entry Home Assistant Cloud for somfy
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 248, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File “/usr/src/homeassistant/homeassistant/components/somfy/init.py”, line 113, in async_setup_entry
if all(not bool(device.states) for device in coordinator.data.values()):
AttributeError: ‘NoneType’ object has no attribute ‘values’
Thanks !
No this is the Somfy Integration not the SomfyProtect2MQTT
Can you update you supervisor add-on to 0.0.4, set debug to true and tell us the log you have in supervisor, in particular MQTT info.
It seems your are not connected to it
@schumijo I have release on master SomfyProtect2MQTT as 0.1.0b. (b for beta)
I will now create a new release on master for each validated change.
It will prevent some issue with new versions on dev and permit a rollback on an older release.
So I think we can create 2 add-ons, one for master and one for dev. I don’t know if @schumijo have time to do this, I can fork your repo and propose update if you prefer.
Maybe a possible improvement could be execute the update_sites_status() function once, just after the command_topic receiving. So the alarm status will get updated in real-time, instead of waiting for delay seconds.
Can be a good idea !
Need to know if the status is updated just after the command or after the delay of 30s (or the one you have setup in the APP).
Addon version 0.1.0 released !
As requested by @Minims, two addons are now available : one base on master branch and one based on dev branch.
Addon name as changed so please remove the old one and install new one (don’t forget to copy paste your configuration 
).
- Addon renamed “SomfyProtect2MQTT”
- Lot of code rewritten (thanks to @Minims)
- Migrate to Minims/SomfyProtect2MQTT master branch
- Based on release v0.1.0b
- Added logo, icon, changelog, docs…
1 Like
It seems you still have mqtt_user as MQTT username. Do you use username/password on your MQTT Broker ?
1 Like
my user is “mqtt_user”, is there something wrong with the debug?
It’s ok if it’s your user. I thought you have forget to fill it in the conf.
Debug log is OK. But there is nothing about MQTT Message. so it seems your are not connected to it and I don’t know why 
this log is missing :
LOGGER.debug(f"Connected: {rc}")
you have only
LOGGER.debug("MQTT client initialized")
What do you have in configuration for port and host for MQTT ? (copy/paste those 2 info in case of typo)
Dev branch updated, I have tried on device update only site status is coded.
Need a delay of 3sec to see the update in the API.
Try it 
2nd update on dev, improve camera snapshot update
I’m trying to install dev addon but I’m getting this error:
Step 8/20 : RUN tar -xvf src.tar.gz
---> Running in 7dda960191b3
tar: invalid tar magic
Oups ! I made a mistake in github link to dev branch.
v0.1.1 available.
2 Likes
It’s working now! Thanks!